Eclipse Community Forums: Eclipse Process Manager (Stardust) » WebService working on Tomcat throws PublicException on Weblogic

Home » Archived » Eclipse Process Manager (Stardust) » WebService working on Tomcat throws PublicException on Weblogic(PublicException: ModelId was not found in request and no default value is defined.)

Show: Today's Messages :: Show Polls :: Message Navigator

WebService working on Tomcat throws PublicException on Weblogic [message #1035712]

Sun, 07 April 2013 09:15

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

Hi,

my webservice call is working in Tomcat, but failing in WebLogic. Here is the error:

Caused by: org.eclipse.stardust.common.error.PublicException: ModelId was not found in request and no default value is define
d.        at org.eclipse.stardust.engine.ws.processinterface.WsUtils.ensureModelIdExists(WsUtils.java:103)      at org.eclipse.stardust.engine.ws.processinterface.GenericWebServiceProvider.getModelId(GenericWebServiceProvider.java:135)        at org.eclipse.stardust.engine.ws.processinterface.GenericWebServiceProvider.invoke(GenericWebServiceProvider.java:58)        at org.eclipse.stardust.engine.ws.processinterface.GenericWebServiceProviderHttpBasicAuth.invoke(GenericWebServiceProviderHttpBasicAuth.java:33)

I am clearly sending the modelId as part of the request and again this is working in Tomcat!

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sun="http://eclipse.org/stardust/models/generated/SunGardEntitlement">
   <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
                <stardust-bpm-model wsa:IsReferenceParameter="1" xmlns="http://eclipse.org/stardust/ws/v2012a/api">SunGardEntitlement</stardust-bpm-model>
   </soapenv:Header>

Report message to a moderator

Re: WebService working on Tomcat throws PublicException on Weblogic [message #1035715 is a reply to message #1035712]

Sun, 07 April 2013 09:16

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

This is a class loading issue with WLS (as so often). WLS is using its own saaj-impl and saaj-api versions that have a bug. To resolve this please add saaj-impl and saaj-api to your project explicitly.
For this you should modify pom.xml by adding below to dependencies section ....

    <dependency>
      <groupId>com.sun.xml.messaging.saaj</groupId>
      <artifactId>saaj-impl</artifactId>
      <version>1.3.2</version>
      <scope>runtime</scope>
      <exclusions>
        <exclusion>
          <groupId>activation</groupId>
          <artifactId>activation</artifactId>
        </exclusion>
      </exclusions>
   </dependency>

... and following dependency to dependencyManagement section ...

          <dependency>
            <groupId>com.infinity.bpm</groupId>
            <artifactId>jax-ws-cxf-module</artifactId>
            <version>${ipp.version}</version>
            <type>pom</type>
            <exclusions>
               <exclusion>
                  <groupId>javax.xml.soap</groupId>
                  <artifactId>saaj-api</artifactId>
               </exclusion>
               <exclusion>
                  <groupId>com.sun.xml.messaging.saaj</groupId>
                  <artifactId>saaj-impl</artifactId>
               </exclusion>
            </exclusions>
         </dependency>

... or you just add saaj-impl-1.3.2.jar and saaj-api-1.3.jar to WEB-INF/lib manually.

Report message to a moderator

Previous Topic:	Support Case Participants do not show
Next Topic:	A "\n" tokenizer used in a Camel route is not persisted to a MySQL AuditTrail

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 13:36:08 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter