[Axis2] Axis2 1.1 and JDK 1.6

We have client proxy code that we generated using axis2 v1.1. This code works fine with jdk 1.5, however we have a need to upgrade to JDK 1.6. During this process, we hit the following exception, javax.xml.stream.FactoryConfigurationError: Provider javax.xml.stream.XMLInputFactory could not be

[jira] [Updated] (AXIS2-5020) ClassCastExceptions between two axis2 client jars with different package

[ https://issues.apache.org/jira/browse/AXIS2-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez updated AXIS2-5020: Priority: Major (was: Blocker) This seems to be a configuration issue on the client. Anyway, if at

[jira] [Resolved] (AXIS2-4244) NullPointerException in generated Stub.

[ https://issues.apache.org/jira/browse/AXIS2-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4244. - Resolution: Fixed Fixed in the forthcoming Axis2 1.6.0 release > NullPointerException in generat

RESTful webservice and session management

Hi, I created a webservice and enabled session management on both server and client. It works FINE until I enable REST on the client by adding the 3rd line of code in the serviceStub.java on the client side. Session management stopped working. // added session management _serviceClient.getOption

[jira] [Created] (AXIS2-5046) Typo in exception message ('charactors' instead of 'characters')

Typo in exception message ('charactors' instead of 'characters') Key: AXIS2-5046 URL: https://issues.apache.org/jira/browse/AXIS2-5046 Project: Axis2 Issue Type: Bug

[jira] [Updated] (AXIS2-5023) Ambigious use of isElementData in the Block interface

[ 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,

[jira] [Commented] (AXIS2-3916) ADB does not handles the daylight saving times

[ https://issues.apache.org/jira/browse/AXIS2-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034673#comment-13034673 ] Christoph Müller commented on AXIS2-3916: - We still see this issue with 1.5.4. In

[jira] [Updated] (AXIS2-5039) Override the SOAPAction from the SOAPMessage MIME header if it is explicitly configured later

[ 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. > Override

[jira] [Updated] (AXIS2-5039) Override the SOAPAction from the SOAPMessage MIME header if it is explicitly configured later

[ 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 is explici