|Problem with cycles between EJB and Utility-project [message #181859]
||Tue, 24 October 2006 09:33
Originally posted by: juergen.hohmann.first-financial.biz|
we have a problem with cycles between an ejb-project (Demo_EJB) and many
utility-projects (Demo_Util and others).
At compile-time we need the ejb-project for most of the utility-projects.
In the ejb-project we have defined service-beans and base-classes.
So in the .classpath files of the util-projects i have an entry to the
ejb-project. Like this:
<?xml version="1.0" encoding="UTF-8"?>
<classpathentry kind="src" path="src"/>
path=" org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.inte rnal.debug.ui.launcher.StandardVMType/jre1.5.0_06 "/>
<classpathentry combineaccessrules="false" kind="src" path="/Demo_EJB"/>
<classpathentry kind="output" path="build/classes"/>
At runtime we have a dependency from the ejb-project to the
utility-projects. The service-beans calls other classes from the
utility-projects with reflection.
So we need entries for all utility-projects in the MANIFEST.MF of the
ejb-project like this:
The new eclipse 3.2.1 adds an entry <classpathentry exported="true"
kind="con" path="org.eclipse.jst.j2ee.internal.module.container"/> in the
classpath of the ejb-project and now we have the cycle, because all
entries of the MANIFEST.MF are added to the classpath of the ejb-project
and the utility-projects have a direct reference to the ejb-project.
Eclipse added the new entry by himself. So we need a configuration-switch,
that eclipse do NOT add the ear libraries automaticaly.
Have anyone an idea?
Thanks a lot
Powered by FUDForum
. Page generated in 0.01482 seconds