it is the first. So in 1.6 I'll follow ant's suggestion to put all necessary utilities on the top-level of the contribution-zip. -- Sebastian
> -----Original Message----- > From: Luciano Resende [mailto:[email protected]] > Sent: Friday, September 03, 2010 1:10 AM > To: [email protected] > Subject: Re: FW: Q: Adding classes to a node > > On Thu, Sep 2, 2010 at 3:29 PM, Millies, Sebastian > <[email protected]> wrote: > > I don't understand. When I start the DomainManagerLauncher and then > use the > > web ui to configure and start my nodes, I can only set the classpath > for > > the VM in which the domain manager runs. Do all nodes in the domain > > automatically share that classpath? I can't imagine that, as the > nodes > > may be distributed over differently configured servers. (I am not > talking > > deployment of web apps etc., just simple Java components in a Tuscany > > runtime.) > > > > -- Sebastian > > Is you scenario more like, your "contribution" that is deployed to a > node requires a system utility or some java code such as Log4J, then > you need to have that available in the classpath or the distribution > being used for that node. If the code is really more like business > functionality needed by your contribution, then your scenario looks > more like what is described in the Tutorial/store where most of the > contributions uses store-assets and then there are imports/exports of > resources, packages, etc. >
