[
https://issues.apache.org/jira/browse/CXF-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Garner updated CXF-2184:
------------------------------
Attachment: publisedEndpointUrl.diff
Patch file for proposed resolutin
> XSD import statements do not apply given confguration
> -----------------------------------------------------
>
> Key: CXF-2184
> URL: https://issues.apache.org/jira/browse/CXF-2184
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2
> Reporter: Nigel Garner
> Fix For: 2.2.1
>
> Attachments: publisedEndpointUrl.diff
>
>
> CXF-1279 led to a change in the code to allow for the inclusion of a
> publishedEndpointUrl configuration parameter in the cxf-servlet.xml. This
> parameter is then used by the WSDLQueryHandler class when building the WSDL
> file to serve.
> We are currently developing a number of services using WSDL first development
> with the added complexity that the web services are deployed behind a proxy
> server that rewrites the incoming URL. The environment has no DNS so all
> configuration has to be IP based. The publishedEndpointURI property allows me
> to adjust the endpoint address in the published wsdl file at deployment time.
> However there is one other locations where IP address is used that I need to
> update, which is in the XSD imports inside the WSDL. These are showing as the
> internal network IP and port of the JBoss server instance as opposed to the
> external facing URL. As such no consumers of the service can use the
> published WSDL to generate a client because the XSD's can not be retrieved.
>
> I have attached a patch to the WSDLQueryHandler class that applies the same
> logic to the building of the base address of the schema imports as is applied
> to the endpoint address.
> Cheers
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
