Hi Chiara, are you sure that you adapted everything you need (correctly) in your deploy.xml? I see that you try to call another Pipeline (AdaptFileCrawlerWorkerOutput) in your PhotoProcessingPipeline. Therefore you have to add both pipelines and some additional stuff in your deploy.xml: (see http://wiki.eclipse.org/SMILA/Documentation/BPEL_Workflow_Processor#Pipeline_invocations) If you think it should be fine, then it maybe helpful for us to see your deploy.xml and the AdaptFileCrawlerWorkerOutput.bpel. Regards, Andreas Von: smila-user-bounces@xxxxxxxxxxx [mailto:smila-user-bounces@xxxxxxxxxxx] Im Auftrag von Chiara Pasini Gesendet: Montag, 18. März 2013 11:51 An: Smila project user mailing list Betreff: Re: [smila-user] error after porting Hi, Afte fixing the deploy.xml another exception raises: Caused by: java.lang.ClassCastException: org.eclipse.smila.ode.PartnerRoleChannelImpl cannot be cast to org.apache.ode.axis2.ExternalService In attachment the SMILA.log file. C 2013/3/18 Jürgen Schumacher <waeller@xxxxxxxxx> I see in the SMILA.log, that the 'PhotoProcessingPipeline' has been compiled successfully, but it is not deployed and registered: this is because you didn't add the pipeline to the deploy.xml file in configuration/org.eclipse.smila.processig.bpel/pipelines. At least it looks the same on my system if I remove a pipeline from this file. After a new update of the configuration files and of the SMILA.launch packege the Crawler finally started. But it fails to invoke the next Pipeline: java.lang.IllegalArgumentException: Configured pipeline 'PhotoProcessingPipeline' doesn't exist. The pipeline starts with no errors with: And it works perfectly with the older version of SMILA. In attachment the SMILA.log file and all the configuration files. 2013/3/15 Jürgen Schumacher <waeller@xxxxxxxxx> Strange, there are no messages from the JobManager in this log. Did you tweak the log4j.properties somehow so that they got lost? Or have been routed to another log file? Also, in the smilaconsole.txt I see no message that the fileCrawler worker has been started. This could be caused missing service dependencies. Make sure that bundles - org.eclipse.smila.importing.compounds.simple - org.eclipse.smila.importing.state.objecstore And we see that the definition of the fieCrawling job is not complete for SMILA 1.1 and above, especially the mapping part is missing. See http://wiki.eclipse.org/SMILA/Documentation/Importing/Crawler/File for details. Also, you must use the workers.json file from the SMILA release you are using. Yours still seems to be the one from SMILA 1.0. Maybe you also need to update the workflows.json to get in sync again. _______________________________________________ smila-user mailing list smila-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/smila-user
_______________________________________________ smila-user mailing list smila-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/smila-user
|