Thanks for all the responses. Switching to T5.1.5 fixed the problem.
thanks,
Joe
buckofive wrote:
>
> Hi Joe/Howard,
>
> I have ran into this same problem a while back and oddly enough (just the
> other day) I finally got around to filing a JIRA
> (https://issues.apache.org/jira/browse/TAP5
Hi Joe/Howard,
I have ran into this same problem a while back and oddly enough (just the
other day) I finally got around to filing a JIRA
(https://issues.apache.org/jira/browse/TAP5-1051). The only help/clue I can
give to the T5 team is that the BeanEditor was working at one time in
T5.2.0-SNAPS
It looks like what you have should work. This may represent a
regression, based on the retooling of the
ComponentClassTransformWorker code; it looks like the BeanEditForm (or
BeanEditor) is possibly holding onto its instance of BeanModel from
one request to the next, rather than starting from scrat
Hi,
I'm trying to use the BeanEditor in a t:form which seems to work fine until
I use the "add" parameter. I've read through the documentation and I'm just
not sure what i'm doing wrong. The form renders fine but no matter what I
do when I submit the form it always throws this exception: "Bean