[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [wtp-dev] EJb 3.0 and Ejb client project
- From: "Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
- Date: Thu, 24 Jul 2008 13:02:31 +0200
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acjs8hlwmRR3AS+2R9mzh3fV82PdIAAiWe2Q
- Thread-topic: [wtp-dev] EJb 3.0 and Ejb client project
Please see related bug https://bugs.eclipse.org/220156 that
explains why having a EJB client project requires having ejb-jar.xml descriptor.
It is not a restriction. It is requirement by the EJB spec to declare the client
jar in the ejb-jar.xml - hence we need to generate ejb-jar.xml.
There are absolutely no restrictions to have an ejb.jar.xml
and all your EJB bean metadata to be in annotations. In this case, the only
metadata in the ejb-jar.xml will be the ejb-client-jar tag, which does not have
a Java annotation alternative. I don't understand your worry here.
In WTP, for EJB 3.0 projects you
can't create EJB client project unless you have deployment descriptor, and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=238830, we are requiring deployment descriptor to
be generated when you create a client project.
I think that is a restriction we are imposing, it means
we cannot create an EJB client view.
Think of the case where you have EJb project with no
deployment descriptor and just have annotated beans, and the clients of
the beans are remote. Since you cannot have client view project, you wont
be able to distribute interfaces easily.
Java EE Tooling
IBM Rational Software