[
https://jira.jboss.org/jira/browse/JBSEAM-3138?page=com.atlassian.jira.pl...
]
Norman Richards commented on JBSEAM-3138:
-----------------------------------------
OK - I definitely see that we have an issue storing property values. Property values set
on a a specific component in components.xml go into the global properties pool, separate
from the component definition. The problem then becomes that if that component definition
isn't actually used, those property values might still be used. That's very
unintuitive.
precedence doesn't work for the component properties specified in
components.xml
--------------------------------------------------------------------------------
Key: JBSEAM-3138
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3138
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.1.GA
Reporter: ihar kuplevich
Assignee: Norman Richards
Fix For: 2.0.3.CR2, 2.1.0.BETA1
Attachments: Initialization.patch
Precedence doesn't work for the component's properties specified in
components.xml. Component's attributes like class for example are taken according
precedence but properties are taken from last loaded components.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira