Hi!
Christophe Demez wrote:
> I have create 2 jar because the "ServicesRegistry" can only create the Share
> beans after the Share.jar is deployed.
> The ServicesRegistry is like a startup class in WebLogic, it must start at
> the startup after all the others beans have been deployed.
> So, WebSphere and JBoss do not provide this feature, so I have create a
> static block that start the ServicesRegistry.
<vendor>
JBoss does indeed have startup class functionality. Actually, it's a
heck of a lot nicer than the WL startup classes, plus they're standards
based (JMX).
All you have to do is make an MBean (look at org.jboss.util.InfoMBean in
the JBoss sources for example) and register it in jboss.jcml.
</vendor>
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
