[
http://jira.jboss.com/jira/browse/JBSEAM-1190?page=all ]
Pete Muir updated JBSEAM-1190:
------------------------------
Assignee: Gavin King (was: Pete Muir)
Priority: Blocker (was: Critical)
This is definitely occurring - the culprit is
Initialization.installComponentsFromXmlElements - if a component has @Name, then it is
just configured, and non-property attributes are just ignored. This occurred due to
JBSEAM-897.
Disabling install of core components no longer works
----------------------------------------------------
Key: JBSEAM-1190
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1190
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Environment: Any
Reporter: Mike Quilleash
Assigned To: Gavin King
Priority: Blocker
Fix For: 1.3.0.BETA1
Upgrading from Seam 1.1.6 to 1.2.1 seems to have broken the ability to do this...
<component class="org.jboss.seam.web.ExceptionFilter"
installed="false"/>
In my WEB-INF/components.xml. The logic in the dependency manager scans both component
descriptors, ignores the first as it is set to not install and then installs the second
(default) one as normal. I believe the precedence of two components is not being honoured
with regard to the installed flag.
Possible in
private boolean tryToInstall(String key) {
it should stop looping immediatly if it finds a non-installed component rather than
skipping that descriptor and continuing to the next loop.
This is a rather major issue for me as the exception filter is causing problems elsewhere
(see bug 1188) and I can't seem to find out how to turn it off!
--
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