On Mon, 28 Jan 2013 07:53:52 -0200, llama-king
wrote:
Sorry to dig up an old thread but seems I'm experiencing precisely the
same issue. Running on 5.3.6, injecting a service, calling method in
service that takes varargs.
Any ideas what might be the cause?
This doesn't look like it's r
http://tapestry.1045711.n5.nabble.com/T5-Varargs-in-service-methods-tp2426400p5719600.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional c
Hi Uli,
The VM argument doesn't help. I use tapestry 5.1.0.5 .
I tried to reproduce the bug in a empty app without luck.
It's hard, because I don't know were I am looking for.
In my main app I can still reproduce it and I also noticed that the
exception is dependent by the method parameter type
I don't think so, I can't reproduce it in 5.2.0-SNAPSHOT with a simple service concatenating a
variable list of string arguments. When running Jetty please try to give the
-Dorg.mortbay.jetty.webapp.parentLoaderPriority=true VM argument. It would also be helpful to know
which version of Tapestry
Interesting; probably a bug, possibly in Javassist.
On Tue, Jul 27, 2010 at 8:44 AM, joris wrote:
> Hi,
>
> if I implement a method with varargs in a tapestry service and try then
> to call it without parameters, I get the following exception:
>
> java.lang.LinkageError: loader constraint violati
Hi,
if I implement a method with varargs in a tapestry service and try then
to call it without parameters, I get the following exception:
java.lang.LinkageError: loader constraint violation: when resolving
interface method "..." the class loader (instance of
org/apache/tapestry5/internal/services
