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

2011-02-11 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett resolved AXIS2-4948. - Resolution: Fixed Patch committed in revision 1069898. Thanks Katherine! > JAX-WS 2.2

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

2011-02-10 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett resolved AXIS2-4938. - Resolution: Fixed Path committed in revision 1069659 Thanks Katherine! > JAX-WS 2.2

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

2011-02-10 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett reassigned AXIS2-4938: --- Assignee: Jeff Barrett > JAX-WS 2.2 CTS - BindingProvider.getEndpointReference should

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

2011-02-10 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett reassigned AXIS2-4948: --- Assignee: Jeff Barrett > JAX-WS 2.2 CTS - Wrong wsdlLocation in EPR returned

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

2011-02-09 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett resolved AXIS2-4952. - Resolution: Fixed Committed revision 1068985 > JAX-WS dynamic ports should be scoped to

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

2011-02-09 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992607#comment-12992607 ] Jeff Barrett commented on AXIS2-4952: - Committed revision 1068985 > JAX-WS

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

2011-02-09 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett closed AXIS2-4952. --- > JAX-WS dynamic ports should be scoped to the service instance the created t

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

2011-02-09 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992571#comment-12992571 ] Jeff Barrett commented on AXIS2-4952: - I have a fix for this Jira. Here are

Re: Running JAX-WS TCK on Axis2

2011-02-09 Thread Jeff Barrett
No I tried 2.1. Just to identify the failing cases. Thanks, ~Isuru On Wed, Feb 9, 2011 at 1:09 AM, Jeff Barrett wrote: Hi Isuru, Is it the TCK for JAX-WS 2.2 you are running? Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: (512) 286-5256 or TieLine: 363-5256 Inte

Re: Running JAX-WS TCK on Axis2

2011-02-08 Thread Jeff Barrett
Hi Isuru, Is it the TCK for JAX-WS 2.2 you are running? Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: (512) 286-5256 or TieLine: 363-5256 Internet e-mail and Sametime ID: barre...@us.ibm.com From: Isuru Suriarachchi To: java-dev@axis.apache.org Date: 02/

Re: [AXIS2] 1.6 release branch created

2011-02-08 Thread Jeff Barrett
Hi Ruwan, That means trunk is back open for business, and we can commit into there as usual, correct? Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: (512) 286-5256 or TieLine: 363-5256 Internet e-mail and Sametime ID: barre...@us.ibm.com From: Ruwan Linton To:

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

2011-02-07 Thread Jeff Barrett (JIRA)
Issue Type: Bug Components: jaxws Reporter: Jeff Barrett Assignee: Jeff Barrett When a JAX-WS dynamic port is added via addPort(...), it should be scoped to the instance of the service that created it. Currently dynamic ports are scoped in the runtime by

[jira] Resolved: (AXIS2-4922) JAX-WS 2.2 CTS failures in WS-A metadata action code

2011-01-14 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett resolved AXIS2-4922. - Resolution: Fixed Committed patch to revision 1059115 > JAX-WS 2.2 CTS failures in W

[jira] Closed: (AXIS2-4922) JAX-WS 2.2 CTS failures in WS-A metadata action code

2011-01-14 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett closed AXIS2-4922. --- Patch committed. > JAX-WS 2.2 CTS failures in WS-A metadata action c

[jira] Assigned: (AXIS2-4922) JAX-WS 2.2 CTS failures in WS-A metadata action code

2011-01-14 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett reassigned AXIS2-4922: --- Assignee: Jeff Barrett > JAX-WS 2.2 CTS failures in WS-A metadata action c

[jira] Closed: (AXIS2-4855) Support new SOAP/JMS binding ID

2011-01-03 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett closed AXIS2-4855. --- Resolution: Fixed Patch committed as noted above. There is follow-on work to support both SOAP11

[jira] Updated: (AXIS2-4876) Support SOAP11 and SOAP12 over JMS binding types

2010-11-08 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett updated AXIS2-4876: Component/s: (was: kernel) Assignee: (was: Jeff Barrett) > Support SOAP11

[jira] Commented: (AXIS2-4876) Support SOAP11 and SOAP12 over JMS binding types

