Archive for July, 2008

Disable Soap1.2 generation in ASMX.NET WSDL generator

July 31, 2008 Leave a comment

Websphere ESB 6.1 does not support Soap 1.2 yet. Presense of Soap1.2 bindings in .NET auto generated  WSDL files created lots of  problems with the new WID 6.1.2 release. So there are two options either modify WSDL manualy  when importing to ESB or modify the .NET web service to supress Soap1.2.

To disable Soap1.2 binding generation add in web.config  under <system.web>




        <add name=HttpSoap />

        <add name=Documentation/>




WID 6.1.2 – problems migrating the mediation module

July 2, 2008 2 comments

After battling WID 6.1.2 start up,  few more problems come up during migration of mediation projects to the new WID 6.1.2

1. WebService export binding does not regenerate the binding servlet in descriptors even after the full clean and rebuild. The error received when sending SOAP

               Error 404: SRVE0190E: File not found: /sca/WebService

Basically the web.xml was missing servlet mapping

<servlet id=”WebService_WebServicePortTypeHttpPort“>

     <display-name>Web Services Router Servlet for SCA</display-name>








 The easiest way for WID to regenerate the web.xml properly was  to “Replace the Binding” on the Export.

2. Web Service Import binding does not regenerate the EJB references in descriptors after full clean and rebuild. Getting the following exeption while testing the mediation module: Resource
java:comp/env/sca/import/SOAServicesInterfacePartner cannot be resovled.:
caused by: javax.naming.NameNotFoundException: Name comp/env/sca not found in  context “java:”.

 This problem looks pretty much the same as in IBM support note:

The following ejb reference is misssing in ejb-jar.xml:







          <service-qname xmlns:pfx=”urn:com:deloitte:pim:soa“>pfx:SOAServices</service-qname>


               <display-name>SCA Service Import Handler</display-name>





 the same trick with refactoring the name of the import did not work – looking for workaround ….

The root cause for both problems were presense of Soap 1.2 bindings in .NET Web Service WSDL. Disabling Soap 1.2 did the trick…

Related Posts