[jbossws-issues] [JBoss JIRA] (JBWS-3759) Bug in schemalocation for swaref for Jboss EAP 6.2

[R Searls (JIRA)]

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

R Searls commented on JBWS-3759:
--------------------------------

Richard,

I get the following error page when attempting to download the WAR and ZIP files.   
       The file system for the given user is unavailable, please try again later. If the problem persists please contact Webdrift.

Would you either upload those archives as attachments in this jira or email them to me?


                
> Bug in schemalocation for swaref for Jboss EAP 6.2
> --------------------------------------------------
>
>                 Key: JBWS-3759
>                 URL: https://issues.jboss.org/browse/JBWS-3759
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>    Affects Versions: jbossws-cxf-4.2.3
>            Reporter: Richard Borge
>            Assignee: R Searls
>            Priority: Minor
>              Labels: cxf, eap-6.2
>
> I am using Jboss EAP-6.2 for a SOAP service which uses the Datahandler to handle returned streams. In the WSDL, I am expecting the xsd for swaref to be imported, but the schemalocation gets messed up. Instead of "http://ws-i.org/profiles/basic/1.1/swaref.xsd" I get "http://localhost:8080/soaptest/mys?xsd=http://ws-i.org/profiles/basic/1.1/swaref.xsd". This is a bit of a problem because, among other things, it messes up soapUI for thos of our customers that want to test the service.
> I have tried to look through the jboss code, but it is very hard to find where the localhost-part gets concatenated onto the swaref XSD.
> The source code:
> http://folk.uio.no/richared/jboss/soaptest.zip

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira