[ https://issues.jboss.org/browse/ARQ-593?page=com.atlassian.jira.plugin.sy... ] Work on ARQ-593 started by Vineet Reynolds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-593?page=com.atlassian.jira.plugin.sy... ] Vineet Reynolds commented on ARQ-593: ------------------------------------- The posted code fails (on both embedded and remote GF), as glassfish-resources.xml is expected to be present in the top-level of the archive. Arquillian eventually creates a WAR file for deployment onto Glassfish, and hence, the glassfish-resources.xml is expected to be present in WEB-INF/glassfish-resources.xml; instead, the posted code places glassfish-resources.xml in WEB-INF/lib/Project-ejb-1.0.0-SNAPSHOT.jar#META-INF/glassfish-resources.xml. The suggested workaround is to explicitly create a {{WebArchive}} with a {{glassfish-resources.xml}} in the {{WEB-INF}} directory, as shown in the below example: {code} @Deployment public static WebArchive createDeployment() { JavaArchive ejbArchive = ShrinkWrap.create(JavaArchive.class, "test-ejb.jar") .addClasses(GreetingManager.class, GreetingManagerBean.class, User.class) .addAsResource("META-INF/ejb-jar.xml", "ejb-jar.xml") .addAsResource("META-INF/persistence-test.xml", "META-INF/persistence.xml"); return ShrinkWrap.create(WebArchive.class, "test.war") .addAsLibrary(ejbArchive) .addAsWebInfResource("META-INF/glassfish-resources-test.xml", "glassfish-resources.xml"); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-593?page=com.atlassian.jira.plugin.sy... ] Vineet Reynolds edited comment on ARQ-593 at 9/30/11 3:40 PM: -------------------------------------------------------------- The posted code fails (on both embedded and remote GF), as glassfish-resources.xml is expected to be present in the top-level of the archive. Arquillian eventually creates a WAR file for deployment onto Glassfish, and hence, the glassfish-resources.xml is expected to be present in WEB-INF/glassfish-resources.xml; instead, the posted code places glassfish-resources.xml in WEB-INF/lib/Project-ejb-1.0.0-SNAPSHOT.jar#META-INF/glassfish-resources.xml. The suggested workaround is to explicitly create a {{WebArchive}} with a {{glassfish-resources.xml}} in the {{WEB-INF}} directory, as shown in the below example: {code} @Deployment public static WebArchive createDeployment() { JavaArchive ejbArchive = ShrinkWrap.create(JavaArchive.class, "test-ejb.jar") .addClasses(GreetingManager.class, GreetingManagerBean.class, User.class) .addAsResource("META-INF/ejb-jar.xml", "ejb-jar.xml") .addAsResource("META-INF/persistence-test.xml", "META-INF/persistence.xml"); return ShrinkWrap.create(WebArchive.class, "test.war") .addAsLibrary(ejbArchive) .addAsWebInfResource("META-INF/glassfish-resources-test.xml", "glassfish-resources.xml"); } {code} To summarize: the WAR archive deployed by Arquillian to Glassfish is a single module (although it contains EJBs). The {{glassfish-resources.xml}} is expected to be present in the top-level archive in the WEB-INF directory for the resources to be application scoped. Also, if module-scoped resources are to be used, an {{EnterpriseArchive}} must used for deployment with the {{glassfish-resources.xml}} file present in the EJB jar, as a {{WebArchive}} is treated as a single module (despite the EJB classes in WEB-INF/classes or WEB-INF/lib). was (Author: vineet.reynolds): The posted code fails (on both embedded and remote GF), as glassfish-resources.xml is expected to be present in the top-level of the archive. Arquillian eventually creates a WAR file for deployment onto Glassfish, and hence, the glassfish-resources.xml is expected to be present in WEB-INF/glassfish-resources.xml; instead, the posted code places glassfish-resources.xml in WEB-INF/lib/Project-ejb-1.0.0-SNAPSHOT.jar#META-INF/glassfish-resources.xml. The suggested workaround is to explicitly create a {{WebArchive}} with a {{glassfish-resources.xml}} in the {{WEB-INF}} directory, as shown in the below example: {code} @Deployment public static WebArchive createDeployment() { JavaArchive ejbArchive = ShrinkWrap.create(JavaArchive.class, "test-ejb.jar") .addClasses(GreetingManager.class, GreetingManagerBean.class, User.class) .addAsResource("META-INF/ejb-jar.xml", "ejb-jar.xml") .addAsResource("META-INF/persistence-test.xml", "META-INF/persistence.xml"); return ShrinkWrap.create(WebArchive.class, "test.war") .addAsLibrary(ejbArchive) .addAsWebInfResource("META-INF/glassfish-resources-test.xml", "glassfish-resources.xml"); } {code} To summarize: the WAR archive deployed by Arquillian to Glassfish is a single module (although it contains EJBs). The {{glassfish-resources.xml}} is expected to be present in the top-level archive in the WEB-INF directory for the resources to be application scoped. Also, if module-scoped resources are be used, an {{EnterpriseArchive}} is used for deployment with the {{glassfish-resources.xml}} file present in the EJB jar, as a {{WebArchive}} is treated as a single module (despite the EJB classes in WEB-INF/classes or WEB-INF/lib). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira