Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dali » Proper Dali use in EJB modules (client jars)
Proper Dali use in EJB modules (client jars) [message #434599] Wed, 26 September 2007 07:29 Go to next message
Alexandros Karypidis is currently offline Alexandros Karypidis
Messages: 32
Registered: July 2009
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.
Re: Proper Dali use in EJB modules (client jars) [message #434601 is a reply to message #434599] Thu, 27 September 2007 09:28 Go to previous messageGo to next message
Karen Butzke is currently offline Karen Butzke
Messages: 220
Registered: July 2009
Senior Member
This is a feature that 1.0 Dali does not support. Please enter an
enhancement request for this use case as we want to support more JPA
project setups in a future Dali release.

thanks,
Karen

Alexandros Karypidis wrote:

> 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.
Re: Proper Dali use in EJB modules (client jars) [message #434603 is a reply to message #434599] Fri, 28 September 2007 11:51 Go to previous message
Paul Fullbright is currently offline Paul Fullbright
Messages: 199
Registered: July 2009
Senior Member
Hi Alexandros,

How does Dali prevent you from editing your entities in your client
project? Have you tried adding the JPA facet to your client project
instead of your EJB project?

(It is true that the standard EJB project wizard doesn't help you to do
this.)

- Paul


Alexandros Karypidis wrote:

> 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.
Re: Proper Dali use in EJB modules (client jars) [message #606113 is a reply to message #434599] Thu, 27 September 2007 09:28 Go to previous message
Karen Butzke is currently offline Karen Butzke
Messages: 220
Registered: July 2009
Senior Member
This is a feature that 1.0 Dali does not support. Please enter an
enhancement request for this use case as we want to support more JPA
project setups in a future Dali release.

thanks,
Karen

Alexandros Karypidis wrote:

> 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.
Re: Proper Dali use in EJB modules (client jars) [message #606118 is a reply to message #434599] Fri, 28 September 2007 11:51 Go to previous message
Paul Fullbright is currently offline Paul Fullbright
Messages: 199
Registered: July 2009
Senior Member
Hi Alexandros,

How does Dali prevent you from editing your entities in your client
project? Have you tried adding the JPA facet to your client project
instead of your EJB project?

(It is true that the standard EJB project wizard doesn't help you to do
this.)

- Paul


Alexandros Karypidis wrote:

> 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.
Previous Topic:Proper Dali use in EJB modules (client jars)
Next Topic:How to use @PersistenceContext
Goto Forum:
  


Current Time: Fri Apr 18 11:58:21 EDT 2014

Powered by FUDForum. Page generated in 0.02197 seconds