On Fri, 24 Feb 2012 11:36:30 -0200, Beat Durrer wrote:
Thanks, good to know.
However, I am pretty sure that it's just bad practive to pass a page
around. In my case, all I wanted was a service that could control the
workflow...
and the pageName is all it needs for that.
Agreed. :) You co
Thanks, good to know.
However, I am pretty sure that it's just bad practive to pass a page around.
In my case, all I wanted was a service that could control the workflow...
and the pageName is all it needs for that.
2012/2/24 Thiago H. de Paula Figueiredo
> On Fri, 24 Feb 2012 08:23:47 -0200,
On Fri, 24 Feb 2012 08:23:47 -0200, Beat Durrer wrote:
Hey guys
Hi!
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
r
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
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 typ
