jmholtz...@gmail.com [mailto:jmholtz...@gmail.com] On Behalf Of
Josh Holtzman
Sent: 31 August 2009 13:04
To: dev@cxf.apache.org
Subject: Re: Integrating JAX-RS runtime into DOSGi
This works when specifying a single property, but not as an array. In
other
words, this is fine:
bu
Missed 'would result in the array value being passed'...
-Original Message-
From: Sergey Beryozkin [mailto:sbery...@progress.com]
Sent: 31 August 2009 13:10
To: dev@cxf.apache.org
Subject: RE: Integrating JAX-RS runtime into DOSGi
Ok, I d
04
To: dev@cxf.apache.org
Subject: Re: Integrating JAX-RS runtime into DOSGi
This works when specifying a single property, but not as an array. In
other
words, this is fine:
but this does not work:
org.whatever.MyJaxRsReaderWriter,
org.whatever.SomeOtherReaderOrWriter
I seem t
on
> (single or multi) that you use...
>
> thanks, Sergey
>
> -Original Message-
> From: jmholtz...@gmail.com [mailto:jmholtz...@gmail.com] On Behalf Of
> Josh Holtzman
> Sent: 31 August 2009 10:38
> To: dev@cxf.apache.org
> Subject: Re: Integrating JAX-RS run
36
To: dev@cxf.apache.org
Subject: RE: Integrating JAX-RS runtime into DOSGi
Hi
I've implemented just now on the trunk. I have the unit test only
assuming that the calling BundleContext will be used to load the classes
- can you please verify it?
I'm not sure when exactly the Hudso
n
Sent: 31 August 2009 10:38
To: dev@cxf.apache.org
Subject: Re: Integrating JAX-RS runtime into DOSGi
I'm using declarative services to register my endpoints, so it would be
useful for me to specify the provider property using class names rather
than
instances in the service properties. Perhaps
would be of help.
>
> thanks for your help
>
> Sergey
>
> - Original Message ----- From: "Josh Holtzman" >
> To:
> Sent: Wednesday, August 26, 2009 5:37 PM
>
> Subject: Re: Integrating JAX-RS runtime into DOSGi
>
>
> Bah, my isReadable and isWri
tances on a per-endpoint basis with jaxrs:endpoints
then it would be of help.
thanks for your help
Sergey
- Original Message -
From: "Josh Holtzman"
To:
Sent: Wednesday, August 26, 2009 5:37 PM
Subject: Re: Integrating JAX-RS runtime into DOSGi
Bah, my isReadable and isWri
o ping you on #cxf but somehow I lost the connection
> - Original Message - From: "Josh Holtzman" >
> To:
> Sent: Wednesday, August 26, 2009 5:02 PM
> Subject: Re: Integrating JAX-RS runtime into DOSGi
>
>
>
> Great, thanks Sergey. I just
utuon ?
I'll look into it...
cheers, Sergey
P.S. was about to ping you on #cxf but somehow I lost the connection
- Original Message -
From: "Josh Holtzman"
To:
Sent: Wednesday, August 26, 2009 5:02 PM
Subject: Re: Integrating JAX-RS runtime into DOSGi
Great, thanks S
Great, thanks Sergey. I just tried this, and wasn't able to read/write an
arbitrary object.
I've registered a MessageBodyReader and a MessageBodyWriter (actually, the
same object) like so:
FooXmlReaderWriter fooReaderWriter = new FooXmlReaderWriter();
context.registerService(MessageBodyR
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
Hi Sergey. Yes, we are using JAXB with both JAX-RS and JAX-WS endpoints.
Josh
On Aug 21, 2009 6:28 PM, "Sergey Beryozkin" wrote:
Hi Josh
Can you please let me know if JAXB is being used for your JAX-RS endpoints ?
I've spotted that for HTTP Service based JAX-RS endpoints no AegisProvider
is be
Ok - for whoever will actually read this email - sorry it's late so my
previous email
may be a bit confusing.
The project I mentioned (included the link) and the Apache CXF
Distributed OSGi seem to
share similarities but the person who is working on that MS thesis is
not really making
a stron
After looking at the project I mentioned - here is the article here on
their web site:
(http://www.dosgi.com/distributed-osgi-webservices-articles-list/39-distributed-osgi-webservices-articles-category/55-initial-idea-distributed-osgi-through-web-services.html)
it seems that the similarities be
Ok so that's it - perfect thanks Sergey
On Aug 21, 2009, at 3:40 PM, Sergey Beryozkin
wrote:
Hi
Have a look here please
http://cxf.apache.org/distributed-osgi.html
cheers, Sergey
Demetris G wrote:
Hey Sergei and Josh
Is the DOSGi you are referring in the essay of an email below
Hi
Have a look here please
http://cxf.apache.org/distributed-osgi.html
cheers, Sergey
Demetris G wrote:
>
> Hey Sergei and Josh
>
> Is the DOSGi you are referring in the essay of an email below the
> Masters thesis I read once (and it became an open source branch of an
> apache projec
Hey Sergei and Josh
Is the DOSGi you are referring in the essay of an email below the
Masters thesis I read once (and it became an open source branch of an
apache project) or is this a separate design?
We worked on a design calked p2pSOA the connected distributed OSGi
containers over p2p te
on the mainline jaxrs work around supporting
the metadata plus some various urgent enhancements but will be able to
reply to all your dosgi jaxrs related queries
Cheers, Sergey
-Original Message-
From: Sergey Beryozkin
Sent: 12 June 2009 14:43
To: 'dev@cxf.apache.org'
Subject: RE: I
Hi all,
2009/6/20 Sergey Beryozkin :
> Hi,
> ... ...
> There's something else David is thinking of doing shortly, possibly next
> week or so. At the moment one has to configure DOSGI properties on the
> individual service basis, either from the code or from the xml. David is
> thinking of introd
us know what you think - comments/objections/etc
and we'll to sort out all the issues.
I'm going to prioritize now on the mainline jaxrs work around supporting
the metadata plus some various urgent enhancements but will be able to
reply to all your dosgi jaxrs related queries
Cheers, Ser
se try the latest trunk (though I'll ping
> you once I can confirm the 2.2.3-SNAPSHOT has been built or please build
> it locally). Please let us know what you think - comments/objections/etc
> and we'll to sort out all the issues.
>
> I'm going to prioritize now on the
supporting
the metadata plus some various urgent enhancements but will be able to
reply to all your dosgi jaxrs related queries
Cheers, Sergey
-Original Message-
From: Sergey Beryozkin
Sent: 12 June 2009 14:43
To: 'dev@cxf.apache.org'
Subject: RE: Integrating JAX-RS runtime into
June 2009 14:20
To: dev@cxf.apache.org
Subject: Re: Integrating JAX-RS runtime into DOSGi
I've attached the jaxws/jaxrs/databinding patch to
https://issues.apache.org/jira/browse/CXF-2252
Thanks,
Josh
On Fri, Jun 12, 2009 at 3:19 AM, Sergey Beryozkin
wrote:
> Hi,
>
> I agree
gt;
> -Original Message-
> From: Eoghan Glynn [mailto:eogl...@gmail.com]
> Sent: 12 June 2009 09:58
> To: dev@cxf.apache.org
> Subject: Re: Integrating JAX-RS runtime into DOSGi
>
> 2009/6/12 David Bosschaert :
> >
> > 2009/6/11 Sergey Beryozkin :
> > ..
g another major patch
point than me just copying his code.
Cheers, Sergey
-Original Message-
From: Eoghan Glynn [mailto:eogl...@gmail.com]
Sent: 12 June 2009 09:58
To: dev@cxf.apache.org
Subject: Re: Integrating JAX-RS runtime into DOSGi
2009/6/12 David Bosschaert :
>
> 2009/
2009/6/12 David Bosschaert :
>
> 2009/6/11 Sergey Beryozkin :
> ...
>> The only question I have is where this model info should reside, in
>> META-INF/cxf-dosgi ? I'll check with Favid/Eoghan
>
> We already use OSGI-INF/cxf/intents for our CXF-DOSGi specific intents
> files, so maybe somewhere in t
Hi Sergey,
2009/6/11 Sergey Beryozkin :
...
> The only question I have is where this model info should reside, in
> META-INF/cxf-dosgi ? I'll check with Favid/Eoghan
...
> thanks, Sergey
We already use OSGI-INF/cxf/intents for our CXF-DOSGi specific intents
files, so maybe somewhere in the OSGI-I
There's some uinfortunate typo in my last message, hope David won't notice it
:-)
- Original Message -
From: "Sergey Beryozkin"
To:
Sent: Thursday, June 11, 2009 5:11 PM
Subject: Re: Integrating JAX-RS runtime into DOSGi
Hi Josh
Great, I'm glad this is
Hi Josh
Great, I'm glad this is helpful. And thanks for explaining the redundancy
regarding databindings... that makes sense.
I'd seen your comments about "model info" earlier in this or a related
thread, but I don't know what "model info" is.
It is just the alternative way to tell the JAX-R
Great, I'm glad this is helpful. And thanks for explaining the redundancy
regarding databindings... that makes sense.
I'd seen your comments about "model info" earlier in this or a related
thread, but I don't know what "model info" is. Perhaps this is a good time
to hand over the reigns to you?
Hi Josh
This is super, thanks for starting the actual integration project.
> I'm not sure how the cxf-rt-frontend-jaxrs dependency should be handled.
It is embedded inside cxf-minimal-bundle (2,3-SNAPSHOT) so there's no need to
update single or multi bundle distributions.
Yesterday I updated
I'm not sure how the cxf-rt-frontend-jaxrs dependency should be handled.
The work I've done so far [1] will tie the DSW software to the JAX-RS
implementation. Since cxf-rt-frontend-jaxrs isn't an osgi bundle, I'd have
to embed the jar within DSW to satisfy the dependency. This doesn't seem
like a
> I've just updated a cxf-minimal bundle to include a jaxrs frontend and I
> updated the cxf.version in dosgi/parent to 2.3.0-SNAPHOT
>
> (David, Eoghan - we can downgrade it easily to 2.2.2 fixes tag if DOSGi will
> need to be released sooner than 2.3 does which is in about 3 months or so I
> beli
Hi Josh
What do you think about this idea. The factory which returns handlers
can check first if a given service intents include "HTTP" but no "SOAP"
and a frontend.jaxrs property is set, and if yes then it returns
JaxRSPojoConfigurationTypeHandler which will do what
PojoConfigurationTypeHandle
Sergey Beryozkin wrote:
This means that
AbstractPojoConfigurationTypeHandler.createClientProxyFactoryBean()
won't be able to return a JAXRSClientFactoryBean.
What do you think about this idea. The factory which returns handlers
can check first if a given service intents include "HTTP" but
Sergey Beryozkin wrote:
This means that
AbstractPojoConfigurationTypeHandler.createClientProxyFactoryBean()
won't be able to return a JAXRSClientFactoryBean.
What do you think about this idea. The factory which returns handlers
can check first if a given service intents include "HTTP" b
way into OSGIUtils.
>
> I agree it would be great if a common interface was there but may be we
> will be able to get to it at some later stage and collapse handlers into
> a single one...
>
> Thanks, Sergey
>
> -Original Message-----
> From: Josh Holtzman [mailto:jholt
From: Josh Holtzman [mailto:jholtz...@berkeley.edu]
Sent: 06 June 2009 00:47
To: dev@cxf.apache.org
Subject: Re: Integrating JAX-RS runtime into DOSGi
Hi Sergey,
Yes, I would like to work on integrating your JAX-RS work with the
JAX-WS patch I put together. I'm still very inexperienced with CXF
in
Hi Sergey,
Yes, I would like to work on integrating your JAX-RS work with the
JAX-WS patch I put together. I'm still very inexperienced with CXF
internals, so I may need a little hand holding.
I took a quick look at JAXRSClientFactory and JAXRSClientFactoryBean.
It looks like these don't sh
40 matches
Mail list logo
