Hi Rick, sorry I wasn't right. The two entities are NOT being created at the client side but they are read from the server via RMI. Then the add() method of one of them is called in order to create a new ManyToMany relationship between these two entities. The add() method then calls the other entities' add() method and the NPE is raised (I showed you the line the exception occurs).
We casted the entity to PersistenceCapable as you requested. In our JUnit integration test a com.ibm.ws.persistence.kernel.WsJpaStateManagerImpl state manager is used (this works). In our RCP client a org.apache.openjpa.kernel.DetachedStateManager state manager is used (this fails). -- View this message in context: http://openjpa.208410.n2.nabble.com/Strange-behaviour-on-ManyToMany-relationship-using-RCP-client-tp6985422p6991859.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
