Hi
On 17/09/17 15:37, John D. Ament wrote:
Hey
So I just ran into an issue where ExceptionMappers weren't being processed
in CXF when they had a CDI normal scope. Switching to a pseudo scope
(@Dependent) fixes it. A similar issue to what I saw recently with Weld
and Generic Type being lost, except this was happening for both OWB and
Weld.
While I was able to dig into the prior issue with generic type arguments,
that was a Weld specific issue. I couldn't figure out why CXF wasn't
reading the metadata of the actual bean class. I'm wondering if for CDI
use cases, if it makes sense for CXF to look at the actual class's
metadata, separate from the CDI instance that's being passed in (which is
just a proxy).
I think this is what is done for ex in the Spring case, is it not the
case in the CXF CDI flow ? When JAXRSServerFactoryBean.createFromBeans,
etc, is called then ClassResourceInfo would be initialized with the
'resource' class which may be the proxy, and the 'service' class which
is the actual class.
ClassHelper is used to find the actual 'service' class.
May be CXF CDI needs to use ClassHelper ?
Sergey
John
