[jira] Resolved: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-3449. -- Resolution: Fixed Fixed in 640319. > JAX-WS 2.1: Support @RespectBinding and RespectBindingFea

[jira] Resolved: (AXIS2-3646) MTOM not enabled for dynamic ports

[ https://issues.apache.org/jira/browse/AXIS2-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-3646. -- Resolution: Fixed This is fixed in 639663. > MTOM not enabled for dynamic ports >

[jira] Created: (AXIS2-3646) MTOM not enabled for dynamic ports

MTOM not enabled for dynamic ports -- Key: AXIS2-3646 URL: https://issues.apache.org/jira/browse/AXIS2-3646 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.4

[jira] Updated: (AXIS2-3646) MTOM not enabled for dynamic ports

[ https://issues.apache.org/jira/browse/AXIS2-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3646: - Attachment: patch.txt > MTOM not enabled for dynamic ports > -- >

[jira] Updated: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

[ https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3547: - Priority: Blocker (was: Major) > JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+Simpl

[jira] Updated: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3449: - Priority: Blocker (was: Major) > JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature >

[jira] Closed: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

[ https://issues.apache.org/jira/browse/AXIS2-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo closed AXIS2-3448. Resolution: Fixed This code has been integrated. > JAX-WS 2.1: Support @MTOM and MTOMFeature > ---

[jira] Updated: (AXIS2-2722) Support for JAX-WS 2.1

[ https://issues.apache.org/jira/browse/AXIS2-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-2722: - Priority: Blocker (was: Major) > Support for JAX-WS 2.1 > -- > >

[jira] Commented: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

[ https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574673#action_12574673 ] Nick Gallardo commented on AXIS2-3547: -- For the Tomcat scenario, if the endpoint calls

[jira] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574669#action_12574669 ] Nick Gallardo commented on AXIS2-3449: -- Dims, Yep, I'm going to start on it this week

[jira] Updated: (AXIS2-2347) When deploying using JAXWSMessageReceiver, the dynamic wsdl (?wsdl) should reflect the annotations

[ https://issues.apache.org/jira/browse/AXIS2-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-2347: - Fix Version/s: 1.4 > When deploying using JAXWSMessageReceiver, the dynamic wsdl (?wsdl) should

[jira] Updated: (AXIS2-3558) XMLDispatch.createMessageFromValue fails to copy mime headers

[ https://issues.apache.org/jira/browse/AXIS2-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3558: - Fix Version/s: 1.4 > XMLDispatch.createMessageFromValue fails to copy mime headers >

[jira] Updated: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3449: - Fix Version/s: 1.4 > JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature >

[jira] Updated: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

[ https://issues.apache.org/jira/browse/AXIS2-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3448: - Fix Version/s: 1.4 > JAX-WS 2.1: Support @MTOM and MTOMFeature >

[jira] Updated: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

[ https://issues.apache.org/jira/browse/AXIS2-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3448: - Fix Version/s: (was: 1.4) Affects Version/s: 1.4 > JAX-WS 2.1: Support @MTOM and MTOM

[jira] Updated: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3449: - Affects Version/s: 1.4 > JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature >

[jira] Updated: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

[ https://issues.apache.org/jira/browse/AXIS2-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3448: - Description: JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding some

[jira] Resolved: (AXIS2-3425) Tolerate Java 6 JRE for JAX-WS applications

[ https://issues.apache.org/jira/browse/AXIS2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-3425. -- Resolution: Fixed This is fixed with Brian's integration of the JAX-WS 2.1 branch. > Tolerate

[jira] Commented: (AXIS2-2722) Support for JAX-WS 2.1

[ https://issues.apache.org/jira/browse/AXIS2-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562104#action_12562104 ] Nick Gallardo commented on AXIS2-2722: -- Here's a quick write up of the changes in the

[jira] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

[ https://issues.apache.org/jira/browse/AXIS2-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559519#action_12559519 ] Nick Gallardo commented on AXIS2-3449: -- It does look to be a combination of the two.

[jira] Created: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature - Key: AXIS2-3449 URL: https://issues.apache.org/jira/browse/AXIS2-3449 Project: Axis 2.0 (Axis2) Issue Type: New Featu

[jira] Work started: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

[ https://issues.apache.org/jira/browse/AXIS2-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AXIS2-3448 started by Nick Gallardo. > JAX-WS 2.1: Support @MTOM and MTOMFeature > - > > Key: AXIS2-3448 >

[jira] Created: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

JAX-WS 2.1: Support @MTOM and MTOMFeature - Key: AXIS2-3448 URL: https://issues.apache.org/jira/browse/AXIS2-3448 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws

[jira] Updated: (AXIS2-3425) Tolerate Java 6 JRE for JAX-WS applications

[ https://issues.apache.org/jira/browse/AXIS2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3425: - Attachment: patch.txt The trunk compiles with this patch. I still haven't gotten through all of

[jira] Created: (AXIS2-3425) Tolerate Java 6 JRE for JAX-WS applications

Tolerate Java 6 JRE for JAX-WS applications --- Key: AXIS2-3425 URL: https://issues.apache.org/jira/browse/AXIS2-3425 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws

[jira] Resolved: (AXIS2-3403) JAX-WS BasicAuth client config should allow no password

[ https://issues.apache.org/jira/browse/AXIS2-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-3403. -- Resolution: Fixed Fixed in 608590. > JAX-WS BasicAuth client config should allow no password >

[jira] Resolved: (AXIS2-3402) Nested swaRef attachments not sent in message

[ https://issues.apache.org/jira/browse/AXIS2-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-3402. -- Resolution: Fixed Fixed in 608602. > Nested swaRef attachments not sent in message > -

[jira] Commented: (AXIS2-3305) When WSDL exists, set wsdl properties for provider

[ https://issues.apache.org/jira/browse/AXIS2-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550997 ] Nick Gallardo commented on AXIS2-3305: -- Roy, there is already a set of context properties available for the WSDL

[jira] Updated: (AXIS2-3403) JAX-WS BasicAuth client config should allow no password

[ https://issues.apache.org/jira/browse/AXIS2-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3403: - Attachment: patch.txt A patch for this issue. > JAX-WS BasicAuth client config should allow no p

[jira] Created: (AXIS2-3403) JAX-WS BasicAuth client config should allow no password

JAX-WS BasicAuth client config should allow no password --- Key: AXIS2-3403 URL: https://issues.apache.org/jira/browse/AXIS2-3403 Project: Axis 2.0 (Axis2) Issue Type: Bug Compone

[jira] Updated: (AXIS2-3402) Nested swaRef attachments not sent in message

[ https://issues.apache.org/jira/browse/AXIS2-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-3402: - Attachment: patch.txt A patch for the issue. > Nested swaRef attachments not sent in message > -

[jira] Created: (AXIS2-3402) Nested swaRef attachments not sent in message

Nested swaRef attachments not sent in message - Key: AXIS2-3402 URL: https://issues.apache.org/jira/browse/AXIS2-3402 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affec

[jira] Resolved: (AXIS2-2125) Asynchronous web service invocation does not return XML response on a SOAP fault

[ https://issues.apache.org/jira/browse/AXIS2-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2125. -- Resolution: Fixed Marking this issue resolved per the fix in JIRA 2091. > Asynchronous web s

[jira] Commented: (AXIS2-2920) JAX-WS 2.0 support for Apache Axis2 WSDL2Java Code Generator

[ https://issues.apache.org/jira/browse/AXIS2-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516717 ] Nick Gallardo commented on AXIS2-2920: -- Note: the JAX-WS runtime already supports both wrapper and non-wrapper s

[jira] Resolved: (AXIS2-2895) Disallow sync/oneway invocations when async property is set

[ https://issues.apache.org/jira/browse/AXIS2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2895. -- Resolution: Fixed Fixed in 556650. > Disallow sync/oneway invocations when async property is s

[jira] Commented: (AXIS2-2895) Disallow sync/oneway invocations when async property is set

[ https://issues.apache.org/jira/browse/AXIS2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512966 ] Nick Gallardo commented on AXIS2-2895: -- No worries David, your concern was valid per the original comments. > D

[jira] Commented: (AXIS2-2895) Disallow sync/oneway invocations when async property is set

[ https://issues.apache.org/jira/browse/AXIS2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512962 ] Nick Gallardo commented on AXIS2-2895: -- David, The defect should really only mention a one-way invocation and n

[jira] Assigned: (AXIS2-2895) Disallow sync/oneway invocations when async property is set

[ https://issues.apache.org/jira/browse/AXIS2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2895: Assignee: Nick Gallardo (was: Jeff Barrett) > Disallow sync/oneway invocations when async

[jira] Resolved: (AXIS2-2817) Create AttachmentDescription objects in the JAX-WS Metadata layer

[ https://issues.apache.org/jira/browse/AXIS2-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2817. -- Resolution: Fixed Cleaning up this issue. This was fixed in 555386. > Create AttachmentDescri

[jira] Resolved: (AXIS2-2548) Handler test with fault causes exception

[ https://issues.apache.org/jira/browse/AXIS2-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2548. -- Resolution: Fixed Fixed in 551215. > Handler test with fault causes exception > --

[jira] Closed: (AXIS2-2539) Add support for the Endpoint.publish() API

[ https://issues.apache.org/jira/browse/AXIS2-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo closed AXIS2-2539. Resolution: Fixed > Add support for the Endpoint.publish() API > --

[jira] Assigned: (AXIS2-2836) Allow a thread factory to be registered with the JAX-WS layer

[ https://issues.apache.org/jira/browse/AXIS2-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2836: Assignee: Nick Gallardo > Allow a thread factory to be registered with the JAX-WS layer > -

[jira] Commented: (AXIS2-2832) provide a public constructor for basemessagecontext

[ https://issues.apache.org/jira/browse/AXIS2-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506911 ] Nick Gallardo commented on AXIS2-2832: -- Hi Lin, I believe BaseMessageContext isn't really intended to be used d

[jira] Assigned: (AXIS2-2832) provide a public constructor for basemessagecontext

[ https://issues.apache.org/jira/browse/AXIS2-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2832: Assignee: Nick Gallardo > provide a public constructor for basemessagecontext > ---

[jira] Commented: (AXIS2-2548) Handler test with fault causes exception

[ https://issues.apache.org/jira/browse/AXIS2-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506179 ] Nick Gallardo commented on AXIS2-2548: -- Glen, This problem surfaced because of some of the conversions that we

[jira] Created: (AXIS2-2539) Add support for the Endpoint.publish() API

Add support for the Endpoint.publish() API -- Key: AXIS2-2539 URL: https://issues.apache.org/jira/browse/AXIS2-2539 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws

[jira] Closed: (AXIS2-2535) EndpointDescription not properly set on MessageContext

[ https://issues.apache.org/jira/browse/AXIS2-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo closed AXIS2-2535. Resolution: Fixed This is fixed in rev. 529302. > EndpointDescription not properly set on MessageC

[jira] Created: (AXIS2-2535) EndpointDescription not properly set on MessageContext

EndpointDescription not properly set on MessageContext -- Key: AXIS2-2535 URL: https://issues.apache.org/jira/browse/AXIS2-2535 Project: Axis 2.0 (Axis2) Issue Type: Bug Component

[jira] Closed: (AXIS2-2532) Add implementation of LogicalMessageContext/LogicalMessage for use in handlers

[ https://issues.apache.org/jira/browse/AXIS2-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo closed AXIS2-2532. Resolution: Fixed Fixed in 529264. > Add implementation of LogicalMessageContext/LogicalMessage fo

[jira] Closed: (AXIS2-2537) ApplicationContextMigrator not called from the JAX-WS Proxy

[ https://issues.apache.org/jira/browse/AXIS2-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo closed AXIS2-2537. Resolution: Fixed Fixed in 529312. > ApplicationContextMigrator not called from the JAX-WS Proxy >

[jira] Created: (AXIS2-2537) ApplicationContextMigrator not called from the JAX-WS Proxy

ApplicationContextMigrator not called from the JAX-WS Proxy --- Key: AXIS2-2537 URL: https://issues.apache.org/jira/browse/AXIS2-2537 Project: Axis 2.0 (Axis2) Issue Type: Bug

[jira] Created: (AXIS2-2532) Add implementation of LogicalMessageContext/LogicalMessage for use in handlers

Add implementation of LogicalMessageContext/LogicalMessage for use in handlers -- Key: AXIS2-2532 URL: https://issues.apache.org/jira/browse/AXIS2-2532 Project: Axis 2.0 (Axis

[jira] Resolved: (AXIS2-2397) Create JAXWS application handlers sample

[ https://issues.apache.org/jira/browse/AXIS2-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2397. -- Resolution: Fixed Fixed in 523344. The handler tests themselves are commented out though as th

[jira] Resolved: (AXIS2-2218) @HandlerChain annotation is not picked up

[ https://issues.apache.org/jira/browse/AXIS2-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2218. -- Resolution: Fixed Fixed in 523344. The handler tests themselves are commented out though as th

[jira] Commented: (AXIS2-2407) RPCProxyTests broke again.

[ https://issues.apache.org/jira/browse/AXIS2-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484466 ] Nick Gallardo commented on AXIS2-2407: -- Didn't see this last night... Did I miss something, or did they break t

[jira] Resolved: (AXIS2-2377) Add metadata layer annotation processing

[ https://issues.apache.org/jira/browse/AXIS2-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2377. -- Resolution: Fixed Fixed in 522702. > Add metadata layer annotation processing > --

[jira] Updated: (AXIS2-2377) Add metadata layer annotation processing

[ https://issues.apache.org/jira/browse/AXIS2-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-2377: - Attachment: patch-2377.txt A patch for this issue... This let's us use JAXB to read the handler

[jira] Created: (AXIS2-2397) Create JAXWS application handlers sample

Create JAXWS application handlers sample Key: AXIS2-2397 URL: https://issues.apache.org/jira/browse/AXIS2-2397 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws

[jira] Resolved: (AXIS2-2396) Change JAXWS MessageContext to use EndpointDescription

[ https://issues.apache.org/jira/browse/AXIS2-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2396. -- Resolution: Fixed Fixed in 522689. > Change JAXWS MessageContext to use EndpointDescription >

[jira] Resolved: (AXIS2-2317) JAXWS client response context properties not found

[ https://issues.apache.org/jira/browse/AXIS2-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2317. -- Resolution: Fixed Fixed in 522637. > JAXWS client response context properties not found >

[jira] Updated: (AXIS2-2317) JAXWS client response context properties not found

[ https://issues.apache.org/jira/browse/AXIS2-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-2317: - Attachment: patch-migrator-impl.txt > JAXWS client response context properties not found > --

[jira] Updated: (AXIS2-2396) Change JAXWS MessageContext to use EndpointDescription

[ https://issues.apache.org/jira/browse/AXIS2-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-2396: - Attachment: patch-2396.txt > Change JAXWS MessageContext to use EndpointDescription > ---

[jira] Created: (AXIS2-2396) Change JAXWS MessageContext to use EndpointDescription

Change JAXWS MessageContext to use EndpointDescription -- Key: AXIS2-2396 URL: https://issues.apache.org/jira/browse/AXIS2-2396 Project: Axis 2.0 (Axis2) Issue Type: Improvement C

[jira] Assigned: (AXIS2-2377) Add metadata layer annotation processing

[ https://issues.apache.org/jira/browse/AXIS2-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2377: Assignee: Nick Gallardo Thanks Roy! > Add metadata layer annotation processing > -

[jira] Commented: (AXIS2-2347) When deploying using JAXWSMessageReceiver, the dynamic wsdl (?wsdl) should reflect the annotations

[ https://issues.apache.org/jira/browse/AXIS2-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482221 ] Nick Gallardo commented on AXIS2-2347: -- I'm guessing that this is related to GERONIMO-2988 opened by Lin today [

[jira] Updated: (AXIS2-2317) JAXWS client response context properties not found

[ https://issues.apache.org/jira/browse/AXIS2-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-2317: - Attachment: patch-migrator-api.txt > JAXWS client response context properties not found > ---

[jira] Created: (AXIS2-2317) JAXWS client response context properties not found

JAXWS client response context properties not found -- Key: AXIS2-2317 URL: https://issues.apache.org/jira/browse/AXIS2-2317 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws

[jira] Assigned: (AXIS2-2232) Class.forName does not use AxisService class loader

[ https://issues.apache.org/jira/browse/AXIS2-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2232: Assignee: Nick Gallardo > Class.forName does not use AxisService class loader > --

[jira] Resolved: (AXIS2-2170) Error in handling async response when executor service is shutdown

[ https://issues.apache.org/jira/browse/AXIS2-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2170. -- Resolution: Fixed Updated WSDL has been committed. Thanks Ann. > Error in handling async resp

[jira] Commented: (AXIS2-2170) Error in handling async response when executor service is shutdown

[ https://issues.apache.org/jira/browse/AXIS2-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473472 ] Nick Gallardo commented on AXIS2-2170: -- Sorry Ann... that was my fault. Thanks for the updated patch. > Err

[jira] Resolved: (AXIS2-2171) JAXWS absorbs async exceptions

[ https://issues.apache.org/jira/browse/AXIS2-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2171. -- Resolution: Fixed Commented out test "testStringInflow4()" in the message tests. This requires

[jira] Assigned: (AXIS2-2171) JAXWS absorbs async exceptions

[ https://issues.apache.org/jira/browse/AXIS2-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2171: Assignee: Nick Gallardo > JAXWS absorbs async exceptions > -- >

[jira] Resolved: (AXIS2-2160) Remove unnecessary log information from JAXBUtils class

[ https://issues.apache.org/jira/browse/AXIS2-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2160. -- Resolution: Fixed Thanks for the patch Lasantha. This change makes sense... I've committed th

[jira] Resolved: (AXIS2-2181) DescriptionUtils class should return null if it cannot load wrapper class

[ https://issues.apache.org/jira/browse/AXIS2-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2181. -- Resolution: Fixed Committed the patch in revision: 507670. Thanks Dustin! > DescriptionUtils

[jira] Assigned: (AXIS2-2181) DescriptionUtils class should return null if it cannot load wrapper class

[ https://issues.apache.org/jira/browse/AXIS2-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2181: Assignee: Nick Gallardo > DescriptionUtils class should return null if it cannot load wrapp

[jira] Assigned: (AXIS2-2160) Remove unnecessary log information from JAXBUtils class

[ https://issues.apache.org/jira/browse/AXIS2-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2160: Assignee: Nick Gallardo > Remove unnecessary log information from JAXBUtils class > ---

[jira] Resolved: (AXIS2-2170) Error in handling async response when executor service is shutdown

[ https://issues.apache.org/jira/browse/AXIS2-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2170. -- Resolution: Fixed Committed the fix in revision 507358. > Error in handling async response whe

[jira] Assigned: (AXIS2-2170) Error in handling async response when executor service is shutdown

[ https://issues.apache.org/jira/browse/AXIS2-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2170: Assignee: Nick Gallardo > Error in handling async response when executor service is shutdow

[jira] Resolved: (AXIS2-2169) JAX-WS MetaData layer should use 2006 MEP URI constants.

[ https://issues.apache.org/jira/browse/AXIS2-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2169. -- Resolution: Fixed Committed patch in revision 507332. > JAX-WS MetaData layer should use 2006

[jira] Assigned: (AXIS2-2169) JAX-WS MetaData layer should use 2006 MEP URI constants.

[ https://issues.apache.org/jira/browse/AXIS2-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2169: Assignee: Nick Gallardo > JAX-WS MetaData layer should use 2006 MEP URI constants. > --

[jira] Resolved: (AXIS2-1822) Dynamic Proxy not reading SOAPAction from WSDL

[ https://issues.apache.org/jira/browse/AXIS2-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-1822. -- Resolution: Fixed This has been fixed. > Dynamic Proxy not reading SOAPAction from WSDL >

[jira] Resolved: (AXIS2-2086) Faults not processed correctly for JAX-WS async clients.

[ https://issues.apache.org/jira/browse/AXIS2-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2086. -- Resolution: Fixed This has been fixed. > Faults not processed correctly for JAX-WS async clien

[jira] Commented: (AXIS2-2154) org.apache.axis2.jaxws.sample.MtomSampleByteArrayTests fails on Solaris

[ https://issues.apache.org/jira/browse/AXIS2-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471797 ] Nick Gallardo commented on AXIS2-2154: -- It looks like the request is being unmarshalled on the server side, but

[jira] Created: (AXIS2-2155) Wrapped marshall/unmarshall without wrapper beans

Wrapped marshall/unmarshall without wrapper beans - Key: AXIS2-2155 URL: https://issues.apache.org/jira/browse/AXIS2-2155 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws

[jira] Commented: (AXIS2-1800) JAX-WS Cache or improve the @XMLRootElement and related annotation lookups

[ https://issues.apache.org/jira/browse/AXIS2-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471079 ] Nick Gallardo commented on AXIS2-1800: -- Rich, The caching here will really help performance. When looking at t

[jira] Commented: (AXIS2-2125) Asynchronous web service invocation does not return XML response on a SOAP fault

[ https://issues.apache.org/jira/browse/AXIS2-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470839 ] Nick Gallardo commented on AXIS2-2125: -- I've addressed this in a different way just yesterday in a different JIR

[jira] Resolved: (AXIS2-2091) Callback.onError() faults should be delivered with a MessageContext

[ https://issues.apache.org/jira/browse/AXIS2-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2091. -- Resolution: Fixed Fixed in rev 503847. > Callback.onError() faults should be delivered with a

[jira] Updated: (AXIS2-2091) Callback.onError() faults should be delivered with a MessageContext

[ https://issues.apache.org/jira/browse/AXIS2-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo updated AXIS2-2091: - Attachment: patch.txt A patch for this issue. All tests, including enterprise tests, passed with

[jira] Created: (AXIS2-2091) Callback.onError() faults should be delivered with a MessageContext

Callback.onError() faults should be delivered with a MessageContext --- Key: AXIS2-2091 URL: https://issues.apache.org/jira/browse/AXIS2-2091 Project: Axis 2.0 (Axis2) Issue Typ

[jira] Resolved: (AXIS2-2082) fault subcodes being ignored for SOAP1.2

[ https://issues.apache.org/jira/browse/AXIS2-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2082. -- Resolution: Fixed Committed Mike's patch under revision 502635. Thanks Mike! > fault subcodes

[jira] Created: (AXIS2-2086) Faults not processed correctly for JAX-WS async clients.

Faults not processed correctly for JAX-WS async clients. Key: AXIS2-2086 URL: https://issues.apache.org/jira/browse/AXIS2-2086 Project: Axis 2.0 (Axis2) Issue Type: Bug Compo

[jira] Assigned: (AXIS2-2082) fault subcodes being ignored for SOAP1.2

[ https://issues.apache.org/jira/browse/AXIS2-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2082: Assignee: Nick Gallardo > fault subcodes being ignored for SOAP1.2 > --

[jira] Resolved: (AXIS2-2079) JAX-WS Fault MessageContexts are created incorrectly

[ https://issues.apache.org/jira/browse/AXIS2-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2079. -- Resolution: Fixed This is fixed in 502367. > JAX-WS Fault MessageContexts are created incorrec

[jira] Resolved: (AXIS2-2078) @WebServiceClient annotation definition does not have correct default values

[ https://issues.apache.org/jira/browse/AXIS2-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2078. -- Resolution: Fixed I've committed the patch under revision 502361. Thanks Dustin! > @WebServic

[jira] Assigned: (AXIS2-2078) @WebServiceClient annotation definition does not have correct default values

[ https://issues.apache.org/jira/browse/AXIS2-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2078: Assignee: Nick Gallardo > @WebServiceClient annotation definition does not have correct def

[jira] Assigned: (AXIS2-2079) JAX-WS Fault MessageContexts are created incorrectly

[ https://issues.apache.org/jira/browse/AXIS2-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2079: Assignee: Nick Gallardo > JAX-WS Fault MessageContexts are created incorrectly > --

[jira] Created: (AXIS2-2079) JAX-WS Fault MessageContexts are created incorrectly

JAX-WS Fault MessageContexts are created incorrectly Key: AXIS2-2079 URL: https://issues.apache.org/jira/browse/AXIS2-2079 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: j

[jira] Resolved: (AXIS2-2061) Wrong SOAPBinding API import

[ https://issues.apache.org/jira/browse/AXIS2-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2061. -- Resolution: Fixed Committed the patch in rev 501722. Thanks Sam. > Wrong SOAPBinding API impo

[jira] Assigned: (AXIS2-2061) Wrong SOAPBinding API import

[ https://issues.apache.org/jira/browse/AXIS2-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2061: Assignee: Nick Gallardo > Wrong SOAPBinding API import > - > >

[jira] Resolved: (AXIS2-2063) NPE in FaultDescriptionImpl

[ https://issues.apache.org/jira/browse/AXIS2-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-2063. -- Resolution: Fixed Committed the fix in rev 501721. Thanks Dustin. > NPE in FaultDescriptionIm

  1   2   3   >