You have to place the ejb interfaces and associated classes into a
jar and load it with a URLClassLoader created by your mbean to isolate
the mbean's use of the ejb from the deployer so that redeployment works.
----- Original Message -----
From: "Victor M." <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 24, 2001 12:02 AM
Subject: [JBoss-user] Accessing EJBs from a custom service.
> Hello,
>
> I need to add a custom service (MBean). This MBean must be able to access
> (instanciate) the EJBs which are hosted on JBoss server itself.
> My MBean service starts correctly, but when attempting to instanciate an EJB
> (the example "interest" bean) it fails with exception:
>
> javax.naming.CommunicationException. Root exception is [Default]
> java.lang.ClassNotFoundException: com.web_tomorrow.interest.InterestHome
> [Default] at javax.management.loading.MLet.findClass(MLet.java:800
>
>
> Instanciating a bean from a "normal" Java client works perfectly.
> Also, when I add the interest EJB to JBOSS_CLASSPATH in run.bat, the bean
> can be accessed from the service. However, in this case, the server must be
> restarted when I deploy new beans and want them to be accessible from the
> service.(no "hot deploy").
>
> My questions are:
> 1) Is it possible to access the hosted EJBs from a service (MBean)
> without putting it explicitly on the classpath and losing "hot deploy"?
> 2) If yes, how should I do it?
>
> Any help is greatly appreciated.
> Thank you,
>
> Victor.
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
