I think that the bpel engine read all the wsdl and bpel that are in the
folder.
You should put your two bpels and associated wsdl in separate folders and
use
classpath:fileValidation/FileValidation.bpel
and
classpath:login/Login.bpel
On 8/7/06, azwan <[EMAIL PROTECTED]> wrote:
Below is the log
At line "Activating component for:
[container=ServiceMix,name=fileValidationProcess] with service: .." it
initialize schema
"file:/home/azwan/tmp/servicemix-3.0-M2/apache-
servicemix-3.0-M2-incubating
/examples/mytest/mytest/epf/build/components/Login.wsdl"
which is wrong...it should be FileValidation.wsdl
Activating component for:
[container=ServiceMix,name=fileValidationProcess]
with service: {urn:imocha:soa:fileValidation}FileValidationService
component: [EMAIL PROTECTED]
Initializing component: fileValidationProcess
Initializing component
Initializing schema collection with baseUri:
file:/home/azwan/tmp/servicemix-3.0-M2/apache-servicemix-3.0-M2-incubating
/examples/mytest/mytest/epf/build/components/Login.wsdl
Component initialized
Activating component for: [container=ServiceMix,name=loginProcess] with
service: {urn:imocha:soa:login}LoginService component:
[EMAIL PROTECTED]
Initializing component: loginProcess
Initializing component
Initializing schema collection with baseUri:
file:/home/azwan/tmp/servicemix-3.0-M2/apache-servicemix-3.0-M2-incubating
/examples/mytest/mytest/epf/build/components/Login.wsdl
Component initialized
.....
......
Starting component
Component: fileValidationProcess activated endpoint:
{urn:imocha:soa:login}LoginService : loginBroker
Querying service description for
ServiceEndpoint[service={urn:imocha:soa:login}LoginService,endpoint=loginBroker]
Endpoint
ServiceEndpoint[service={urn:imocha:soa:login}LoginService,endpoint=loginBroker]
implements interface {urn:imocha:soa:login}StringBroker
Component started
Starting component
Component: loginProcess activated endpoint:
{urn:imocha:soa:login}LoginService : loginBroker
My servicemix.xml:
<sm:activationSpec id="fileValidationProcess"
service="fv:FileValidationService" endpoint="fileValidationProcess">
<sm:component>
<bpws:component
bpelResource="classpath:FileValidation.bpel" />
</sm:component>
</sm:activationSpec>
<sm:activationSpec id="loginProcess"
service="login:LoginService"
endpoint="loginProcess">
<sm:component>
<bpws:component
bpelResource="classpath:Login.bpel" />
</sm:component>
</sm:activationSpec>
I place Login.bpel, FileValidation.bpel, Login.wsdl and
FileValidation.wsdl
in classpath. And during activation of fileValidationProcess, it reads
Login.wsdl. How to specify the wsdl file to be read by
fileValidationProcess? I just specify bpelResources to
FileValidation.bpel
which then should read FileValidation.wsdl. Is this the caused?
Thanks..
--
View this message in context:
http://www.nabble.com/2-bpel-component-in-1-servicemix-instance-tf2061589.html#a5681973
Sent from the ServiceMix - User forum at Nabble.com.
--
Cheers,
Guillaume Nodet
