Hi, Chester
> Thanks for respond to my post.
>
> To make sure I understands this. ams.jar actually contains both EJB (Stateless session beans) and Entities Persistence (@Entity) and POJO helper classes.
>
> Glassfish reported that ams.jar has 0 EJB, which I don't understand why it is correct.
>
> I don't have a ejb-jar.xml, as I used the annotations only.
>
> But I did declare <module><ejb>ams.jar</ejb></module> in application.xml.
>
> ams.jar jas no web component (such as Servlet etc.), to change this
> we would I have to change it to
> <module><java>ams.jar</java></module>
>
> which doesn't seem right to me. The JEE5_SDK samples use <java> tag to store the application client .jar file
>
>
Sahoo must've thought you only had @Entity in the jar. If you have
Stateless bean inside, this should be a valid ejb jar. Can you please
check the server.log to see if there is any warnings w.r.t annotation
processing? If there are some problems in annnotation processing (due
to NoClassDefFoundError etc), the ejb component annotations might not be
processed properly, and as a result, we could find any valid ejbs inside
the jar.
Thanks,
- Hong
> Are you suggesting that I have to separate EJBs into a sparate .jar file (which GlassFish seems to suggest). and declare separate modules for ejb and non-ejb java file ?
>
> Your respond will be appreciated.
>
> I recently started EJB3 Project with Weblogic/Kodo JPA, in general, things went well (it doesn't complaint ams.jar has 0 EJB), except for one critical issue: under multiple-concurrent threads and a special parent-child data model, the transaction would fail and rollback (even though it works find under 1-thread). I sent the issue to BEA support, unfortunately, their support is really bad, it has dragged for months (1-2 months), I still haven't got any resolution.
>There are also other non-critital issues, where I won't mention here. Since I can't put this into production, I thought I would try some thing else.
>
> I then tried Weblogic + Toplink, I did not go very far with this combo, I got exceptions from toplink when I try to call EntityManager.flush(). The real issue, somehow the Enitity Manager doesn't seems to commit, i.e. there is no database record in the database after the EntityManager.persist() call. I am "sure" Toplink work and weblogic work. It could be the combo causing the problem. I post some message on Toplink forum and did not get any response.
>
>So now I am trying the GlassFish + Toplink, as this is the reference Implementation. Hope I got better luck this time.
>
>
>Chester
>[Message sent by forum member 'chesterxgchen123' (chesterxgchen123)]
>
>http://forums.java.net/jive/thread.jspa?messageID=225512
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>