[ https://jira.jboss.org/jira/browse/JBSEAM-4247?page=com.atlassian.jira.pl... ] Christian Bauer commented on JBSEAM-4247: ----------------------------------------- If you can, please attach a DEBUG level startup log of category org.jboss.seam.resteasy. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4247?page=com.atlassian.jira.pl... ] Matthew Bowman commented on JBSEAM-4247: ---------------------------------------- The log shows 'registering provider as Seam component: serviceExceptionMapper' however it is never actually registered. I traced it to org.jboss.resteasy.spi.ResteasyProviderFactory.addExceptionMapper(ExceptionMapper): {code} public void addExceptionMapper(ExceptionMapper provider) { providers.put(provider.getClass(), provider); PropertyInjectorImpl injector = new PropertyInjectorImpl(provider.getClass(), this); injector.inject(provider); Type[] intfs = provider.getClass().getGenericInterfaces(); for (Type type : intfs) { if (type instanceof ParameterizedType) { ParameterizedType pt = (ParameterizedType) type; if (pt.getRawType().equals(ExceptionMapper.class)) { exceptionMappers.put(Types.getRawType(pt.getActualTypeArguments()[0]), provider); } } } } {/code} In short, when it queries the provider class' generic interfaces, the Type[] array returned is that of the proxy and not the Seam component itself. Therefore, the check of "type instanceof ParameterizedType" never succeeds. In other words, it doesn't see the "... implements ExceptionMapper<E>" on the provider and hence is never actually added to the exceptionMappers map. Hope this helps. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4247?page=com.atlassian.jira.pl... ] Matthew Bowman commented on JBSEAM-4247: ---------------------------------------- For my purposes, it's ok for my provider to not be a seam component. The only thing I can think of off the top of my head would be to recurse the proxy chain to discover the generic type of the exception that is to be mapped. Something like... if (Proxy.isProxyClass(provider.getClass())) { // ... recurse ... } This is not the cleanest of things, and like I said, this is the only thing I can think of for the time being. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-4247?page=com.atlassian.jira.pl... ] Christian Bauer closed JBSEAM-4247. ----------------------------------- Fix Version/s: 2.2.1.CR1 Resolution: Done Removed the support for JAX RS providers as Seam components, and documented the limitation. There are two possible clean solutions for a future version of Seam: - enhance RESTEasy with a metadata SPI for registration of a Provider instance/type/factory, to avoid scanning of the supplied instance (in other words, instead of scanning the supplied class for interfaces and annotations, RE would use the metadata supplied externally by Seam bootstrap) - if RE can or is not improved with this SPI, write a custom ResteasyProviderFactory instance (this is not ideal because a lot of RE code would have to be duplicated in Seam) Note that not all kinds of providers are affected. For example, MessageBodyReader/Writer would be fine as Seam components, because these are not scanned by RE, their API actually has a isWritable()/isReadable() method that is used to detect metadata about the provider. ExceptionMapper on the other hand can not be supported because the parameterized type of the instance has to be scanned. So a third alternative would be enabling support for Seam component providers again but documenting and logging a WARN for unsupported providers such as ExceptionMappers. If there are strong reactions against removing this support with the candidate releases of 2.2.1, we can go that route for 2.2.1 GA and put it back in. -- 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