[
https://jira.jboss.org/jira/browse/JBSEAM-4140?page=com.atlassian.jira.pl...
]
Christian Bauer commented on JBSEAM-4140:
-----------------------------------------
I'm thinking that we should probably make ResteasyDispatcher configurable, so you
don't set the path on the ResourceHome/Query in components.xml, you map it into the
dispatcher. Something like this:
<resteasy:resource-home name="configuredCategoryResourceHome"
entity-home="#{categoryHome}"
entity-id-class="java.lang.Integer"
media-types="application/xml application/json"/>
<resteasy:dispatcher>
<resteasy:resourceMappings>
<key>/configuredCategory</key><value>configuredCategoryResourceHome</value>
<key>...</key><value>...</value>
</resteasy:resourceMappings>
</resteasy:dispatcher>
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