[daryl.robbins@mxi.com]

We have already purchased a number of copies of MyEclipse, but in order for us to deploy it more widely, there are a number of features that we would require. These include:

1. Use a module structure for EJBs
2. Module support for SARs (JBoss Services)
3. Multiple modules per project (e.g. two EJB’s in a single project)
4. Filter what gets copied to the module directory (and thus the server directory through synchronization)
5. Server deployment support for non-module projects (i.e. utility JARs)

Thanks.

[Riyad Kalla]

1. Use a module structure for EJBs

EJB projects are already considered modules of Enterprise Projects. This allows you to add/remove EJB projects from/to your Enterprise Project before deploying.

2. Module support for SARs (JBoss Services)

Because of the numerous custom extensions that JBoss supports, we added the ability to deploy Java Projects based on the name of the project. So for exaple you can name a project “Customer.sar”, when you deploy it, our deployment tool will JAR it up for your and deploy it as “Customer.sar”.

3. Multiple modules per project (e.g. two EJB’s in a single project)

This is supported, I’m curious why you thought this wasn’t supported? Each EJB Project can either be one EJB, or many EJBs. Some people like to group multiple EJBs that serve similar purposes together into a single project, for example product processing EJBs could be in a single “Product” EJB Project.

4. Filter what gets copied to the module directory (and thus the server directory through synchronization)

Can you explain what you mean by “module directory” and the behavior you need? I don’t quite follow, we might already support this.

5. Server deployment support for non-module projects (i.e. utility JARs)

Any Java Project can be marked as a dependency of any other type of project, if it is, and you have configured the deployment rules to JAR up and deploy dependent projects, then this is done for you.

[Author]

Posts