ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From patrosk <sunita_pa...@rediffmail.com>
Subject Re: problem in delpoying BPEL service unit on ODE-JBI, servicemix
Date Tue, 18 Mar 2008 09:09:00 GMT

Hi Simone, 
I tested using sendsoap. In another thread, i found that, any service that
you invoke outside of the JBI bus needs to have a corresponding binding
component.
So i took the simpleservice.wsdl, which is in my process-su and created
another simpleservice-http-su.
here is the simpleservice.wsdl,

<?xml version="1.0" encoding="UTF-8" ?> 
<wsdl:definitions targetNamespace="http://www.example.org/SimpleService/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://www.example.org/SimpleService/"
xmlns:intf="http://www.example.org/SimpleService/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:smix="http://servicemix.org/wsdl/jbi/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<!--
WSDL created by Apache Axis version: 1.3
Built on Oct 05, 2005 (05:23:37 EDT)

  --> 
<wsdl:types>
<schema targetNamespace="http://www.example.org/SimpleService/"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="concatRequest">
<complexType>
<sequence>
  <element name="s1" type="xsd:string" /> 
  <element name="s2" type="xsd:string" /> 
  </sequence>
  </complexType>
  </element>
<element name="concatResponse">
<complexType>
<sequence>
  <element name="s3" type="xsd:string" /> 
  </sequence>
  </complexType>
  </element>
  </schema>
  </wsdl:types>
<wsdl:message name="concatResponse">
  <wsdl:part element="impl:concatResponse" name="concatResponse" /> 
  </wsdl:message>
<wsdl:message name="concatRequest">
  <wsdl:part element="impl:concatRequest" name="concatRequest" /> 
  </wsdl:message>
<wsdl:portType name="SimpleService">
<wsdl:operation name="concat" parameterOrder="concatRequest">
  <wsdl:input message="impl:concatRequest" name="concatRequest" /> 
  <wsdl:output message="impl:concatResponse" name="concatResponse" /> 
  </wsdl:operation>
  </wsdl:portType>
<wsdl:binding name="SimpleServiceSOAPSoapBinding" type="impl:SimpleService">
  <wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" /> 
<wsdl:operation name="concat">
  <wsdlsoap:operation
soapAction="http://www.example.org/SimpleService/concat" /> 
<wsdl:input name="concatRequest">
  <wsdlsoap:body use="literal" /> 
  </wsdl:input>
<wsdl:output name="concatResponse">
  <wsdlsoap:body use="literal" /> 
  </wsdl:output>
  </wsdl:operation>
  </wsdl:binding>
<wsdl:service name="SimpleService">
<wsdl:port binding="impl:SimpleServiceSOAPSoapBinding"
name="SimpleServiceSOAP">
  <wsdlsoap:address
location="http://localhost:8085/axis/services/SimpleServiceSOAP" /> 
  <!-- Connect this external HTTP endpoint to the process internal 
                       JBI endpoint defined in dd -->
    <smix:endpoint role="provider" defaultMep="in-out"/>
  </wsdl:port>
  </wsdl:service>
  </wsdl:definitions>

the problem is SimpleService is not getting invoked
I get the following in the log.

