[kepler-dev] Issues in loading a new actor module

[David Welker]

Hi Balachandar,

It sounds as though you need to use a separate class loader for your  
module, at least for now. If it was not so close to the time for the  
release, I would look into discussing with the appropriate maintainers  
of those modules the possibility of upgrading the jars to the versions  
you need.

First, lets look at what you did and understand why it didn't work.  
When your module is in the HIGHER PRIORITY position (above the other  
modules in modules.txt) your jars are used for EVERYTHING at run time.  
If the jars are compatible, this doesn't matter. But in this case, the  
jars are not compatible, and you are breaking existing functionality.  
When you put your module in the LOWER PRIORITY position (below the  
other modules in modules.txt), then the jars provided by the system  
are used for EVERYTHING at run time. Which means you do not get the  
additional functionality you expect from the new jars you have added.

So, here is the solution. You need to use a separate class loader, and  
explained in the build system instructions. In this email to me, you  
say that you put the actor name in classloaders.txt. But you need to  
put the MODULE name, not the actor name in that file. You also have to  
put the module "multiple-class-loaders" in the highest priority  
position in the suite you are developing. This is described in the  
build system instruction here:

https://kepler-project.org/developers/teams/build/documentation/build-system-instructions 
#using-a-separate-class

So, can you try this? If it doesn't work, let me know and we will look  
more deeply into this.

-David


On May 12, 2010, at 5:01 AM, AMARNATH, Balachandar wrote:

> Dear David Welker
>
>
> My issue is straight forward that is it possible to have separate  
> set of jar files to be loaded for my module ? Can I get some example  
> solution ?
>
>
> I have wrote a new actor using kepler 2.0 that uses the following  
> jar file 'castor-1.0.jar and jsch-0.1.37.jar'. However, when i run  
> the actor from the workflow canvas, it is not functioning as i  
> exepected and i found that is due to the conflicts of similar jars  
> 'castor-0.95.jar' and jsch-0.1.31' present in the module 'actors-2.0  
> and ssh-2.0' respectively.
>
> I tried to load my actor module ahead of 'actors-2.0' and 'ssh-2.0'  
> by editing modules.txt in build-area folder. This fixed the issue  
> but right clicking over the actor is not functioning ..!!!.
>
> I have also tried to create a text file callled 'environment.txt' in  
> module-info folder of my actor which i specified the CLASSPATH and  
> its values, didnt work
>
> I also created a text filed classloaders.txt in build-area  
> specifying my actor name in it so that kepler understands this actor  
> requires a separate class loader. Didnt work.
>
> Can you help me out to come of this issue, I have also posted this  
> to forum :)
>
>
> with thanks and regards
> Balachandar
>
> The information in this e-mail is confidential. The contents may not  
> be disclosed or used by anyone other than the addressee. Access to  
> this e-mail by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus  
> immediately and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or  
> completeness of this e-mail as it has been sent over public  
> networks. If you have any concerns over the content of this message  
> or its Accuracy or Integrity, please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated  
> virus scanning software but you should take whatever measures you  
> deem to be appropriate to ensure that this message and any  
> attachments are virus free.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20100512/c01384d4/attachment.html>