[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4247) Remove Seam component support for JAX RS providers
[
https://jira.jboss.org/jira/browse/JBSEAM-4247?page=com.atlassian.jira.pl...
]
Adam Thomas commented on JBSEAM-4247:
-------------------------------------
We currently rely on a custom MessageBodyReader provider being a Seam component. It seems
like this change would make this impossible even though it works fine in 2.2.0.GA.
We use the componentness of the Reader to inject a helper that is used during the reading
process. This helper uses an EntityManager to turn references into full entities. I
suppose if the contexts are all there we could rely on Component.getInstance() to do this,
but that doesn't seem optimal to me if there is nothing preventing MessageBodyReaders
from being Seam components.
Remove Seam component support for JAX RS providers
--------------------------------------------------
Key: JBSEAM-4247
URL: https://jira.jboss.org/jira/browse/JBSEAM-4247
Project: Seam
Issue Type: Task
Components: WS
Affects Versions: 2.1.2.GA
Reporter: Matthew Bowman
Assignee: Christian Bauer
Fix For: 2.2.1.CR1
Attachments: resteasy-debug.log
Example:
@Name("serviceExceptionMapper")
@Scope(ScopeType.APPLICATION)
@Provider
public class ServiceExceptionMapper implements ExceptionMapper<ServiceException> {
public Resposne toResponse(ServiceException ex) {
return Response.noContent().build();
}
}
This custom ExceptionMapper provider will not be registered with ResteasyProviderFactory.
If I remove the @Name + @Scope annotations, the provider is registered.
--
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