12:48:44,115 | DEBUG | pool-flow.seda.servicemix-http-thread-7 | SedaQueue               
| .jbi.nmr.flow.seda.SedaQueue$1  132 |
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@176323e dequeued
exchange: InOut[
  id: ID:10.192.56.109-118c0bcc549-2:3
  status: Active
  role: provider
  service: {http://www.example.org/SimpleService/}SimpleService
  endpoint: SimpleServiceSOAP
  operation: {http://www.example.org/SimpleService/}concat
  in: <?xml version="1.0" encoding="UTF-8"?><concatRequest
xmlns="http://www.example.org/SimpleService/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
         <s1 xmlns="http://www.example.org/BpelService/">fgdf</s1>
         <s2 xmlns="http://www.example.org/BpelService/">dfgdf</s2>
      </concatRequest>
]
12:48:44,115 | DEBUG | pool-flow.seda.servicemix-http-thread-7 |
HttpComponent            | emix.common.AsyncBaseLifeCycle  419 | Received
exchange: status: Active, role: provider
12:48:44,131 | DEBUG | pool-flow.seda.servicemix-http-thread-7 |
HttpComponent            | emix.common.AsyncBaseLifeCycle  487 | Retrieved
correlation id: null
12:48:44,131 | ERROR | pool-flow.seda.servicemix-http-thread-7 |
HttpComponent            | ervicemix.common.BaseLifeCycle   48 | Error
processing exchange InOut[
  id: ID:10.192.56.109-118c0bcc549-2:3
  status: Active
  role: provider
  service: {http://www.example.org/SimpleService/}SimpleService
  endpoint: SimpleServiceSOAP
  operation: {http://www.example.org/SimpleService/}concat
  in: <?xml version="1.0" encoding="UTF-8"?><concatRequest
xmlns="http://www.example.org/BpelService/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
         <s1 xmlns="http://www.example.org/BpelService/">fgdf</s1>
         <s2 xmlns="http://www.example.org/BpelService/">dfgdf</s2>
      </concatRequest>
]
org.apache.servicemix.soap.SoapFault: Unexpected fault code:
{http://www.w3.org/2003/05/soap-envelope}Server.userException
	at
org.apache.servicemix.soap.marshalers.SoapReader.readFaultUsingDom(SoapReader.java:259)
	at
org.apache.servicemix.soap.marshalers.SoapReader.readFaultUsingStax(SoapReader.java:341)
	at
org.apache.servicemix.soap.marshalers.SoapReader.readSoapUsingStax(SoapReader.java:203)
	at
org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:89)
	at
org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:76)
	at
org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:174)
	at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
	at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
	at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
	at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
	at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
	at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
	at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
	at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
	at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
	at java.lang.Thread.run(Thread.java:595)
12:48:44,193 | DEBUG | pool-flow.seda.servicemix-http-thread-7 |
DeliveryChannelImpl      | .messaging.DeliveryChannelImpl  413 | Send
ID:10.192.56.109-118c0bcc549-2:3 in DeliveryChannel{servicemix-http}
12:48:44,193 | DEBUG | pool-flow.seda.servicemix-http-thread-7 | SedaFlow                
| emix.jbi.nmr.flow.AbstractFlow  121 | Called Flow send
12:48:44,193 | DEBUG | pool-flow.seda.servicemix-http-thread-8 | SedaQueue               
| .jbi.nmr.flow.seda.SedaQueue$1  132 |
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1@fe8ee7 dequeued
exchange: InOut[
  id: ID:10.192.56.109-118c0bcc549-2:3
  status: Error
  role: consumer
  service: {http://www.example.org/SimpleService/}SimpleService
  endpoint: SimpleServiceSOAP
  operation: {http://www.example.org/SimpleService/}concat
  in: <?xml version="1.0" encoding="UTF-8"?><concatRequest
xmlns="http://www.example.org/BpelService/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
         <s1 xmlns="http://www.example.org/BpelService/">fgdf</s1>
         <s2 xmlns="http://www.example.org/BpelService/">dfgdf</s2>
      </concatRequest>
  error: org.apache.servicemix.soap.SoapFault: Unexpected fault code:
{http://www.w3.org/2003/05/soap-envelope}Server.userException

SimpleService is a axis service running at port 8085. The SOAP message that
is being passed to simpleservice doesnt contain
http://www.example.org/SimpleService/ namespace, isnt it a problem?
<?xml version="1.0" encoding="UTF-8"?><concatRequest
xmlns="http://www.example.org/BpelService/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
         <s1 xmlns="http://www.example.org/BpelService/">fgdf</s1>
         <s2 xmlns="http://www.example.org/BpelService/">dfgdf</s2>
      </concatRequest>

Any thoughts??


Simone Maletta wrote:
> 
> I'm sorry I forget,
>     I never used soapui I always make my test using sendsoap.
> I repeat all seems to be good in your deploy and in your wsdl files.
> regards
> Simone
> ----- Original Message ----- 
> From: "patrosk" <sunita_patro@rediffmail.com>
> To: <user@ode.apache.org>
> Sent: Tuesday, March 18, 2008 5:34 AM
> Subject: Re: problem in delpoying BPEL service unit on ODE-JBI, servicemix
> 
> 
>>
>>
>> Yes..the last wsdl i sent is the updated one. I started redoing the whole
>> exercise, and in the mean time, changed the port-type name also.
>>
>> Please donot get confused with the 1st one. The Bpel-process-su and the
>> http-su, both contain the same wsdls.
>>
>> I am using my SOAPUI to test, but not the sendsoap client. Does it not
>> supporting doc-literal style? Do i need to change my BpelService.wsdl to
>> rpc-literal style?
>>
>> Thank you.
>>
>> Simone Maletta wrote:
>>>
>>> Hi patrosk,
>>>     I have got some problems following your work, then I have to ask to
>>> you
>>> some question:
>>> 1) the last wsdl come form you http su? and the first one where it come
>>> from?
>>> 2) there is mismatches in names between the two wsdl, in fact your
>>> portType
>>> change name, I don't know if it is a relevant problem, I'm using wsdl 
>>> form
>>> september, but it is a thing I saw
>>> 3) you're using a document style description, are you using sendsoap as
>>> client? In this case try to use an rpc descritpion style, I found
>>> problem
>>> in
>>> such a way.
>>>
>>> I don't know if there is a debugger that pemits to follow message flow
>>> into
>>> ODE, I've to say the true.
>>>
>>> Regards
>>> Simone
>>>
>>>
>>>
>>> ----- Original Message ----- 
>>> From: "patrosk" <sunita_patro@rediffmail.com>
>>> To: <user@ode.apache.org>
>>> Sent: Monday, March 17, 2008 1:41 PM
>>> Subject: Re: problem in delpoying BPEL service unit on ODE-JBI, 
>>> servicemix
>>>
>>>
>>>>
>>>> HI..i guess you may need my BpelService.wsdl. here iit is,
>>>>
>>>> <?xml version="1.0" encoding="UTF-8" ?>
>>>> <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>>>> xmlns:tns="http://www.example.org/BpelService/"
>>>> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
>>>> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
>>>> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
>>>> xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>>>> xmlns:smix="http://servicemix.org/wsdl/jbi/"
>>>> targetNamespace="http://www.example.org/BpelService/">
>>>> <wsdl:types>
>>>> <xsd:schema attributeFormDefault="unqualified"
>>>> elementFormDefault="unqualified"
>>>> targetNamespace="http://www.example.org/BpelService/">
>>>>  <xsd:element name="outputResponse" type="xsd:string" />
>>>>  <xsd:element name="inputRequest" type="tns:AssignTask" />
>>>> <xsd:complexType name="AssignTask">
>>>> <xsd:sequence>
>>>>  <xsd:element name="s1" type="xsd:string" />
>>>>  <xsd:element name="s2" type="xsd:string" />
>>>>  </xsd:sequence>
>>>>  </xsd:complexType>
>>>>  </xsd:schema>
>>>>  </wsdl:types>
>>>> <wsdl:message name="inputRequest">
>>>>  <wsdl:part name="inputRequest" element="tns:inputRequest" />
>>>>  </wsdl:message>
>>>> <wsdl:message name="outputResponse">
>>>>  <wsdl:part name="outputResponse" element="tns:outputResponse" />
>>>>  </wsdl:message>
>>>> <wsdl:portType name="BpelServiceSOAPPortType">
>>>> <wsdl:operation name="submitjob">
>>>>  <wsdl:input message="tns:inputRequest"
>>>> wsaw:Action="http://www.example.org/BpelService/submitjob" />
>>>>  <wsdl:output message="tns:outputResponse"
>>>> wsaw:Action="http://www.example.org/BpelService/BpelService/submitjobResponse"
>>>> />
>>>>  </wsdl:operation>
>>>>  </wsdl:portType>
>>>> <wsdl:binding name="BpelServiceSOAPSOAP11Binding"
>>>> type="tns:BpelServiceSOAPPortType">
>>>>  <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
>>>> style="document" />
>>>> <wsdl:operation name="submitjob">
>>>>  <soap:operation
>>>> soapAction="http://www.example.org/BpelService/submitjob"
>>>> style="document" />
>>>> <wsdl:input>
>>>>  <soap:body use="literal" />
>>>>  </wsdl:input>
>>>> <wsdl:output>
>>>>  <soap:body use="literal" />
>>>>  </wsdl:output>
>>>>  </wsdl:operation>
>>>>  </wsdl:binding>
>>>> <wsdl:service name="BpelServiceSOAP">
>>>> <wsdl:port name="BpelServiceSOAPSOAP11port_http"
>>>> binding="tns:BpelServiceSOAPSOAP11Binding">
>>>>  <soap:address location="http://localhost:8080/BpelServiceSOAP" />
>>>> <!-- Connect this external HTTP endpoint to the process internal
>>>>                     JBI endpoint defined in dd -->
>>>>    <smix:endpoint role="consumer" defaultMep="in-out"/>
>>>>  </wsdl:port>
>>>>
>>>>  </wsdl:service>
>>>>
>>>>  </wsdl:definitions>
>>>>
>>>>
>>>> patrosk wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have a bpel process running, in ODE WAR, hosted on tomcat.
>>>>> I want to deploy the same process, on ODE -JBI on servicemix3.1.1.
>>>>>
>>>>> I have created 2 service units, 1 service unit contains, the .bpel,
>>>>> .wsdl's, deploy.xml, i want to deploy the bpel process as http 
>>>>> endpoint.
>>>>> so i have one more http service unit, which contains only the wsdl, 
>>>>> that
>>>>> describes the bpel service.
>>>>>
>>>>> package structure,
>>>>> 1. BpelService-process-su.zip(BpelService.wsdl, SimpleService.wsdl,
>>>>> BpelService.bpel, deploy.xml)
>>>>> 2.BpelService-http-su.zip(BpelService.wsdl (added smix endpoint here))
>>>>> 3.meta-inf/jbi.xml
>>>>> So zipped together, the bpel service unit, http service unit and the
>>>>> meta-inf/jbi.xml as BpelService-sa.zip and copied to deploy folder of
>>>>> servicemix.
>>>>> But i am facing the following deployment issue,
>>>>>
>>>>> INFO  - AutoDeploymentService          - Directory: deploy: Archive
>>>>> changed: processing BpelService-
>>>>> sa.zip ...
>>>>> ERROR - OdeServiceUnit                 - Error deploying process
>>>>> described
>>>>> by deployment descriptor
>>>>> "E:\servicemix\apache-servicemix-3.1.1-incubating\data\smx\service-assemblies\BpelService-SA\version
>>>>> _7\sus\OdeBpelEngine\BpelService-process" for service unit
>>>>> "BpelService-process".
>>>>> java.lang.IllegalArgumentException: Directory
>>>>> E:\servicemix\apache-servicemix-3.1.1-incubating\data\
>>>>> smx\service-assemblies\BpelService-SA\version_7\sus\OdeBpelEngine\BpelService-process
>>>>> does not conta
>>>>> in a deploy.xml file!
>>>>>         at
>>>>> org.apache.ode.store.DeploymentUnitDir.<init>(DeploymentUnitDir.java:103)
>>>>>         at
>>>>> org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:163)
>>>>>         at
>>>>> org.apache.ode.jbi.OdeServiceUnit.deploy(OdeServiceUnit.java:62)
>>>>>         at
>>>>> org.apache.ode.jbi.OdeSUManager.deploy(OdeSUManager.java:60)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentSer
>>>>> vice.java:527)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentSer
>>>>> vice.java:335)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeployment
>>>>> Service.java:646)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentServic
>>>>> e.java:62)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.jav
>>>>> a:609)
>>>>>         at java.util.TimerThread.mainLoop(Timer.java:512)
>>>>>         at java.util.TimerThread.run(Timer.java:462)
>>>>> ERROR - OdeSUManager                   - Error deploying service unit
>>>>> "BpelService-process".
>>>>> INFO  - DeploymentService              - UnDeployed ServiceUnit
>>>>> BpelService-process from Component:
>>>>> OdeBpelEngine
>>>>> ERROR - AutoDeploymentService          - Failed to update Service
>>>>> Assembly: BpelService-SA
>>>>> java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
>>>>> <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"
>>>>> version="1.0">
>>>>> <jbi-task-result>
>>>>> <frmwk-task-result>
>>>>> <frmwk-task-result-details>
>>>>> <task-result-details>
>>>>> <task-id>deploy</task-id>
>>>>> <task-result>FAILED</task-result>
>>>>> <message-type>ERROR</message-type>
>>>>> </task-result-details>
>>>>> </frmwk-task-result-details>
>>>>> </frmwk-task-result>
>>>>> <component-task-result
>>>>> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>>>>>         <component-name>servicemix-http</component-name>
>>>>>         <component-task-result-details>
>>>>>                 <task-result-details>
>>>>>                         <task-id>deploy</task-id>
>>>>>                         <task-result>FAILED</task-result>
>>>>>                         <message-type>ERROR</message-type>
>>>>>                         <task-status-msg>
>>>>> <msg-loc-info>
>>>>> <loc-token/>
>>>>> <loc-message>Unable to find suitable deployer for Service Unit
>>>>> 'BpelService-HTTP'</loc-message>
>>>>> </msg-loc-info>
>>>>> </task-status-msg>
>>>>>                 </task-result-details>
>>>>>         </component-task-result-details>
>>>>> </component-task-result>
>>>>> <component-task-result>
>>>>> <component-name>OdeBpelEngine</component-name>
>>>>> <component-task-result-details>
>>>>> <task-result-details>
>>>>> <task-id>deploy</task-id>
>>>>> <task-result>SUCCESS</task-result>
>>>>> <message-type>WARNING</message-type>
>>>>> <task-status-msg>
>>>>> <msg-loc-info>
>>>>> <loc-token/>
>>>>> <loc-message>Unable to parse result string</loc-message>
>>>>> </msg-loc-info>
>>>>> </task-status-msg>
>>>>> <exception-info>
>>>>> <nesting-level>1</nesting-level>
>>>>> <loc-token/>
>>>>> <loc-message/>
>>>>> <stack-trace><![CDATA[java.lang.NullPointerException
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.DeploymentService.getChildElement(DeploymentService.j
>>>>> ava:648)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.DeploymentService.getComponentTaskResult(DeploymentSe
>>>>> rvice.java:600)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentSer
>>>>> vice.java:528)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentSer
>>>>> vice.java:335)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeployment
>>>>> Service.java:646)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentServic
>>>>> e.java:62)
>>>>>         at
>>>>> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.jav
>>>>> a:609)
>>>>>         at java.util.TimerThread.mainLoop(Timer.java:512)
>>>>>         at java.util.TimerThread.run(Timer.java:462)
>>>>> ]]></stack-trace>
>>>>> </exception-info>
>>>>> </task-result-details>
>>>>> </component-task-result-details>
>>>>> </component-task-result>
>>>>> </jbi-task-result>
>>>>> </jbi-task>
>>>>>
>>>>>
>>>>> the deploy.xml of Bpel process looks like this,
>>>>> <deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
>>>>>         xmlns:pns="http://BpelService"
>>>>>         xmlns:bs="http://www.example.org/BpelService/"
>>>>>         xmlns:ss="http://www.example.org/SimpleService/">
>>>>>
>>>>>         <process name="pns:BpelService">
>>>>>                 <active>true</active>
>>>>>                 <provide partnerLink="ConsumerBpelService">
>>>>>                         <service name="bs:BpelService"
>>>>> port="BpelServiceSOAP"/>
>>>>>                 </provide>
>>>>>                 <invoke partnerLink="ProviderSimpleService">
>>>>>                         <service name="ss:SimpleService"
>>>>> port="SimpleServiceSOAP"/>
>>>>>                 </invoke>
>>>>>         </process>
>>>>>
>>>>> </deploy>
>>>>> Can anyone help me out in figuring out the issue.
>>>>>
>>>>> Thank you.
>>>>>
>>>>>
>>>>
>>>> -- 
>>>> View this message in context:
>>>> http://www.nabble.com/problem-in-delpoying-BPEL-service-unit-on-ODE-JBI%2C-servicemix-tp16088774p16092374.html
>>>> Sent from the Apache Ode User mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>>
>>
>> -- 
>> View this message in context: 
>> http://www.nabble.com/problem-in-delpoying-BPEL-service-unit-on-ODE-JBI%2C-servicemix-tp16088774p16114263.html
>> Sent from the Apache Ode User mailing list archive at Nabble.com.
>> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/problem-in-delpoying-BPEL-service-unit-on-ODE-JBI%2C-servicemix-tp16088774p16116805.html
Sent from the Apache Ode User mailing list archive at Nabble.com.


Mime
View raw message