[
https://issues.apache.org/jira/browse/TAPESTRY-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620190#action_12620190
]
Martin Papy commented on TAPESTRY-2460:
---------------------------------------
Hi Kristian,
The only workaround I found, is the way I did it in the first place :
In AppModule :
public static void
contributeDefaultDataTypeAnalyzer(MappedConfiguration<Class<?>, String>
configuration) {
configuration.add(Address.class, "address");
}
In tml file :
<t:beanEditForm t:object="user">
<t:parameter name="address">
<t:beanEditor t:object="user.address" />
</t:parameter>
</t:beanEditForm>
I hoped it would be corrected for T5.0.14, but it seems it won't be the case.
> Nested BeanEditors (where the block parameter for a property to one
> BeanEditor contains another BeanEditor) results in a StackOverflowException
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2460
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2460
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.13
> Reporter: Kristian Marinkovic
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.14
>
> Attachments: beaneditor.zip
>
>
> the eclipse/maven example project shows how a StackOverflowException is
> thrown if a Form is submitted that contains a BeanEditor that itself contains
> another BeanEditor. However the initial display works perfectly.
> somehow i suspect the PropertyConduits to be responsible because two of them
> produce the infinite loop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
