[#PETALSSTUD-84] Problem with Studio when a WSDL contains multiple ports (creating SOAP provider) - Petals Link JIRA

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

Description:

Hide

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

... 
  </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

... 
 </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.

Show

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

... 
  </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

... 
 </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.

Environment:

Windows XPsp3, PetalsStudio 1.1, PetalsESB 3.1

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Vincent Zurczak added a comment - Sun, 26 Sep 2010 - 15:08:40 +0200

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).

Show

Vincent Zurczak added a comment - Sun, 26 Sep 2010 - 15:08:40 +0200 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).

Petals Studio

Problem with Studio when a WSDL contains multiple ports (creating SOAP provider)

Details

Activity

People

Dates