[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2174) ELResolvers added by BaseSeamTest are not usable as property resolvers (as opposed to base/variable resolvers)
Matt Drees (JIRA)
jira-events at lists.jboss.org
Mon Oct 29 01:14:01 EDT 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-2174?page=all ]
Matt Drees updated JBSEAM-2174:
-------------------------------
Attachment: elresolver-patch.txt
Attached a patch to MockApplication that potentially solves the problem by putting all custom EL resolvers at the front of the chain.
> ELResolvers added by BaseSeamTest are not usable as property resolvers (as opposed to base/variable resolvers)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-2174
> URL: http://jira.jboss.com/jira/browse/JBSEAM-2174
> Project: JBoss Seam
> Issue Type: Bug
> Components: Test Harness
> Affects Versions: 2.0.0.CR3
> Reporter: Matt Drees
> Attachments: elresolver-patch.txt, elresolvertest-patch.txt
>
>
> When you add an ELResolver by overriding BaseSeamTest.getELResolvers(), your resolver is added (in MockApplication) after the default CompositeELResolver, which includes a BeanELResolver. BeanELResolver throws a PropertyNotFoundException when it can't resolve a property, which prevents your custom resolver from being consulted. Therefore, BeanELResolver really should be placed at the very end of the chain, not your custom resolver(s).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list