At 20:43 10.11.00 , you wrote:
>Not at all, the mistake is on your end - I have hundreds of beans per jar ;)
same here. check all ejb-refs and the corresponding mappings, it's usually
something like that.
robert
>-mike
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Crossley
> > Sent: Friday, November 10, 2000 10:19 AM
> > To: Orion-Interest
> > Subject: Multiple beans in one jar
> >
> >
> > I seem to get different behavior when I package beans in my ear file
> > differently.
> >
> > Within one application (ear), I have one servlet, one session bean, and
> > one entity bean. Very simply, the first tells the second to create the
> > third.
> >
> > When I package the servlet up into its war file and each bean into its
> > own jar file, and then all three into the ear file, everything works
> > fine when auto-deployed on orion.
> >
> > However, if I package the two beans up into the same jar file, I get a
> > NameNotFoundException and the transaction is rolled back. The
> > ejb-jar.xml file looks as I would expect -- like a combination of the
> > separate ejb-jar.xml files in the working ear.
> >
> > Before I dig too much further, I was wondering if this was a known bug.
> > Should I just get in the habit of putting each bean in its own jar file?
> >
> > Thanks.
> >
> >
(-) Robert Krüger
(-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH
(-) Brüder-Knauß-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
