Petals BC SOAP

A proxy SOAP written using only one service unit is not supported

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.3.4
  • Fix Version/s: 4.4.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Writing a service unit as following, including a service provider and a service consumer linked to the previous service provider:

    <jbi:jbi version="1.0" ...>
   <jbi:services binding-component="true">
      <jbi:provides
         interface-name="generatedNs:SoapAction"
         service-name="generatedNs:SoapActionService"
         endpoint-name="GivenSoapActionServiceEndpointSOAP11">

         ...

      </jbi:provides>

      <jbi:consumes
         interface-name="generatedNs:SoapAction"
         service-name="generatedNs:SoapActionService"
         endpoint-name="GivenSoapActionServiceEndpointSOAP11">

         ...

      </jbi:consumes>

    we get the following error:

    sample-0 2015/08/07 15:39:48,113 GMT+0200 SEVERE [org.apache.axis2.transport.http.AxisServlet] : null
java.lang.NullPointerException
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:223)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
	at org.eclipse.jetty.server.Server.handle(Server.java:499)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
	at java.lang.Thread.run(Thread.java:745)
    Show
    Writing a service unit as following, including a service provider and a service consumer linked to the previous service provider: 
    <jbi:jbi version="1.0" ...>
   <jbi:services binding-component="true">
      <jbi:provides
         interface-name="generatedNs:SoapAction"
         service-name="generatedNs:SoapActionService"
         endpoint-name="GivenSoapActionServiceEndpointSOAP11">

         ...

      </jbi:provides>

      <jbi:consumes
         interface-name="generatedNs:SoapAction"
         service-name="generatedNs:SoapActionService"
         endpoint-name="GivenSoapActionServiceEndpointSOAP11">

         ...

      </jbi:consumes>
    we get the following error: 
    sample-0 2015/08/07 15:39:48,113 GMT+0200 SEVERE [org.apache.axis2.transport.http.AxisServlet] : null
java.lang.NullPointerException
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144)
	at org.ow2.petals.binding.soap.listener.incoming.servlet.SoapServlet.doPost(SoapServlet.java:223)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
	at org.eclipse.jetty.server.Server.handle(Server.java:499)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
	at java.lang.Thread.run(Thread.java:745)
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Fri, 7 Aug 2015 - 16:05:45 +0200 - edited

The error reported corresponds to PETALSBCSOAP-116: the requested service does not exist.

The problem is due to ServiceUnitDataHandler#configurationExtensionsMap for which the key includes service name and endpoint name, the characteristic "Provide" or "Consume" is missing in our case.

Show
Christophe DENEUX added a comment - Fri, 7 Aug 2015 - 16:05:45 +0200 - edited The error reported corresponds to PETALSBCSOAP-116: the requested service does not exist. The problem is due to ServiceUnitDataHandler#configurationExtensionsMap for which the key includes service name and endpoint name, the characteristic "Provide" or "Consume" is missing in our case.
Hide
Permalink
Christophe DENEUX added a comment - Mon, 10 Aug 2015 - 15:59:30 +0200

Fixed in trunk using PETALSCDK-142

Show
Christophe DENEUX added a comment - Mon, 10 Aug 2015 - 15:59:30 +0200 Fixed in trunk using PETALSCDK-142

People

Dates

  • Created:
    Fri, 7 Aug 2015 - 15:58:21 +0200
    Updated:
    Mon, 10 Aug 2015 - 16:02:56 +0200
    Resolved:
    Mon, 10 Aug 2015 - 16:02:55 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.