[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2776) WSDL unavailable for deployed web service in AS5.1

[Richard Opalka (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBWS-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12487653#action_12487653 ] 

Richard Opalka commented on JBWS-2776:
--------------------------------------

Try with JBossAS 5.2.0.Beta1, it includes JBossWS 3.2.0 (this issue should be fixed there)

> WSDL unavailable for deployed web service in AS5.1
> --------------------------------------------------
>
>                 Key: JBWS-2776
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2776
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>            Reporter: Gary Brown
>            Assignee: Alessio Soldano
>         Attachments: Issue-riftsaw-55.ear
>
>
> Found an issue with an example for RiftSaw (BPEL engine) when used with ESB. The example uses JAX-WS services. The issue is recorded at: https://jira.jboss.org/jira/browse/RIFTSAW-55
> The issue was that the endpoint address listed in the localhost:8080/jbossws/services console in AS5.1 was different to the one in AS4.2.3, and it navigated to an unavailable page, whereas the AS4.2.3 version displayed the correct WSDL.
> In AS5.1, it appears that if the war containing the JAX-WS service is embedded within another deployment (whether esb or ear), it includes the name of the parent deployment in the endpoint address.
> This extended endpoint address goes to an 'unavailable resource' error page, whereas the original shorter address results in a stack trace (shown in RiftSaw-55).
> I have attached an example ear containing the war, to demonstrate the issue. Install this in AS5.1, go to the jbossws/services console, and select the endpoint address link for either service.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira