Try running your Disconnected remote standalone Java (EJB) client application
with the java VM argument:
-javaagent:<eclipselink.jar.location>/eclipselink.jar
where <eclipselink.jar.location> is the path to your eclipselink jar. This will
enable weaving on the client side.
-Tom
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
>> entity manager?
>
> Database
> |
> Glassfish v3
> |__ EclipseLink
> |__ 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
> the server.
>
> I do not serialize manually any entity.
>
> The entity classes are in a separated .jar shared by the server and the
> client.
>
> 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.
>
>
> Regards.
> Xavier.