[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 RespectBindingFeature - Key: AXIS2-3449 URL: https://issues.apache.org/jira/browse/AXIS2-3449 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo Priority: Blocker Fix For: 1.4 RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element. In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint. Here's a quick summary of the work to be done: 1. Update the metadata APIs to expose the RespectBinding data available 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation. 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature. 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property. 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input. This is described in the check that exists in the EndpointController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- 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 Reporter: Nick Gallardo Assignee: Nick Gallardo Fix For: 1.4 Attachments: patch.txt When a dynamic port is added to a ServiceDescription, and used to create a Dispatch, the binding type is not checked to enable MTOM for that client. This results in requests not sending the proper MIME payload. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Reporter: Nick Gallardo Assignee: Nick Gallardo Fix For: 1.4 Attachments: patch.txt When a dynamic port is added to a ServiceDescription, and used to create a Dispatch, the binding type is not checked to enable MTOM for that client. This results in requests not sending the proper MIME payload. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- 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 Reporter: Nick Gallardo Assignee: Nick Gallardo Fix For: 1.4 Attachments: patch.txt When a dynamic port is added to a ServiceDescription, and used to create a Dispatch, the binding type is not checked to enable MTOM for that client. This results in requests not sending the proper MIME payload. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2722 URL: https://issues.apache.org/jira/browse/AXIS2-2722 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Affects Versions: 1.4 Reporter: Brian DePradine Assignee: Brian DePradine Priority: Blocker Fix For: 1.4 Attachments: addressing.txt, jaxws-api.txt, jaxws.txt, kernel.txt, metadata.txt Add support for the JAX-WS 2.1 MR (JSR 224) which was recently released by Sun. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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
-
Key: AXIS2-3448
URL: https://issues.apache.org/jira/browse/AXIS2-3448
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: jaxws
Affects Versions: 1.4
Reporter: Nick Gallardo
Assignee: Nick Gallardo
Fix For: 1.4
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding
some new capabilities to the MTOM function. This will mostly leverage
existing infrastructure, but will also require some additional functionality
and coordination with the message model. A quick summary of the work to be
done:
1. [DONE] Update the metadata APIs to reflect whether or not the MTOM
configuration was found on the endpoint.
2. [DONE] Update the annotation processing code to pick off the @MTOM
annotation when included on an endpoint.
3. [DONE] Update the client creation code off of the ServiceDelegate to set
the appropriate values when the MTOMFeature is configured for client
instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are
a few examples of how this will be done.
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);
Service service = Service.create(myServiceWSDL, serviceName);
MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-3449 URL: https://issues.apache.org/jira/browse/AXIS2-3449 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo Priority: Blocker Fix For: 1.4 RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element. In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint. Here's a quick summary of the work to be done: 1. Update the metadata APIs to expose the RespectBinding data available 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation. 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature. 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property. 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input. This is described in the check that exists in the EndpointController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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+SimpleAxisServer with Simple JAXWS client --- Key: AXIS2-3547 URL: https://issues.apache.org/jira/browse/AXIS2-3547 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assignee: Bill Nagy Priority: Blocker Fix For: 1.4 Looks like the JAXWS Sessions scenarios need work. - JAXWS Service inside Tomcat/Axis2 should be able to participate in a transport session - JAXWS Service inside SimpleAxisServer/Axis2 should be able to participate in a transport session These services should be able to work with - Standalone Axis2/ADB client with sessions enabled. - JAXWS Client with sessions enabled. thanks., dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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-tabpanelfocusedCommentId=12574673#action_12574673 ] Nick Gallardo commented on AXIS2-3547: -- For the Tomcat scenario, if the endpoint calls getSession() or getSession(true) on the HttpServletRequest object, then it should trigger the servlet container to send back the necessary info. The question then becomes a question of whether or not the right info (cookie or URL re-write) is sent and consumed. I don't know how that endpoint mechanism aligns with the SimpleAxisServer though. JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client --- Key: AXIS2-3547 URL: https://issues.apache.org/jira/browse/AXIS2-3547 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assignee: Bill Nagy Fix For: 1.4 Looks like the JAXWS Sessions scenarios need work. - JAXWS Service inside Tomcat/Axis2 should be able to participate in a transport session - JAXWS Service inside SimpleAxisServer/Axis2 should be able to participate in a transport session These services should be able to work with - Standalone Axis2/ADB client with sessions enabled. - JAXWS Client with sessions enabled. thanks., dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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
-
Key: AXIS2-3448
URL: https://issues.apache.org/jira/browse/AXIS2-3448
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: jaxws
Affects Versions: 1.4
Reporter: Nick Gallardo
Assignee: Nick Gallardo
Fix For: 1.4
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding
some new capabilities to the MTOM function. This will mostly leverage
existing infrastructure, but will also require some additional functionality
and coordination with the message model. A quick summary of the work to be
done:
1. [DONE] Update the metadata APIs to reflect whether or not the MTOM
configuration was found on the endpoint.
2. [DONE] Update the annotation processing code to pick off the @MTOM
annotation when included on an endpoint.
3. [DONE] Update the client creation code off of the ServiceDelegate to set
the appropriate values when the MTOMFeature is configured for client
instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are
a few examples of how this will be done.
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);
Service service = Service.create(myServiceWSDL, serviceName);
MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-3558 URL: https://issues.apache.org/jira/browse/AXIS2-3558 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Fix For: 1.4 In JAXWS, it XMLUtils.createMessageFromValue(Object) is failing to copy mimeheaders, and thus they are not sent. See the test: org.apache.axis2.jaxws.provider.SoapMessageProviderTests.testProviderSourceXMLOnly() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-3449 URL: https://issues.apache.org/jira/browse/AXIS2-3449 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Fix For: 1.4 RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element. In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint. Here's a quick summary of the work to be done: 1. Update the metadata APIs to expose the RespectBinding data available 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation. 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature. 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property. 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input. This is described in the check that exists in the EndpointController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 reflect the annotations -- Key: AXIS2-2347 URL: https://issues.apache.org/jira/browse/AXIS2-2347 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.3 Reporter: Davanum Srinivas Assignee: Nick Gallardo Fix For: 1.4 Do we update the existing java2wsdl...how do we handle this situation? thanks, dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-3449 URL: https://issues.apache.org/jira/browse/AXIS2-3449 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element. In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint. Here's a quick summary of the work to be done: 1. Update the metadata APIs to expose the RespectBinding data available 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation. 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature. 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property. 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input. This is described in the check that exists in the EndpointController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 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 Reporter: Nick Gallardo Assignee: Nick Gallardo Attachments: patch.txt The current trunk cannot be compiled using a Java 6 JDK due to some API conflicts. We should be able to run existing JAX-WS applications with a Java 6 runtime. The Java 6 runtime has its own JAX-WS 2.1 implementation. When you try to compile the existing Axis2 JAX-WS module with that runtime, slight differences in the APIs cause compile errors. Here's what I see compiling against the latest trunk: C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\BindingImpl.java:[36,7] org.apache .axis2.jaxws.binding.BindingImpl is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\HTTPBinding.java:[23,7] org.apache .axis2.jaxws.binding.HTTPBinding is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\BindingProvider.java:[40,7] org.apache.axi s2.jaxws.BindingProvider is not abstract and does not override abstract method TgetEndpointReference(java.lang.ClassT ) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\spi\ServiceDelegate.java:[69,7] org.apache .axis2.jaxws.spi.ServiceDelegate is not abstract and does not override abstract method createDispatch(javax.xml.ws.Endpo intReference,javax.xml.bind.JAXBContext,javax.xml.ws.Service.Mode,javax.xml.ws.WebServiceFeature...) in javax.xml.ws.spi .ServiceDelegate C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\spi\Provider.java:[29,7] org.apache.axis2. jaxws.spi.Provider is not abstract and does not override abstract method createW3CEndpointReference(java.lang.String,jav ax.xml.namespace.QName,javax.xml.namespace.QName,java.util.Listorg.w3c.dom.Element,java.lang.String,java.util.Listorg .w3c.dom.Element) in javax.xml.ws.spi.Provider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\SOAPBinding.java:[44,7] org.apache .axis2.jaxws.binding.SOAPBinding is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\client\dispatch\XMLDispatch.java:[45,7] or g.apache.axis2.jaxws.client.dispatch.XMLDispatch is not abstract and does not override abstract method TgetEndpointRef erence(java.lang.ClassT) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\client\dispatch\JAXBDispatch.java:[47,7] o rg.apache.axis2.jaxws.client.dispatch.JAXBDispatch is not abstract and does not override abstract method TgetEndpointR eference(java.lang.ClassT) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\context\WebServiceContextImpl.java:[29,7] org.apache.axis2.jaxws.context.WebServiceContextImpl is not abstract and does not override abstract method TgetEndpoin tReference(java.lang.ClassT,org.w3c.dom.Element...) in javax.xml.ws.WebServiceContext C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\server\endpoint\EndpointImpl.java:[43,7] o rg.apache.axis2.jaxws.server.endpoint.EndpointImpl is not abstract and does not override abstract method TgetEndpointR eference(java.lang.ClassT,org.w3c.dom.Element...) in javax.xml.ws.Endpoint This can be fixed with some simple API changes. I will provide a patch that includes the necessary changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 new capabilities to the MTOM function. This will mostly leverage existing
infrastructure, but will also require some additional functionality and
coordination with the message model. A quick summary of the work to be done:
1. [DONE] Update the metadata APIs to reflect whether or not the MTOM
configuration was found on the endpoint.
2. [DONE] Update the annotation processing code to pick off the @MTOM
annotation when included on an endpoint.
3. [DONE] Update the client creation code off of the ServiceDelegate to set the
appropriate values when the MTOMFeature is configured for client instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are a
few examples of how this will be done.
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);
Service service = Service.create(myServiceWSDL, serviceName);
MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);
was:
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding
some new capabilities to the MTOM function. This will mostly leverage existing
infrastructure, but will also require some additional functionality and
coordination with the message model. A quick summary of the work to be done:
1. Update the metadata APIs to reflect whether or not the MTOM configuration
was found on the endpoint.
2. Update the annotation processing code to pick off the @MTOM annotation when
included on an endpoint.
3. Update the client creation code off of the ServiceDelegate to set the
appropriate values when the MTOMFeature is configured for client instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are a
few examples of how this will be done.
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);
Service service = Service.create(myServiceWSDL, serviceName);
MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);
Fix Version/s: 1.4
Marking completed items.
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
Reporter: Nick Gallardo
Assignee: Nick Gallardo
Fix For: 1.4
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding
some new capabilities to the MTOM function. This will mostly leverage
existing infrastructure, but will also require some additional functionality
and coordination with the message model. A quick summary of the work to be
done:
1. [DONE] Update the metadata APIs to reflect whether or not the MTOM
configuration was found on the endpoint.
2. [DONE] Update the annotation processing code to pick off the @MTOM
annotation when included on an endpoint.
3. [DONE] Update the client creation code off of the ServiceDelegate to set
the appropriate values when the MTOMFeature is configured for client
instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are
a few examples of how this will
[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 MTOMFeature
-
Key: AXIS2-3448
URL: https://issues.apache.org/jira/browse/AXIS2-3448
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: jaxws
Affects Versions: 1.4
Reporter: Nick Gallardo
Assignee: Nick Gallardo
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding
some new capabilities to the MTOM function. This will mostly leverage
existing infrastructure, but will also require some additional functionality
and coordination with the message model. A quick summary of the work to be
done:
1. [DONE] Update the metadata APIs to reflect whether or not the MTOM
configuration was found on the endpoint.
2. [DONE] Update the annotation processing code to pick off the @MTOM
annotation when included on an endpoint.
3. [DONE] Update the client creation code off of the ServiceDelegate to set
the appropriate values when the MTOMFeature is configured for client
instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are
a few examples of how this will be done.
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);
Service service = Service.create(myServiceWSDL, serviceName);
MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[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-tabpanelfocusedCommentId=12562104#action_12562104 ] Nick Gallardo commented on AXIS2-2722: -- Here's a quick write up of the changes in the jaxws/jaxws-api/metadata modules. modules/jaxws --- org.apache.axis2.jaxws.addressing - added implementations of JAX-WS EndpointReference APIs and associated factories/utils. org.apache.axis2.jaxws.binding - integrated JAX-WS 2.1 WebServiceFeature mechanism into generic Binding implementation and SOAPBinding. org.apache.axis2.jaxws.client.config - introduced set of known configurators for JAX-WS 2.1 WebServiceFeature classes. org.apache.axis2.jaxws.context - added in mechanism for getting WS-A reference params setup correctly on the JAX-WS MessageContext. Also added EPR accessibility from the injected WebServiceContext org.apache.axis2.jaxws.server - add JAX-WS EPR to EndpointController org.apache.axis2.jaxws.spi - added new 2.1 method signatures to the Provider/ServiceDelegate implementations. org.apache.axis2.jaxws - added support for retreiving the client side EPR from the BindingProvider (Proxy or Dispatch) client. modules/jaxws-api --- Several changes to add in the new APIs defined by JAX-WS 2.1 modules/metadata --- org.apache.axis2.jaxws.addressing - new objects to support the SubmissionAddressingFeature extension org.apache.axis2.jaxws.description.* - changes to support processing WebServiceFeatureAnnotation instances found on endpoints org.apache.axis2.jaxws.feature - new server framework for WebServiceFeature elements org.apache.axis2.jaxws.server.config - new configurator implementations that support the know WebServiceFeature set Support for JAX-WS 2.1 -- Key: AXIS2-2722 URL: https://issues.apache.org/jira/browse/AXIS2-2722 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Reporter: Brian DePradine Assignee: Brian DePradine Attachments: addressing.txt, jaxws-api.txt, jaxws.txt, kernel.txt, metadata.txt Add support for the JAX-WS 2.1 MR (JSR 224) which was recently released by Sun. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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-tabpanelfocusedCommentId=12559519#action_12559519 ] Nick Gallardo commented on AXIS2-3449: -- It does look to be a combination of the two. Can you think of any other wsdl:binding extensions beyond addressing stuff that we would need to be aware of? 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 Feature Components: jaxws Reporter: Nick Gallardo RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element. In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint. Here's a quick summary of the work to be done: 1. Update the metadata APIs to expose the RespectBinding data available 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation. 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature. 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property. 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input. This is described in the check that exists in the EndpointController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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
Reporter: Nick Gallardo
Assignee: Nick Gallardo
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding
some new capabilities to the MTOM function. This will mostly leverage existing
infrastructure, but will also require some additional functionality and
coordination with the message model. A quick summary of the work to be done:
1. Update the metadata APIs to reflect whether or not the MTOM configuration
was found on the endpoint.
2. Update the annotation processing code to pick off the @MTOM annotation when
included on an endpoint.
3. Update the client creation code off of the ServiceDelegate to set the
appropriate values when the MTOMFeature is configured for client instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are a
few examples of how this will be done.
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);
Service service = Service.create(myServiceWSDL, serviceName);
MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[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
URL: https://issues.apache.org/jira/browse/AXIS2-3448
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: jaxws
Reporter: Nick Gallardo
Assignee: Nick Gallardo
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding
some new capabilities to the MTOM function. This will mostly leverage
existing infrastructure, but will also require some additional functionality
and coordination with the message model. A quick summary of the work to be
done:
1. Update the metadata APIs to reflect whether or not the MTOM configuration
was found on the endpoint.
2. Update the annotation processing code to pick off the @MTOM annotation
when included on an endpoint.
3. Update the client creation code off of the ServiceDelegate to set the
appropriate values when the MTOMFeature is configured for client instances.
4. Change the marshalling code to read the threshold and toggle MTOM when
appropriate.
Here are some examples of the new ways that MTOM can be configured.
Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
...
}
After:
@WebService
@MTOM
public class MyServiceImpl {
...
}
Additionally, the threshold is configured as such.
@WebService
@MTOM(enabled=true, threshold=2000)
public class MyServiceImpl {
...
}
On the client side, the configuration changes a little bit as well. Here are
a few examples of how this will be done.
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);
Service service = Service.create(myServiceWSDL, serviceName);
MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[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 Feature Components: jaxws Reporter: Nick Gallardo RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element. In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint. Here's a quick summary of the work to be done: 1. Update the metadata APIs to expose the RespectBinding data available 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation. 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature. 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property. 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input. This is described in the check that exists in the EndpointController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Reporter: Nick Gallardo Assignee: Nick Gallardo The current trunk cannot be compiled using a Java 6 JDK due to some API conflicts. We should be able to run existing JAX-WS applications with a Java 6 runtime. The Java 6 runtime has its own JAX-WS 2.1 implementation. When you try to compile the existing Axis2 JAX-WS module with that runtime, slight differences in the APIs cause compile errors. Here's what I see compiling against the latest trunk: C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\BindingImpl.java:[36,7] org.apache .axis2.jaxws.binding.BindingImpl is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\HTTPBinding.java:[23,7] org.apache .axis2.jaxws.binding.HTTPBinding is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\BindingProvider.java:[40,7] org.apache.axi s2.jaxws.BindingProvider is not abstract and does not override abstract method TgetEndpointReference(java.lang.ClassT ) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\spi\ServiceDelegate.java:[69,7] org.apache .axis2.jaxws.spi.ServiceDelegate is not abstract and does not override abstract method createDispatch(javax.xml.ws.Endpo intReference,javax.xml.bind.JAXBContext,javax.xml.ws.Service.Mode,javax.xml.ws.WebServiceFeature...) in javax.xml.ws.spi .ServiceDelegate C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\spi\Provider.java:[29,7] org.apache.axis2. jaxws.spi.Provider is not abstract and does not override abstract method createW3CEndpointReference(java.lang.String,jav ax.xml.namespace.QName,javax.xml.namespace.QName,java.util.Listorg.w3c.dom.Element,java.lang.String,java.util.Listorg .w3c.dom.Element) in javax.xml.ws.spi.Provider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\SOAPBinding.java:[44,7] org.apache .axis2.jaxws.binding.SOAPBinding is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\client\dispatch\XMLDispatch.java:[45,7] or g.apache.axis2.jaxws.client.dispatch.XMLDispatch is not abstract and does not override abstract method TgetEndpointRef erence(java.lang.ClassT) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\client\dispatch\JAXBDispatch.java:[47,7] o rg.apache.axis2.jaxws.client.dispatch.JAXBDispatch is not abstract and does not override abstract method TgetEndpointR eference(java.lang.ClassT) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\context\WebServiceContextImpl.java:[29,7] org.apache.axis2.jaxws.context.WebServiceContextImpl is not abstract and does not override abstract method TgetEndpoin tReference(java.lang.ClassT,org.w3c.dom.Element...) in javax.xml.ws.WebServiceContext C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\server\endpoint\EndpointImpl.java:[43,7] o rg.apache.axis2.jaxws.server.endpoint.EndpointImpl is not abstract and does not override abstract method TgetEndpointR eference(java.lang.ClassT,org.w3c.dom.Element...) in javax.xml.ws.Endpoint This can be fixed with some simple API changes. I will provide a patch that includes the necessary changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 the tests though. 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 Reporter: Nick Gallardo Assignee: Nick Gallardo Attachments: patch.txt The current trunk cannot be compiled using a Java 6 JDK due to some API conflicts. We should be able to run existing JAX-WS applications with a Java 6 runtime. The Java 6 runtime has its own JAX-WS 2.1 implementation. When you try to compile the existing Axis2 JAX-WS module with that runtime, slight differences in the APIs cause compile errors. Here's what I see compiling against the latest trunk: C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\BindingImpl.java:[36,7] org.apache .axis2.jaxws.binding.BindingImpl is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\HTTPBinding.java:[23,7] org.apache .axis2.jaxws.binding.HTTPBinding is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\BindingProvider.java:[40,7] org.apache.axi s2.jaxws.BindingProvider is not abstract and does not override abstract method TgetEndpointReference(java.lang.ClassT ) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\spi\ServiceDelegate.java:[69,7] org.apache .axis2.jaxws.spi.ServiceDelegate is not abstract and does not override abstract method createDispatch(javax.xml.ws.Endpo intReference,javax.xml.bind.JAXBContext,javax.xml.ws.Service.Mode,javax.xml.ws.WebServiceFeature...) in javax.xml.ws.spi .ServiceDelegate C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\spi\Provider.java:[29,7] org.apache.axis2. jaxws.spi.Provider is not abstract and does not override abstract method createW3CEndpointReference(java.lang.String,jav ax.xml.namespace.QName,javax.xml.namespace.QName,java.util.Listorg.w3c.dom.Element,java.lang.String,java.util.Listorg .w3c.dom.Element) in javax.xml.ws.spi.Provider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\binding\SOAPBinding.java:[44,7] org.apache .axis2.jaxws.binding.SOAPBinding is not abstract and does not override abstract method getBindingID() in javax.xml.ws.Bi nding C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\client\dispatch\XMLDispatch.java:[45,7] or g.apache.axis2.jaxws.client.dispatch.XMLDispatch is not abstract and does not override abstract method TgetEndpointRef erence(java.lang.ClassT) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\client\dispatch\JAXBDispatch.java:[47,7] o rg.apache.axis2.jaxws.client.dispatch.JAXBDispatch is not abstract and does not override abstract method TgetEndpointR eference(java.lang.ClassT) in javax.xml.ws.BindingProvider C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\context\WebServiceContextImpl.java:[29,7] org.apache.axis2.jaxws.context.WebServiceContextImpl is not abstract and does not override abstract method TgetEndpoin tReference(java.lang.ClassT,org.w3c.dom.Element...) in javax.xml.ws.WebServiceContext C:\work\apps\eclipse\workspace\axis2\modules\jaxws\src\org\apache\axis2\jaxws\server\endpoint\EndpointImpl.java:[43,7] o rg.apache.axis2.jaxws.server.endpoint.EndpointImpl is not abstract and does not override abstract method TgetEndpointR eference(java.lang.ClassT,org.w3c.dom.Element...) in javax.xml.ws.Endpoint This can be fixed with some simple API changes. I will provide a patch that includes the necessary changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 --- Key: AXIS2-3403 URL: https://issues.apache.org/jira/browse/AXIS2-3403 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo Attachments: patch.txt The AxisInvocationController throws an exception when a user tries to specify a username and no password for the BASIC_AUTH configuration. This is a valid scenario and should be allowed to pass through. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-3402 URL: https://issues.apache.org/jira/browse/AXIS2-3402 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo Attachments: patch.txt If someone has defined a swaRef attachment that is nested within an element, we will do the correct processing and include the swaRef href=blah/ element when writing out to the wire. The problem is that we don't include the actual attachment data for the individual MIME parts. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-3402 URL: https://issues.apache.org/jira/browse/AXIS2-3402 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo Attachments: patch.txt If someone has defined a swaRef attachment that is nested within an element, we will do the correct processing and include the swaRef href=blah/ element when writing out to the wire. The problem is that we don't include the actual attachment data for the individual MIME parts. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo If someone has defined a swaRef attachment that is nested within an element, we will do the correct processing and include the swaRef href=blah/ element when writing out to the wire. The problem is that we don't include the actual attachment data for the individual MIME parts. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 password --- Key: AXIS2-3403 URL: https://issues.apache.org/jira/browse/AXIS2-3403 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo Attachments: patch.txt The AxisInvocationController throws an exception when a user tries to specify a username and no password for the BASIC_AUTH configuration. This is a valid scenario and should be allowed to pass through. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 constructs that we should be passing in. Take a look at javax.xml.ws.handler.MessageContext. In there, the following properties are defined: public static final String WSDL_DESCRIPTION = javax.xml.ws.wsdl.description; public static final String WSDL_SERVICE = javax.xml.ws.wsdl.service; public static final String WSDL_PORT = javax.xml.ws.wsdl.port; public static final String WSDL_INTERFACE = javax.xml.ws.wsdl.interface; public static final String WSDL_OPERATION = javax.xml.ws.wsdl.operation; Are you seeing a scenario where we're not setting values for those properties? When WSDL exists, set wsdl properties for provider -- Key: AXIS2-3305 URL: https://issues.apache.org/jira/browse/AXIS2-3305 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Roy A. Wood Jr. Priority: Minor To support WS-Notification, add functionality to supply provider-based endpoints with a context property for wsdl operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Components: jaxws Affects Versions: 1.4 Reporter: Nick Gallardo Assignee: Nick Gallardo The AxisInvocationController throws an exception when a user tries to specify a username and no password for the BASIC_AUTH configuration. This is a valid scenario and should be allowed to pass through. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 service invocation does not return XML response on a SOAP fault Key: AXIS2-2125 URL: https://issues.apache.org/jira/browse/AXIS2-2125 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Environment: All Reporter: Jeff Faath Assignee: Nick Gallardo Priority: Minor When using the asynchronous sendReceiveNonBlocking call to invoke a web service, there is no way to retrieve the XML response if a SOAP Fault occurs. The XML response is always returned on the blocking invocation methods. I believe the same should hold for the asynchronous calls - there should always be a way to retreive the raw XML response. I sifted through the source code, in particular the NonBlockingInvocationWorker class (I'm looking at the one in OutInAxisOperation). The block of code that appears to be the problem looks something like this (in the run() method of NonBlockingInvocationWorker): if (body.hasFault()) ..call the callback's onError method else ..call the callback's onComplete method It seems the else clause should be eliminated and onComplete should always be called whether it is a SOAP Fault or not. This would result in both onError() and onComplete() being called in the case of a SOAP Fault, but I don't see that as being a big problem as the client can deal with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 style generated artifacts. JAX-WS 2.0 support for Apache Axis2 WSDL2Java Code Generator Key: AXIS2-2920 URL: https://issues.apache.org/jira/browse/AXIS2-2920 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: codegen Affects Versions: 1.3 Reporter: Sameera Jayasoma Assignee: Amila Chinthaka Suriarachchi Attachments: jaxws_patch_08_07_2007.txt Hi all, Herewith I have attached a patch which will enable WSDL2Java to generate code based on JAX-WS 2.0 standard. I would like to mark this as experimental because there are several thins to be completed.. 1. Improve the usage of annotations. 2. Support for wrapper style mapping of method parameters. Once these things are completed this feature can be put into the actual usage. I would like to make a humble request to you all to use this feature and let me know your comments. Sameera jayasoma. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 AttachmentDescription objects in the JAX-WS Metadata layer - Key: AXIS2-2817 URL: https://issues.apache.org/jira/browse/AXIS2-2817 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.3 Reporter: Dustin Amrhein Assignee: Nick Gallardo Fix For: 1.3 The JAX-WS metadata layer needs to create AttachmentDescription objects if the WSDL indicates that the input or output message contains attachments. This will be used later on by the marshalling code to determine the correct information to marshall/demarshall. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 property is set --- Key: AXIS2-2895 URL: https://issues.apache.org/jira/browse/AXIS2-2895 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Nick Gallardo Priority: Minor Attachments: patch_65250.txt Currently, it is possible to have the USE_ASYNC_MEP property setting on a sync or oneway invocation. This will not be allowed past the AxisInvocationController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 not include a sync (two-way) invoke. For one-way invokes, my understanding is that there shouldn't be a reason to setup a listener and save off a message context for a response that will never be returned.You'd also have to setup an Axis2 callback instance that will never be called either. The patch only reflects the one-way portion, which should be what's mentioned in the earlier comments. Do you envision a scenario where that would be required? Thanks, Nick Disallow sync/oneway invocations when async property is set --- Key: AXIS2-2895 URL: https://issues.apache.org/jira/browse/AXIS2-2895 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Nick Gallardo Priority: Minor Attachments: patch_65250.txt Currently, it is possible to have the USE_ASYNC_MEP property setting on a sync or oneway invocation. This will not be allowed past the AxisInvocationController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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. Disallow sync/oneway invocations when async property is set --- Key: AXIS2-2895 URL: https://issues.apache.org/jira/browse/AXIS2-2895 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Nick Gallardo Priority: Minor Attachments: patch_65250.txt Currently, it is possible to have the USE_ASYNC_MEP property setting on a sync or oneway invocation. This will not be allowed past the AxisInvocationController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 set --- Key: AXIS2-2895 URL: https://issues.apache.org/jira/browse/AXIS2-2895 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Roy A. Wood Jr. Assignee: Nick Gallardo Priority: Minor Attachments: patch_65250.txt Currently, it is possible to have the USE_ASYNC_MEP property setting on a sync or oneway invocation. This will not be allowed past the AxisInvocationController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Key: AXIS2-2548 URL: https://issues.apache.org/jira/browse/AXIS2-2548 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Assignee: Nick Gallardo This is most likely an axiom problem, but opened against JAXWS until such determination is made. When I enable the AddNumbersHandlerTests.testAddNumbersWithFault, I get: javax.xml.ws.soap.SOAPFaultException: java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMSourcedElementImpl incompatible with org.apache.axiom.soap.SOAPFault at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1057) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:811) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedPlusMethodMarshaller.demarshalFaultResponse(DocLitWrappedPlusMethodMarshaller.java:725) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:394) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:369) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:291) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:141) at $Proxy19.addNumbersHandler(Unknown Source) at org.apache.axis2.jaxws.sample.AddNumbersHandlerTests.testAddNumbersHandlerWithFault(AddNumbersHandlerTests.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) I believe Nick has worked on this code before and can address it. If not, I'll take a look. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2539 URL: https://issues.apache.org/jira/browse/AXIS2-2539 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assignee: Nick Gallardo This JIRA will be used for adding more support to the JAX-WS dynamic Endpoint API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 --- Key: AXIS2-2832 URL: https://issues.apache.org/jira/browse/AXIS2-2832 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: nightly Reporter: Lin Sun Assignee: Nick Gallardo Fix For: nightly Attachments: Axis2-2832.patch Hi, I noticed that this org.apache.axis2.jaxws.handler.ProtectedMessageContext has been removed today, which has a public constructor and we use it in geronimo. And I saw a new file called basemessagecontext is provided to implment javax.xml.ws.handler.MessageContext. Can you make the constructor public (instead of protected)? Thanks. Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 directly, but rather as an abstract context that is extended by either the SoapMessageConext or LogicalMessageContext, such that the end object that's being used is really the javax.xml.ws.handler.LogicalMessageContext or the javax.xml.ws.handler.soap.SOAPMessageContext. Are those the objects that you were consuming, or did you really need a base javax.xml.ws.handler.MessageContext instance? provide a public constructor for basemessagecontext --- Key: AXIS2-2832 URL: https://issues.apache.org/jira/browse/AXIS2-2832 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: nightly Reporter: Lin Sun Assignee: Nick Gallardo Fix For: nightly Attachments: Axis2-2832.patch Hi, I noticed that this org.apache.axis2.jaxws.handler.ProtectedMessageContext has been removed today, which has a public constructor and we use it in geronimo. And I saw a new file called basemessagecontext is provided to implment javax.xml.ws.handler.MessageContext. Can you make the constructor public (instead of protected)? Thanks. Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-2836 URL: https://issues.apache.org/jira/browse/AXIS2-2836 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: nightly Reporter: Dustin Amrhein Assignee: Nick Gallardo Fix For: nightly Attachments: patch.txt The JAX-WS layer should provide a way to allow for the registration of a thread excecutor factory. This executor factory will be used by the ServiceDelegate to obtain an instance of an Executor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 were having to do between SAAJ and Axiom for the JAX-WS handler support. When a fault is stored in a SOAP Axiom structure, it is always represented as a SOAP 1.2 fault. So, if I walked that and tried to build a SOAP 1.1 fault, I'd be creating elements with the wrong QName. For now, the solution is to serialize the whole structure and then read it back in. That's horribly non-performant, but at least a step to get us going. Once I get the patch integrated, I'll build a small sample that shows what I'm talking about and we can see how to solve that at the Axiom level. Handler test with fault causes exception Key: AXIS2-2548 URL: https://issues.apache.org/jira/browse/AXIS2-2548 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Assignee: Nick Gallardo This is most likely an axiom problem, but opened against JAXWS until such determination is made. When I enable the AddNumbersHandlerTests.testAddNumbersWithFault, I get: javax.xml.ws.soap.SOAPFaultException: java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMSourcedElementImpl incompatible with org.apache.axiom.soap.SOAPFault at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1057) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:811) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedPlusMethodMarshaller.demarshalFaultResponse(DocLitWrappedPlusMethodMarshaller.java:725) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:394) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:369) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:291) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:141) at $Proxy19.addNumbersHandler(Unknown Source) at org.apache.axis2.jaxws.sample.AddNumbersHandlerTests.testAddNumbersHandlerWithFault(AddNumbersHandlerTests.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) I believe Nick has worked on this code before and can address it. If not, I'll take a look. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo We need an implementation of the APIs that are used in a LogicalHandler flow. I have some of this completed already and will be contributing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo the migrator is being called from the Dispatch, but not the proxy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 --- Key: AXIS2-2537 URL: https://issues.apache.org/jira/browse/AXIS2-2537 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo the migrator is being called from the Dispatch, but not the proxy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 for use in handlers -- Key: AXIS2-2532 URL: https://issues.apache.org/jira/browse/AXIS2-2532 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo We need an implementation of the APIs that are used in a LogicalHandler flow. I have some of this completed already and will be contributing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo The JAXWS code is not setting the EndpointDescription on the MessageContext in certain scenarios. I have a patch that addresses this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 MessageContext -- Key: AXIS2-2535 URL: https://issues.apache.org/jira/browse/AXIS2-2535 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo The JAXWS code is not setting the EndpointDescription on the MessageContext in certain scenarios. I have a patch that addresses this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Reporter: Nick Gallardo Assigned To: Nick Gallardo This JIRA will be used for adding more support to the JAX-WS dynamic Endpoint API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 they cause issues with the SAAJ implementation. Separate JIRAs will be opened for those. @HandlerChain annotation is not picked up - Key: AXIS2-2218 URL: https://issues.apache.org/jira/browse/AXIS2-2218 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Davanum Srinivas Assigned To: Nick Gallardo Priority: Blocker When i deploy a service using JAXWSMessageReceiver that has @HandlerChain annotation. the handlers are not picked up nor invoked. There is a TODO item in the EndpointInterfaceDescriptionImpl.java (line 198) as follows. I can also see a JavaClassToDBCConverter that has a attachHandlerChainAnnotation which can help. But the only location the JavaClassToDBCConverter class is instantiated is in a test case... //TODO: Need to process the other annotations that can exist, on the server side // and at the class level. // They are, as follows: // HandlerChain (181) // SoapBinding (181) // WebServiceRefAnnot (List) (JAXWS) // BindingTypeAnnot (JAXWS Sec. 7.8 -- Used to set either the AS.endpoint, or AS.SoapNSUri) // WebServiceContextAnnot (JAXWS via injection) thanks, dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 they cause issues with the SAAJ implementation. Separate JIRAs will be opened for those. 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 Reporter: Nick Gallardo Assigned To: Nick Gallardo We need a sample/test case for the handler chain integration that will run in the automated bucket. For now, this will be a simple ProtocolHandler sample, but will need to be upgraded to include LogicalHandlers as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 this morning? RPCProxyTests broke again. -- Key: AXIS2-2407 URL: https://issues.apache.org/jira/browse/AXIS2-2407 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Davanum Srinivas Keith has commented out the RPCProxyTests. http://svn.apache.org/viewvc?view=revrevision=522768 Keith, Could you please comment on why the test broke? Can someone please help fix it? thanks, dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo The JAXWS MessageContext should hold a reference to the EndpointDescription, rather than the ServiceDescription. This JIRA will be used to change all of the places where that is referenced. This is also needed by AXIS2-2218 for integration of the handlers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2396 URL: https://issues.apache.org/jira/browse/AXIS2-2396 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: patch-2396.txt The JAXWS MessageContext should hold a reference to the EndpointDescription, rather than the ServiceDescription. This JIRA will be used to change all of the places where that is referenced. This is also needed by AXIS2-2218 for integration of the handlers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2317 URL: https://issues.apache.org/jira/browse/AXIS2-2317 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: patch-migrator-api.txt, patch-migrator-impl.txt When the response comes back (in either a Dispatch or Proxy) there are a certain set of properties that should be available in the response context of the BindingProvider. This JIRA is to address this issue by introducing a mechanism to make the right properties available to the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2317 URL: https://issues.apache.org/jira/browse/AXIS2-2317 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: patch-migrator-api.txt, patch-migrator-impl.txt When the response comes back (in either a Dispatch or Proxy) there are a certain set of properties that should be available in the response context of the BindingProvider. This JIRA is to address this issue by introducing a mechanism to make the right properties available to the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2396 URL: https://issues.apache.org/jira/browse/AXIS2-2396 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: patch-2396.txt The JAXWS MessageContext should hold a reference to the EndpointDescription, rather than the ServiceDescription. This JIRA will be used to change all of the places where that is referenced. This is also needed by AXIS2-2218 for integration of the handlers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Reporter: Nick Gallardo Assigned To: Nick Gallardo We need a sample/test case for the handler chain integration that will run in the automated bucket. For now, this will be a simple ProtocolHandler sample, but will need to be upgraded to include LogicalHandlers as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 xml file. Add metadata layer annotation processing Key: AXIS2-2377 URL: https://issues.apache.org/jira/browse/AXIS2-2377 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Reporter: Roy A. Wood Jr. Assigned To: Nick Gallardo Priority: Minor Attachments: patch-2377.txt Within the metadata layer, we added processing of the @HandlerAnnotation. This consists of adding a new method EndpointDescriptionImp.getHandlerChain that ultimately reads the xml file from the annotation and converts it into a JAXB object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Key: AXIS2-2377 URL: https://issues.apache.org/jira/browse/AXIS2-2377 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Reporter: Roy A. Wood Jr. Assigned To: Nick Gallardo Priority: Minor Attachments: patch-2377.txt Within the metadata layer, we added processing of the @HandlerAnnotation. This consists of adding a new method EndpointDescriptionImp.getHandlerChain that ultimately reads the xml file from the annotation and converts it into a JAXB object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Key: AXIS2-2377 URL: https://issues.apache.org/jira/browse/AXIS2-2377 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Reporter: Roy A. Wood Jr. Assigned To: Nick Gallardo Priority: Minor Within the metadata layer, we added processing of the @HandlerAnnotation. This consists of adding a new method EndpointDescriptionImp.getHandlerChain that ultimately reads the xml file from the annotation and converts it into a JAXB object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 [1]. The scenario here is an annotated class that's to be deployed as a JAX-WS service without a WSDL. Since there's no WSDL, we need to generate one somehow for a ?WSDL request. One way to do this would be to use the metadata APIs (org.apache.axis2.jaxws.description) to configure your service, then you can leverage the WsdlGenerator plugin at make a call to whatever JSR181/JAX-WS aware WSDL generation tool you look (like wsgen for instance). Changing the existing Java2WSDL to handle this is a huge amount of work. That's basically signing up for creating a complete 181/JAX-WS aware generation tool, which is more that I think anyone wants to do right now. Using that you could configure your service like so: // The ServiceDescription *should* have all the required service metadata ServiceDescription serviceDesc = DescriptionFactory.createServiceDescription(MyServiceImpl.class); // Get the AxisService to add it to the ConfigurationContext so the request can be // handled appropriately AxisService service = (serviceDesc.getEndpointDescriptions()[0] ).getAxisService(); // Get the associated WSDL Definition(s). In some cases, there might be more than one WSDL document // associated with a service endpoint (example: WSDL docs with imports) ListWSDLDefinition wsdls = servicesDesc.getWSDLDefinitions(); So, in this case, you would need to provide an implementation of the WsdlGenerator interface. With that, you could setup the appropriate classpath and make a call out to your favorite WSDL gen tool. Note, the last call listed in the sample (getWSDLDefinitions()) doesn't yet exist. Most of the code needed for this is available, but some slight restructuring of how the metadata APIs return that will be required. We can use this JIRA to track these changes. [1] - https://issues.apache.org/jira/browse/GERONIMO-2988 When deploying using JAXWSMessageReceiver, the dynamic wsdl (?wsdl) should reflect the annotations -- Key: AXIS2-2347 URL: https://issues.apache.org/jira/browse/AXIS2-2347 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assigned To: Nick Gallardo Do we update the existing java2wsdl...how do we handle this situation? thanks, dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2317 URL: https://issues.apache.org/jira/browse/AXIS2-2317 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: patch-migrator-api.txt When the response comes back (in either a Dispatch or Proxy) there are a certain set of properties that should be available in the response context of the BindingProvider. This JIRA is to address this issue by introducing a mechanism to make the right properties available to the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Reporter: Nick Gallardo Assigned To: Nick Gallardo When the response comes back (in either a Dispatch or Proxy) there are a certain set of properties that should be available in the response context of the BindingProvider. This JIRA is to address this issue by introducing a mechanism to make the right properties available to the user. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Key: AXIS2-2232 URL: https://issues.apache.org/jira/browse/AXIS2-2232 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Davanum Srinivas Assigned To: Nick Gallardo Priority: Critical Folks, Just noticed that everywhere, the TCCL is used to load classes. So i was not able to drop classes into the service directory and get them to load up. WEB-INF/services/MyServices/my/package/MyClass.class I had to place MyClass.clas in WEB-INF/classes to get the JAXWSMessageReceiver to pick it up. Is there a reason for not using AxisService's class loader? thanks, dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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. Error in handling async response when executor service is shutdown -- Key: AXIS2-2170 URL: https://issues.apache.org/jira/browse/AXIS2-2170 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Ann Robinson Assigned To: Nick Gallardo Attachments: patch.txt, patch_update.txt When the ExecutorService associated with a service is shutdownNow(), the ExecutorService will attempt to stop all actively executing tasks, halt the processing of waiting tasks, and refuse to accept new tasks. However, a client is not getting the appropriate notification that asynchronous requests/responses can not proceed. The solution needs to cover: (a) When the asynchronous response is received in the CallbackFuture, the Executor is normally given the task to execute. If the Executor throws an exception, then the task needs to be cancelled. Since the Executor won't process the response task, the callback handler doesn't get the response or an error. But, cancelling the task will let the client check the Future object and will get a cancellation exception. (b) When the client submits a request with an asynchronous response and the ExecutorService is shutdown, then JAXWS needs to refuse the request and throw an exception back to the client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 response when executor service is shutdown -- Key: AXIS2-2170 URL: https://issues.apache.org/jira/browse/AXIS2-2170 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Ann Robinson Assigned To: Nick Gallardo Attachments: patch.txt, patch_update.txt When the ExecutorService associated with a service is shutdownNow(), the ExecutorService will attempt to stop all actively executing tasks, halt the processing of waiting tasks, and refuse to accept new tasks. However, a client is not getting the appropriate notification that asynchronous requests/responses can not proceed. The solution needs to cover: (a) When the asynchronous response is received in the CallbackFuture, the Executor is normally given the task to execute. If the Executor throws an exception, then the task needs to be cancelled. Since the Executor won't process the response task, the callback handler doesn't get the response or an error. But, cancelling the task will let the client check the Future object and will get a cancellation exception. (b) When the client submits a request with an asynchronous response and the ExecutorService is shutdown, then JAXWS needs to refuse the request and throw an exception back to the client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 wrapper class - Key: AXIS2-2181 URL: https://issues.apache.org/jira/browse/AXIS2-2181 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt The DescriptionUtils class in the JAX-WS metadata layer should return null if it can't load a wrapper class. This will signify to any calling code that the cache has not been created and the wrapper classes still need to be found and loaded. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 class should return null if it cannot load wrapper class - Key: AXIS2-2181 URL: https://issues.apache.org/jira/browse/AXIS2-2181 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt The DescriptionUtils class in the JAX-WS metadata layer should return null if it can't load a wrapper class. This will signify to any calling code that the cache has not been created and the wrapper classes still need to be found and loaded. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 this in revision: 507681 Remove unnecessary log information from JAXBUtils class --- Key: AXIS2-2160 URL: https://issues.apache.org/jira/browse/AXIS2-2160 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Lasantha Ranaweera Assigned To: Nick Gallardo Priority: Minor Attachments: AXIS2-2160.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-2171 URL: https://issues.apache.org/jira/browse/AXIS2-2171 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Assigned To: Nick Gallardo Attachments: patch.txt, patch_20070214.txt, patch_20070214_b.txt JAXWS absorbs async exceptions This patch fixes the async case with no AsyncHandler (callback), but does not fix the Future case. Please see patch, and my comments in AxisInvocationController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 a fix for WSCOMMONS-166, which isn't available yet. Committed the patch in revision 507692. Thanks Mike! JAXWS absorbs async exceptions -- Key: AXIS2-2171 URL: https://issues.apache.org/jira/browse/AXIS2-2171 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Assigned To: Nick Gallardo Attachments: patch.txt, patch_20070214.txt, patch_20070214_b.txt JAXWS absorbs async exceptions This patch fixes the async case with no AsyncHandler (callback), but does not fix the Future case. Please see patch, and my comments in AxisInvocationController. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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. Key: AXIS2-2169 URL: https://issues.apache.org/jira/browse/AXIS2-2169 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt JAX-WS MetaData layer should use 2006 MEP URI constants. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 MEP URI constants. Key: AXIS2-2169 URL: https://issues.apache.org/jira/browse/AXIS2-2169 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt JAX-WS MetaData layer should use 2006 MEP URI constants. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 shutdown -- Key: AXIS2-2170 URL: https://issues.apache.org/jira/browse/AXIS2-2170 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Ann Robinson Assigned To: Nick Gallardo Attachments: patch.txt When the ExecutorService associated with a service is shutdownNow(), the ExecutorService will attempt to stop all actively executing tasks, halt the processing of waiting tasks, and refuse to accept new tasks. However, a client is not getting the appropriate notification that asynchronous requests/responses can not proceed. The solution needs to cover: (a) When the asynchronous response is received in the CallbackFuture, the Executor is normally given the task to execute. If the Executor throws an exception, then the task needs to be cancelled. Since the Executor won't process the response task, the callback handler doesn't get the response or an error. But, cancelling the task will let the client check the Future object and will get a cancellation exception. (b) When the client submits a request with an asynchronous response and the ExecutorService is shutdown, then JAXWS needs to refuse the request and throw an exception back to the client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 when executor service is shutdown -- Key: AXIS2-2170 URL: https://issues.apache.org/jira/browse/AXIS2-2170 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Ann Robinson Assigned To: Nick Gallardo Attachments: patch.txt When the ExecutorService associated with a service is shutdownNow(), the ExecutorService will attempt to stop all actively executing tasks, halt the processing of waiting tasks, and refuse to accept new tasks. However, a client is not getting the appropriate notification that asynchronous requests/responses can not proceed. The solution needs to cover: (a) When the asynchronous response is received in the CallbackFuture, the Executor is normally given the task to execute. If the Executor throws an exception, then the task needs to be cancelled. Since the Executor won't process the response task, the callback handler doesn't get the response or an error. But, cancelling the task will let the client check the Future object and will get a cancellation exception. (b) When the client submits a request with an asynchronous response and the ExecutorService is shutdown, then JAXWS needs to refuse the request and throw an exception back to the client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 --- Key: AXIS2-2160 URL: https://issues.apache.org/jira/browse/AXIS2-2160 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Lasantha Ranaweera Assigned To: Nick Gallardo Priority: Minor Attachments: AXIS2-2160.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Reporter: Nick Gallardo Assigned To: Nick Gallardo We need to see if it is possible to add functionality to the JAX-WS MethodMarshallers that would allow a wrapped message to be marshalled or unmarshalled without the use of generated wrapper beans. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 only
the wrapper is unmarshalled. The following check fails:
if (request == null) {
throw new WebServiceException(Null input received.);
} else if (request.getImageData() == null) {
throw new WebServiceException(Image is null);
}
meaning that JAXB created an ImageDepot object, but the actual image data
inside of it was omitted.
org.apache.axis2.jaxws.sample.MtomSampleByteArrayTests fails on Solaris
---
Key: AXIS2-2154
URL: https://issues.apache.org/jira/browse/AXIS2-2154
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Jeff Barrett
org.apache.axis2.jaxws.sample.MtomSampleByteArrayTests fails on Solaris
This problem is seen in the Continum builds of Apache Axis2. Since this
causes the Continum build to fail, the test has been commented out of
JAXWSTest (Committed revision 505375).
The test runs successfully on Windows and Linux.
Failure from
target/test-reports/TEST-org.apache.axis2.jaxws.framework.JAXWSTest.txt:
=
Testcase:
testAttachmentByteArrayAPI11(org.apache.axis2.jaxws.sample.MtomSampleByteArrayTests):
Caused an ERROR
Image is null
javax.xml.ws.soap.SOAPFaultException: Image is null
at
org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:946)
at
org.apache.axis2.jaxws.client.BaseDispatch.getFaultResponse(BaseDispatch.java:360)
at
org.apache.axis2.jaxws.client.BaseDispatch.invoke(BaseDispatch.java:129)
at
org.apache.axis2.jaxws.sample.MtomSampleByteArrayTests.testAttachmentByteArrayAPI11(MtomSampleByteArrayTests.java:60)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[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 clients. Key: AXIS2-2086 URL: https://issues.apache.org/jira/browse/AXIS2-2086 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Faults that occur during an async invocation are not being processed correctly during a JAX-WS async flow. The JAX-WS code needs to call in to the demarshalling APIs that are used for normal responses to create the appropriate SOAPFaultException or user-defined fault type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 -- Key: AXIS2-1822 URL: https://issues.apache.org/jira/browse/AXIS2-1822 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo The dynamic proxy client should be picking up the SOAPAction value for an operation if it is specificed in a WSDL. This is not currently happening. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 JIRA. http://issues.apache.org/jira/browse/AXIS2-2091 The fault that you are returned will be an AxisFault (which was happening already). The only difference is that now you can get the MessageContext for the response from the AxisFault. Asynchronous web service invocation does not return XML response on a SOAP fault Key: AXIS2-2125 URL: https://issues.apache.org/jira/browse/AXIS2-2125 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Environment: All Reporter: footh Priority: Minor When using the asynchronous sendReceiveNonBlocking call to invoke a web service, there is no way to retrieve the XML response if a SOAP Fault occurs. The XML response is always returned on the blocking invocation methods. I believe the same should hold for the asynchronous calls - there should always be a way to retreive the raw XML response. I sifted through the source code, in particular the NonBlockingInvocationWorker class (I'm looking at the one in OutInAxisOperation). The block of code that appears to be the problem looks something like this (in the run() method of NonBlockingInvocationWorker): if (body.hasFault()) ..call the callback's onError method else ..call the callback's onComplete method It seems the else clause should be eliminated and onComplete should always be called whether it is a SOAP Fault or not. This would result in both onError() and onComplete() being called in the case of a SOAP Fault, but I don't see that as being a big problem as the client can deal with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 the patch, the first question that came to mind though was, what's the difference between this as some of the information that's already being stored on the serviceDescription/OperationDescription? If I understand you correctly, then the distinction that you're making is that anything that would use the ServiceRuntimeDescription or the OperationRuntimeDescription would be some information that we couldn't already get from the service metadata (WSDL JSR-181/JAX-WS annotations), right? JAX-WS Cache or improve the @XMLRootElement and related annotation lookups -- Key: AXIS2-1800 URL: https://issues.apache.org/jira/browse/AXIS2-1800 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Rich Scheuerle Assigned To: Rich Scheuerle Attachments: patch.txt The JAX-WS doc/lit wrapped marshalling code needs to query annotations such as @XmlRootElement, @XmlList, @XmlType etc. This defect is opened to save/cache the resulting information on the OperationDescription or possibly a static WeakHashtable to improve performance. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 MessageContext --- Key: AXIS2-2091 URL: https://issues.apache.org/jira/browse/AXIS2-2091 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: patch.txt When Axis2 delivers a fault message via the Callback.onError() method, it delivers just the fault or exception object with no other additional data. For sync cases, we are able to get the MessageContext for the fault response from the OperationClient and then go down the fault processing chain for JAX-WS. We need this same capability for async cases as well so that similar fault processing can occur. This can be addressed by changing the AxisFault that's already being delivered to be constructed with the MessageContext inside of it. The APIs already exist to store the MessageContext on the fault, we just need to make the callback delivery code make use of it. This can be done with a slight change to org.apache.axis2.util.Util.getInboundFaultFromMessageContext(). The other change that needs to be made is to the OutInAxisOperation.NonBlockInvocationWorker. The way the fault is constructed there is not symmetric with the way it's being done in the CallbackReceiver. This code needs to be changed to mirror the CallbackReceiver's implementation. I'm working on a patch and should have something posted shortly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Key: AXIS2-2082 URL: https://issues.apache.org/jira/browse/AXIS2-2082 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Assigned To: Nick Gallardo Attachments: patch.txt fault subcodes being ignored for SOAP1.2. This one-liner patch fixes that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Faults that occur during an async invocation are not being processed correctly during a JAX-WS async flow. The JAX-WS code needs to call in to the demarshalling APIs that are used for normal responses to create the appropriate SOAPFaultException or user-defined fault type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 being ignored for SOAP1.2 Key: AXIS2-2082 URL: https://issues.apache.org/jira/browse/AXIS2-2082 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Assigned To: Nick Gallardo Attachments: patch.txt fault subcodes being ignored for SOAP1.2. This one-liner patch fixes that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Type: Bug Components: kernel Reporter: Nick Gallardo Assigned To: Nick Gallardo When Axis2 delivers a fault message via the Callback.onError() method, it delivers just the fault or exception object with no other additional data. For sync cases, we are able to get the MessageContext for the fault response from the OperationClient and then go down the fault processing chain for JAX-WS. We need this same capability for async cases as well so that similar fault processing can occur. This can be addressed by changing the AxisFault that's already being delivered to be constructed with the MessageContext inside of it. The APIs already exist to store the MessageContext on the fault, we just need to make the callback delivery code make use of it. This can be done with a slight change to org.apache.axis2.util.Util.getInboundFaultFromMessageContext(). The other change that needs to be made is to the OutInAxisOperation.NonBlockInvocationWorker. The way the fault is constructed there is not symmetric with the way it's being done in the CallbackReceiver. This code needs to be changed to mirror the CallbackReceiver's implementation. I'm working on a patch and should have something posted shortly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 this. 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 Type: Bug Components: kernel Reporter: Nick Gallardo Assigned To: Nick Gallardo Attachments: patch.txt When Axis2 delivers a fault message via the Callback.onError() method, it delivers just the fault or exception object with no other additional data. For sync cases, we are able to get the MessageContext for the fault response from the OperationClient and then go down the fault processing chain for JAX-WS. We need this same capability for async cases as well so that similar fault processing can occur. This can be addressed by changing the AxisFault that's already being delivered to be constructed with the MessageContext inside of it. The APIs already exist to store the MessageContext on the fault, we just need to make the callback delivery code make use of it. This can be done with a slight change to org.apache.axis2.util.Util.getInboundFaultFromMessageContext(). The other change that needs to be made is to the OutInAxisOperation.NonBlockInvocationWorker. The way the fault is constructed there is not symmetric with the way it's being done in the CallbackReceiver. This code needs to be changed to mirror the CallbackReceiver's implementation. I'm working on a patch and should have something posted shortly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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: jaxws Reporter: Nick Gallardo When a fault occurs, JAX-WS is creating a normal response MessageContext when it should be a fault MessageContext. This will be fixed by calling the Axis2 MessageContextBuilder.createFaultMessageContext() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 Key: AXIS2-2079 URL: https://issues.apache.org/jira/browse/AXIS2-2079 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo When a fault occurs, JAX-WS is creating a normal response MessageContext when it should be a fault MessageContext. This will be fixed by calling the Axis2 MessageContextBuilder.createFaultMessageContext() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 default values Key: AXIS2-2078 URL: https://issues.apache.org/jira/browse/AXIS2-2078 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt The @WebServiceClient annotation needs to provide default values specified in the JAX-WS specification. This will prevent compile time errors if users don't specify one of the member attributes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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! @WebServiceClient annotation definition does not have correct default values Key: AXIS2-2078 URL: https://issues.apache.org/jira/browse/AXIS2-2078 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt The @WebServiceClient annotation needs to provide default values specified in the JAX-WS specification. This will prevent compile time errors if users don't specify one of the member attributes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 incorrectly Key: AXIS2-2079 URL: https://issues.apache.org/jira/browse/AXIS2-2079 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo When a fault occurs, JAX-WS is creating a normal response MessageContext when it should be a fault MessageContext. This will be fixed by calling the Axis2 MessageContextBuilder.createFaultMessageContext() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2063) NPE in FaultDescriptionImpl
[ https://issues.apache.org/jira/browse/AXIS2-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo reassigned AXIS2-2063: Assignee: Nick Gallardo NPE in FaultDescriptionImpl --- Key: AXIS2-2063 URL: https://issues.apache.org/jira/browse/AXIS2-2063 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt When the faultBean attribute of the @WebFault annotation is not specified, it is possible that the result of WebFaultAnnot.faultBean() is null. Code that relies on the faultBean must first check for null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 FaultDescriptionImpl --- Key: AXIS2-2063 URL: https://issues.apache.org/jira/browse/AXIS2-2063 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.2 Reporter: Dustin Amrhein Assigned To: Nick Gallardo Priority: Minor Fix For: 1.2 Attachments: patch.txt When the faultBean attribute of the @WebFault annotation is not specified, it is possible that the result of WebFaultAnnot.faultBean() is null. Code that relies on the faultBean must first check for null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 - Key: AXIS2-2061 URL: https://issues.apache.org/jira/browse/AXIS2-2061 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Environment: Win XP Reporter: Samuel Isokpunwu Assigned To: Nick Gallardo Attachments: proxyClientpatch.txt Wrong SOAPBinding API import causes the Poxy client side attachment optimization code path to be skipped even when optimization is enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1824) Response.get() does not block
[ https://issues.apache.org/jira/browse/AXIS2-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Gallardo resolved AXIS2-1824. -- Resolution: Fixed This has already been fixed. Response.get() does not block - Key: AXIS2-1824 URL: https://issues.apache.org/jira/browse/AXIS2-1824 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nick Gallardo Assigned To: Nick Gallardo Async polling requests use the javax.xml.ws.Response object to collect responses. The get() and the get(long, TimeUnit) are used by the client to get the response contents. The spec states that the call to get() should block until the response has been returned. Javadoc reference: http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html#get() The current implementation of the method does not block. Also, the get(long, TimeUnit) method is unimplemented. This JIRA will address both of these issues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
