SOAP over JMS Problem

Question

I'm trying to call a SOAP over JMS Service form the BPEL process manager. For a simple example I use the Apache CXF example with Active MQ. The service has the following WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:jms="http://cxf.apache.org/transports/jms" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://cxf.apache.org/jms_greeter" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:x1="http://cxf.apache.org/jms_greeter/types" name="JMSGreeterService" targetNamespace="http://cxf.apache.org/jms_greeter">
     <wsdl:types>
          <schema targetNamespace="http://cxf.apache.org/jms_greeter/types" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
               <element name="sayHi">
                    <complexType/>
               </element>
               <element name="sayHiResponse">
                    <complexType>
                         <sequence>
                              <element name="responseType" type="xsd:string"/>
                         </sequence>
                    </complexType>
               </element>
               <element name="greetMe">
                    <complexType>
                         <sequence>
                              <element name="requestType" type="xsd:string"/>
                         </sequence>
                    </complexType>
               </element>
               <element name="greetMeResponse">
                    <complexType>
                         <sequence>
                              <element name="responseType" type="xsd:string"/>
                         </sequence>
                    </complexType>
               </element>
               <element name="greetMeOneWay">
                    <complexType>
                         <sequence>
                              <element name="requestType" type="xsd:string"/>
                         </sequence>
                    </complexType>
               </element>
          </schema>
     </wsdl:types>
     <wsdl:message name="sayHiRequest">
          <wsdl:part name="in" element="x1:sayHi"/>
     </wsdl:message>
     <wsdl:message name="sayHiResponse">
          <wsdl:part name="out" element="x1:sayHiResponse"/>
     </wsdl:message>
     <wsdl:message name="greetMeRequest">
          <wsdl:part name="in" element="x1:greetMe"/>
     </wsdl:message>
     <wsdl:message name="greetMeResponse">
          <wsdl:part name="out" element="x1:greetMeResponse"/>
     </wsdl:message>
     <wsdl:message name="greetMeOneWayRequest">
          <wsdl:part name="in" element="x1:greetMeOneWay"/>
     </wsdl:message>
     <wsdl:portType name="JMSGreeterPortType">
          <wsdl:operation name="sayHi">
               <wsdl:input name="sayHiRequest" message="tns:sayHiRequest"/>
               <wsdl:output name="sayHiResponse" message="tns:sayHiResponse"/>
          </wsdl:operation>
          <wsdl:operation name="greetMe">
               <wsdl:input name="greetMeRequest" message="tns:greetMeRequest"/>
               <wsdl:output name="greetMeResponse" message="tns:greetMeResponse"/>
          </wsdl:operation>
          <wsdl:operation name="greetMeOneWay">
               <wsdl:input name="greetMeOneWayRequest" message="tns:greetMeOneWayRequest"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="JMSGreeterPortBinding" type="tns:JMSGreeterPortType">
          <soap:binding style="document" transport="http://cxf.apache.org/transports/jms"/>
          <wsdl:operation name="greetMe">
               <soap:operation soapAction="" style="document"/>
               <wsdl:input name="greetMeRequest">
                    <soap:body use="literal"/>
               </wsdl:input>
               <wsdl:output name="greetMeResponse">
                    <soap:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="sayHi">
               <soap:operation soapAction="" style="document"/>
               <wsdl:input name="sayHiRequest">
                    <soap:body use="literal"/>
               </wsdl:input>
               <wsdl:output name="sayHiResponse">
                    <soap:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="greetMeOneWay">
               <soap:operation style="document" soapaction=""/>
               <wsdl:input name="greetMeOneWayRequest">
                    <soap:body use="literal"/>
               </wsdl:input>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="JMSGreeterService">
          <wsdl:port name="GreeterPort" binding="tns:JMSGreeterPortBinding">
               <jms:address destinationStyle="queue" jndiConnectionFactoryName="ConnectionFactory" jndiDestinationName="dynamicQueues/test.cxf.jmstransport.queue">
                    <jms:JMSNamingProperty name="java.naming.factory.initial" value="org.apache.activemq.jndi.ActiveMQInitialContextFactory"/>
                    <jms:JMSNamingProperty name="java.naming.provider.url" value="tcp://localhost:61616"/>
               </jms:address>
               <jms:clientConfig useConduitIdSelector="false"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
When trying to call the service i get the follwing errror:
<messages>
<input>
<Invoke_2_greetMeOneWay_InputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="in">
<greetMeOneWay xmlns="http://cxf.apache.org/jms_greeter/types">
<requestType>
sdfsdf!
</requestType>
</greetMeOneWay>
</part>
</Invoke_2_greetMeOneWay_InputVariable>
</input>
<fault>
<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="summary">
<summary>
Unable to find an available port
</summary>
</part>
</bindingFault>
</fault>
</messages>
When using a JMS Adapter Service i can access the queue without any problems.
Any ideas? Thanks!

Answer 1

Above all, really thank you for your precious help.
I thought about resolving the problem with JMS because it was studied to resolve asynchronous message delivery, which is what I'm trying to achieve.
So, I think I'll try the second solution you indicated. Let's see if I understood:
1- my customer decides to send some messages he wants to send [to better understand, I'll call them SMS] through the interface I developed
2- a new JMS Message is created
3- a MDB wake up and performs the initial steps to connect throught native calls
4- new MDB wake up and, using the connection, send created SMS
5- another process use the connection to read the StatusInd and create a new JMS Message to describe the message status
My implementation doubt is that I must send a lot of SMS (around 4000 SMS in one action), so, in pass 4, should I create 4000 MDB instances? It should be a clean implementation, maybe this way I could use also correlation id/replyto headers in passage 5, but I would it waste many resources?
And, also, how can I implement the "native calls"? Is there a way to create a class that support this proprietary protocol?
And what about creating the connections with the server? Should I use java.net.socket?
Really thank you,
Andrea
P.S.
I'll look for implementing it using Arjuna+JBoss ;)