[Users] petals-se-orchestra 1.0.1 and petals-standalone-2.2.1

nguyen petals-components at ebmwebsourcing.com
Wed Mar 16 10:24:23 CET 2011


Hi,

I tried use the petals-se-orchestra 1.0.1 component on the petals-standalone-2.2.1 with an sample bpel process generated by petals orchestra plugin installed on Eclipse Ganymede 3.4.1.
The deployment of the petals-se-orchestra and my SA was OK. But I got un error below when the test with Eclipse :

IWAB0135E An unexpected error has occurred.
java.net.MalformedURLException
unknown protocol: petals

Thank in advance


This is the deployment trace of the component and service on the Petals server :

C:\petals-standalone-2.2.1\bin>startup

 -----------------------------------------------------------
|                                                           |
|             OW2 PEtALS Enterprise Service Bus             |
|                   http://petals.ow2.org                   |
|                                                           |
 -----------------------------------------------------------

PEtALS ESB is starting...
[petals.RMI]-INFO 2008-10-20 11:11:18,245 JMX RMI server started at : service:jm
x:rmi:///jndi/rmi://localhost:7700/jmxRmiConnector

PEtALS ESB standalone distribution successfully started - 20/10/08 11:11
System Information : Petals JBI Container - version: 2.2.1
PEtALS prompt. Tape 'help' for help.

