[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1190) Disabling install of core components no longer works

Tue May 8 08:35:52 EDT 2007

    [ 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