Hey Andriy
IMHO it might wait till 3.2.1 (may be we can do a camel cxf demo making
sure the context can flow from Camel to CXF and vice versa) as a POC and
tweak few things along the way ? If we doc it right now in a bit of a
hurry then we will have less space for the changes ?
Thanks, Sergey
On 04/09/17 21:22, Andriy Redko wrote:
Hey Dan,
Sorry for last minute thing (always pops up), do I have time to push this
guy https://issues.apache.org/jira/browse/CXF-7439? I am mostly done with the
implementation,
need couple of more days to add a sample project and update the documentation.
It is considerably
large chunk of the code, no urgency to have it in 3.2 really (could go to
3.2.1). Just appreciate
the opinions, it is worth to delay a build for a couple of more days (Wed/Thu)
or not.
Thanks!
Best Regards,
Andriy Redko
DK> We just got the final releases of WSS4J and the JAX-RS api and I’ve also
just managed to figure out how to get
DK> atmosphore and the latest Jetty releases to play nicely together. Also
considering it’s 4pm my time on a Friday
DK> before a long weekend, I’m not going to start the 3.2 build. I think it’s
best to delay until Tuesday to give the updates and such a chance to be tested.
DK> Dan
On Aug 10, 2017, at 12:22 PM, Daniel Kulp <dk...@apache.org> wrote:
It’s been over two years since 3.1.0 was released which is a long time. I’d
like to get 3.2.0 out shortly. Looking through things, the major outstanding
things are snapshots of a couple deps (xjc-utils,build-utils, wss4j) and
updates to the JAX-RS stuff to use the released 2.1. What else do folks have
outstanding that would be “needed” to get into 3.2? Would Sept 1st be a good
target for getting 3.2 built? That would give use a few weeks to finish
things up and get the releases out.
Thoughts?
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
