[jira] [Resolved] (AXIS2-5136) Simple Axis2 Server failed on deploying aar file

2011-09-28 Thread Sagara Gunathunga (Resolved) (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagara Gunathunga resolved AXIS2-5136. --- Resolution: Fixed Fix Version/s: 1.7.0 Applied patch in r1176811. Thanks Ping

[jira] [Assigned] (AXIS2-4170) WSDL2JAVA for WSDL2.0 has CodeGenerationException/NullPointerException

2011-09-28 Thread Sagara Gunathunga (Assigned) (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagara Gunathunga reassigned AXIS2-4170: - Assignee: Ping Liu (was: Sagara Gunathunga ) > WSDL2JAVA for WSDL2.0 has Co

[jira] [Updated] (AXIS2-5136) Simple Axis2 Server failed on deploying aar file

2011-09-28 Thread Sagara Gunathunga (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagara Gunathunga updated AXIS2-5136: -- Component/s: kernel > Simple Axis2 Server failed on deploying aar file > --

[jira] [Resolved] (AXIS2-5123) Please help me out to sort out this issue its really urgent!!!!

2011-09-28 Thread Sagara Gunathunga (Resolved) (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagara Gunathunga resolved AXIS2-5123. --- Resolution: Invalid Use Axis2 user list to ask these question, JIRA is not to answer

[jira] [Commented] (AXIS2-5136) Simple Axis2 Server failed on deploying aar file

2011-09-28 Thread Hudson (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116355#comment-13116355 ] Hudson commented on AXIS2-5136: --- Integrated in Axis2 #1003 (See [https://builds.apache.org/j

WS-Addressing metadata/WSDL compliance

2011-09-28 Thread Tammo van Lessen
Hi guys, I'd like to discuss the usage and compliance of Axis2 with WS-Addressing, since I think there is some potential for improvements. I started already with Deepal but we decided to move the discussion to this list since I think its of broader interest. It is basically about two things, stan

Re: Jar file dependencies, specifically for geronimo-stax-api_1.0_spec-1.0.1.jar

2011-09-28 Thread Andreas Veithen
Removing geronimo-stax-api_1.0_spec-1.0.1.jar is safe, but you should double check that after removing that JAR, Axis2 is still using the Woodstox StAX implementation and not the one provided by the server runtime (WebSphere's XLXP parser is supported, but less well tested than Woodstox, and WebLog

Re: svn commit: r1176281 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/description/java2wsdl/TypeTable.java

2011-09-28 Thread Andreas Veithen
That doesn't look like good OO design. XMLGregorianCalendar is an abstract API and the actual runtime type is completely implementation dependent. Trying to enumerate every possible existing implementation is obviously not a correct approach. I would not be surprised if e.g. on IBM WebSphere, that

Re: WS-Addressing metadata/WSDL compliance

2011-09-28 Thread Deepal jayasinghe
On 9/28/2011 12:25 PM, Tammo van Lessen wrote: > My second point is about the interplay between the Anonymous element and > the dual channel implementation provided by Axis. If I understand it > correctly, Axis supports the dual channel invocation out of the box and > I consider this a great featur

[jira] [Updated] (RAMPART-336) EncryptedParts header encrpyion with namespace and EncryptedElements with xpath policy, missing some elements in MessageReceiver on server side.

2011-09-28 Thread Amila Jayasekara (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/RAMPART-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Jayasekara updated RAMPART-336: - Attachment: RAMPART-336.diff Hi Vijay, I am attaching a patch for this issue. Please te

[jira] [Commented] (RAMPART-336) EncryptedParts header encrpyion with namespace and EncryptedElements with xpath policy, missing some elements in MessageReceiver on server side.

2011-09-28 Thread Amila Jayasekara (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/RAMPART-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116939#comment-13116939 ] Amila Jayasekara commented on RAMPART-336: -- The patch is created on revision 117

[jira] [Assigned] (RAMPART-334) Unable to set TTL and maxTimeStampSkew values through a rampart callback

2011-09-28 Thread Thilina Buddhika (Assigned) (JIRA)
[ https://issues.apache.org/jira/browse/RAMPART-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Buddhika reassigned RAMPART-334: Assignee: Thilina Buddhika > Unable to set TTL and maxTimeStampSkew values thr

[jira] [Commented] (RAMPART-324) Caused by: org.apache.ws.security.WSSecurityException: General security error (WSEncryptBody/WSSignE nvelope: Element to encrypt/sign not found: {http://ws.apache.org/

2011-09-28 Thread Thilina Buddhika (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/RAMPART-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117053#comment-13117053 ] Thilina Buddhika commented on RAMPART-324: -- Hi Amila, Thanks for the patch and