[
https://issues.apache.org/jira/browse/CXF-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047982#comment-16047982
]
Sergey Beryozkin commented on CXF-7406:
---------------------------------------
Hi Romain, having integration/common-cdi and integration/cdi-ws would make
sense IMHO, perhaps your point 2 can be addressed at the cdi-ws level
> JAXWS CDI integration
> ---------------------
>
> Key: CXF-7406
> URL: https://issues.apache.org/jira/browse/CXF-7406
> Project: CXF
> Issue Type: New Feature
> Reporter: Romain Manni-Bucau
>
> As the cdi module for jaxrs it would be neat to have one for jaxws,
> meecrowave created one (assuming jaxrs one is there):
> https://github.com/apache/meecrowave/commit/1350935b2eecaba8ffee9f0df1de0912960b1cee
> Questions:
> 1. can CXF integrate such a module (with probably more work for providers)
> 2. how to ensure core doesnt have jaxws code to allow [jaxrs container
> classloader] -> [webapp adding jaxws dependencies but reusing container cxf
> part], here SchemaInfo is an issue since jaxrs will not bring xmlschema for
> instance
> 3. how to handle the shared area of cdi (the bus for instance): common-cdi
> module?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
