[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2076) let EL access qualified @Factory and @Out names

[Matt Drees (JIRA)]

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

Matt Drees updated JBSEAM-2076:
-------------------------------

    Attachment: BazFactory.java
                NameSpaceElTest.java

So, it turns out I was half-wrong.  If the factory's prefix matches the component's prefix, it works.  But if not, it doesn't.  So in the attached test, the second two tests fail, but not if I change BazFactory's @Name to "foo.bar.bazFactory".

Maybe this is expected behavior; I can't tell from the documentation.
In my app, I had a miscellaneous Factories component named "factories", and I wanted to change one of the factories in it from "uscmRegions" to "uscm.regions", which seems like a reasonable thing to me.  So I'd argue that @Factory name prefix shouldn't be forced to match the component name's prefix.

> let EL access qualified @Factory and @Out names
> -----------------------------------------------
>
>                 Key: JBSEAM-2076
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2076
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>            Reporter: Matt Drees
>            Priority: Minor
>         Attachments: BazFactory.java, NameSpaceElTest.java
>
>
> I can use "dot" qualified component names in EL.  (I.e, I can use #{org.jboss.seam.security.identity.username} in my page instead of #{identity.username}).
> However, I can't do the same for @Factory variables (and presumably other kinds of non-component context variables).
> I'd like to. :-)

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