Remote / Local Mismatch

[snavjot]

hi,

I have 2 entities CustomerLogin and CustomerProfile wth 1:N relation. Both local and remote interfaces are generated for them.

ServiceLocator locator = ServiceLocator.getInstance();
CustomerProfileHome cpHome = (CustomerProfileHome) locator.getHome(CustomerProfileHome.JNDI_NAME, CustomerProfileHome.class);

try{
CustomerProfile cp = cpHome.create(cpvo);
getCustomerProfiles().add(cp); // exception line
}

This is my CustomerLogin bean, when i create new CustomerProfile and try to add. it throws the following error.
I have created a REMOTE CustomerProfile. Then why is it expecting a LOCAL CustomerProfile??? Any clues.

BTW, the getCustomerProfiles() return empty collection in this case.


Caused by: java.lang.IllegalArgumentException: Object must be an instance of com.fz.customer.interfaces.CustomerProfileLocal, but is an isntance of [com.fz.customer.interfaces.CustomerProfile]
at org.jboss.ejb.plugins.cmp.jdbc.bridge.RelationSet.add(RelationSet.java:117)

TIA
Navjot Singh
Jboss 3.2.3

[aloubyansky]

Because this is the spec.

[snavjot]

spec of whom?

I have created a REMOTE object. I am trying to retreive a collection of REMOTE objects and trying to add the create REMOTE object to that collection.

Then why is EJB Container expecting the object to be LOCAL.

loubyansky, I am surely missing your point but you can help me understand. Any pointers.

thx
Navjot

[aloubyansky]

The EJB spec. You are trying to add a remote object to a CMR collection (local objects).

[snavjot]

Thanks a lot, loubyansky.

May i know then how should i proceed with my development. I have a collection of entity beans. Some are remote and some are local. I have got them in heritage from old team ;-)

I have started adding CMR fields to the relations.

How do i decide which of them should be moved on to LOCAL? I might end up converting all my entities to LOCAL. I can foresee lots of work on my part but this time i will do it for good.

TIA
Navjot Singh

[darranl]

All CMR fields must be Local, CMP fields can be either.

[aloubyansky]

It's a good practice to use local where possible.