[jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-4140) ResteasyDispatches instantiates resources even if they are not instantiable at that time.

Wed Apr 22 14:59:22 EDT 2009

     [ https://jira.jboss.org/jira/browse/JBSEAM-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Bauer reopened JBSEAM-4140:
-------------------------------------

I do not see how the commit you made changes the problem, it still instantiates the resource component on startup. Also, why the change to the class/type check? It's not wrong just not as flexible as before.

> ResteasyDispatches instantiates resources even if they are not instantiable at that time.
> -----------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4140
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4140
>             Project: Seam
>          Issue Type: Bug
>          Components: WS
>    Affects Versions: 2.1.2.CR1
>            Reporter: Jozef Hartinger
>            Assignee: Jozef Hartinger
>            Priority: Critical
>             Fix For: 2.1.2.CR2
>
>
> right now, for every descendant of AbstractResource we simply create an instance and take a look at the path attribute value - this breaks if someone is extending the component and injects another component which is not available when resources get registered, uses @Restrict etc...

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