[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipselink-users] GFv3 + EclipseLink >=2.1.1: Remote EJB client cannot transfer JPA entities through remote session bean
- From: Tom Ware <tom.ware@xxxxxxxxxx>
- Date: Fri, 17 Dec 2010 11:46:04 -0500
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 126.96.36.199 (Windows/20090605)
Try running your Disconnected remote standalone Java (EJB) client application
with the java VM argument:
where <eclipselink.jar.location> is the path to your eclipselink jar. This will
enable weaving on the client side.
Xavier Callejas wrote:
On Vie 17 Dic 2010 10:00:44 Tom Ware escribió:
What is the application you are serializing from? A JPA application
running on glassfish? A standalone JPA application? How do you get your
|__ My EAR
|__ EJB module
|__ Session beans (facades for JPA and DTO entities)
( LAN / Internet (VPN) )
Disconnected remote standalone Java (EJB) client application
(it is a NetBeans Platform App.).
The EJB remote client application request entities to the server, DTOs but
some of them are pure JPA entities, this entities are binded to GUI forms, the
users change the entity and send it back to the server.
The client use remote (interfaces) ejb session beans to request these beans to
I do not serialize manually any entity.
The entity classes are in a separated .jar shared by the server and the
In the server side the Entity Manager is in the EJB module, the persitence
unit is configurated with JTA, I must list all the JPA entities in
persistence.xml because they are in a separated .jar. The session beans
facades are the one that make use of EntityManager.