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 you are using.

Uli

On 27.07.2010 17:58, Howard Lewis Ship wrote:
Interesting; probably a bug, possibly in Javassist.

On Tue, Jul 27, 2010 at 8:44 AM, joris<jogo...@web.de>  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 violation: when resolving
interface method "..." the class loader (instance of
org/apache/tapestry5/internal/services/ComponentInstantiatorSourceImpl
$PackageAwareLoader) of the current class, ..., and the class loader
(instance of org/mortbay/jetty/webapp/WebAppClassLoader) for resolved
class, ..., have different Class objects for the type ... used in the
signature

Example:

public interface MyService{
        Data getData(Permission...permissions);
}

public class MyPage{

@Inject
private MyService service;

void onActivate(){
        service.getData();
}
}

It looks like the loader does not handle this special case.
Is this a bug or is there a reason why it behaves like that?

Joris


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org






---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to