Re: [smila-user] SMILA vs Human Computing |
The problem is that the BPEL processor cannot find the pipelet class. There are a lot of reasons why this can happen, please check http://wiki.eclipse.org/SMILA/Documentation/HowTo/How_to_write_a_Pipelet#Implementation (especially the part about the pipelet description file in the “SMILA-INF” directory). Note that the pipelet class name must be used strictly case-sensitive in the description file and the pipeline. Finally make sure that your pipelet bundle is checked in the SMILA launch configuration so that it is available for SMILA. Cheers, Jürgen. From: smila-user-bounces@xxxxxxxxxxx [mailto:smila-user-bounces@xxxxxxxxxxx] On Behalf Of Ilio Catallo Hi Juergen, we're having some troubles in getting the pipeline work properly. In particular, while executing the "job 1", once the first pipelet is called we get the following error in SMILA.log: org.eclipse.smila.processing.ProcessingException: Error processing BPEL workflow RetrieveLogoInstancesPipeline: Invocation of pipeline element RetrieveLogoInstancesPipeline/RetrieveLogoInstancesFromGooglePipelet@36 failed due to pipelet error: Pipelet of class it.polimi.RetrieveLogoInstance.RetrieveLogoInstancesFromGooglePipelet for activity RetrieveLogoInstancesPipeline/RetrieveLogoInstancesFromGooglePipelet@36 is not yet instantiated. Our .bpel definition for the pipeline is the following: <process name="RetrieveLogoInstancesPipeline" targetNamespace="http://www.eclipse.org/smila/processor" xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:proc="http://www.eclipse.org/smila/processor" xmlns:rec="http://www.eclipse.org/smila/record" xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"> <import location="processor.wsdl" namespace="http://www.eclipse.org/smila/processor" importType="http://schemas.xmlsoap.org/wsdl/" /> <partnerLinks> <partnerLink name="Pipeline" partnerLinkType="proc:ProcessorPartnerLinkType" myRole="service" /> </partnerLinks> <extensions> <extension namespace="http://www.eclipse.org/smila/processor" mustUnderstand="no" /> </extensions> <variables> <variable name="request" messageType="proc:ProcessorMessage" /> </variables> <sequence name="RetrieveLogoInstancesPipeline"> <receive name="start" partnerLink="Pipeline" portType="proc:ProcessorPortType" operation="process" variable="request" createInstance="yes" /> <extensionActivity> <proc:invokePipelet name="RetrieveLogoInstancesFromGooglePipelet"> <proc:pipelet class="it.polimi.RetrieveLogoInstance.RetrieveLogoInstancesFromGooglePipelet" /> <proc:variables input="request" output="request" /> <proc:configuration /> </proc:invokePipelet> </extensionActivity> <reply name="end" partnerLink="Pipeline" portType="proc:ProcessorPortType" operation="process" variable="request" /> <exit /> </sequence> </process> deploy.xml should be fine: <process name="proc:RetrieveLogoInstancesPipeline"> <in-memory>true</in-memory> <provide partnerLink="Pipeline"> <service name="proc:RetrieveLogoInstancesPipeline" port="ProcessorPort" /> </provide> </process> </deploy> We're wondering which is the problem that doesn't allow us to invoke the pipeline. Thanks, Cheers, Ilio. Il giorno 28/feb/2012, alle ore 08:57, Jürgen Schumacher ha scritto:
our workflows.json is completely equivalent to yours (the only difference is that the startAction is
Our proof-of-concept retrieveLogoInstancesPipelet.process()
The questions are:
How is it possible to save the variable record in the object store associated to the output bucket?
|