Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1.0
-
Fix Version/s: 1.1.1
-
Component/s: Petals Tools
-
Security Level: Public
-
- Environment:
- Windows XPsp3, PetalsStudio 1.1, PetalsESB 3.1
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Problem with Studio when a wsdl contains multiple ports (creating SOAP provider) | Problem with Studio when a WSDL contains multiple ports (creating SOAP provider) |
| Environment | Windows XPsp3, PetalsStudion 1.1, PetalsESB 3.1 | Windows XPsp3, PetalsStudio 1.1, PetalsESB 3.1 |
| Priority | Major [ 3 ] | |
| Description |
I am trying to expose webservices on Petals ESB ( 3.05 and 3.1). For that purpose, I use Petal Studio ( 1.0 and 1.1)
When I create a Provider Service Unit ( SOAP), the wsdl.wsdl or importedwsdl.wsdl is different from teh original one : End of imported wsdl Code: ... </wsdl:binding> <wsdl:service name="ws_sgp"> <wsdl:port name="ws_sgpSoap" binding="tns:ws_sgpSoap12"> <soap12:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx"/> </wsdl:port> <wsdl:port name="ws_sgpSoap" binding="tns:ws_sgpSoap"> <soap:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx"/> </wsdl:port> </wsdl:service> </wsdl:definitions> End of original wsdl Code: ... </wsdl:binding> <wsdl:service name="ws_sgp"> <wsdl:port name="ws_sgpSoap" binding="tns:ws_sgpSoap"> <soap:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx" /> </wsdl:port> <wsdl:port name="ws_sgpSoap12" binding="tns:ws_sgpSoap12"> <soap12:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx" /> </wsdl:port> </wsdl:service> </wsdl:definitions> As you notice, in the imported wsdl, the second port has an original name of ws_sgpSoap12, whereas the imported one is named ws_sgpSoap, which is not unique. Is there a way to fix this ? I tried different options in the wizard, but did not find a way to get proper behaviour. |
I am trying to expose webservices on Petals ESB ( 3.05 and 3.1). For that purpose, I use Petal Studio ( 1.0 and 1.1)
When I create a Provider Service Unit ( SOAP), the wsdl.wsdl or importedwsdl.wsdl is different from teh original one : End of imported wsdl {code:lang=xml} ... </wsdl:binding> <wsdl:service name="ws_sgp"> <wsdl:port name="ws_sgpSoap" binding="tns:ws_sgpSoap12"> <soap12:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx"/> </wsdl:port> <wsdl:port name="ws_sgpSoap" binding="tns:ws_sgpSoap"> <soap:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx"/> </wsdl:port> </wsdl:service> </wsdl:definitions> {code} End of original wsdl {code:lang=xml} ... </wsdl:binding> <wsdl:service name="ws_sgp"> <wsdl:port name="ws_sgpSoap" binding="tns:ws_sgpSoap"> <soap:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx" /> </wsdl:port> <wsdl:port name="ws_sgpSoap12" binding="tns:ws_sgpSoap12"> <soap12:address location="http://tecdvpweb.gial.be/ws_sgp/ws_sgp.asmx" /> </wsdl:port> </wsdl:service> </wsdl:definitions> {code} As you notice, in the imported wsdl, the second port has an original name of ws_sgpSoap12, whereas the imported one is named ws_sgpSoap, which is not unique. Is there a way to fix this ? I tried different options in the wizard, but did not find a way to get proper behaviour. |
| Component/s | Core Tools [ 10032 ] | |
| Component/s | Studio Product [ 10076 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 1.1.1 [ 10078 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Closed [ 10005 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Commit # 1858
The end-point is updated in the WSDL if, and only if the end-point must be generated at deployment time.
In provides mode, JBI fields are editable only if there is no WSDL or if this WSDL could not be parsed.
Otherwise, only WSDL values can be chosen.
A regression in the SOAP wizard was fixed (case of WSDL with several services).