rmannibucau commented on issue #487: Ensure JAXB and javax.activation are not
required for JAX-RS
URL: https://github.com/apache/cxf/pull/487#issuecomment-453097049
@coheigea have to admit i used CDI to test so commons-annotation was there
(and @Priority) but good catch, updated
On Thu, Jan 10, 2019 at 11:59 AM Dennis Kieselhorst wrote:
> Let's focus on JAX-WS and JAX-RS (along with JAXB) for 3.3.0 as those
> are the main implementations that we are offering. Everything else can
> be done for 3.4.0.
>
+1, assuming the JAX-WS upgrade is seamless. JAX-RS is already done
Hi Andriy!
> I also noticed that some of our integrations, like fe Swagger / OpenApi do
> explicitly depend on JAXB APIs artifacts. I think we should be careful here
> and at least add exclusions, avoiding classpath collisions. There could be
> more examples like that. Thanks.
You are absolutely
On Thu, Jan 10, 2019 at 1:59 PM Dennis Kieselhorst wrote:
>
> > It would be great to get CXF out soon enough, since more and more
> projects switch
> > to Java 11. From practical standpoint, releasing CXF 3.3.0 with JAXB
> deps would
> > make a lot of sense (in my opinion), since every other
I'm a bit concerned that we we delay indefinitely, when we need to get a
release out that supports Java 11. Perhaps CXF 3.3.0 should just contain
the JAXB upgrade and let CXF 3.4.0 pick up all of the newer dependencies?
Colm.
On Thu, Jan 10, 2019 at 10:28 AM Dennis Kieselhorst wrote:
>
> > Can
> Can you update JAX-WS + SAAJ when the JAXB switch is done and working?
Yes. The question is when do we update the other stuff (Activation,
Annotation, CDI, EL, Mail, Validation, JSON, ...)? I'd like to have it
clean for 3.3.0 but it's kind of transitive dependency hell.
> Do
> you know when
coheigea edited a comment on issue #487: Ensure JAXB and javax.activation are
not required for JAX-RS
URL: https://github.com/apache/cxf/pull/487#issuecomment-453083194
I did a test with a simple spring endpoint and ran into this problem -
ProviderFactory has a method:
static int
coheigea commented on issue #487: Ensure JAXB and javax.activation are not
required for JAX-RS
URL: https://github.com/apache/cxf/pull/487#issuecomment-453083194
ProviderFactory has a method:
static int comparePriorityStatus(Class cl1, Class cl2) {
Integer value1 =
Can you update JAX-WS + SAAJ when the JAXB switch is done and working? Do
you know when they plan to release 4.0.2?
Colm.
On Wed, Jan 9, 2019 at 6:08 PM Dennis Kieselhorst wrote:
> Hi,
>
> the JAXB, JAX-WS, SAAJ and some more API dependencies are now available on
> central.
>
> Servlet-API is
It would be great to get CXF out soon enough, since more and more projects
switch
to Java 11. From practical standpoint, releasing CXF 3.3.0 with JAXB deps would
make a lot of sense (in my opinion), since every other project around did
exactly
that. However, we've already started moving to
amarkevich opened a new pull request #498: cxf-systests-databinding: run tests
without internet connection
URL: https://github.com/apache/cxf/pull/498
This is an automated message from the Apache Git Service.
To respond to
> It would be great to get CXF out soon enough, since more and more projects
> switch
> to Java 11. From practical standpoint, releasing CXF 3.3.0 with JAXB deps
> would
> make a lot of sense (in my opinion), since every other project around did
> exactly
> that. However, we've already
I guess jakarta will "relocate" ([1]) the jars so frameworks will start
getting warnings and fix it so sounds like a move forward anyway.
Side note: we got the same issue with geronimo spec jars for years and it
never had been a real issue in practise so not a big deal IMHO.
[1]
>
>> Let's focus on JAX-WS and JAX-RS (along with JAXB) for 3.3.0 as those
>> are the main implementations that we are offering. Everything else can
>> be done for 3.4.0.
>>
> +1, assuming the JAX-WS upgrade is seamless. JAX-RS is already done right?
> Then let's use a single version of JAXB for
coheigea commented on issue #498: cxf-systests-databinding: run tests without
internet connection
URL: https://github.com/apache/cxf/pull/498#issuecomment-453194126
+1
This is an automated message from the Apache Git
amarkevich closed pull request #498: cxf-systests-databinding: run tests
without internet connection
URL: https://github.com/apache/cxf/pull/498
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As
Hi Dennis,
I will take a look tonight if no one does it before me. Thanks!
Best Regards,
Andriy Redko
On Thu, Jan 10, 2019, 10:51 AM Dennis Kieselhorst
> >
> >> Let's focus on JAX-WS and JAX-RS (along with JAXB) for 3.3.0 as those
> >> are the main implementations that we are offering.
I will also take a look at the OSGi issues if not done yet.
－
Freeman(Yue) Fang
Red Hat, Inc.
> On Jan 11, 2019, at 2:59 AM, Andrey Redko wrote:
>
> Hi Dennis,
>
> I will take a look tonight if no one does it before me. Thanks!
>
> Best Regards,
>Andriy Redko
>
> On
18 matches
Mail list logo
