ize the design.
Coming soon... :-)
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Adrian Brock
> Sent: Wednesday, February 01, 2006 4:57 AM
> To: jboss-development@lists.sourceforge.net
> Subject: [JBoss-dev] Generic Embedded
L PROTECTED] On Behalf Of
Adrian Brock
Sent: Wednesday, February 01, 2006 4:57 AM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] Generic Embedded/Bootstrap was RE: [JBoss-dev]
EJB3StandaloneBootstrap implementation
FYI
I am starting work on a prototype of the following three
new mo
pment@lists.sourceforge.net
Subject: Re: [JBoss-dev] EJB3StandaloneBootstrap implementation
Scott M Stark wrote:
> How can the scanClasspath() step be optimized/skipped in say an
embedded
> ejb3 project in jbosside where the data obtained during the scan was
> written out in an optimized
Hello Adrian,
This is really great, that is a much needed step for the MC usage/adoption
IMHO.
> I am starting work on a prototype of the following three new
> modules (I am not sure these are good names :-)
Yeah, not sure as well, but I am not sure i have great ideas at this point.
> 1) Inte
ent@lists.sourceforge.net
Subject: Re: [JBoss-dev] EJB3StandaloneBootstrap implementation
I think going the E-EJB3 route to start is a good idea as it will force
us to implement bare-bones implementations that do not have the idea of
a classloader or j2ee deployment schemes within them. Once we have
e
Burke
> Sent: Tuesday, January 31, 2006 9:28 AM
> To: jboss-development@lists.sourceforge.net
> Subject: Re: [JBoss-dev] EJB3StandaloneBootstrap implementation
>
> I think going the E-EJB3 route to start is a good idea as it will force
> us to implement bare-bones implementation
shing this forward.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Tuesday, January 31, 2006 9:28 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] EJB3StandaloneBootstrap implementation
I think going the E-EJB3 rout
I think going the E-EJB3 route to start is a good idea as it will force
us to implement bare-bones implementations that do not have the idea of
a classloader or j2ee deployment schemes within them. Once we have
e-ejb3 (really e-jboss) in place, it will force us to be careful about
adding thing
