You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@cxf.apache.org by jbradfor <jb...@amfam.com> on 2011/03/02 17:44:05 UTC

Take 2 - Dynamic WSDL - Published Endpoint is relative to Schema Loc

Reposting due to code sample display issues in the last post.


All of our Endpoints must be routed through an ESB.  We also would like to
be able to use the Dynamic WSDL (?WSDL).  Therefore, we set it up like this,
where the published endpoint is the ESB path.






  
    /wsdl/schema/Automation_Ping.xsd
  /wsdl/schema/Message_LocationInformationService.xsd





The problem is that the WSDL displayed, with the ?WSDL path, uses the ESB
path as the relative path for the imported schema.  Like this:








So therefore, when you go to generate from the Dynamic WSDL (i.e. SoapUI) it
fails, because it cannot find the schema.  It is looking in the ESB for it.


If I change the published endpoint to the services path (i.e.
http://host/servicecontext/services/servicename) it works, but then the
EndPoint is not pointing to the required ESB path.


Anyone know how to resolve this?







--
View this message in context: http://cxf.547215.n5.nabble.com/Take-2-Dynamic-WSDL-Published-Endpoint-is-relative-to-Schema-Loc-tp3406799p3406799.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: Take 2 - Dynamic WSDL - Published Endpoint is relative to Schema Loc

Posted by Daniel Kulp <dk...@apache.org>.


This MAY be a bug in the ESB.   I don't really know.

That said, with 2.4.0-SNAPSHOT, this MAY be fixed. The WSDL query stuff was 
redone as an interceptor and, as such, I was able to access a bit more 
information and I cleaned up the URL rewriting in it a bit.   Thus, it may be 
fixed there.  

Otherwise, we'd probably need a testcase.

Dan



On Wednesday 02 March 2011 11:44:05 AM jbradfor wrote:
> Reposting due to code sample display issues in the last post.
> 
> 
> All of our Endpoints must be routed through an ESB.  We also would like to
> be able to use the Dynamic WSDL (?WSDL).  Therefore, we set it up like
> this, where the published endpoint is the ESB path.
> 
> 
> 
> 
> 
> 
> 
>     /wsdl/schema/Automation_Ping.xsd
>   /wsdl/schema/Message_LocationInformationService.xsd
> 
> 
> 
> 
> 
> The problem is that the WSDL displayed, with the ?WSDL path, uses the ESB
> path as the relative path for the imported schema.  Like this:
> 
> 
> 
> 
> 
> 
> 
> 
> So therefore, when you go to generate from the Dynamic WSDL (i.e. SoapUI)
> it fails, because it cannot find the schema.  It is looking in the ESB for
> it.
> 
> 
> If I change the published endpoint to the services path (i.e.
> http://host/servicecontext/services/servicename) it works, but then the
> EndPoint is not pointing to the required ESB path.
> 
> 
> Anyone know how to resolve this?
> 
> 
> 
> 
> 
> 
> 
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Take-2-Dynamic-WSDL-Published-Endpoint-is-
> relative-to-Schema-Loc-tp3406799p3406799.html Sent from the cxf-user
> mailing list archive at Nabble.com.

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com