[Users] Problem with Studio when a wsdl contains multiple ports

[vzurczak]

Hi Philip, :)

When you create a jbi.xml for the SOAP component, the interface, end-point and service names must match the WSDL definition.
The end-point name is in fact the port name of a SOAP binding.
If for any reason, the end-point name and this port name are different, then the wizard updates the WSDL to use the defined end-point.

Your use case was clearly not expected (2 ports with a SOAP binding).
In any case, only the first port will be exposed by Petals (because it is the only that is registered in the Petals registry / declared in the jbi.xml).
If you want to expose the second one, you should create a second provides block in your jbi.xml, or create a new SU.
Anyway, it is a bug in the studio.

But I'm not sure to know which behavior choose:
	Remove the WSDL update behavior, except for auto-generated end-points.

	Remove the WSDL update behavior for services that have more than one port with a SOAP binding.



The first solution seems to be the best for me.
In both cases, your WSDL would not be modified anymore.

Could you post a bug on Petals Studio's JIRA (http://jira.petalslink.com/browse/PETALSSTUD)?
I could fix it for the next release of the studio, that is planned for very soon.




-------------------- m2f --------------------

Subscribe/Unsubscribe emails notifications :
http://forum.petalslink.com/m2f_usercp.php

Response to this email will be posted on the Petals forum.
Please delete the existing text before responding :)

Read the topic online:
http://forum.petalslink.com/viewtopic.php?p=31543#31543

-------------------- m2f --------------------