| Proper Dali use in EJB modules (client jars) [message #606109] |
Wed, 26 September 2007 11:29 |
 Alex Mising name
Messages: 149
Registered: March 2010 |
Senior Member |
|
|
Hi,
I'm using Eclipse WTP and Dali to write EJB 3.0 modules for JBoss 4.2.
All my EJB projects have "client JAR" projects, as I also use them from
an RCP client. My problem is that Dali/WTP forces me to put Entities in
the "server" project and not the "client JAR" project, as follows:
my.ejb.prj
MyBean
MyEntity
my.ejb.prjClient
MyBeanRemote (interface)
Short story: I need to move MyEntity to the client project, but this
breaks Dali.
Long story: Under EJB 3.0, it is acceptable to pass entities back and
forth among the application server / remote client: they just become
detached (and must be merged if returned to the server for use). To do
this, I just move MyEntity from my.ejb.prj to my.ejb.prjClient (it is
still available to MyBean because the server side implicitly depends on
the client project and has it in its classpath). But then Dali stops
working (the "JPA Details" view is no longer attached to the editor as
if I am no longer editing an Entity).
As a result, I now have 2 copies (one in each project) and I edit the
one in my.ejb.prj, having to update my.ejb.prjClient every time I make a
change.
|
|
|
Powered by
FUDForum. Page generated in 0.02813 seconds
] 
Search
Help
Register
Login
Home
