Hi all,
I've created a persistence jar using the embedded version of EJB3 (i.e. 
persistence.xml that points directly to a database, not JDNI).

This has been tested and works fine.  When I deploy the persistence jar 
directly to /deploy (with an ejb3.deployer-enabled jboss), it deploys fine.

However, putting the persistence jar in a SAR causings a lot of issues.  Would 
this be a normal circumstance of putting an EJB3-embed persistence jar into a 
SAR for use with an EJB3 session bean, or should it never be put in a SAR?

thanks,
-D

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910143#3910143

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910143


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to