> |I don't remember what jason wanted with unix admin pellets, can someone
> |remind me?
>
> Jason made the point that the dynamic nature of RH was adapted to build
> administration frameworks. The installation of units on target machines can
> even include machine dependent stuff. Wrapping UNIX specific files inside
> the Java packaging and letting JBoss take care of the management of the SARs
> is something interesting. Most of this would be file based.
How is this a "pellet"... pellet reminds me of deer droppings.
> The point being here that Jetty requires its own files, MQ requires its own
> files, a workspace.
>
> Keep it simple, give a "directory" entry like the "META-INF" or even put
> META-INF/directory/...<files in natural directory>
Might want to keep it outside of META-INF, perhaps a peer to META-INF
(SERVICE-ROOT).
> and expand it like maplesden recommended (under the sar name). The question
> remains in my mind (I mentionned it with davidM) how does the main sar know
> to look up the directory... did someone mention something about JNDI?
Scott and I both mentioned JNDI, which is probably the easiest and most
portable solutio. Perhaps the Filessytem extention to JNDI could help?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
