It looks like I am unable to launch and debug jboss applications from within JBDS at all due to the above issue.  Every path to launch and debug a server application attempts to deploy the invalid bundles mentioned in my first post.

Looks like I will have to revert to launching jboss from the command line in debug mode and attaching to the jvm from the tool.  This is unfortunate because that is one more nice feature in JBDS I can't use.

If anyone can offer guidance on my question I would appreciate it.

Problem solved but I think there is a bug in the EE tools.

I created a new ejb project within the context of the ee project and it now publishes as part of the EAR instead of adjacent to it.

When I started I created a jar, ejb and web project.  Then I created a ee project and added the other 3 as EE modules.

For server publishing to work in this scenario it seems I have to create ejb modules from within the context of the ee module.  This was not a problem for the web project, only for the ejb project.

I will submit as a JIRA bug.

Max,

I tried to reproduce the problem from memory but was not able to.

1) Start in the Java perspective

2) Create a Java project

   2.0) Use default project contents is Checked

   2.1) Create a dummy class

3) Create an Ejb project

   3.0) Use default project contents is Checked

   3.1) Add new target server runtime

   3.2) Target Jboss EAP 5.0

   3.3) Set Jboss home to the JBDS bundled EAP 5.0

   3.4) Set JRE to Java 1.6

   3.5) Set configuration directory to my own configuration (copy of standard)

   3.6) I do not select Create and EJB Client Jar

   3.7) I do select Generate ejb-jar.xml deployment descriptor

   3.8) JBDS prompts me to open the Java EE perspective, I click on Yes

   3.9) Create a dummy EJB 3 stateless session bean with local interface only and container managed transactions

      3.9.1) I do not select any EJB 2.x options

4) Create a Jboss Tools Web/JSF project

   4.0) Use default project contents is Checked

   4.1) JSF environment is JSF 1.2 with Facelets

   4.2) Template is FaceletsKickStartWithoutLibs

   4.3) Servlet version is 2.5

   4.4) I set target runtime to the target runtime I created in step 3

   4.5) Target Server jboss-eap is checked

   4.6) JBDS prompts me to open the Web Development perspective, I click Yes

5) Create a Java EE Enterprise Application Project

   5.0) Use default project contents is Checked

   5.1) I set target runtime to the target runtime I created in step 3

   5.2) EAR version is 5.0

   5.3) Configuration is Default Configuration for my target runtime

   5.4) Java EE module dependencies: I select all of the components created above

   5.5) I check Generate application.xml deployment descriptor

   5.6) Content directory defaults to EarContent

   5.7) JBDS prompts me to open the Java EE perspective, I click on Yes

6) Open the Servers view

   6.1) Add the EE module to the server

   6.2) This is where the Ejb module would appear adjacent to the EE module instead of nested below.

        In this scenario I could not reproduce the problem; the Ejb module is nested under the EE module.

If I see it again I will post it.

Thanks.

This problem keeps coming back.  I've tried starting fresh with a new workspace and creating all new modules.  There are too many steps in the process for me to continue to identify a scenario that can be reproduced.  I simply don't have the time available.

What I am trying to do in the tool is pretty straight forward: create an EAR that contains a JAR, EJB and JSF Web component.

Surely someone else has run into the same problem.  If I continue to use JBDS I will have to run Jboss outside of the tool and attach remotely.

I really don't want to go down the path of building a Seam application and trying to remove all the stuff I won't use.  I'm not building a Seam application.  I'm building a classic layered web application using JSF => EJB3 => NaviteHibernate/POJO => MySQL.

Another limitation with this issue is I can't find a way to export or deploy the EAR exploded.  I can only export as a compressed EAR.  Not ideal for doing JSF.  I tried the Project Archives view to export an exploded EAR but it's behaving the same way as the Server Publish feature; it doesn't see that there is an EJB declared in the application.xml for the EAR.

Max,

I tried deploying using both JBoss AS deployer and Project Archives.  They both behave the same way.  I will try the Seam project approach and see what happens.

I will open a jira but probably not until the weekend.

Max,

I looked at the seam perspective.  In the ejb component it defaults to jpa configuration.  Is it possible to delete this and insert a hibernate.har tree using native hibernate configuration?

I see the seam root project contains the richfaces jars.  Why doesn't a JSF facelets project contain the same jars?  They are in the palette but not in the web app lib path.  I had to add them manually.

Seems like there is more emphasis on the seam tools than the others.  I would hope that the JBDS could support any development scenario consistent with the javaee specification.

Based on what I have seen so far I will pass on trying to use the seam tools.

I didn't intend to spark a philosophical debate.  Yes, native hibernate is not javaee but that is what I want to use.  That is simply a personal preference and Jboss does continue to support native hibernate.

I'm not bashing the tool.  I'm just trying to determine the best way to use the tool given my own requirements and personal preferences.  I do still believe there is a bug in JBDS regarding deployment of EE modules and I will follow up on this when I have time.  By the way, this issue is independent of how I use hibernate or whether or not I choose to use seam. 

Thanks for the suggestion to use a seam project as a workaround.