On 02.07.2009, at 16:06, David Bosschaert wrote:
If you still have the problem with trunk, please file an issue with
the Distributed OSGi component at CXF:
http://issues.apache.org/jira/browse/CXF
Hi,
I use the trunk of Felix and CXF both with the single and multi
distribution and it works. The issue was about hooks that was not
correctly called, but this is fixed in the Felix trunk.
Regards,
Clement
Cheers,
David
2009/7/2 Karl Pauls <[email protected]>:
On Thu, Jul 2, 2009 at 3:33 PM, Joel Schuster<[email protected]>
wrote:
Thanks all, I've figured out what I needed to get things working...
However, I've been forced to use the single bundle distro 1.0 of
cxf and therefore the old spec for properties.
When I use the 1.1 SNAPSHOT something gets messed up so that the
Shell TUI stops working. I'm looking into some sort of conflict
with the felix' webconsole bundle and/or the felix.http.jetty
bundle.
Should I just move to felix 1.8.1?
You might have to move to trunk.
regards,
Karl
- Joel
-----Original Message-----
From: Clement Escoffier [mailto:[email protected]]
Sent: Thursday, July 02, 2009 3:12 AM
To: [email protected]
Subject: Re: iPojo as WebService
On 01.07.2009, at 20:02, Richard S. Hall wrote:
On 7/1/09 1:39 PM, Clement Escoffier wrote:
Last things, to work I started two gateway:
- Felix 1.8.1 with iPOJO, Compendium, CXF (Snapshot) single
bundle,
AdderServiceInterface and AdderServiceProvider
- Equinox 3.5 with iPOJO, OSGi service, OSGi Utils, CXF
(Snapshot)
single bundle, AdderServiceInterface, AdderServiceImporter and
AdderServiceConsumer
For some strange reason, I was not able to import the service
from
Felix... Maybe a detail of CXF that I ignore. equinox 3.5 is
required as CXF relies on ServiceHooks.
Felix has implemented the service hooks needed by CXF for a little
while now, I think. Trunk has full support, although I have some
outstanding patches to commit for the TCK.
Good news.
It works on the latest Felix trunk !
Regards,
Clement
-> richard
Regards,
Clement
On 30.06.2009, at 20:41, Joel Schuster wrote:
Great, thanks!
I can't get it to work at all. This actually may be more a
question then for the CXF people, just let me know. I'm not sure
which properties to set. Based on what you see on those links I
referred to, @ServiceProperty is the correct annotation to use,
right?
Do you know of a single bundle solution that iPojo integrates
easily with? I'd like to just provide a simple annotation or
config property and have it just make my service available
automatically.
Why did you make the decision to write your own?
- Joel
-----Original Message-----
From: Bourret Pierre [mailto:[email protected]]
Sent: Tuesday, June 30, 2009 9:54 AM
To: [email protected]
Subject: Re: iPojo as WebService
Hi Joel.
I'm daily using iPOJO service as web services. I don't use CXF
but a
home-made Distributed Service implementation. However, it
should
be very
similar.
Feel free to ask me if you encounter any issue.
--
Pierre Bourret
2009/6/30 Joel Schuster <[email protected]>
I'd like to expose my iPojo as a WebService.
I'm using the Distributed OSGi single bundle from apache cxf:
http://cxf.apache.org/distributed-osgi.html
Based on what I read, (http://cxf.apache.org/dosgi-ds-demo-page.html
)
theoretically I should be able to take a working iPojo based
service and
add
add a few @ServiceProperties and deploy a .cfg file with
FileInstall
bundle:
osgi.remote.interfaces=*
osgi.remote.configuration.type=pojo
osgi.remote.configuration.pojo.address=http://localhost:9090/mypojoservice
Has anyone tried this or something similar without having to
add
the
overhead of going all the way to ServiceMix?
Any help would be appreciated.
- Joel
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Karl Pauls
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
