Hiya,
I can confirm that yes, it does appear to be a bug - an
IllegalAccessError is thrown when trying to access a protected method
on the contribution.
After playing with the code, a workaround is to declare the methods on
MyContribution as public.
public class MyContribution {
private String name;
public MyContribution(final String name) {
this.name = name;
}
public String getName() {
return name;
}
}
Then it works like a charm!
I've had another quick squizz at the IoC Docs (
http://tapestry.apache.org/tapestry-ioc-configuration.html ) but nope,
nothing there mentions you can't have *protected* methods in your
contribution classes.
Steve.
On 11 October 2011 15:13, antalk <ant...@intercommit.nl> wrote:
> Hi Guys,
>
> I would really appreciate if someone could have a look at this and see if it
> really is a bug...
>
> Thx.
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/TAP5-1233-re-open-java-lang-IllegalAccessError-tp4864790p4890925.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> 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
