Hi!,
I read that people are using Value Objects (VO) with Entity JB because is
better in terms of RMI. But, for my project I need to used diferent VO for
the same Entity so the program can adopt to diferent clients. I thought
that using diferent VO and a general way for reading then was enought but I
also read that you need to declare the get and set methods abstract for the
EJB so the container can implemente them. ( I thought using CMP)
Without using BMP (Bean Managed Persistence) do have any idea ou know any
design pattern to resolve this issue ?
The ideia is that the system allways manipulates the same Entity, but the
entity details differ from client to client. (If the client makes cars the
details will be color, model, etc.. if the client produces furneture, the
details will be the the size, the type of material, etc..)
Aidan - 10 Jun 2004 14:47 GMT
> The ideia is that the system allways manipulates the same Entity,
> but the entity details differ from client to client. (If the
> client makes cars the details will be color, model, etc.. if the
> client produces furneture, the details will be the the size, the
> type of material, etc..)
Not quite sure what kind of CMP EJB you are planning - something
with generic text fields?
You might want to look at https://strutsejb.dev.java.net/
StrutsEJB which has an example of using dynamic map based VOs with
CMP EJBs.
A.