Just a warning, if I can get all the tests passing, I have a big commit coming
in today (although broken across a couple commits that will all come at once)
that touches a LOT of stuff.
Basically, I'm trying to reduce the startup time. Specifically, the
"BusFactory.createDefaultBus()" time.
OK Dan,
interesting changes :-)
Btw, once it's all on svn and a couple of days passed, I can try
pointing the jbossws-cxf build to a recent snapshot to check early the
integration is fine.
Thanks
Alessio
Daniel Kulp wrote:
Just a warning, if I can get all the tests passing, I have a big commi
Hi Josh
I've updated the JAX-RS layer in DOSGi such that it will now discover JAXRS
(and CXF specific providers) which have been registered as (global) OSGI
services. At the moment I've decided not to use a ServiceTracker and instead
a calling BundleContext is asked to exercise a filter expressio
On Mon August 24 2009 9:54:20 am Glen Mazza wrote:
> Hello, the search functionality on this page is no longer working (possibly
> related to the new layout?):
> http://cxf.apache.org/docs/index.html
>
> Could someone in the know fix this?
Well, it has to do with pulling the "links" to the docs of
OK. "Part 1" (I have more ideas) is in. A "default" bus has gone from over
55 beans created and initialized down to 12. Startup time for the first Bus
has dropped from 2.1 seconds on my machine to 0.9. After the jit warms up
and classes loaded and such, subsequent Bus creation has dropp
Hi Benson et. al.,
I tried running the D-OSGi in Equinox under J2ME CDC on a Nokia N800
but it failed (I downloaded
and activated the single-bungle distro). So I have a feeling I will have
the same luck running the CXF
stack on that mobile. But I will give the WSDL2JS tool a shot as
stand