2010-11-08 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929621#action_12929621 ] Jeff Barrett commented on AXIS2-4876: - As noted in AXIS2-4855, JAX-WS does

[jira] Created: (AXIS2-4876) Support SOAP11 and SOAP12 over JMS binding types

2010-11-08 Thread Jeff Barrett (JIRA)
, kernel Reporter: Jeff Barrett Assignee: Jeff Barrett The W3C SOAP/JMS binding specification (located here: http://www.w3.org/2002/ws/soapjms/) is nearing its first approved version, and has defined a more up to date binding ID for use in the @BindingType annotation (for JAX

[jira] Commented: (AXIS2-4855) Support new SOAP/JMS binding ID

2010-11-08 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929612#action_12929612 ] Jeff Barrett commented on AXIS2-4855: - Patch from Phil with additional comments

[jira] Commented: (AXIS2-4855) Support new SOAP/JMS binding ID

2010-11-08 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929611#action_12929611 ] Jeff Barrett commented on AXIS2-4855: - One other important point. The issue is

[jira] Commented: (AXIS2-4855) Support new SOAP/JMS binding ID

2010-11-08 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929608#action_12929608 ] Jeff Barrett commented on AXIS2-4855: - This patch uncovered a pre-existing issu

[jira] Commented: (AXIS2-4855) Support new SOAP/JMS binding ID

2010-11-02 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927572#action_12927572 ] Jeff Barrett commented on AXIS2-4855: - The patch causes a JAX-WS integration tes

[jira] Assigned: (AXIS2-4855) Support new SOAP/JMS binding ID

2010-10-20 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett reassigned AXIS2-4855: --- Assignee: Jeff Barrett > Support new SOAP/JMS binding

[jira] Resolved: (AXIS2-4715) Client-side enforcement for AddressingFeature.required

2010-05-14 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett resolved AXIS2-4715. - Resolution: Fixed Patch committed in revision 944485 > Client-side enforcement

[jira] Resolved: (AXIS2-4699) JAX-WS 2.2: Add new Provider.createW3CEndpointReference method

2010-04-30 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett resolved AXIS2-4699. - Resolution: Fixed Patch Committed to revision 939784 > JAX-WS 2.2: Add

[jira] Assigned: (AXIS2-4699) JAX-WS 2.2: Add new Provider.createW3CEndpointReference method

2010-04-30 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Barrett reassigned AXIS2-4699: --- Assignee: Jeff Barrett > JAX-WS 2.2: Add new Provider.createW3CEndpointReference met

Re: svn commit: r937071 - in /axis/axis2/java/core/trunk/modules: jaxws-integration/ metadata/ metadata/src/org/apache/axis2/jaxws/server/config/ metadata/test/org/apache/axis2/jaxws/description/fea

2010-04-28 Thread Jeff Barrett
the mailing list. Does anybody know what needs to be done to allow hud...@hudson.zones.apache.org to post to java-...@axis.apache.org? Andreas On Tue, Apr 27, 2010 at 17:13, Jeff Barrett wrote: > Andreas, > > Thanks for fixing this! I had run the tests with Java 1.6 prior to > com

Re: svn commit: r937071 - in /axis/axis2/java/core/trunk/modules: jaxws-integration/ metadata/ metadata/src/org/apache/axis2/jaxws/server/config/ metadata/test/org/apache/axis2/jaxws/description/fea

2010-04-27 Thread Jeff Barrett
Andreas, Thanks for fixing this! I had run the tests with Java 1.6 prior to committing, and they passed. Sorry to all for the inconvenience. Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: (512) 286-5256 or TieLine: 363-5256 Internet e-mail and Sametime ID: barre..

[jira] Commented: (AXIS2-4601) AddressingOutHandler performance improvements

2010-04-01 Thread Jeff Barrett (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852388#action_12852388 ] Jeff Barrett commented on AXIS2-4601: - Commited rollback.patch in revision 92

Re: [VOTE] Nikil Thaker for committer (again)

2010-02-24 Thread Jeff Barrett
+1 Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: (512) 286-5256 or TieLine: 363-5256 Internet e-mail and Sametime ID: barre...@us.ibm.com From: Glen Daniels To: java-dev@axis.apache.org Date: 02/23/2010 07:21 PM Subject: [VOTE] Nikil Thaker for committer (again)