Large Enterprise App with ROO with multiple Modules

[camechis]

I am trying to figure out what the best practices would be for doing a large enterprise app with ROO that has multiple modules. We will probably Have a couple different web apps that would need to share a common Business Logic/Service Layer and maybe another that does some processing. My idea was to create multiple modules as such that would either run on Tomcat or TC-Server.

common-api = jar project
webapp1 = war project
webapp2 = war project
Business/Service/JPA = war project
Processing = war project

1. Is this a good practice to do if not what is?

2. How would the web app WAR talk with the Business/Service Layer WAR( Spring Remoting)?

Thanks for any help/suggestions.

[jbbarquero]

Supporting multiple modules for Roo is a very popular request.

My suggestion is that you vote for it in JIRA: https://jira.springsource.org/browse/ROO-120

[camechis]

I have voted for this request. Just trying to figure out what I have planned is a good thing and what the best practice is.

[Ben Alex]

We're planning on addressing ROO-120 in the Roo 1.2 release. It has some 74 votes at this time, making it one of the most popular outstanding issues.