[jira] [Issue Comment Edited] (AXIS2-3967) JDk5 Enum Support in AXIS2

[ https://issues.apache.org/jira/browse/AXIS2-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082951#comment-13082951 ] Shameera Rathnayaka edited comment on AXIS2-3967 at 8/11/11 6:19 AM: ---

[jira] [Issue Comment Edited] (AXIS2-3967) JDk5 Enum Support in AXIS2

[ https://issues.apache.org/jira/browse/AXIS2-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082951#comment-13082951 ] Shameera Rathnayaka edited comment on AXIS2-3967 at 8/11/11 6:19 AM: ---

[jira] [Commented] (AXIS2-3967) JDk5 Enum Support in AXIS2

[ https://issues.apache.org/jira/browse/AXIS2-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082951#comment-13082951 ] Shameera commented on AXIS2-3967: - Hi im looking into implement this feature for 1.7 relea

Re: Is there possible for 1.7.0 release ?

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 merge > > the changes to 1.6.1-

Re: Is there possible for 1.7.0 release ?

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 merge > the changes to 1.6.1-SNAPSHOT ? Thanks > ---> > Revision: 1068985 > AXIS2-4952 > Sc

[jira] [Commented] (AXIS2-5067) content-type header is not generated with SAAJ API

[ https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082868#comment-13082868 ] Hudson commented on AXIS2-5067: --- Integrated in axis2-1.5 #161 (See [https://builds.apache.o

[jira] [Commented] (AXIS2-4948) JAX-WS 2.2 CTS - Wrong wsdlLocation in EPR returned by BindingProvider.getEndpointReference

[ https://issues.apache.org/jira/browse/AXIS2-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082796#comment-13082796 ] Hudson commented on AXIS2-4948: --- Integrated in axis2-1.6 #66 (See [https://builds.apache.org

[jira] [Commented] (AXIS2-5067) content-type header is not generated with SAAJ API

[ https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082793#comment-13082793 ] Hudson commented on AXIS2-5067: --- Integrated in axis2-1.6 #66 (See [https://builds.apache.org

[jira] [Commented] (AXIS2-5021) Extra slash is added for wsdl access address

[ https://issues.apache.org/jira/browse/AXIS2-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082795#comment-13082795 ] Hudson commented on AXIS2-5021: --- Integrated in axis2-1.6 #66 (See [https://builds.apache.org

[jira] [Commented] (AXIS2-4938) JAX-WS 2.2 CTS - BindingProvider.getEndpointReference should put reference parameters from WSDL in returned EPR

[ https://issues.apache.org/jira/browse/AXIS2-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082797#comment-13082797 ] Hudson commented on AXIS2-4938: --- Integrated in axis2-1.6 #66 (See [https://builds.apache.org

[jira] [Commented] (AXIS2-4952) JAX-WS dynamic ports should be scoped to the service instance the created them

[ https://issues.apache.org/jira/browse/AXIS2-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082794#comment-13082794 ] Hudson commented on AXIS2-4952: --- Integrated in axis2-1.6 #66 (See [https://builds.apache.org

[jira] [Commented] (AXIS2-4263) Stopping ListenerManager does not cleanup several Timer threads

[ https://issues.apache.org/jira/browse/AXIS2-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082739#comment-13082739 ] Hudson commented on AXIS2-4263: --- Integrated in Axis2 #912 (See [https://builds.apache.org/jo

[jira] [Updated] (AXIS2-5067) content-type header is not generated with SAAJ API

[ https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5067: --- Fix Version/s: 1.5.6 > content-type header is not generated with SAAJ API > -

[jira] [Assigned] (AXIS2-5079) 1.5.5 does not alow exploaded services to be dropped in services directory

[ https://issues.apache.org/jira/browse/AXIS2-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS2-5079: -- Assignee: Andreas Veithen > 1.5.5 does not alow exploaded services to be dropped in ser

[jira] [Updated] (AXIS2-5086) destroy(ServiceContext context) method never called in request scope.

[ https://issues.apache.org/jira/browse/AXIS2-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5086: --- Assignee: Sagara Gunathunga > destroy(ServiceContext context) method never called in request

[jira] [Updated] (AXIS2-5067) content-type header is not generated with SAAJ API

[ https://issues.apache.org/jira/browse/AXIS2-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5067: --- Fix Version/s: 1.6.1 > content-type header is not generated with SAAJ API > -

[jira] [Updated] (AXIS2-4948) JAX-WS 2.2 CTS - Wrong wsdlLocation in EPR returned by BindingProvider.getEndpointReference

[ https://issues.apache.org/jira/browse/AXIS2-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4948: --- Fix Version/s: 1.7.0 1.6.1 > JAX-WS 2.2 CTS - Wrong wsdlLocation in EPR re

[jira] [Updated] (AXIS2-5021) Extra slash is added for wsdl access address

[ https://issues.apache.org/jira/browse/AXIS2-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5021: --- Fix Version/s: 1.6.1 > Extra slash is added for wsdl access address > ---

[jira] [Updated] (AXIS2-4938) JAX-WS 2.2 CTS - BindingProvider.getEndpointReference should put reference parameters from WSDL in returned EPR

[ https://issues.apache.org/jira/browse/AXIS2-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4938: --- Fix Version/s: 1.7.0 1.6.1 > JAX-WS 2.2 CTS - BindingProvider.getEndpointR

[jira] [Resolved] (AXIS2-4952) JAX-WS dynamic ports should be scoped to the service instance the created them

[ https://issues.apache.org/jira/browse/AXIS2-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4952. Resolution: Fixed Fix Version/s: 1.7.0 1.6.1 > JAX-WS dynamic por

[jira] [Reopened] (AXIS2-4952) JAX-WS dynamic ports should be scoped to the service instance the created them

[ https://issues.apache.org/jira/browse/AXIS2-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reopened AXIS2-4952: Temporarily reopen the issue to update the fix version (this is not possible on closed issues)

[jira] [Commented] (AXIS2-4263) Stopping ListenerManager does not cleanup several Timer threads

[ https://issues.apache.org/jira/browse/AXIS2-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082672#comment-13082672 ] Hudson commented on AXIS2-4263: --- Integrated in axis2-1.6 #65 (See [https://builds.apache.org

[jira] [Resolved] (TRANSPORTS-42) Axis2 JMS transport violates W3C SOAP over JMS, Protocol-2038

[ https://issues.apache.org/jira/browse/TRANSPORTS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved TRANSPORTS-42. --- Resolution: Duplicate Same as TRANSPORTS-43. > Axis2 JMS transport violates W3C S

[jira] [Commented] (AXIS2-5110) Compatibility with WebSphere Application Server on z/OS

[ https://issues.apache.org/jira/browse/AXIS2-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082627#comment-13082627 ] William Walsh commented on AXIS2-5110: -- Andreas, Thanks for he confirmation on that

[jira] [Resolved] (AXIS2-4263) Stopping ListenerManager does not cleanup several Timer threads

[ https://issues.apache.org/jira/browse/AXIS2-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4263. Resolution: Fixed Fix Version/s: 1.7.0 1.6.1 1.

[jira] [Commented] (AXIS2-4263) Stopping ListenerManager does not cleanup several Timer threads

[ https://issues.apache.org/jira/browse/AXIS2-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082615#comment-13082615 ] Hudson commented on AXIS2-4263: --- Integrated in axis2-1.5 #160 (See [https://builds.apache.o

[jira] [Updated] (AXIS2-5117) CLONE - sources unavailable in the maven repository.

[ https://issues.apache.org/jira/browse/AXIS2-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Shemansky updated AXIS2-5117: -- Fix Version/s: (was: 1.4) Description: It would appear that some/most of the s

[jira] [Created] (AXIS2-5117) CLONE - sources unavailable in the maven repository.

CLONE - sources unavailable in the maven repository. Key: AXIS2-5117 URL: https://issues.apache.org/jira/browse/AXIS2-5117 Project: Axis2 Issue Type: Improvement Components: samp

Re: How to include Axis2 modules in self-contained executable jar?

Oops, the article I mentioned near the end was meant to link to: http://wso2.org/library/182 -- Jay Sullivan

[jira] [Commented] (AXIS2-5110) Compatibility with WebSphere Application Server on z/OS

[ https://issues.apache.org/jira/browse/AXIS2-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082537#comment-13082537 ] Andreas Veithen commented on AXIS2-5110: The scripting module is a file called scr

[jira] [Assigned] (AXIS2-4263) Stopping ListenerManager does not cleanup several Timer threads

[ https://issues.apache.org/jira/browse/AXIS2-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS2-4263: -- Assignee: Andreas Veithen (was: Srinath Perera) > Stopping ListenerManager does not cl

How to include Axis2 modules in self-contained executable jar?

I currently have an Axis2 web service client. Right now, I've got build.xml configured to package all of the Axis2 jars along with my client, and the result is a single executable jar file. This works fine. However, I need to load two modules: rampart.mar and addressing.mar. Right now, my app l

[jira] [Issue Comment Edited] (AXIS2-5108) Axis2 code generator plugin for eclipse

[ https://issues.apache.org/jira/browse/AXIS2-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082307#comment-13082307 ] Harshana Eranga Martin edited comment on AXIS2-5108 at 8/10/11 12:38 PM: ---

[jira] [Issue Comment Edited] (AXIS2-5108) Axis2 code generator plugin for eclipse

[ https://issues.apache.org/jira/browse/AXIS2-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082307#comment-13082307 ] Harshana Eranga Martin edited comment on AXIS2-5108 at 8/10/11 12:39 PM: ---

[jira] [Updated] (AXIS2-5108) Axis2 code generator plugin for eclipse

[ https://issues.apache.org/jira/browse/AXIS2-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshana Eranga Martin updated AXIS2-5108: -- Attachment: 5108.zip I tried with the wsdl file which has referenced namespaces

[jira] [Created] (AXIS2-5116) AxisFault: string at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext When server is deployed in tomcat

AxisFault: string at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext When server is deployed in tomcat Key: AXIS2-5116 URL: https:/