We've resolved over 40 issues since 2.7.4. Not a lot, but it includes an OSGi
fix that is blocking a Camel issues which may also be causing issues with the
ServiceMix release. This also affects CXF 2.6.x which affects Camel
2.10.x/ServiceMix 4.5.1 so I decided to do a 2.6.x release as well.
+1 for all of your points.
We should also take a look at the classes that we pulled into api to
remove the split package problem in OSGi.
3.0 would be a good time to move some of these to a better place. Not
sure about the effect on compatibility though.
Christian
On 07.05.2013 20:31, Daniel
Basically writing a custom provider preinitializing contexts if genrerally
far better and trivial
Le 10 mai 2013 17:18, "Sergey Beryozkin" a écrit :
> Hi Romain
> On 10/05/13 11:03, Romain Manni-Bucau wrote:
>
>> Hi,
>>
>> It doesnt urge (and im cleaning up tomee after the owb update which broke
Hi Dan,
Definitely +1 for (1), (2), (3), (4), (5).
Regarding (6): +1 for wsdl; I would also suggest to review some other stuff in
cxf-api (like StaxTranformFeature and LoggingFeature) that IMO not really
belongs to api.
Regards,
Andrei.
> -Original Message-
> From: Daniel Kulp [mailto:
Hi Romain
On 10/05/13 11:03, Romain Manni-Bucau wrote:
Hi,
It doesnt urge (and im cleaning up tomee after the owb update which broke a
bunch of stuff for weeks so no real time ATM ;) but saw it several times
integrating cxf in tomee and each time i tested/debugged doing a POST data
provisioning
Hi,
On 10/05/13 12:47, Bill Burke wrote:
Hope you don't mind giving my 2-cents based on Resteasy.
Unless you're doing in-memory mock JAX-RS invocations, I've found that
any overhead of JAX-RS is pretty much dwarfed by any
marshalling/unmarshalling of entities i.e. JSON/XML. I've also found
that
Hope you don't mind giving my 2-cents based on Resteasy.
Unless you're doing in-memory mock JAX-RS invocations, I've found that
any overhead of JAX-RS is pretty much dwarfed by any
marshalling/unmarshalling of entities i.e. JSON/XML. I've also found
that there's a lot of static processing you
Hi,
It doesnt urge (and im cleaning up tomee after the owb update which broke a
bunch of stuff for weeks so no real time ATM ;) but saw it several times
integrating cxf in tomee and each time i tested/debugged doing a POST data
provisioning i was womdering why it was so complicated since it was th
Hi Romain
On 10/05/13 10:27, Romain Manni-Bucau wrote:
Hi guys
Excepted if i didnt get the code right it seems the endpoint resolution is
done each time in rs impl.
Couldnt it be cached a bit more? (i think to fixed uri which is common for
not GET cases). In such a case cxf could skip a bunch o
Hi guys
Excepted if i didnt get the code right it seems the endpoint resolution is
done each time in rs impl.
Couldnt it be cached a bit more? (i think to fixed uri which is common for
not GET cases). In such a case cxf could skip a bunch of logic no?
The idea is to get perf closer to servlets s
Fine with me.
I agree on all points; I'm not really sure of the actual impact of 6,
but 3.0 is definitely the proper time for doing this ;-)
Alessio
On 05/07/2013 08:31 PM, Daniel Kulp wrote:
>
> I'd like to do a couple refactoring things for 3.0 to simplify the class
> structure a little bit:
Nervemind and sorry for the noise, it's the class reference, not the
actual databinding instance, being cached. Sorry.
On 05/10/2013 10:17 AM, Alessio Soldano wrote:
> Hi Dan,
> this would likely break a minor thing in JBossWS (I still need to check,
> might possibly workaround it by being sure to
Hi Dan,
this would likely break a minor thing in JBossWS (I still need to check,
might possibly workaround it by being sure to always use a new
databinding when I need to customize it), but besides that it raises a
question from me: is a DataBinding (JAXBDataBinding here) really meant
to be shared
13 matches
Mail list logo
