|
| Hi,
I don't know if you already have this similar problem but your solution only works if the the Java object that is send from source to target is loaded by a common classloader.
Probably your example works because you have the send portlet and target portlet in the same porlet project.
If you have two portlet projects, one for target portlet and another to source portlet, it is possible that works too if you have you Java object in a jar on the EAR that contains the two portlets projects.
If you have two projects, and an EAR for each, and the Java class is duplicated on the two projects, when you receive the object in target portlet you will catch a ClassCastException because the object created on source portlet has loaded by source portle
t classloader and it is different from the object in target portlet classloader.
The only solution I could think is to deploy the jar with the common Java object in portal lib, but it is not a good solution (you have to reboot the portal every time you have to update the jar).
Best regards,
Helder Sousa
|
|