[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1190) Disabling install of core components no longer works
4:46 a.m.
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
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
4:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=comments#action_12359397 ]
Mike Quilleash commented on JBSEAM-1190:
----------------------------------------
For now I've just disabled the main SeamFilter.
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
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
1:57 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=all ]
Pete Muir updated JBSEAM-1190:
------------------------------
Fix Version/s: 1.3.0.BETA1
Priority: Critical (was: Major)
Yes, I've seen this too.
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
Priority: Critical
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
12:05 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=all ]
Pete Muir reassigned JBSEAM-1190:
---------------------------------
Assignee: Pete Muir
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: Pete Muir
Priority: Critical
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
1:11 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1190) Disabling install of core components no longer works
[ 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
9:36 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=all ]
Gavin King closed JBSEAM-1190.
------------------------------
Fix Version/s: (was: 1.3.0.BETA1)
Resolution: Won't Fix
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
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
9:36 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=comments#action_12361720 ]
Gavin King commented on JBSEAM-1190:
------------------------------------
Yes, I know about this. It is semantically consistent with other behavior. Nobody has yet
given me a good reason for why you would want to be able to do this.
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
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
5:52 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=comments#action_12361751 ]
Pete Muir commented on JBSEAM-1190:
-----------------------------------
To disable one of the Seam filters - e.g. if you aren't using Seam's fileupload
then you need to disable the MultipartFilter as it breaks other file uploads (e.g.
trinidad)
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
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
6:15 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=comments#action_12361754 ]
Pete Muir commented on JBSEAM-1190:
-----------------------------------
Also, I don't see why this is consistent:
<my:component installed="true" /> on a @Install(false) causes the
component to be installed
AND
<my:component installed="false" /> on a @Install(true) causes the
component to be installed
Huh?
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
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
7:35 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=comments#action_12361766 ]
Mike Quilleash commented on JBSEAM-1190:
----------------------------------------
Agree with Pete, my particular use case is to disable one of the Seam filters, but not
all. For example I was having trouble with the exception filter (see JBSEAM-1188) so I
wanted to just disable that filter. I think this is a reasonable thing to want to do.
In addition in the past it has been necessary to disable the subscriptionRegistry
component because it used classes not on my classpath (I didn't need it). Now it has
been moved out into its own jar this problem has gone away. Still a useful 'get out
of jail free card' when something like this crops up.
Regarding Pete's last post I think XML should beat annotation precedence wise so I
would expect the first example above to install and the second not to.
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
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
11:24 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=all ]
Mike Quilleash reopened JBSEAM-1190:
------------------------------------
Reopening as I believe this is an important feature that has been lost.
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
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
11:43 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=comments#action_12363102 ]
Gavin King commented on JBSEAM-1190:
------------------------------------
It is consistent because it says "ignore this definition of the component", and
uses whatever the lower-priority definition was.
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
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
6:08 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1190) Disabling install of core components no longer works
[ http://jira.jboss.com/jira/browse/JBSEAM-1190?page=all ]
Pete Muir closed JBSEAM-1190.
-----------------------------
Resolution: Out of Date
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
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
6086
days inactive
6256
days old
12 comments
3 participants
participants (3)
-
Gavin King (JIRA) -
Mike Quilleash (JIRA)
-
Pete Muir (JIRA)