Howard Lewis Ship wrote:
The limit hasn't change, and is enforced by Javassist and/or the JVM.
However, 5.2 may be adding more constructor arguments than 5.1 to
accomplish the same thing. I may need to think about restructuring
this a bit (i.e., if most of what I pass in to the constructor are now
pretty uniform) ... for instance, passing in an array of
ComponentValueProvider, rather than individual instances.
That sounds like a good idea.
I think the (jvm) limit is a maximum of 256 parameters on a constructor.
The page has 104 persisted fields, so it seems to be creating three
times as many parameters.
I would say it makes sense to put that in an array or list or something.
That is also how I would try to fix the offending page.
Kind regards,
Joachim
On Wed, Mar 10, 2010 at 11:25 AM, Joachim Van der Auwera
<joac...@progs.be> wrote:
On a specific page (which has generated content), I get a "Too many
arguments in method signature in class" exception when loading the page.
I am assuming this is related to the page having a lot of persistent fields
(over 100).
Is there a limit on the number of allowed persistent fields in a page? Has
this limit changed between 5.1 and 5.2 ?
Kind regards,
Joachim
--
Joachim Van der Auwera
PROGS bvba, progs.be
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
Joachim Van der Auwera
PROGS bvba, progs.be
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
