ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Waruna Ranasinghe <waruna...@gmail.com>
Subject Re: port name generation
Date Fri, 16 Sep 2011 11:04:25 GMT
This could be an issue related to the axis2. We are using an old axis2
Can you please create a jira for this?


On 26 August 2011 05:03, Jonathan Coogan <Jonathan.Coogan@attachmate.com>wrote:

> I have a question about WSDL port name generation.  I am using the WAR
> distribution of ODE 1.3.5.  I would like to expose my BPEL services via
> HTTP and HTTPS.  Everything seems to be working ok, except that I've
> noticed the WSDL port names get regenerated (and changed) as soon as I
> access a WSDL via the HTTPS port.  For instance, the first time I deploy a
> process and access the WSDL on the HTTP port, it might contain something
> like this:
> <wsdl:port name="testSOAP11port_http" binding="tns:testSOAP11Binding">
> <soap:address location="http://localhost:8080/ode/processes/test"/>
> </wsdl:port>
> Now, say I access that same WSDL (or even an entirely different WSDL, it
> doesn't matter) on the HTTPS port.  The original WSDL is regenerated and
> now it contains several other ports ‹ both HTTP and HTTPS.  This is all
> well and good.  The annoyance is that the original port name changes.  Now
> it looks like this, no matter if I use the HTTP port or the HTTPS port:
> <wsdl:port name="testSOAP11port_http1" binding="tns:testSOAP11Binding">
> <soap:address location="http://localhost:8080/ode/processes/test"/>
> </wsdl:port>
> Notice the 1 that got appended to the name.  Why is this happening?  I
> suspect this could cause problems with some clients.  Is there any way to
> control the name generation?
> Thank you.
> -Jon

Waruna Ranasinghe

mob: 0724318285
blog: http://warunapw.blogspot.com
twitter: http://twitter.com/warunapww

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message