ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naoki Okitsu" <okit...@m2.gyao.ne.jp>
Subject RE: About HelloWorld Process
Date Wed, 20 May 2009 12:19:44 GMT
Hi Daniel

Thank you for nice comment.
As you say,the behavior of Geronimo is strange.
Each time I select "Web Services>Test with Web Services Explorer",
process is created.Please see attached file.


This is deploy.xml
----------------------------------------------------------------------------
---
<?xml version="1.0" encoding="UTF-8"?>
<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
xmlns:helloWorld="http://helloWorld">
  <process name="helloWorld:HelloWorld">
    <active>true</active>
    <retired>false</retired>
    <in-memory>false</in-memory>
    <process-events generate="all"/>
    <provide partnerLink="client">
      <service name="helloWorld:HelloWorldProcessServiceService"
port="HelloWorldProcessPortPort"/>
    </provide>
  </process>
</deploy>
----------------------------------------------------------------------------
---


This is HelloWorld.bpel
----------------------------------------------------------------------------
----<!-- HelloWorld BPEL Process [Generated by the Eclipse BPEL Designer]
-->
<bpel:process name="HelloWorld"
         targetNamespace="http://helloWorld"
         suppressJoinFailure="yes"
         xmlns:tns="http://helloWorld"
 
xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
         >

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

    <!-- =================================================================
-->         
    <!-- ORCHESTRATION LOGIC
-->
    <!-- Set of activities coordinating the flow of messages across the
-->
    <!-- services integrated within this business process
-->
    <!-- =================================================================
-->         
    <bpel:sequence name="main">
        
        <!-- Receive input from requester. 
             Note: This maps to operation defined in HelloWorld.wsdl 
             -->
        <bpel:receive name="receiveInput" partnerLink="client"
                 portType="tns:HelloWorld"
                 operation="process" variable="input"
                 createInstance="yes"/>
        
        <!-- Generate reply to synchronous request -->
        <bpel:assign validate="no" name="Assign">
            <bpel:copy>
                <bpel:from>
                    <bpel:literal
xml:space="preserve"><tns:HelloWorldResponse xmlns:tns="http://helloWorld"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <tns:result></tns:result>
</tns:HelloWorldResponse>
</bpel:literal>
                </bpel:from>
                <bpel:to variable="output" part="payload"></bpel:to>
            </bpel:copy>
            <bpel:copy>
                <bpel:from part="payload" variable="input">
                    <bpel:query
queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[tns:
input]]></bpel:query>
                </bpel:from>
                <bpel:to part="payload" variable="output">
                    <bpel:query
queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[tns:
result]]></bpel:query>
                </bpel:to>
            </bpel:copy>
        </bpel:assign>
        <bpel:reply name="replyOutput" 
               partnerLink="client"
               portType="tns:HelloWorld"
               operation="process" 
               variable="output"
               />
    </bpel:sequence>
</bpel:process>
----------------------------------------------------------------------------
----


This is HelloWorldArtifacts.wsdl
----------------------------------------------------------------------------
---
<?xml version="1.0"?>
<definitions name="HelloWorld"
        targetNamespace="http://helloWorld"
        xmlns:tns="http://helloWorld"
        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://helloWorld" 
                xmlns="http://www.w3.org/2001/XMLSchema">

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

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


<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     MESSAGE TYPE DEFINITION - Definition of the message types used as 
     part of the port type defintions
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->    
    <message name="HelloWorldRequestMessage">
        <part name="payload" element="tns:HelloWorldRequest"/>
    </message>
    <message name="HelloWorldResponseMessage">
        <part name="payload" element="tns:HelloWorldResponse"/>
    </message>

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

    <!-- portType implemented by the HelloWorld BPEL process -->
    <portType name="HelloWorld">
        <operation name="process">
            <input  message="tns:HelloWorldRequestMessage" />
            <output message="tns:HelloWorldResponseMessage"/>
        </operation>
    </portType>
  

<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     PARTNER LINK TYPE DEFINITION
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->    
    <plnk:partnerLinkType name="HelloWorld">
        <plnk:role name="HelloWorldProvider" portType="tns:HelloWorld"/>
    </plnk:partnerLinkType>
    
    <binding name="HelloWorldSOAPBinding" type="tns:HelloWorld">
    	<soap:binding style="document"
    		transport="http://schemas.xmlsoap.org/soap/http">
    	</soap:binding>
    	<operation name="process">
    		<soap:operation
soapAction="http://helloWorld/process"></soap:operation>
    		<input>
    			<soap:body use="literal"></soap:body>
    		</input>
    		<output>
    			<soap:body use="literal"></soap:body>
    		</output>
    	</operation>
    </binding>
    <service name="HelloWorldProcessServiceService">
    	<port name="HelloWorldProcessPortPort"
binding="tns:HelloWorldSOAPBinding">
    		<soap:address
location="http://localhost:8080/ode/processes/HelloWorld"></soap:address>
    	</port>
    </service>
</definitions>
----------------------------------------------------------------------------
----


This is reponse SOAP message
----------------------------------------------------------------------------
---
- <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
- <soapenv:Body>
- <soapenv:Fault xmlns:java="java:package org.apache.ode.bpel.iapi">
  <faultcode>java:org.apache.ode.bpel.iapi.ContextException</faultcode> 
  <faultstring>An exception occured while invoking ODE.</faultstring> 
- <detail>
  <Exception>org.apache.ode.axis2.OdeFault: An exception occured while
invoking ODE. at
org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java:134)
at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessage
Receiver.java:67) at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODEMessage
Receiver.java:50) at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageRe
ceiver.java:96) at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145) at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HT
TPTransportUtils.java:275) at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:290) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:233) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128
) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102
) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http
11Protocol.java:583) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at
java.lang.Thread.run(Unknown Source) Caused by:
org.apache.ode.bpel.iapi.ContextException: The execution queue is backed
up... Forcing ContextException at
org.apache.ode.scheduler.simple.SimpleScheduler.schedulePersistedJob(SimpleS
cheduler.java:222) at
org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl.invoke(MyRoleMessageExc
hangeImpl.java:143) at
org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java:118)
... 20 more</Exception> 
  </detail>
  </soapenv:Fault>
  </soapenv:Body>
  </soapenv:Envelope>
----------------------------------------------------------------------------
----



Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message