- No explicit references to File or fileystems in the core - Dependency on a filesystem would have to be a dependency on a filesystem service with a more abstract API, for example, JNDI - Log4j intialization needs to be able to integrate with existing log4j usage - The embedded main needs to accept a parent class loader to which it delegates to - The current references to JMS need to be removed from the interceptors as this can be handled by log4j and we need to minimize the API requirements in low devices. - The base deployment information should not depend the standard XML descriptors directly. An object model needs to exist that would allow one to deploy components without having to go through a J2EE package. For example, it should be possible to take an existing service and expose it as an EJB without creating an ejb-jar.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jason Dillon" <[EMAIL PROTECTED]> To: "marc fleury" <[EMAIL PROTECTED]> Cc: "Jboss-Development@Lists. Sourceforge. Net" <[EMAIL PROTECTED]> Sent: Friday, February 15, 2002 3:57 PM Subject: Re: [JBoss-dev] embeddable Main > Can anyone find this information? > > --jason > > > On Mon, 2002-01-28 at 18:05, marc fleury wrote: > > I remember scott stark putting out a list of todos to make the embedable > > main real, like no reliance on filesystem necessarily, passing streams to > > deploy etc etc > > > > what would be the requirements to make JBoss totally embeddable in > > applications > > marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
