[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-1785) SeamTest to consider ELResolver from faces-config

[Pete Muir (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1785?page=all ]

Pete Muir resolved JBSEAM-1785.
-------------------------------

    Resolution: Done

Fixed in CVS.  Override the method getELResolvers in SeamTest and return your custom resolvers there (n.b. we don't process faces-config.xml inside the test env.)

Made a bug as our ELResolver/Context handling in Mock was IMO broken.

> SeamTest to consider ELResolver from faces-config
> -------------------------------------------------
>
>                 Key: JBSEAM-1785
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1785
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Test Harness
>    Affects Versions: 2.0.0.BETA1
>            Reporter: Diego Ballve
>         Assigned To: Pete Muir
>             Fix For: 2.0.0.CR1
>
>
> Extra ELResolvers defined in faces-config.xml do not get considered when running tests based on SeamTest. This can be verified by checking the registered resolvers in debug mode, from:
>   ELResolver resolver = FacesContext.getCurrentInstance().getELContext().getELResolver();
> As a consequence, applications that depend on those resolver extensions cannot be tested w/o some hacking to register the extra resolve - and then be able to use SeamTest getValue/setValue methods.
> Btw, extra resolver works fine when the application is deployed, as expected.

-- 
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