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
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,
I agree, putting the jaxrs-specific resources into OSGI-INF/cxf/jaxrs
makes sense.
I'll wait for Josh to submit his patch and then I'll add a simple demo
and also tests if needed. Josh has already kindly shown all the code in
his code review page, but I'd rather him collecting another major p
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, putting the jaxrs-specific resources into OSGI-INF/cxf/jaxrs
> makes sense.
> I'll wait for Josh to submit hi
Fantastic, thanks a million. I might not be able to apply it today as
I'd like to finish some initial WADL work but I will start working with
it on Monday
Cheers, Sergey
-Original Message-
From: jmholtz...@gmail.com [mailto:jmholtz...@gmail.com] On Behalf Of
Josh Holtzman
Sent: 12 June 2
Hi CXF Team,
what's the current CXF roadmap from WS-* point of view?
What specs are you going to work on next and what is the schedule for them?
The roadmap as defined here:
http://cxf.apache.org/roadmap.html
just specifies "Other WS-* stuff"
Richard
--
Richard Opalka
JBoss Software Enginee
One thing I've had at the back of my mind is WS-RM 1.1 support.
Is that something that would be of interest to you?
Cheers,
Eoghan
2009/6/12 Richard Opalka :
> Hi CXF Team,
>
> what's the current CXF roadmap from WS-* point of view?
> What specs are you going to work on next and what is the sch
I've got some code that allows OSGI bundles to use the whiteboard pattern to
register restful services. When a service is registered with a specific
property, say, "jaxrs.resource=true" the JAX-RS implementation registers
that service as a JAX-RS resource. The same could be done with message body
Hi Eoghan,
I'm interested mainly in WS-Trust and WS-Management now ;)
Richard
Eoghan Glynn wrote:
One thing I've had at the back of my mind is WS-RM 1.1 support.
Is that something that would be of interest to you?
Cheers,
Eoghan
2009/6/12 Richard Opalka :
Hi CXF Team,
what's the cur
I've updated the roadmap with stuff *I* know about:
http://cwiki.apache.org/confluence/display/CXF/Roadmap
Since we JUST moved trunk 2.3 development, it's a bit early. If others have
cool stuff to add, please add it to the list.
Dan
On Fri June 12 2009 9:50:29 am Richard Opalka wrote:
> Hi
WS-Trust
WS-Management
Is interesting us Daniel ;)
Richard
Daniel Kulp wrote:
I've updated the roadmap with stuff *I* know about:
http://cwiki.apache.org/confluence/display/CXF/Roadmap
Since we JUST moved trunk 2.3 development, it's a bit early. If others have
cool stuff to add, please add
Hi Josh
It seems that in DOSGi RI this is actually what is being done. When a
service is being registered a DSW provider picks up this event and
creates an endpoint. So it should work in the case of JAX-RS & JAX-WS
with the help of properties you introduced in your patch.
David told me that if a
Yeah, so simply putting the property
osgi.remote.interfaces=*
on an OSGi service that is put in the OSGi service registry makes it
available remotely through CXF/DOSGi. If you select the JAX/RS
configueration type (which is currently being worked on) it should
make it available via JAX-RS
Isn't
In the patch I submitted, I don't think there's a way to expose a service as
both a wsdl-based endpoint and a restful endpoint. I've been using the
wsdl-based endpoints for DOSGi communication (hence, my initial focus on
JAX-WS and the JAXB databinding), and registering jax-rs resources
separately
Hi Josh,
With the upcoming OSGi 4.2 remote services spec (should be out this
summer) you should be able to do this with a single service that
specifies two configuration types.
Let's say the configuration types are pojo (for the web service -
maybe we need to give this a more descriptive name) and
Yes, you can expose the same service bean using JAXWS & JAXRS.
So registering the same instance using diff frontend property should
work.
The only limitation at the moment is that a different address needs to
be specified, that is say it should be
"http://localhost:8080:services/jaxws";
and "http:/
Ok great, thanks Sergey and David! I'll just expose the service twice
for now, and update my DS descriptors when the 4.2 spec is released,
and when Cxf supports the new syntax.
Josh
On Friday, June 12, 2009, David Bosschaert wrote:
> Hi Josh,
>
> With the upcoming OSGi 4.2 remote services spec
17 matches
Mail list logo
