Hi Neil,
The JAXB libraries have some really annoying ordering requirements in
them which makes them not ideal in an OSGi or any modular/dynamic
environment.
If I remember it well, the JAXB impl bundle must be started/resolved
before the JAXB spec bundle because the spec bundle in a static
I *think* there is but I can't really remember which dependency had
the ordering requirement :(
I started working on a subsystem definition for CXF-DOSGi, which is
unfinished, but it does contain what I think was the working order of
dependencies. It might help:
Hi Adrian,
You might want to try using an EndpointListener [1] or an
RemoteServiceAdminListener [2]. You should be able to get callbacks
through those once the remoting work is done.
Cheers,
David
[1]
http://www.osgi.org/javadoc/r4v42/org/osgi/service/remoteserviceadmin/EndpointListener.html
Caused by: java.lang.NoClassDefFoundError:
org/osgi/framework/BundleActivator
Is the bundle importing the org.osgi.framework package?
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
I think it's better in general to use the multi-bundle distribution.
The single-bundle distro is really only good to get started, but I
would not recommend using it in real scenarios.
If there is an issue with the multi-bundle distro it's worth figuring
out what it is. In this case apparently a
Hi Sunil,
See here for the list of bundles that I recently used. This is pretty
much CXF-DOSGi 1.4-SNAPSHOT:
http://github.com/bosschaert/osgi-cloud-infra/tree/master/osgi/equinox/bundles
There are a few extra ones in there but you'll easily spot those.
There is a 'launch-osgi-local.sh' script
Just as a sanity check I ran the REST Greeter demo with discovery
(with a CXF-DOSGi build from trunk) and it seems to work fine.
All I did was deploy the following two bundles in a framework with
CXF-DOSGi and discovery set up (I used my multi-bundle setup that I
still had from this blog article
On 25 July 2012 12:30, Sergey Beryozkin sberyoz...@gmail.com wrote:
On 25/07/12 12:11, Spandit2 wrote:
David
I am using the setup you have outlined in the blog using cxf multi bundle
jar. I am still not able to get the information .
*[zk: localhost:2181(CONNECTED) 19] get
On 24 July 2012 17:46, Spandit2 spand...@csc.com wrote:
Hello All ,
I am using CXF DOSGI and ZooKeeper . I have some REST services which I can
see being registered in service registry .
I have a client application which is plain Java application implemented
using ZooKeeper API .
My
Hi Sunil,
Looks like you only did ls, you'll get the details with the 'get'
command...
David
On Tuesday, 24 July 2012, Spandit2 spand...@csc.com wrote:
Hi David ,
Thanks for your quick response. I think I am missing something. When I run
zkcli I get following
WatchedEvent
or document and solition. What is you suggest.
Thank You!!!
From: David Bosschaert david.bosscha...@gmail.com
To: Koray Duman koray_...@yahoo.com
Cc: users@cxf.apache.org users@cxf.apache.org
Sent: Monday, July 16, 2012 6:32 PM
Subject: Re: Remote OSGI
. Which platform can be used Apache CXF servises as a client. Can I use
apache cxf services only on web applications.
From: David Bosschaert david.bosscha...@gmail.com
To: users@cxf.apache.org; Koray Duman koray_...@yahoo.com
Sent: Monday, July 16, 2012 5:01 PM
Hi Thomas,
I'm not sure I fully follow your scenario.
I think the best way to do this is by using a shared interface bundle.
Like is done in the greeter demo:
http://cxf.apache.org/distributed-osgi-greeter-demo-walkthrough.html
Since you probably want to program against the API on the client
PM, David Bosschaert wrote:
Hi Thomas,
I'm not sure I fully follow your scenario.
I think the best way to do this is by using a shared interface
bundle. Like is done in the greeter demo:
http://cxf.apache.org/distributed-osgi-greeter-demo-walkthrough.html
Since you probably want to program
You could try the latest code on trunk to see whether the changes I
made actually work for you.
Best regards,
David
On 12 March 2012 15:27, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi
On 12/03/12 15:19, Vásáry Dániel wrote:
Hi,
I'm using CXF DOSGI for years. Now, I would like to
Then the issue reported here is a different issue.
One of the things that I fixed was the proper exporting of packages
that are part of the org.osgi.enterprise-4.2.jar. I fixed a few other
small issues as well, but to be honest it looks like they are in a
different area than the issue you're
Was just looking at http://cxf.apache.org/dosgi-releases.html and
noticed that the 1.3 multi-bundle distro link from there was not
correct. It was pointing at
cxf-dosgi-ri-multibundle-distribution-1.3.jar which contains pretty
much nothing.
It should have been pointing at:
I think the bottom line is someone needs to take it on an refactor it.
Unfortunately I don't have the time for this currently, but I'm happy
to look at patches and apply. There were a few patches provided
earlier but there were issues with those, unfortunately (see DOSGI-69
for details).
Cheers,
Hi mikssin,
As you've seen, location of the zookeeper server is set into the DOSGi
system through configuration admin.
I'm not sure zookeeper itself supports dynamic discovery of its server
(check their docs etc) but if it does you could write a a little
bundle that uses that mechanism to find
this yourself on top of zookeeper and CXF-DOSGi with the help
some broadcast library.
Could you please clarify a little bit more the following point?
David Bosschaert wrote:
...
Possibly a generally better approach would be to use a
management/orchestration system which knows where in your system
Hi Emmanuel,
It's the order of dependencies and the specification of the start
level that's the issue, right? It should not really be needed to start
bundles in a certain order, but there a number of dependencies of
DOSGi that need to be started in a specific order to work properly.
This is
Hi Emmanuel,
You may want to look at the multi-bundle distro
http://cxf.apache.org/dosgi-multi-bundle-setup.html
The single-bundle distro was really created to get started quickly but
it's not quite the right solution for real deployment in many cases.
One of the issue is that you might have
=bundleguiutilities.service.IBundleManagerGuiProvider)(!(endpoint.framework.uuid=15dba8b8-1547-4f01-9031-575eb11a27ca)))]
Mar 7, 2011 3:25:33 PM
org.apache.cxf.dosgi.topologymanager.TopologyManager$1 modifiedService
INFO: TopologyManager: EndpointListener changed ...
--
Christophe
David
It would be good if someone would contribute a fix for this. Just
attach it as a patch to https://issues.apache.org/jira/browse/DOSGI-89
I would be happy to apply it ;)
David
On 4 March 2011 15:41, Christophe Collet collet.christo...@gmail.com wrote:
Hi all,
I'm facing the same problem.
Is
Hi Christophe,
remote-services.xml will not really deactivate discovery, but to
/activate remote discovery/ you need to properly configure it.
Regardless, if I remember it correctly the remote-services.xml based
configuration internally uses the discovery API (through the
Hi Pierre,
Not sure I fully understand your setup but it seems like this is
pretty much exactly what happens in the Greeter Demo [1].
This demo does not use any discovery but reads the configuration of
the remote service from a remote-services.xml file that is part of the
client bundle [2]. The
Yes, the osgi Remote Discovery service should do this for you. If you
only want to use it locally, then you can configure it just on your
local machine...
See also: http://cxf.apache.org/dosgi-discovery-demo-page.html
Cheers,
David
On 27 January 2011 08:50, phper...@gmail.com
Hi Charles,
I've created a JIRA for this; https://issues.apache.org/jira/browse/DOSGI-89
Cheers,
David
On 2 September 2010 15:45, Charles Vuijst charles.vui...@infor.com wrote:
Hi,
I've followed the Setting up Equinox for DOSGi 1.2 Multi Bundle as
described on
Hi Markus,
You may want to try out the CXF-DOSGi subproject, which comes with a
spring-dm demo. See here: http://cxf.apache.org/distributed-osgi.html
Best regards,
David
On 15 December 2010 09:51, Markus zombiefromvalha...@web.de wrote:
Hello,
after I am finally able to run CFX in OSGi, I
Hi Michael,
I have never tried this at all and this might very well fall into the
area where Sergey suggested to provide external configuration to
DOSGi.
Sergey would you have any thoughts here?
Cheers,
David
On 22 November 2010 10:18, Michael Illgner
michael.illg...@googlemail.com wrote:
Hi
Hi Fabio,
It looks like you found a bug in the intents mechanism. Feel free to
provide a patch with a fix that works for you. The intent handling in
CXF-DOSGi hasn't had the attention it deserves recently so I would be
happy to see someone improving it!
And David, about our previous
Hi Fabio,
Yes, you should be able to include the intent-map.xml file in your own
bundle. Your bundle shouldn't have to be a fragment for that. The
intent map that is part of the distro is the default intent map and
the one in your bundle is specific to your application, so it
overrides the
Hi Zoe,
Yes, the DOSGi distro contains Pax-Web as a convenience but as far as
I can remember this is only used when you are using the HTTP Service
to make your CXF services available (via the
org.apache.cxf.ws.httpservice.context property, see [1] and [2]). So
you should be able to do one of the
Hi Zoe,
Don't know about the second issue - does it happen if you take the
pure multi bundle distro without any modifications?
Cheers,
David
On 28 October 2010 08:05, zoe slattery zoe.slatt...@gmail.com wrote:
Hi David - excellent - that's what I hoped.
Any thoughts on the second issue -
Hmm, that sounds like a bug then, definitely file a JIRA. Did you try
the actual release too and/or try it with Felix?
Cheers,
David
On 28 October 2010 09:55, zoe slattery zoe.slatt...@gmail.com wrote:
On 28/10/2010 08:42, David Bosschaert wrote:
Hi Zoe,
Don't know about the second issue
of debate is very important to
me. Thank you again!
Cheers,
Fábio
On Tue, Oct 19, 2010 at 12:10 PM, David Bosschaert
david.bosscha...@gmail.com wrote:
Hi Fabio,
Thanks for explaining your question further.
The client side looking for SERVICE_EXPORTED_INTENTS or
SERVICE_EXPORTED_INTENTS_EXTRA
to the consumer side and,
if this is the case, why does createProxy calls applyIntents method?
Thank you, very much again!
Cheers,
Fábio
On Mon, Oct 18, 2010 at 3:57 AM, David Bosschaert
david.bosscha...@gmail.com wrote:
Hi Fabio,
You are right that the service.intents, service.exported.intents
Hi Fabio,
You are right that the service.intents, service.exported.intents and
service.exported.intents.extra are all merged on the distributed
discovery information.
These properties do serve different purposes, however.
On the service provider side:
* service.intents: indicates any intents
On 15 October 2010 10:48, Ronald Müller r.muel...@unicomp-berlin.de wrote:
Finally i solved my issue by kicking the following bundles:
* geronimo-activation_1.1_spec-1.0.2.jar
* org.apache.servicemix.bundles.jaxb-impl-2.1.6_1.jar
* org.apache.servicemix.specs.jaxb-api-2.1-1.3.0.jar
*
On 15 October 2010 14:51, Daniel Kulp dk...@apache.org wrote:
On Friday 15 October 2010 5:57:55 am David Bosschaert wrote:
On 15 October 2010 10:48, Ronald Müller r.muel...@unicomp-berlin.de wrote:
Finally i solved my issue by kicking the following bundles:
* geronimo-activation_1.1_spec
, ext David Bosschaert david.bosscha...@gmail.com
wrote:
Hi Peter,
AFAIK, the CXF-DOSGi subproject doesn't yet support the cxf.xml.
Configuration is done through OSGI-INF/cxf/intents/intent-map.xml
although it doesn't fully support everything yet. Enhancements welcome
:)
Cheers
probably not the cleanest way, but i'm far to new to OSGi to
figure out all of its concepts.
regards
Ronald
Am 12.10.2010 08:49, schrieb David Bosschaert:
Hi Ronald,
I am not aware this is possible yet with the current CXF-DOSGi
codebase. If you are interested in making this possible
Hi Peter,
AFAIK, the CXF-DOSGi subproject doesn't yet support the cxf.xml.
Configuration is done through OSGI-INF/cxf/intents/intent-map.xml
although it doesn't fully support everything yet. Enhancements welcome
:)
Cheers,
David
On 13 October 2010 19:14, Peter Lauri peter.lauri@nsn.com
Hi Ronald,
I am not aware this is possible yet with the current CXF-DOSGi
codebase. If you are interested in making this possible feel free to
take a look at the code an provide patches :)
Just a note on annotations... One point of Distributing OSGi services
was to not have the configuration as
Hi Teemu,
The API for discovery is defined by the OSGi Remote Services Admin
specification (chapter 122 in [1]). The API basically goes through the
EndpointListener.
In the CXF-DOSGi project this is implemented and backed by Zookeeper
as you say. There is a demo for this here:
Hi Fabio,
The extensibility of the intents implementation in CXF-DOSGi is
currently probably a little limited. Maybe you would like to look in
the source code and see if you can come up with an improvement that
would make it more extensible?
Cheers,
David
On 21 September 2010 22:33, Fabio
Hi Sven,
CXF-DOSGi is simply using the cxf-bundle-minimal jar provided by the
main CXF project. If you think that the cxf-bundle-minimal should
contain more classes maybe you should file a bug on CXF for this?
Best regards,
David
On 16 September 2010 14:02, Sven Zethelius sv...@expedia.com
Hi Amogh,
Good point on the confusion between 32 and 81. I fixed that. It should be 81.
A hang like that is almost certainly caused by bundles not starting up
in the right order. At least that's the only time I've ever seen it
before. I know - in an ideal world there shouldn't be a dependency on
Hi Philip,
You should be able to build CXF-DOSGi *without* a settings.xml.
This should also apply to plain CXF...
Cheers,
David
On 21 May 2010 12:35, Philip Yankov duxmas...@gmail.com wrote:
Is it possible for anyone who is using windows to send me his settings.xml
configuration file of
Hi all,
Earlier this week the OSGi Alliance has approved the OSGi 4.2
Enterprise Conformance Tests and Reference Implementations. The
CXF-DOSGi project [1] is the Reference Implementation for the
following OSGi 4.2 specs [2]:
* Chapter 13 - Remote Services
This spec describes Distributed OSGi
Hi Julien,
You are right, this is a known problem
(https://issues.apache.org/jira/browse/DOSGI-69)
I think it's related to the XML parsing not being fully set up
correctly as apparently it tries to go to the internet to resolve XML
Schemas. Not what you want, especially given that these schemas
Hi Julien,
This is configuration for the OSGi Configuration Admin Service. The
Discovery Service consumes it through the OSGi Configuration Admin API
(via a ManagedService:
http://www.osgi.org/javadoc/r4v42/org/osgi/service/cm/ManagedService.html).
There are various ways in which you can feed
Hi Sergio,
Yeah, the osgi.remote.configuration.pojo.httpservice.context property
is currently not yet supported for multiple interfaces...
What should work though is *not* specifying this property. This should
then use the default context for each interface. So if your service is
exporting both
David Bosschaert wrote:
Sure, but it helps pinpointing where the issue is.
If it doesn't work plain, then we know to look in DOSGi.
If it doesn't work with Karaf, then its in the interaction between
DOSGi Karaf...
David
On 22 April 2010 08:14, olamalam ilker.cikrikc...@aspone.co.uk wrote
Hi Julien,
I have wondered about this as well. It would be nice if we could
automatically reconnect to zookeeper after connection loss. I have
noticed that this seems to work if the connection wasn't lost for too
long, but after a while zookeeper seems to give up...
Maybe Marc has some ideas here
Hi Ilker,
Just wondering are you getting it to work outside of Karaf, just with
plain Felix or Equinox?
David
On 19 April 2010 10:42, olamalam ilker.cikrikc...@aspone.co.uk wrote:
Hi to all,
I'm trying to run Spring Dm demo with karaf 1.4 for a couple of days but I
still couldn't manage
Hi Ilker,
Have a look at the CXF-DOSGi Spring-DM demo documentation:
http://cxf.apache.org/dosgi-spring-dm-demo-page.html
I see that you're using the single bundle distro, but when using
Spring you should really use the multi-bundle distro as CXF-DOSGi
itself also uses spring internally, but it
it?
Thanks
Ilker
David Bosschaert wrote:
Hi Ilker,
Have a look at the CXF-DOSGi Spring-DM demo documentation:
http://cxf.apache.org/dosgi-spring-dm-demo-page.html
I see that you're using the single bundle distro, but when using
Spring you should really use the multi-bundle distro as CXF
Hi Ilker,
Did you also put in the following line (which is also in the
felix.config.properties.append file):
org.osgi.framework.startlevel.beginning=81
This is needed to automatically start bundles with felix.auto.start.XX
where XX can be up to 81 in this case.
BTW having two instances of
FYI.
BTW anyone know why Nick might have problems sending to us...@cxf.apache.org?
David
-- Forwarded message --
From: Pan Nick penguin_1...@hotmail.com
Date: 2010/3/29
Subject: Re: Questions About the DOSGi Greeter Demo
To: david.bosscha...@gmail.com
Hi David,
This seems to
registered again hence the multiples...
Hope that 1.2-SNAPSHOT version fixes it for you too.
David
2010/3/25 David Bosschaert david.bosscha...@gmail.com:
Hi Nick,
I have been able to reproduce your problem with CXF-DOSGi 1.1.
The good news is that it seems to be fixed on trunk. Try installing
Hi Nick,
I have been able to reproduce your problem with CXF-DOSGi 1.1.
The good news is that it seems to be fixed on trunk. Try installing
the single bundle distro from [1] and see if that helps.
Hope this helps,
David
[1]
I also had a look at the patch. While the code looks fine to me I'm
concerned that there is no unit tests with it.
David
On 19 March 2010 14:54, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi Josh
On Fri, Mar 19, 2010 at 7:09 AM, Josh Holtzman jholtz...@berkeley.eduwrote:
Hi Sergey,
The
Hi Nick,
This seems to be the same issue as discussed here:
http://old.nabble.com/Re:-Problem-with-Distributed-OSGi-and-complex-data-types-%28AWT%29-td26329316.html
Bottom line is, that you have to design your interfaces to be suitable
for remoting with DOSGi and the AWT classes aren't designed
Hi Norbert,
That's good to know thanks for trying it out!
The CXF-DOSGi trunk version has gone through a refactoring effort to
make it compliant with the OSGi 4.2 Remote Service Admin standard.
There are a few small things that we still have to work on and
documentation and backward
is to pack up all my Felix and Zookeeper folders and
the startup scripts and put it up somewhere for download. Estimated size is
65MB. Let me know if you would like me to do this.
Norbert
David Bosschaert wrote:
Sorry - I thought you were also using a custom bundle.
Now
Hi Chris,
WRT to the Felix, you could try Equinox and see if that solves the
hanging issue.
On your custom bundle, this is the remote service client bundle right?
You say: when I try and use the ServiceTracker object (or the
Context.getServiceReference method) I am unable to retrieve the
service
crazy about the support for RMI/JMS/etc..., these were just
examples, and probably bad ones to supply because of their nature (not based
on HTTP), but I can see you know what I generally mean...
Chris Clark
Audio, Video, Disco
-Original Message-
From: David Bosschaert
Hi Chris,
Yes, this should be possible. The idea of using OSGi services and then
distribute them without having to worry about the protocol is exactly
what we had in mind when developing DOSGi!
The CXF-DOSGi implementation currently supports: SOAP/HTTP and
REST/HTTP. They can be configured by
Hi Christopher,
Have a look at the CXF-DOSGi Greeter Demo walkthrough:
http://cxf.apache.org/distributed-osgi-greeter-demo-walkthrough.html
It shows you how to use CXF-DOSGi from within Felix and Equinox. It
should give you a working baseline that you may be able to build on
top of...
Best
Hi all,
Sorry for chiming in late. I was on leave...
On why these new bundles are part of the 1.1 single bundle distro.
With 1.1 support for distributed discovery was now implemented. The
discovery component uses the OSGi Configuration Admin service so
that's why it was added to the single
Hi Heiko,
I definitely agree with Alexander. Using the dynamic discovery will
handle all of this for you. You don't need a service-description
descriptor on the client side at all any more when using that. The
discovery demo should explain it all.
Cheers,
David
On 2 February 2010 14:40,
Hi Sergey,
In CXF-DOSGi we have the option to use a similar mechanism, whereby
we're registering CXFNonSpringServlets with pax web (through the OSGi
HTTP Service) to make them available. The way it's done is one servlet
per service which means that they don't have to share a context, but
they do
Hi FrozenQ,
I have seen this message before and although ugly it was harmless in
my experience.
I just tried to reproduce your problem with Eclipse 351 and the
CXF-DOSGi 1.1 multi-bundle release and didn't actually get the
exception. Things worked fine for me.
When starting all bundles that come
Hi Gpinkham,
I don't think anyone has tried this yet. Obviously CXF itself supports
it, but the CXF-DOSGi code might need some additional configuration to
support it.
David
2010/1/11 Gpinkham gpink...@kronos.com:
Did a quick search thru the mailing list and didn't quite see the answer..
:
By CXF-DOSGi code might need some additonal configuration do you mean me
supplying some XML/properties or that the actual code of DOSGi needs to
change?
Thanks again
Gary
David Bosschaert wrote:
I don't think anyone has tried this yet. Obviously CXF itself supports
it, but the CXF
Hi Alexander,
I haven't tried sending EventAdmin Events with CXF-DOSGi, but there is
a project called LightSabre that does this using Active MQ, see here:
http://lightsabre.fusesource.org/
I believe that the Eclipse ECF project also provides similar functionality.
Hope this helps,
David
-cxf-1.1.jar
(i.e. have to wait for all the timeouts).
Thanks,
Thom
-Original Message-
From: David Bosschaert [mailto:david.bosscha...@gmail.com]
Sent: Tuesday, December 22, 2009 9:19 AM
To: users@cxf.apache.org
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download
Hi Thomas,
Hmmm, I would think so, but the 1.1 release also has 2.2.4.
I'll update the build system to pick up 2.2.5.
BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT
at this moment in time as there is a lot of refactoring going on @
dosgi trunk [1]. So unless you like
I've just updated CXF/DOSGi trunk to use CXF 2.2.5
BTW you should be able to use CXF 2.2.5 with the DOSGI 1.1 release. In
the multi bundle distro, just replace the cxf-bundle-minimal-2.2.5.jar
with the 2.2.5 version. Haven't tried it but it should work...
Cheers,
David
2009/12/22 David
: []
-Original Message-
From: David Bosschaert [mailto:david.bosscha...@gmail.com]
Sent: Tuesday, December 22, 2009 6:27 AM
To: users@cxf.apache.org
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
I've just updated CXF/DOSGi trunk to use CXF 2.2.5
BTW you should
single bundle distros).
Thanks,
Thom
-Original Message-
From: David Bosschaert [mailto:david.bosscha...@gmail.com]
Sent: Tuesday, December 22, 2009 7:23 AM
To: users@cxf.apache.org
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
Hi Thomas,
The 1.2-SNAPSHOT CXF
Hi Alexander,
Yes, at the moment the discovery implementation relies on the
objectClass being set. The reasoning behind this relates to
scalability. If you have a large distributed discovery system you
probably don't want to select all the available remote services in the
system, as that could
.
I filed a jira issue for the request:
https://issues.apache.org/jira/browse/CXF-2580
Alexander
On Fri, Dec 11, 2009 at 12:37 PM, David Bosschaert
david.bosscha...@gmail.com wrote:
Hi Alexander,
Yes, at the moment the discovery implementation relies on the
objectClass being set
to be expected.
Again, thanx for the quick fix!
On Wed, Dec 9, 2009 at 12:16 PM, David Bosschaert
david.bosscha...@gmail.com wrote:
Hi Alexander,
I tried to reproduce your issue on both Windows XP and Linux (Ubuntu
9.10) with JDK 1.6 but wasn't able to.
As an experiment I modified the start
Hi Alexander,
On the face of it this should work just fine.
Could you please file a JIRA for this issue and attach a small
testcase to reproduce your problem?
https://issues.apache.org/jira/secure/CreateIssue!default.jspa
Thanks,
David
2009/12/9 Alexander Broekhuis a.broekh...@gmail.com:
Hi
Hi Bernd,
On your questions:
(a) instead of going the route of generating the java source code and
compiling that (which should work) you could take a look at libraries
like CGLib (http://cglib.sourceforge.net) or ASM
(http://forge.ow2.org/projects/asm) they should allow you to do this
without
Hi Kits,
If you're using the built-in Jetty from CXF (which is the default) you
simply put the port you want in the org.apache.cxf.ws.address
property, e.g. for port 9876 you do
props.put(org.apache.cxf.ws.address, http://localhost:9876/greeter;)
If you're using the OSGi Http Service instead
Hi Bernd,
There are two ways in which you could do this with CXF-DOSGi.
1. With DOSGi you simply register your Java Object as an OSGi Service
with the following Service Registration property:
service.exported.interfaces=...
As the value you provide the name or names of all the interfaces (or
Hi Jozsef,
I'm copying users@cxf.apache.org as that's a good place to discuss
these questions.
What you're asking should be possible as long as the container that
you're running in registers the OSGi HTTP Service. As you're already
in Equinox I suspect that this is happening already (you can
the OSGi container like the functionality of the
bridgeservlet in the equinox's servletbridge.
For a better understanding I attached an architecture sketch.
Best regards,
Jozsef
-Original Message-
From: David Bosschaert [mailto:david.bosscha...@gmail.com]
Sent: Thursday, November 26, 2009 12
Hi Bodgan,
(Including users@cxf.apache.org since your question is better handled
on a mailing list where more people than just me can provide help)
First of all, when you say D-OSGi I assume you mean the CXF-based
D-OSGi Implementation (http://cxf.apache.org/distributed-osgi.html).
The
I'm only guessing but it might be related to XML schema resolution. I think
it still tries to go to remote hosts to resolve the schemas in some cases,
even though they are available in the bundle.
One way to try this out is to start it up without a network. I have seen
stack traces appear without
Yeah, pretty much all of the samples require 1.1-SNAPSHOT. Hopefully we'll
get a 1.1 release soon...
Looks like the Maven repo server on https://repository.apache.org/ has died.
Anyone an idea how to get it back up?
In the mean time you can build your own 1.1-SNAPSHOT by checking out
Yes, make sure the the configuration in your
OSGI-INF/remote-service/remote-services.xml file contains the right host
name (by default it contains localhost). Assuming you're not using discovery
this file must contain the correct URL of the remote service.
If you run the system using discovery,
will try using discovery.
Please, can you confirm if using the discovery I still need the OSGI-INF
files (intent-map.xml remote-service.xml) that I am using for the
original
Greeter example?
Thanks in advance.
Kind regards.
Maurizio
David Bosschaert wrote:
Yes, make sure
Hi,
This is really a Fuse support issue, so you're right in posting it on the
fusesource forums.
I guess in general, the best way to approach something like this is by
taking individual bundles from the multi-bundle distro's (as you've done).
Start with root bundles and cxf-dosgi-ri-dsw-cxf and
Hi Miguel,
(copying users@cxf.apache.org)
Yes, you can return certain objects, have a look at the Greeter Demo on the
CXF-DOSGi wiki:
http://cxf.apache.org/distributed-osgi-greeter-demo-walkthrough.html
It has the following Service Interface:
public interface GreeterService {
, David Bosschaert wrote:
greetMe
1 - 100 of 133 matches
Mail list logo
