WID 6.1.2 – problems migrating the mediation module

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>

     <servlet-name>WebService_WebServicePortTypeHttpPort</servlet-name>

      <servlet-class>com.ibm.ws.webservices.engine.transport.http.WebServicesServlet</servlet-class>

 </servlet>

  <servlet-mapping>

      <servlet-name>WebService_WebServicePortTypeHttpPort</servlet-name>

      <url-pattern>sca/WebService</url-pattern>

  </servlet-mapping>

 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:

com.ibm.websphere.sca.ServiceRuntimeException: 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:

http://www-1.ibm.com/support/docview.wss?rs=203&context=SW000&dc=DA410&dc=DA450&dc=DA430&dc=DA440&dc=D600&dc=D700&dc=DB510&dc=DB520&dc=D800&dc=D900&dc=DA900&dc=DA800&dc=DB540&dc=DB400&dc=DB560&dc=DB530&dc=DA600&dc=DB550&dc=D100&dc=DA420&dc=DA460&dc=DB300&dc=DA470&dc=DA480&dc=DB100&dc=DA4A10&dc=DA4A20&dc=DA700&dc=DA4A30&dc=DA400&dc=DA100&dc=DA500&dc=D200&dc=DB700&dc=DB600&q1=JR24087&uid=swg1JR24087&loc=en_US&cs=UTF-8&lang=all

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

<service-ref>

        <description>SOAServicesInterfacePartner</description>

        <service-ref-name>sca/import/SOAServicesInterfacePartner</service-ref-name>

        <service-interface>javax.xml.rpc.Service</service-interface>

         <wsdl-file>META-INF/wsdl/validateUser.wsdl</wsdl-file>

          <jaxrpc-mapping-file>META-INF/validateUser_mapping.xml</jaxrpc-mapping-file>

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

         <handler>

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

               <handler-name>ServiceImportHandler</handler-name>

               <handler-class>com.ibm.wsspi.sca.webservice.jaxrpc.ServiceImportHandler</handler-class>

          </handler>

    </service-ref>

 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

This entry was posted on Wednesday, July 2nd, 2008 at 7:04 pm and is filed under Integration Developer, Websphere. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “WID 6.1.2 – problems migrating the mediation module”

  1. Dan Zrobok Says:
    July 4, 2008 at 2:56 am | Reply

    I’m surprised that something so core to the platform is broken like this. I assume it’s a problem that only manifests itself with Mediation Modules created in WID 6.0.x? Is it also ‘Module’ Projects?

  2. enerosweb Says:
    July 7, 2008 at 6:37 pm | Reply

    Yes, looks like it affects only the Mediation Modules created with WID 6.1.0.1

Leave a Reply