Hi,
I am writing special deployer that needs to add some support jar files
to a classpath of a module being deployed (almost like with manifest.mf
but the list of jar files is kept in a different format). I checked how
MainDeployer handles manifest.mf and tried to do similar thing - for
each additional jar file I create/deploy sub-DeploymentInfo in
deployer's init method. I'm getting following deployment structure
DeploymentInfo d0 (url=file:///c:/ejb/classes/, deployer=JARDeployer)
+ DeploymentInfo d1 (url=file:///c:/support1/classes /,
deployer=JARDeployer)
Although all these deployments are reported as deployed by MainDeployer
mbean, my module does not see support classes. I have couple of question
here.
First of all - am I moving into right direction or it is not that easy
to put jar files on a classpath?
Second, what code is actually setting classpath of a deployment? I spent
few hours hunting for it but still have no clue.
Any help is appreciated.
--
Igor Fedorenko
Think smart. Think automated. Think Dynamics.
www.thinkdynamics.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
