ummm...
being able to configure the container on a "per bean" basis, is truly a
"alien" feature... something out there that i think is truly kick ass.
However having the beans carry the same information over and over is
completely stupid... moreover, if you missed a hair in those files, jboss
used to roll over and die... not good.
This is why we provided default so that if you don't provide the file you
still stay alive... I guess we need to document that better in the user
guide (right now it sounds a bit magic).
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Saturday, July 01, 2000 8:48 AM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] Why Container Configurations?
>
>
> Hi!
>
> Aaron Mulder wrote:
> > I have a jboss.xml for a single EJB. It contains 66 lines of
> > "container configurations" for 4 configurations, only 1 of
> which is used.
> <snip>
>
> Fixing this is part of Project Game Over (see project list at
> jboss.org).
>
> Yes, it is not good, although I think it is "ok". For now.
>
> The principle is good (being able to share settings between beans), but
> the execution could be better.
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
