[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-7423) examples with datasources does not get deployed before "make deployable" is called

[ https://issues.jboss.org/browse/JBIDE-7423?page=com.atlassian.jira.plugin... ] Snjezana Peco resolved JBIDE-7423. ---------------------------------- Resolution: Done https://jira.jboss.org/browse/JBAS-8377 is fixed in JBoss AS 6.0.Final. Now the booking22 example can be deployed to JBoss AS 6.0 and JBoss EAP 5.x. In order to deploy this example to JBoss AS 6.0, I had to add the following changes: - removed META-INF/MANIFEST.MF from the bookin22-ejb project - added jboss-seam.jar to the Build Path of the booking22-ejb and booking22-test project - added <context-param> <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name> <param-value>Mojarra-1.2</param-value> </context-param> to booking22/WebContent/WEB-INF/web.xml The last change is necessary because Seam 2.x isn't compatible with JSF2. See: https://issues.jboss.org/browse/JBSEAM-4637 https://issues.jboss.org/browse/JBSEAM-4652 https://issues.jboss.org/browse/JBSEAM-4639 https://issues.jboss.org/browse/JBSEAM-4621 On the other hand, JBoss AS 6.0 adds the JSF libs when finding faces-config.xml, but doesn't check a JSF version and adds Mojarra 2.0 by default. The above mentioned context parameter ensures JBoss AS 6.0 adds JSF 1.2 that works correctly with Seam 2.x. Since the booking22-ds.xml datasource is defined in jboss-app.xml, the user doesn't have to call "Mark as Deployable". -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira