You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Katherine Sanders (JIRA)" <ji...@apache.org> on 2010/01/05 13:00:56 UTC
[jira] Created: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Client unable to turn on addressing with UsingAddressing in the WSDL
--------------------------------------------------------------------
Key: AXIS2-4596
URL: https://issues.apache.org/jira/browse/AXIS2-4596
Project: Axis2
Issue Type: Bug
Components: Addressing
Reporter: Katherine Sanders
Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reopened AXIS2-4596:
------------------------------------
Kathrine,
Brian,
I just updated my working copy with the change and it causes a build failure:
testWithoutUsingAddressing(org.apache.axis2.jaxws.addressing.UsingAddressingTests) Time elapsed: 0.084 sec <<< ERROR!
javax.xml.ws.WebServiceException: The following WSDL exception occurred: WSDLException: faultCode=WSDL4JWrapper : : javax.wsdl.WSDLException: WSDLException: faultCode=WSDL4JWrapper : : java.net.UnknownHostException: Users
at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupWsdlDefinition(ServiceDescriptionImpl.java:1082)
at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(ServiceDescriptionImpl.java:237)
at org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.<init>(ServiceDescriptionImpl.java:160)
at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:133)
at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:79)
at org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(DescriptionFactory.java:78)
at org.apache.axis2.jaxws.spi.ServiceDelegate.<init>(ServiceDelegate.java:213)
at org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:59)
at javax.xml.ws.Service.<init>(Service.java:36)
at javax.xml.ws.Service.create(Service.java:116)
at org.apache.axis2.jaxws.addressing.UsingAddressingTests.testWithoutUsingAddressing(UsingAddressingTests.java:81)
...
Note that "Users" is actually the first component of the path to my working copy. I think the problem is due to URL manipulations that are not portable (I'm running the build on Mac OS X).
I will do an attempt to fix this issue.
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Assignee: Brian DePradine
> Fix For: 1.6
>
> Attachments: AXIS2-4596.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders updated AXIS2-4596:
-------------------------------------
Attachment: AXIS2-4596.patch
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Attachments: AXIS2-4596.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian DePradine resolved AXIS2-4596.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Assignee: Brian DePradine
> Fix For: 1.6
>
> Attachments: AXIS2-4596.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders updated AXIS2-4596:
-------------------------------------
Attachment: 632660.patch
Here's a patch that fixes the problem. I've modified BindingProvider to check if addressing is turned on in the WSDL when it's setting the default. I've also added some unit tests to check that UsingAddressing is correctly read from the WSDL, that addressing is off by default if there isn't a WSDL or the WSDL doesn't contain UsingAddressing, and that addressing is on if the WSDL contains UsingAddressing.
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Attachments: 632660.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-4596:
-----------------------------------
Component/s: (was: Addressing)
jaxws
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian DePradine reassigned AXIS2-4596:
--------------------------------------
Assignee: Brian DePradine
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Assignee: Brian DePradine
> Attachments: AXIS2-4596.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4596.
------------------------------------
Resolution: Fixed
Fixed the build failure (see r905830).
Note that you should avoid building URLs (especially file: URLs) using string manipulations, since this in most cases results in non portable code or code that fails in some border cases. There are two good ways to get an URL to a test file:
a. If the test file is part of the resources, request an URL from the class loader. This has the additional advantage of making the test independent of the project layout (i.e. the folder that contains the test resources).
b. Construct a java.io.File object (in a portable way) and use toURI or toURL.
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Assignee: Brian DePradine
> Fix For: 1.6
>
> Attachments: AXIS2-4596.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829029#action_12829029 ]
Brian DePradine commented on AXIS2-4596:
----------------------------------------
Andreas,
Apologies for that, I will keep your comments in mind in the future.
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Assignee: Brian DePradine
> Fix For: 1.6
>
> Attachments: AXIS2-4596.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4596) Client unable to turn on addressing
with UsingAddressing in the WSDL
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders updated AXIS2-4596:
-------------------------------------
Attachment: (was: 632660.patch)
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in BindingProvider, however it didn't add any code to turn addressing on if <wsaw:usingAddressing /> is present in the WSDL. This means that addressing is always off on the client unless AddressingFeature is used to turn it on, and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.