Marc,

I've been looking at what it would take to embed jboss.  This has been from
the perspective of trying to embed it into and IDE for development, but I
don't think that matters, there are many similar issues.  A couple of things
jump right out.

1.  Logging.  Does logging make sense in an embedded application?  Where do
you log?  This will be interest on a handheld!  The issue with no logging is
that everything seems to rely on it being there.  What are your thoughts?

2.  The ClassPathExtension class.  The extensions are relative to the jar
that the class is in.  This is jboss.jar in lib/ext.  I'm not sure if this
is the best approach.  It of course works fine in the space of jboss as the
server and controlling agent, but for an embedded applications I don't think
it would.  You at least want to provide a way to specify an absolute path.


Ken
----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: "Jboss-Development@Lists. Sourceforge. Net"
<[EMAIL PROTECTED]>
Sent: Monday, January 28, 2002 8:05 PM
Subject: [JBoss-dev] embeddable Main


> 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


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to