"Stephen McConnell" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > Eike Stepper wrote: > > > hi stephen, > > > > the "bin/BLOCK-INF/block.xml" looks like: > > > > <container name='econ'> > > > > <classloader> > > <classpath> > > <repository> > > <resource id="avalon-framework:avalon-framework-impl" version="4.1.5"/> > > </repository> > > </classpath> > > </classloader> > > > > <component name='hello' class='tutorial.impl.HelloComponent'/> > > > > </container> > > > > The above definition looks like a block.xml file that was packaged > inside a jar file (in which case the enclosing jar is implicitly > included in the classpath). In you scenario your referencing the block > as a stand-alone definition in which case you need to include a jar file > that contains the HelloComponent class in the <classpath> declaration > and make sure the corresponding jar is put into your repository. > > So assuming that the jar file containing HelloComponent is named > hello-1.0.jar - you can put this into you repository under a group (e.g. > tutorials), then reference it in your classloader definition: > > <classloader> > <classpath> > <repository> > <resource id="tutorials:hello" version="1.0"/> > </repository> > </classpath> > </classloader>
ok, that sounds reasonable for jar archives and becomes important when releasing the projet. but i'm at the very beginning of playing with merlin. the sources are copied from the some of the tutorial chapters and compiled into a bin-folder (along with the block.xml and the .xinfos). i thought the merlin-deployment criteria had set the respective classpath. i even see the components being contextualized, configured, initialized and started on the console. for prototyping, debugging, etc. it would be more convenient to have merlin load the .class files instead of packaging a jar each time. /eike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
