Hi Adrián Roselló,
On 21/10/13 14:54, Adrián Roselló Rey wrote:
Hi Sergey,
Thanks for your quick response. I tested your suggestion, but I didn't make
it works.
But we discovered something. Several days ago, we had some problems to
start one of our project's feature, due to dependencies between bundles
using JPA. After looking for some information, we discovered the following
issue https://issues.apache.org/jira/browse/KARAF-1002
Basically, by adding the following propertiy in etc/config.propertries
file, the bundle is not started, but scheduled.
"org.apache.aries.blueprint.synchronous=true"
Just for testing, we commented this line again, and all services were
published by DOSGI again.
Thanks for experimenting with it all, this is very helpful.
It appears to me that having that property enabled by default causes the
side-effects, so I wonder, should that Karaf issue be re-opened ?
We were wondering if this information is usefull for you in order to see
what could be happening, since we don't know DOSGI and CXF so much ;)
This is not a DOSGi for sure, and I doubt that it is a CXF issue either.
Dan, do you reckon it could be of concern to CXF, specifically, is there
some code in CXF that may not be dealing with this correctly ?
That appears to be unlikely to me, if the bundles installed concurrently
are getting published as expected, why would a synchronous orderly
installation cause CXF Blueprint code to fail ?
Thanks, Sergey
Thanks again!
Cheers,
Adrián Roselló
2013/10/18 Sergey Beryozkin <sberyoz...@gmail.com>
Hi
I wonder if it is the same 'CXFServlet overriding the endpoint address by
default' issue which gets in the way now. In fact I don't think this is
even possible to disable in DOSGI if no default CXF Servlet is used.
Lets try this option for now:
- remove "org.apache.cxf.rs.**httpservice.context" properties from both
registrations, and set "org.apache.cxf.rs.address" to "/serviceA" and
"/serviceB" respectively.
in Karaf/etc/org.apache.cxf.osgi.**cfg file set:
org.apache.cxf.servlet.**context=/myservice/myapp
org.apache.cxf.servlet.**disable-address-updates=true
This should lead to the default CXFServlet listening on "/myservice/myapp"
register 2 endpoints and block the default overriding of the endpoint
address.
Can you give it a try please ?
Cheers, Sergey
On 18/10/13 08:37, Adrián Roselló Rey wrote:
Hi Sergey, David
Thanks for your suggestions. I installed the bundles you mentioned and its
dependencies, and I could start our platform without problems, but the
extrange behaviour with DOSGI is still there, even though in logs we can
read "Successfully registered CXF DOSGi servlet at xxxx" for all our
services.
Cheers,
Adrián Roselló
2013/10/17 David Bosschaert <david.bosscha...@gmail.com>
On 17 October 2013 18:00, Sergey Beryozkin <sberyoz...@gmail.com> wrote:
though this issue needs to be fixed for 2.7.8
I would recommend trying to get the maven-bundle-plugin/bnd to compute
the imports... That way you can't forget them going forward.
It's not 100% foolproof, you still need to check that the imports are
what you want, because if you use the automatic computation you might
inadvertently import additional things that you didn't intend to
import if you accidentally use them, but I think in general, and also
for the imported versions, it's a safer thing to do...
Cheers,
David
