> This is definitely a possibility. Another I thought of is to have a
> "AreYouDeployedSuccessfully" mbean that interdependent mbeans like the
> ConnectionFactoryLoader mbean can register notificationListeners with. Via
> a button or perhaps periodically this bean can ask all its notifyees if
> they are completely set up and ok., producing some kind of report.
Sounds like the start of a DependencyManager, which would be cool... but
complicated =( Could try and keep it simple though. MBean's could register
with it and list there dependencies (on other MBeans), then it could notify
when the dependency is complete or when it has reached a timeout waiting to
resolve the dependency. The MBean could then decide what to do.
Does JMX have anything like that already? If not it sould like it would be
a valuable feature... and now that I think about it... rather simple.
> > Just a thought. I wish J2EE was more complete in this area. Perhaps
> > this
> > will be fixed, or perhaps we should provide a solution to the community
> > and
> > lets the gobble it up 'cause it will be so darn cool!
>
> I like the result, I'm not sure yet how to do it.
Magic...
There simply needs to be a unique link from deployable archive to a specific
configuration. This could be done by settitng a service id or something in
the archive. The deployment process would look up the config for that
service id then start it up.
The tricky part is when you want to startup more than one service based on
the same deployment archinve but with different configurations. I think
this could be solved by one more layer of indirection, such that the service
id or better yet the service archive id gets matched up with service ids and
then configurations.
Where each SAID is unique and there is a one to many relationship with
one more more SID. Each SID will have a many to one relationship with a
given configuration. In most cases this will be one to one, but there is no
reason why the same config couldn't be used by on other SID.
The hard part is the Configuration API. Perhaps simply wrapping JAXP will
work... don't know.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development