curiously, the error message is similar to my other post "classloader
error constructing helper classes within service" however I was not
passing page classes (or anything tapestry-managed) around...
On 24/02/2012 9:23 PM, Beat Durrer wrote:
Hey guys
I just spent a whole day on a issue, where a service call in a page class
ended in a "java.lang.LinkageError: loader constraint violation the class
loader {...} of the current class, MyPage, and the class loader {...} for
resolved class, MyService, have different Class objects for the type used
in the signature"
What I did was totally stupid (at least in hindsight): I accidentally
passed the page object to the service:
MyPage{
Object onSuccess(){
return myService.doStuff(this);
}
}
It's no suprise that that wouldn't work when accustomed to J2EE and remote
stuff, althrough I didn't expect that to happen in T5.3.
The whole point of this mail:
DO NOT pass your page object to the service.
Cheers
Beat
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
