Rickard, before I dive in (let's move it to jBoss dev)
I believe we can probably work mostly from the ejb-jar.xml (with no CMP
stuff R>O, we can do O>R default)
however if this file is screwed up (as I understand might be the case with
the user now) we need that error since the EJB configuration is screwed up.
I believe Dan OConnor mapped these cases in a previous mail (<much
respect/>) and it seems we are running head first in his design. So in case
ejb-jar is f*cked up we need an explicit error I can catch and say "yo! get
your base file in order" and barf. For the jboss.xml and such we can be
more lenient (case 2 of Dan) with the message from Jim archer (as I have
now) so either explicit classes EJBJARSuckedUpException.java and such or
explicit returns I can check.
Can you tell me where the "exception" generation stands at right now? it
might save me some digging (with no doco, no comments, implicit stuff and in
the case of EJX, not even code ;-) yeah! yeah! yeah!
marc
_______________________
"welcome to the future"
-- A techno song--
_______________________
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> Sent: Tuesday, May 23, 2000 9:45 AM
> To: jBoss
> Subject: RE: [jBoss-User] A little help please
>
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> > Sent: Tuesday, May 23, 2000 9:32 AM
> > To: jBoss
> > Subject: Re: [jBoss-User] A little help please
> >
> >
> > Hey
> >
> > marc fleury wrote:
> > > in jBoss 1.0 part of the "ease of deploy" is that you did not
> > need all this
> > > stuff you could default to the "ejb" name in the ejb-jar.xml.
> I.e if a
> > > deployer doesn't provide a JNDI name it will default to the
> > "ejb" name from
> > > the main file, this makes sense for developers of beans that
> > don't really
> > > want to provide heavy "deployment" files.
> > >
> > > I will include the code that defaults it shouldn't take me long (maybe
> > > today),
> >
> > Hmm... just checked.. the JndiName *is* set to EjbName as default...
>
> Then it should not be dying on them... do you propagate a
> specific exception
> that says ejb-jar.xml screwed up?
>
> marc
>
> >
> > /Rickard
> >
> > --
> > Rickard �berg
> >
> > @home: +46 13 177937
> > Email: [EMAIL PROTECTED]
> > http://www.telkel.com
> > http://www.jboss.org
> > http://www.dreambean.com
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
