"Jung , Dr. Christoph" wrote:
> >I gather that the JBoss server needs to restarted for this
> >to take effect? If so, is there no way to deploy
> >a jar file, which is not a bean, but which classes are
> >available in the context of any other bean in the deployed
> >server?
>
> In addition to Rickards answer, I would have proposed to use the
> ClassPathExtension-MBean. But if you intend to hot-develop/change/"redeploy"
> those classes (which requires to also redeploy every dependent bean!), this
> is AFAICS not possible this way.
>
> But as I mentioned in an earlier posting, we are currently discussing an
> extension of the J2EEDeployer which will allow to do such things int the
> near future ... and much more ... sophisticated ... comfortable ...
> bleeding-edge ;-)
>
> Best,
> CGJ
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
Hi
I think the best solution for me
at this point is to put all the beans
in one jar file This will enable
the beans to see each others classes.
This is not a problem for the beans is quite closely coupled.
So long, and thanks for all the fish
Manie Coetzee
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
