For the users, having Camel & CXF 4.x lines available makes a lot of
sense - if splitting the work out to a repo to facilitate its
maintenance then that's ok.
Will Apache Karaf by default pick up these two repos, making it
effectively seamless from the end user point of view? They'll just
install
Hey JB,
Thanks a lot for stepping in and offering your help here. We just recently
discussed
that exact same subject with Colm, which resulted in [1]. From my side, there
are few
questions:
- is OSGI ecosystem leveled up on Jakarta? (seems like not fully)
- do you need help from CXF folks?
Yes, no impact for users (exactly as I did on camel-karaf).
I’m ready to work on this if we have a consensus.
Regards
JB
Le ven. 13 déc. 2024 à 19:15, Jamie G. a écrit :
> For the users, having Camel & CXF 4.x lines available makes a lot of
> sense - if splitting the work out to a repo to faci
Hey all,
with 4.1.0 being out of the door now, I am curious if there is any timeline
when you’re planning to integrate the (rather small) changes for MP Rest Client
4.0 so we could potentially move TomEE to being MicroProfile 7.0 compatible.
Will this happen with the next “big bang” release (e.g
Hi Markus,
We already planning for Jakarta EE 11 (see please [1]), and MP 4.0 is listed
there.
Since this is a major release (3.x -> 4.x), we usually do not do major version
bumps within
maintenance releases. Thank you.
[1] https://issues.apache.org/jira/browse/CXF-8828
Best Regards,
And
Hi everyone,
we recently moved from Camel 2 to Camel 3 and we are now observing the
following problem with CXF. If a OneWay message exceeds a certain length, the
messages fail with a parser error like:
Caused by: java.lang.IllegalStateException: Current event not START_ELEMENT or
END_ELEMENT
Hi,
With 7 binding +1s
Andriy Redko
Jeff Genender
Francesco Chicchiriccò
Alexey Markevich
Colm O hEigeartaigh
Jim Ma
Freeman Fang
2 non-binding +1s
Jamie Goodyear
Mark Struberg
and no other votes, this vote passes and I will release the artifacts soon.
Thanks all for the vote!
Freeman
On Mon,
reta merged PR #2194:
URL: https://github.com/apache/cxf/pull/2194
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org
For q
Hi folks,
CXF 4.x first removed the OSGi support (headers), and later re-add
only the headers.
We can consider the OSGi support non-operational in CXF as the
blueprint extension, etc have been removed.
Also, the Apache Karaf support has been removed (e.g. features.xml).
I think it makes sense to
Here is my +1.
On Mon, Dec 9, 2024 at 1:05 PM Freeman Fang wrote:
> Hi,
>
> Here is the VOTE for Apache CXF 4.1.0. The biggest feature of Apache CXF
> 4.1.0 is Jakarta EE 10 compatibility, with more improvements and bug fixes.
>
> Staging area:
> https://repository.apache.org/content/repositorie
reta opened a new pull request, #2195:
URL: https://github.com/apache/cxf/pull/2195
Support SeBootstrap HTTPS configuration (JAX-RS 3.1 spec)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the s
Welcome to the final OpenJDK Quality Outreach update of 2024!
JDK 24, scheduled for General Availability on March 18, 2025 [1], is now in
Rampdown Phase One (RDP1) [2]. At this point, the overall JDK 24 feature set is
frozen and only low-risk enhancements might still be considered. You will find
12 matches
Mail list logo
