cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <>
Subject [jira] [Commented] (CXF-7406) JAXWS CDI integration
Date Tue, 13 Jun 2017 17:21:00 GMT


Romain Manni-Bucau commented on CXF-7406:

Hey Sergey,

well for the split also keep in mind cdi is auto activated so using a bit of reflection (for
the factory/server) can also work and enable a single module to just work (that's where I'm
unsure, kind of user easiness vs code easiness)

for 2. issue is really in cxf and not in cdi integration. Think to a tomcat with cxf-rs in
common.lib and a webapp deployed to this tomcat adding just cxf-ws, then it wouldnt load until
cxf-ws is moved to the container where expectation can be to have core reusable for both rs
and ws. Can be another ticket though.

> JAXWS CDI integration
> ---------------------
>                 Key: CXF-7406
>                 URL:
>             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):
> 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

View raw message