- This topic has 1 reply, 2 voices, and was last updated 20 years ago by
.
-
Posts
-
Today I can’t create a war module within a subdir of a ear module project, this is very limiting, in that I want to use myeclipse to manage modules, and if I do so thru an ear… everything is on the same level, and can’t be nested.
Is there a specific reason as to why a war or ejb project can’t be within another project?
-jason poley
Jason,
Good question. Yes, there is a specific reason. Eclipse allows configuration of classloaders at the project level only. If nested projects were allowed it would be impossible to configure your project’s classloader in the development enviornment to be exactly the same as it will be when deployed in a J2EE server. With the current setup, we can ensure that you won’t get any compilation problems or ClassNotFoundExceptions when your application is deployed, but with nested modules we could not. In fact, with nested modules you could build an appication that you simply *can’t* deploy in a J2EE server, given then classloader nesting model that the J2EE server must implement.