petals at localhost:/> [petals.InstallationService]-INFO 2008-10-20 11:11:42,573 Co
mponent 'petals-se-orchestra' succesfully installed
[petals.container.components.petals-se-orchestra]-INFO 2008-10-20 11:11:43,541 O
rchestra Intialization...
20 oct. 2008 11:11:44 org.jbpm.pvm.internal.log.Jdk14Log debug
FIN: eagerly initializing repository
20 oct. 2008 11:11:44 org.jbpm.pvm.internal.log.Jdk14Log debug
FIN: eagerly initializing servicePublisher
20 oct. 2008 11:11:44 org.jbpm.pvm.internal.log.Jdk14Log debug
FIN: eagerly initializing serviceInvoker
[petals.container.components.petals-se-orchestra]-INFO 2008-10-20 11:11:44,463 C
omponent initialized
[petals.container.components.petals-se-orchestra]-INFO 2008-10-20 11:11:44,494 S
tart Component
[petals.container.components.petals-se-orchestra]-INFO 2008-10-20 11:11:48,729 P
erform BPEL-Processes deployment on Orchestra server
Retrieving document at 'file:/C:/petals-standalone-2.2.1/repository/service-asse
mblies/petals-sa-bpeltest-10-20-2008-111148651/install/petals-su-bpeltest/proces
s.wsdl'.
Retrieving document at 'file:/C:/petals-standalone-2.2.1/repository/service-asse
mblies/petals-sa-bpeltest-10-20-2008-111148651/install/petals-su-bpeltest/proces
s.wsdl'.
Retrieving document at 'file:/C:/petals-standalone-2.2.1/repository/service-asse
mblies/petals-sa-bpeltest-10-20-2008-111148651/install/petals-su-bpeltest/proces
s.wsdl'.
[petals.container.components.petals-se-orchestra]-INFO 2008-10-20 11:11:55,447 T
he BPEL Process /process.bpel has been succesfully deployed on Orchestra server
and is available on the endpoint {http://exemple.bpel.acoss.fr/exemple1}bpelTest
Servicepetals:autogenerate
[petals.container.components.petals-se-orchestra]-INFO 2008-10-20 11:11:55,447 B
PEL-Processes deployment on Orchestra server has been performed
[petals.DeploymentService]-INFO 2008-10-20 11:11:55,463 Service Assembly 'petals
-sa-bpeltest' succesfully deployed
[petals.container.components.petals-se-orchestra]-INFO 2008-10-20 11:11:55,635 N
ew Service Endpoint has been deployed : {http://exemple.bpel.acoss.fr/exemple1}b
pelTestService ->petals:uid:15CCF5D77FDBC7C9455288527478011871 (INTERNAL):subdom
ain1/0/petals-se-orchestra
[petals.DeploymentService]-INFO 2008-10-20 11:11:55,635 Service Assembly 'petals
-sa-bpeltest' succesfully started


This is the log file on the Petals server :

INFO 2008-10-20 11:11:18,245 [Petals.Communication.RMIConnector]
    JMX RMI server started at : service:jmx:rmi:///jndi/rmi://localhost:7700/jmxRmiConnector
INFO 2008-10-20 11:11:42,573 [Petals.JBI-Management.InstallationServiceImpl]
    Component 'petals-se-orchestra' succesfully installed
INFO 2008-10-20 11:11:43,541 [Petals.Container.Components.petals-se-orchestra]
    Orchestra Intialization...


This is my process.bpel :

<process name="bpelTestService"
         targetNamespace="http://exemple.bpel.acoss.fr/exemple1"
         suppressJoinFailure="yes"
         xmlns:tns="http://exemple.bpel.acoss.fr/exemple1"
         xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
         >

    <!-- Import the client WSDL -->
	<import location="process.wsdl" namespace="http://exemple.bpel.acoss.fr/exemple1" 
	        importType="http://schemas.xmlsoap.org/wsdl/" />
         
    <!-- ================================================================= -->         
    <!-- PARTNERLINKS                                                      -->
    <!-- List of services participating in this BPEL process               -->
    <!-- ================================================================= -->         
    <partnerLinks>
        <!-- The 'client' role represents the requester of this service. -->
        <partnerLink name="client"
                     partnerLinkType="tns:bpelTest"
                     myRole="bpelTestProvider"
                     />
    </partnerLinks>
  
    <!-- ================================================================= -->         
    <!-- VARIABLES                                                         -->
    <!-- List of messages and XML documents used within this BPEL process  -->
    <!-- ================================================================= -->         
    <variables>
        <!-- Reference to the message passed as input during initiation -->
        <variable name="input"
                  messageType="tns:bpelTestRequestMessage"/>
                  
        <!-- 
          Reference to the message that will be returned to the requester
          -->
        <variable name="output"
                  messageType="tns:bpelTestResponseMessage"/>
    </variables>

    <!-- ================================================================= -->         
    <!-- ORCHESTRATION LOGIC                                               -->
    <!-- Set of activities coordinating the flow of messages across the    -->
    <!-- services integrated within this business process                  -->
    <!-- ================================================================= -->         
    <sequence name="main">
        
        <!-- Receive input from requester. 
             Note: This maps to operation defined in processName.wsdl 
             -->
        <receive name="receiveInput" partnerLink="client"
                 portType="tns:bpelTest"
                 operation="process" variable="input"
                 createInstance="yes"/>
                 
        <assign validate="no" name="Assign">
            <copy>
                <from>$input.payload/tns:input</from>
                <to>$output.payload/tns:result</to>
            </copy>
        </assign>
        
        <!-- Generate reply to synchronous request -->
        <reply name="replyOutput" 
               partnerLink="client"
               portType="tns:bpelTest"
               operation="process" 
               variable="output"
               />
    </sequence>
</process>

This my process.wsdl :

<?xml version="1.0"?>
<definitions name="bpelTest"
        targetNamespace="http://exemple.bpel.acoss.fr/exemple1"
        xmlns:tns="http://exemple.bpel.acoss.fr/exemple1"
        xmlns:petals="http://petals.objectweb.org/"
        xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
        xmlns="http://schemas.xmlsoap.org/wsdl/"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        >

<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     TYPE DEFINITION - List of types participating in this BPEL process 
     The BPEL Designer will generate default request and response types
     but you can define or import any XML Schema type and use them as part 
     of the message types.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
    <types>
        <schema attributeFormDefault="unqualified" elementFormDefault="qualified" 
                targetNamespace="http://exemple.bpel.acoss.fr/exemple1" 
                xmlns="http://www.w3.org/2001/XMLSchema">

            <complexType name="bpelTestRequest">
                    <sequence>
                        <element name="input" type="string"/>
                    </sequence>
            </complexType>

            <complexType name="bpelTestResponse">
                    <sequence>
                        <element name="result" type="string"/>
                    </sequence>
            </complexType>
        </schema>
    </types>


<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     MESSAGE TYPE DEFINITION - Definition of the message types used as 
     part of the port type defintions
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
    <message name="bpelTestRequestMessage">
        <part name="payload" type="tns:bpelTestRequest"/>
    </message>
    <message name="bpelTestResponseMessage">
        <part name="payload" type="tns:bpelTestResponse"/>
    </message>

    
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PORT TYPE DEFINITION - A port type groups a set of operations into
     a logical service unit.
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    

    <!-- portType implemented by the processName BPEL process -->
    <portType name="bpelTest">
        <operation name="process">
            <input name="bpelTestRequestMessage" message="tns:bpelTestRequestMessage" />
            <output name="bpelTestResponseMessage" message="tns:bpelTestResponseMessage"/>
        </operation>
    </portType>

 
 <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     BINDING DEFINITION 
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
  
 	<binding name="bpelTestBinding" type="tns:bpelTest">
    	
    	<soap:binding style="rpc"
 			transport="http://schemas.xmlsoap.org/soap/http" />
   		
   		<operation name="process">
			<soap:operation soapAction="{http://exemple.bpel.acoss.fr/exemple1}process" />
			<input name="bpelTestRequestMessage">
    			<soap:body use="literal" 
					namespace="http://exemple.bpel.acoss.fr/exemple1" />
    		</input>
    		<output name="bpelTestResponseMessage">
    			<soap:body use="literal"
    				namespace="http://exemple.bpel.acoss.fr/exemple1" />
    		</output>
		</operation>
		
	</binding>
      
 <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     SERVICE DEFINITION 
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
  
    <service name="bpelTestService">
    	<port name="bpelTestPort" binding="tns:bpelTestBinding">
    		<soap:address location="petals:autogenerate"></soap:address>
    	</port>
    </service>

<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PARTNER LINK TYPE DEFINITION
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->    
    <plnk:partnerLinkType name="bpelTest">
        <plnk:role name="bpelTestProvider" portType="tns:bpelTest"/>
    </plnk:partnerLinkType>
    
</definitions>

This is my jbi.xml generated by the plugin :

<?xml version="1.0" encoding="UTF-8"?>
<!-- JBI descriptor for PEtALS' "petals-se-orchestra" (Orchestra), version 1.1 -->
<jbi:jbi version="1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jbi="http://java.sun.com/xml/ns/jbi"
xmlns:petals="http://petals.objectweb.org/"
xmlns:orchestra="http://petals.ow2.org/components/orchestra/version-1.0"
xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
xmlns:generatedNs="http://exemple.bpel.acoss.fr/exemple1">

<!-- Import a Service into PEtALS or Expose a PEtALS Service => use a BC. -->
<jbi:services binding-component="false">

<!-- Import a Service into PEtALS => provides a Service. -->
<jbi:provides 		
interface-name="generatedNs:bpelTest"
service-name="generatedNs:bpelTestService"
endpoint-name="petals:autogenerate">

<!-- CDK specific elements -->
<petalsCDK:wsdl>process.wsdl</petalsCDK:wsdl>

<!-- Component specific elements -->	
<orchestra:bpel>process.bpel</orchestra:bpel>			
</jbi:provides>
</jbi:services>
</jbi:jbi>

This is jbi.xml of my SA :

<?xml version="1.0" encoding="UTF-8"?>
<jbi version="1.0" 
xmlns='http://java.sun.com/xml/ns/jbi'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns:hw='http://petals.objectweb.org/'>
<service-assembly>
<identification>
<name>petals-sa-bpeltest</name>
<description>Service Assembly that registers endpoints for bpel test</description>
</identification>
<service-unit>
<identification>
<name>petals-su-bpeltest</name>
<description>Exemple Test bpel service unit</description>
</identification>
<target>
<artifacts-zip>petals-su-bpeltest.zip</artifacts-zip>
<component-name>petals-se-orchestra</component-name>
</target>
</service-unit>
</service-assembly>
</jbi>




-------------------- m2f --------------------

Read this forum topic online here:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=250#250

-------------------- m2f --------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20110316/052c9bbd/attachment.htm>


More information about the Users mailing list