My bpel suitcase when deployed throws following exception. Can someone please help me to figure what is wrong here? I have also pasted my bpel and wsdl files
Error while loading process.
The process domain encountered the following errors while loading the process "H
ello" (revision "2_14_2007_1171468848577"): Can't find prefix for 'http://schema
s.xmlsoap.org/ws/2003/03/business-process/'. Namespace prefixes must be set on t
he Definition object using the addNamespace(...) method..
If you have installed a patch to the server, please check that the bpelcClasspat
h domain property includes the patch classes.
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcess
Holder.java:285)
at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(De
ploymentManager.java:804)
at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(D
eploymentManager.java:670)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDo
mainManagerBean.java:445)
BPEL file -
<?xml version="1.0" encoding="UTF-8"?>
<!--
BPEL Process Definition
Edited using ActiveWebflow(tm) Professional Designer Version 1.6.0 (http://www.active-endpoints.com)
-->
<process name="Hello" targetNamespace="http://Hello/0" suppressJoinFailure="yes" xmlns:tns="http://Hello/0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:wsdlARMALFServiceFlow="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:schemaARMALFServiceFlow="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:nsTTService="http://localhost:80/gsoap/ttwebservices.wsdl" xmlns:schemaTTService="urn:ttwebservices">
<!-- ================================================================= -->
<!-- PARTNERLINKS -->
<!-- List of services participating in this BPEL process -->
<!-- ================================================================= -->
<partnerLinks>
<!-- The 'client' role represents the requester of this service. -->
<partnerLink name="HelloClient" partnerLinkType="tns:AlfServiceFlow" myRole="AlfServiceFlowProvider" />
<partnerLink name="TTServicePartnerLink" partnerLinkType="nsTTService:TTServicePartnerLinkType" partnerRole="TTServiceProvider" />
</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="wsdlARMALFServiceFlow:ARMEventNotice" />
<!-- Variables generated by Studio -->
<variable name="DataElement" type="xsd:string" />
<variable name="TTService-GetItem" messageType="nsTTService:GetItem" />
<variable name="TTService-GetItemResponse" messageType="nsTTService:GetItemResponse" />
</variables>
<!--<correlationSets>
<correlationSet name="ServiceFlowIdCS" properties="tns:ServiceFlowId" />
</correlationSets>-->
<sequence name="SerenaSequence">
<receive createInstance="yes" operation="EventNotice" partnerLink="HelloClient" portType="wsdlARMALFServiceFlow:ARMALFServiceFlowEventNotice" variable="input">
<!--<correlations>
<correlation initiate="yes" set="ServiceFlowIdCS" />
</correlations>-->
</receive>
<assign name="InitVars">
<!-- InitVars generated by Studio -->
<copy>
<from expression=""This is default value"" />
<to variable="DataElement" />
</copy>
</assign>
<!-- Activities generated by Studio -->
<!-- Final Reply activity generated by Studio -->
<invoke name="TTService" operation="GetItem" inputVariable="TTService-GetItem" outputVariable="TTService-GetItemResponse" portType="nsTTService:ttwebservicesPortType" partnerLink="TTServicePartnerLink" />
</sequence>
</process>
WSDL file -
<?xml version="1.0"?>
<definitions name="AlfServiceFlow" targetNamespace="http://Hello/0"
xmlns:tns="http://Hello/0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:evt="http://www.eclipse.org/alf/schema/EventBase/1"
xmlns:ARMALFServiceFlow="http://www.eclipse.org/alf/schema/EventBase/1" >
<import namespace="http://www.eclipse.org/alf/schema/EventBase/1" location="resources/xml/ARMServiceFlows.wsdl" />
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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>
<xs:schema xmlns="http://Hello/0" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://Hello/0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="DataElement" type="xs:string" />
</xs:schema>
</types>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MESSAGE TYPE DEFINITION - Definition of the message types used as
part of the port type defintions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!--<message name="AlfServiceFlowRequestMessage">
<part name="payload" element="tns:ALFEvent"/>
</message>-->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PORT TYPE DEFINITION - A port type groups a set of operations into
a logical service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- portType implemented by the AlfServiceFlow BPEL process -->
<!--<portType name="AlfServiceFlow">
<operation name="process">
<input message="tns:AlfServiceFlowRequestMessage" />
</operation>
</portType>-->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARTNER LINK TYPE DEFINITION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="AlfServiceFlow">
<plnk:role name="AlfServiceFlowProvider">
<plnk:portType name="ARMALFServiceFlow:ARMALFServiceFlowEventNotice" />
</plnk:role>
</plnk:partnerLinkType>
<!--<bpws:property name="ServiceFlowId" type="xs:string" />
<bpws:propertyAlias messageType="ARMALFServiceFlow:ARMEventNotice" part="parameters" propertyName="tns:ServiceFlowId" query="/parameters/ARMALFServiceFlow:Base/ARMALFServiceFlow:EventControl/ARMALFServiceFlow:ServiceFlowId" />
-->
</definitions>
Thank you,
Meghana