For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 21 years, 11 months ago by
.
-
Posts
-
Hi,
I have an enterprise application composed of EJB and a Web module.
Some of the packages are shared utilities and are used by the two modules.I am working with JBoss 3.2.3 and for developement I use the exploded deployment way of working.
Originally my application was developed under JBuilder where the entire source tree was structured under a single src directory. When I ported to MyEclipse, I used the linked-resource folder to point my ‘src’ to my real ‘src’ directory and in each project (EJB or Web module) I used the filter to exclude the unnecessary. Now, the linked resources are not such a happy feature since they are not relative but absolute, a clear disadvantage making the project fixed on an absolute path in the file system.
My question is what is the best or alternative way to structure my sources under Eclipse/MyEclipse? Or better say, what is recommended?
Thanks in advance,
Erez
We typically setup our EAR projects such that common code shared between an EJB and Web project is packaged in the EJB project. Scan down the thread in the following link and see my last comment.
I tried it but the link seems to be broken,
Erez
I tried the link after I posted it as well as the version you posted with no problems.
Here is a fragment of that thread that I was referring:
So I set up my EJB projects to hold all DO/VO objects transfered from the biz service tier to the web tier. This assumes that the web module and ejb modules will be deployed as part of the same EAR. The MyEclipse EAR project creation mechanism sets up a classpath dependencies from Web Modules to EJB Modules analogous to the manner in which J2EE hierarchical classloader behaviors. This is one reason that MyEclipse does not support nested modules within an EAR project like some other OSS Eclipse products have tried. The advantage of the MyEclipse model is that you are able to discover at design time if you have partitioned your modules correctly. Otherwise you’re stuck diagnosing more costly runtime classnotfound exceptions
.
