Eclipse Community Forums: ServerTools (WTP) » Circular Project References?

Home » Language IDEs » ServerTools (WTP) » Circular Project References?

Circular Project References? [message #108173]

Mon, 30 May 2005 14:26

Eclipse User

Originally posted by: cmarshall.jlc.net

This may be a newbie mistake but I am not seeing a way around it. I have
an application that I created about a year and a half ago using XDoclet
1.2 to generate various pieces based on the annotations in the main Entity
and Session beans. I have been trying to get the same application put
together using the web tools and JST and I have run into a strange
circular series of references. I created an EJB project following the
tutorial that is available and this create both a project where I first
created a session bean (under Ejb Projects) and a "client" project (under
Other Projects). I eventually imported all my session, BMP and CMP entity
beans into the project. When all the various artifacts (interfaces, etc.)
are generated by XDoclet they are moved to the "client" project. The
session beans make reference to the local home interface of the entity
beans and thus the Ejb Project needs the client project on its build path.
For some reason XDoclet is generating concrete classes for each entity
bean that are also be placed in the client project. These sub-class or
extend my entity beans and thus the client project now needs the Ejb
project on its build path. This is then a circular reference and Eclipse
is not to happy about this. What was supposed to happen? How should this
have been structured?
I am using Eclipse 3.1M7 and the integration builds from May 26.

Chris Marshall

Re: Circular Project References? [message #112496 is a reply to message #108173]

Sat, 18 June 2005 18:38

Eclipse User

Originally posted by: cmarshall.jlc.net

I discovered some of the answer to my question. It appears that the
plugin that handles EJBs expects the beans the developer creates (as
opposed to what it generates) to have a name that ends with "Bean". This
raises the question, why is there this restriction? And second if there
is going to be this restriction why doesn't the plugin enforce it? The
plugin lets one create a session bean for example without the ending
"Bean" in the name and things get very confused.

Chris

Previous Topic:	Problems with "Simple Web Project"
Next Topic:	No J2EE Web Project available

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 00:04:56 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter