Ivan Varga created AXIS2-5376:
-
Summary: Improving faultstring messages for type restrictions
(ADBException)
Key: AXIS2-5376
URL: https://issues.apache.org/jira/browse/AXIS2-5376
Project: Axis2
[
https://issues.apache.org/jira/browse/AXIS2-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5323:
Attachment: AXIS2-5323.patch
Attach a new patch including error messages.
> Follow the lat
[
https://issues.apache.org/jira/browse/AXIS2-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5323:
Attachment: (was: LegacyExceptionUtil.java.patch)
> Follow the latest exclude rule for properties in
Ivan created AXIS2-5323:
---
Summary: Follow the latest exclude rule for properties in the
exception class
Key: AXIS2-5323
URL: https://issues.apache.org/jira/browse/AXIS2-5323
Project: Axis2
Issue Type
[
https://issues.apache.org/jira/browse/AXIS2-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5323:
Attachment: LegacyExceptionUtil.java.patch
Attach a proposed patch file for this JIRA, using Introspector to find
-aar-maven-plugin-1.6.1.jar.asc
> axis2-aar-maven-plugin-1.6.1-sources.jar
> axis2-aar-maven-plugin-1.6.1.jar
> axis2-aar-maven-plugin-1.6.1.pom
> axis2-aar-maven-plugin-1.6.1-sources.jar.asc
> axis2-aar-maven-plugin-1.6.1-javadoc.jar
> axis2-java2wsdl-maven-plugin-1.6.1.pom.asc
> axis2-java2wsdl-maven-plugin-1.6.1.pom
> axis2-java2wsdl-maven-plugin-1.6.1-sources.jar
> axis2-java2wsdl-maven-plugin-1.6.1-sources.jar.asc
> axis2-java2wsdl-maven-plugin-1.6.1-javadoc.jar.asc
> axis2-java2wsdl-maven-plugin-1.6.1.jar.asc
> axis2-java2wsdl-maven-plugin-1.6.1.jar
> axis2-java2wsdl-maven-plugin-1.6.1-javadoc.jar
> axis2-codegen-1.6.1-javadoc.jar
> axis2-codegen-1.6.1.pom.asc
> axis2-codegen-1.6.1.pom
> axis2-codegen-1.6.1-sources.jar.asc
> axis2-codegen-1.6.1.jar.asc
> axis2-codegen-1.6.1.jar
> axis2-codegen-1.6.1-javadoc.jar.asc
> axis2-codegen-1.6.1-sources.jar
>
> -
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Ivan
Hi, Andreas, thanks for following this, and do you plan to review those
JIRAs recently ? Geronimo community hopes to release 3.0 recently, if you
are busy with other stuffs, is it possible to have Axis2 1.6.1 release ?
Thanks.
2011/8/11 Ivan
> Thanks, Andreas.
>
>
> 2011/8/11 And
[
https://issues.apache.org/jira/browse/AXIS2-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085002#comment-13085002
]
Ivan commented on AXIS2-5115:
-
Hi, Andreas, the changes fix the issue, please help to por
[
https://issues.apache.org/jira/browse/AXIS2-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084919#comment-13084919
]
Ivan commented on AXIS2-5062:
-
Hi, Andreas, just tried the changes, the results seems t
[
https://issues.apache.org/jira/browse/AXIS2-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084834#comment-13084834
]
Ivan edited comment on AXIS2-5062 at 8/14/11 1:42 PM:
--
Hi, And
[
https://issues.apache.org/jira/browse/AXIS2-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084834#comment-13084834
]
Ivan commented on AXIS2-5062:
-
Hi, Andreas, I have not tried the changes, but from the s
[
https://issues.apache.org/jira/browse/AXIS2-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084617#comment-13084617
]
Ivan commented on AXIS2-5115:
-
Thanks for looking at this, one possible solution is to r
Thanks, Andreas.
2011/8/11 Andreas Veithen
> Done.
>
> Andreas
>
> On Tue, Jul 26, 2011 at 05:16, Ivan wrote:
> > Hi, Geronimo is trying to switch to use 1.6.1-SNAPSHOT, while it looks
> that
> > some codes are also required to merge from trunk, Could you help to
: Axis2
Issue Type: Bug
Components: jaxws
Affects Versions: 1.6.0, 1.7.0
Reporter: Ivan
While constructing the EndpointInterfaceDescriptionImpl instance from WSDL on
the line 1222 of EndpointDescriptionImpl, if the log level is configured with
debug, some
Hi, we got a good testing result for the 1.6.1-SNAPSHOT + listed revision
changes. So, is there a plan for 1.6.1 release ?
Thanks.
2011/7/26 Ivan
> Hi, Geronimo is trying to switch to use 1.6.1-SNAPSHOT, while it looks that
> some codes are also required to merge from trunk, Could you h
IS2-5021: Committed patch provided by Ivan (xuhaihong).
Revision: 1136177
AXIS2-5067: Committed patch provided by Ivan (xuhaihong), with minor
changes. This implements the saveChanges method and calculates the correct
content type for a SOAPMessage.
2011/7/13 Ivan
> Hi, devs, I just uploaded a
Hi, devs, I just uploaded a patch for
AXIS2-5023<https://issues.apache.org/jira/browse/AXIS2-5023>.
If possible, please help to review it first, as I am not quite confident for
the changes for this jira, although it seems to work now.
Thanks.
2011/7/12 Ivan
> OK, I forget to reply to A
[
https://issues.apache.org/jira/browse/AXIS2-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5023:
Attachment: AXIS2-5023.patch
In the patch, a new method isXMLData is added to indicate whether the contents
of
OK, I forget to reply to Axis2 mail list again ...
2011/7/12 Ivan
>
>
> 2011/7/12 Andreas Veithen
>
>> The changes for Neethi 3.0.x (including the three changes mentioned in
>> your mail) should now be included in the latest 1.6.1-SNAPSHOT build.
>> The rel
Hi, Axis2 devs, any thought to port those listed changes to 1.6 branch ?
Thanks.
2011/7/8 Ivan
> Just add the geronimo mail address.
>
>
> 2011/7/8 Ivan
>
>> Hi, the initial reason for moving to 1.7.0-SNAPSHOT is for the Policy
>> support, the changes are list below.
Just add the geronimo mail address.
2011/7/8 Ivan
> Hi, the initial reason for moving to 1.7.0-SNAPSHOT is for the Policy
> support, the changes are list below. If they could be ported to 1.6 branch,
> we are fine to try to turn to 1.6 branch.
> Also, understand that you guys are bu
(AXIS2-5001) SOAPMessage.getSOAPHeaders() return null while no headers in
the soap envelope
(AXIS2-4996) Exclude content-length header while chunked is enabled
2011/7/8 Andreas Veithen
> Ivan,
>
> There are no plans for a 1.7.0 release, but we can do a 1.6.1
> maintenance release. For that you ne
Hi, Axis2 devs,
Geronimo bundles the some Axis2 components of 1.7.0-SNAPSHOT, and it is
obviously that we could not release these bundles with snapshot. I am
wondering that whether Axis2 could have chance to have a 1.7.0 release, or
maybe a milestone release ?
thanks.
--
Ivan
[
https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050165#comment-13050165
]
Ivan commented on AXIS2-5067:
-
Thanks, Andreas.
> content-type header is not generat
[
https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5067:
Attachment: AXIS2-5067-01.patch
I add one more case for the patch. And now all of them should pass with RI. One
[
https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047813#comment-13047813
]
Ivan commented on AXIS2-5067:
-
Thanks, Andreas, I will check it,
> content-type he
[
https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047031#comment-13047031
]
Ivan commented on AXIS2-5067:
-
A bit explanation for the patch
a. From the JavaDo
[
https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5067:
Attachment: AXIS2-5067.patch
Attach a patch for it, please help to review, thanks.
> content-type header is
Affects Versions: 1.7.0
Reporter: Ivan
In the scenario below :
SOAPMessage msg = MessageFactory.newInstance().createMessage();
SOAPPart sp = msg.getSOAPPart();
SOAPEnvelope envelope = sp.getEnvelope();
SOAPBody bdy = envelope.getBody();
SOAPBodyElement
Glad to hear that, Sagara. Definitely appreciated with your helps, if any
further questions on those JIRAs, please help to comment on them, and I will
reply as soon as possible.
2011/6/7 Sagara Gunathunga
> Hi Ivan,
>
> Thanks a lot for your contribution so far ! Geronimo projec
Hi, devs:
This is Ivan from Geronimo project, in the past few months, I was
working on the Axis2 1.7.0-SNAPSHOT integration with Geronimo 3.0-SNAPSHOT,
and also investigating JAX-WS 2.2 CTS failures of Axis2 running in the
Geronimo environment. You might see that I asked some questions and
[
https://issues.apache.org/jira/browse/AXIS2-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5062:
Attachment: AXIS2-5062-Port.patch
AXIS2-5062-Dispatch.patch
Attach two patch files.
> Connect
, transports
Affects Versions: 1.7.0
Reporter: Ivan
1. Using Dispatch API
A bit more description for my case, the server side is a simple web service,
for the client side, the codes are something like :
--->
Service service = new HelloService();
Dispatch dispatchJ
[
https://issues.apache.org/jira/browse/AXIS2-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan resolved AXIS2-4999.
-
Resolution: Invalid
Finally, I found that my failed cases passed while using customized class
finder, so close
[
https://issues.apache.org/jira/browse/AXIS2-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4999:
Attachment: AXIS2-4999-01.patch
Update the patch a bit, seems that only the wrapper class detection for
request
[
https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035954#comment-13035954
]
Ivan commented on AXIS2-5039:
-
Just update a new patch and a case to reproduce this i
[
https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5039:
Attachment: (was: AXIS2-5039.patch)
> Override the SOAPAction from the SOAPMessage MIME header if it
[
https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5039:
Attachment: AXIS2-5039-Test.patch
AXIS2-5039.patch
Update a new patch and a case for it
[
https://issues.apache.org/jira/browse/AXIS2-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5023:
Attachment: AXIS2-5023-Test.patch
The patch takes advantage of an existing test suite in jaxws-integration
module
[
https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5039:
Attachment: AXIS2-5039.patch
Update the patch, and will provide a test case to demonstrate the issue.
> Overr
[
https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5039:
Attachment: (was: AXIS2-5039.patch)
> Override the SOAPAction from the SOAPMessage MIME header if it
[
https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5022:
Attachment: AXIS2-5022-01.patch
Fix a typo error in the last patch, I am still thinking how to implement it
more
[
https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5022:
Attachment: (was: AXIS2-5022.patch)
> Support addressing meta data with policy 1.5 framew
[
https://issues.apache.org/jira/browse/AXIS2-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5040:
Attachment: AXIS2-5040.patch
> Ignore the methods while no webmethod annotation and no webservice annotation
&
/AXIS2-5040
Project: Axis2
Issue Type: Bug
Components: jaxws
Affects Versions: 1.7.0
Reporter: Ivan
Per JAX-WS spec 3.3,
the class implicitly defines a service endpoint interface (SEI) which comprises
all of the public
non-static or non-final
[
https://issues.apache.org/jira/browse/AXIS2-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5039:
Attachment: AXIS2-5039.patch
> Override the SOAPAction from the SOAPMessage MIME header if it is explici
Project: Axis2
Issue Type: Bug
Components: jaxws
Affects Versions: 1.7.0
Reporter: Ivan
While using RI SAAJ impl with Axis2, it seems that RI SAAJ will always adds a
SOAPAction header with the value "" if it is a SOAP 1.1 message. I found th
[
https://issues.apache.org/jira/browse/AXIS2-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5034:
Attachment: AXIS2-5034.patch
In the attached patch, it uses the value of name attribute of the message
element
Project: Axis2
Issue Type: Bug
Components: kernel
Affects Versions: 1.7.0
Reporter: Ivan
Per the JAX-WS spec 2.5
Conformance (Exception naming): In the absence of customizations, the name of a
mapped exception
MUST be the value of the name attribute of the
[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5001:
Attachment: AXIS2-5001.patch
The patch uses a system property to control the behavior. by default, it keeps
on
[
https://issues.apache.org/jira/browse/AXIS2-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030589#comment-13030589
]
Ivan commented on AXIS2-5023:
-
I am thinking to add a new method isElementDataOnly()
Affects Versions: 1.7.0
Reporter: Ivan
In the Block interface, a method named isElementData is defined with doc
description below, from my understanding, it only return true while the block
could be represented as a single element.
/**
* @return true if data is always an
[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030587#comment-13030587
]
Ivan edited comment on AXIS2-5001 at 5/9/11 2:48 AM:
-
I also che
[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030587#comment-13030587
]
Ivan commented on AXIS2-5001:
-
I also checked all SAAJ, JAX-WS and even SOAP spec in the
[
https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030570#comment-13030570
]
Ivan commented on AXIS2-5022:
-
Before creating the patch, I checked those sub module
[
https://issues.apache.org/jira/browse/AXIS2-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030562#comment-13030562
]
Ivan commented on AXIS2-5021:
-
Hehe, should clearly refer the spec, :-)
--->
Spe
[
https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5022:
Attachment: AXIS2-5022.patch
Attach a draft patch, and it works in my local environment. Some of TCK cases
: Addressing
Affects Versions: 1.7.0
Reporter: Ivan
Fix For: 1.7.0
Since the trunk has been upgraded to use neethi 3.0.0, those addressing
metadata should be supported. Actually, in the JAX-WS TCK cases, many cases use
it for declaring addressing requirement.
--
This message
[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030487#comment-13030487
]
Ivan commented on AXIS2-5001:
-
Hi, Andreas, thanks for following this issue. Fro
[
https://issues.apache.org/jira/browse/AXIS2-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-5021:
Attachment: AXIS2-5021.patch
Attach a patch to remove the extra slash in the wsdl address.
> Extra slash is ad
: 1.7.0
Reporter: Ivan
Per the JAX-WS, the wsdl address for should be web service endpoint access with
?wsdl suffix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019155#comment-13019155
]
Ivan commented on AXIS2-5001:
-
Yes, I already mentioned it in the email posted in the
[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018754#comment-13018754
]
Ivan commented on AXIS2-5001:
-
The link for the message in the mail list.
http://ap
Issue Type: Bug
Components: saaj
Affects Versions: 1.6.0
Reporter: Ivan
Per Java doc, SOAPMessage.getSOAPHeaders() should throw SOAPException while no
header exists in the soap message, while it returns null in current axis2-saaj
implementation.
--
This message is
[
https://issues.apache.org/jira/browse/AXIS2-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4999:
Attachment: AXIS2-4999.patch
Attach a proposed patch, please help to review, thanks.
> Not dectecting wrap
Versions: 1.6.0
Reporter: Ivan
I found that the class
org.apache.axis2.jaxws.runtime.description.marshal.impl.ArtifactProcessor is
used to find the wrapper class for request, response and fault. But is it
required to check the parameter first, and if it is of bare style, the
[
https://issues.apache.org/jira/browse/AXIS2-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014950#comment-13014950
]
Ivan commented on AXIS2-4996:
-
After using soap monitor, it is caused by Axis2 or com
[
https://issues.apache.org/jira/browse/AXIS2-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4996:
Issue Type: Bug (was: Improvement)
> Exclude content-length header while chunked is enab
: transports
Affects Versions: 1.6.0
Reporter: Ivan
Attachments: Axis2-4996.patch
I am running Axis2 on Tomcat 7, and get some exception message saying :
--->
java.util.concurrent.ExecutionException: javax.xml.ws.soap.SOAPFaultExcept
[
https://issues.apache.org/jira/browse/AXIS2-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4996:
Attachment: Axis2-4996.patch
Attach a patch file, please help to review it. Thanks.
> Exclude content-len
[
https://issues.apache.org/jira/browse/AXIS2-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4993:
Attachment: AXIS-4993-01.patch
> Throw JAXBException if the built JAXBContext from classes are not va
[
https://issues.apache.org/jira/browse/AXIS2-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014383#comment-13014383
]
Ivan commented on AXIS2-4993:
-
I tried to read more Axis2 codes, and find that it migh
[
https://issues.apache.org/jira/browse/AXIS2-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan resolved AXIS2-4992.
-
Resolution: Invalid
Thanks, Jarek, I found that my case is caused by other reasons, the codes here
should be
[
https://issues.apache.org/jira/browse/AXIS2-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4992:
Attachment: AXIS2-4992-02.patch
Sorry, did not check the codes carefully, the service is of bare style, so
should
[
https://issues.apache.org/jira/browse/AXIS2-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4993:
Attachment: AXIS2-4993.patch
Attach a patch, please help to review, thanks.
> Throw JAXBException if the bu
: Bug
Components: jaxws
Affects Versions: 1.6.0
Reporter: Ivan
In the class JAXWSProxyHandler, there is some logic for choosing classloader of
SEI and context classloader. Currently, it would try to build the JAXBContext
with both classloaders, and compare them with a
[
https://issues.apache.org/jira/browse/AXIS2-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan closed AXIS2-4990.
---
Resolution: Fixed
Fix Version/s: 1.7.0
1.6.0
Thanks, Jarek, I will open another JIRA for
Affects Versions: 1.6.0
Reporter: Ivan
Attachments: AXIS2-4992.patch
While detecting the request wrapper class, a typo error for the default request
wrapper class name in ArtifactProcessor class.
--
This message is automatically generated by JIRA.
For more information on
[
https://issues.apache.org/jira/browse/AXIS2-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4992:
Attachment: AXIS2-4992.patch
> Incorrect default requrest wrapper class name is u
[
https://issues.apache.org/jira/browse/AXIS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan closed AXIS-2845.
--
Resolution: Invalid
Sorry, I mean to open for Axis2
> Incorrect default requrest wrapper class name is u
Incorrect default requrest wrapper class name is used
-
Key: AXIS-2845
URL: https://issues.apache.org/jira/browse/AXIS-2845
Project: Axis
Issue Type: Bug
Reporter: Ivan
While
[
https://issues.apache.org/jira/browse/AXIS2-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4990:
Attachment: AXIS-4990-ThrowException.patch
Throw exception if the built JAXBContext did not contains the expected
[
https://issues.apache.org/jira/browse/AXIS2-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4990:
Attachment: AXIS-4990-TypoError.patch
Just one line change.
> Typo error for variable name in JAXWSProxyHand
Versions: 1.6.0
Reporter: Ivan
On the line 691 of class org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler,
there is a typo error, the variable name should be classCL, not contextCL.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http
[
https://issues.apache.org/jira/browse/AXIS2-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan closed AXIS2-4984.
---
> Use a property to force to use the post web method ru
[
https://issues.apache.org/jira/browse/AXIS2-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011524#comment-13011524
]
Ivan commented on AXIS2-4984:
-
Thanks so much, Jarek.
> Use a property to force to
[
https://issues.apache.org/jira/browse/AXIS2-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4984:
Attachment: AXIS2-4984.patch
> Use a property to force to use the post web method ru
I opened a JIRA https://issues.apache.org/jira/browse/AXIS2-4984, and attach
a patch. Please help to review it, thanks.
2011/3/21 Ivan
> Could anyone give any hits for it ? Or there is another way could solve it.
> thanks.
>
>
> 2011/3/18 Ivan
>
>> Hi,
>>In
: jaxws
Affects Versions: 1.6
Reporter: Ivan
In the latest Axis2 1.6 branch, a new PostRI216MethodRetrieverImpl is provided
to keep compatibility with the new specification. Currently, it checks the
wsgen version to determine whether to use it or the legacy one. It is a good
solution
Could anyone give any hits for it ? Or there is another way could solve it.
thanks.
2011/3/18 Ivan
> Hi,
>In the latest Axis2 1.6 branch, I found a new
> PostRI216MethodRetrieverImpl is provided to keep compatibility with the new
> specification. Currently, it checks the wsge
adding a system property to force the use of new
method retriever ?
Thanks.
--
Ivan
Reporter: Ivan Dubrov
Observable behaviour:
Sometimes WSDL request returns wrong WSDL. This occurs when multiple WSDL
requests are made at the same time.
The cause:
org.apache.axis2.dataretrieval.WSDLDataLocator is created only once and reused
in a multiple requests (see DataLocatorFactory
[
https://issues.apache.org/jira/browse/AXIS2-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated AXIS2-4751:
Attachment: Axis2-475.patch
Attach a patch, try to clear the cookie values if session_maintain_property is
false
: Axis2
Issue Type: Bug
Components: jaxws
Affects Versions: 1.5.1
Reporter: Ivan
Cookie value is always kept whatever SESSION_MAINTAIN_PROPERTY value is
configured
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to
94 matches
Mail list logo
