does not have be
implemented literally the way it's documented in the spec, rather the final
result should be correct.
So let me know please what exactly is happening in your case
Thanks, Sergey
-Original Message-
From: Tong, Gary [mailto:gary.t...@morganstanley.com]
Sent: 11
a number of criteria.
Another thing is that the JAX-RS selection algorithm does not have be
implemented literally the way it's documented in the spec, rather the final
result should be correct.
So let me know please what exactly is happening in your case
Thanks, Sergey
-Orig
Hello,
Hey guys, just fyi, CXF's jax-rs doesn't do request matching correctly.
According to JSR 311 in section 3.7.2, the jax-rs server is supposed to apply a
series of steps to determine which URL to use for the request. Instead, CXF
applies a path filter at the class level, and then returns
t would qualify ? Would you define the scope
differently ?
cheers, Sergey
- Original Message -----
From: "Tong, Gary (IDEAS)"
To:
Sent: Tuesday, April 07, 2009 2:21 PM
Subject: RE: JSON in CXF
Would you want to give this to someone from GSoC? This could actually b
eek I should be able to package something together
> and send it to you.
it would be super, take your time please...
> Rewriting Sun libraries? Working with JSON? Hells yeah.
that's the right attitude :-).
cheers, Sergey
- Original Message -----
From: "Tong, Gary (IDEAS)&q
Hi Sergey,
If you give me until next week I should be able to package something together
and send it to you.
Alternatively, this would be a great project for GSoC, if it's not too late to
submit projects. Rewriting Sun libraries? Working with JSON? Hells yeah.
Cheers,
Gary
-Original Me
Is there any value in allowing a method to respond to both GET and POST
requests?
Currently something like:
class Foo {
@GET
@POST
public String test() {...}
}
Only responds to @GET but does not respond to @POST.
I agree that conceptually, @GET and @POST should be completely different
m
pache.org]
Sent: 09 March 2009 18:53
To: dev@cxf.apache.org
Cc: Tong, Gary (IDEAS)
Subject: Re: ProviderFactory singleton?
It's not just OSGi as well. One way of setting up CXF with tomcat is to put
the CXF jars into the tomcat shared/lib directory and then deploy 100
wars/applications each
continue working on this bit. When I get time I'll probably look into how best
to change the ProviderFactory singleton bit.
Cheers,
Gary
-----Original Message-
From: Tong, Gary (FID)
Sent: 22 December 2008 15:51
To: dev@cxf.apache.org
Subject: Issue with multiple CXF servlets (and pro
like to
>> understand better when it may be unrealistic to ensure that different
>> endpoints have their own addresses : perhaps there're policies on
>> which uri patterns go to web.xml or to resource classes, etc ?
>>
>> Cheers, Sergey
>>
>>
>
nrealistic to ensure that different endpoints have their own
addresses : perhaps there're policies on which uri patterns go to web.xml or to
resource classes, etc ?
Cheers, Sergey
-Original Message-
From: Tong, Gary (IDEAS) [mailto:gary.t...@morganstanley.com]
Sent: 06 March 2009 11
F servlets, each of them referencing different
spring configuration files ?
Cheers, Sergey
-----Original Message-
From: Tong, Gary (IDEAS) [mailto:gary.t...@morganstanley.com]
Sent: 06 March 2009 09:14
To: dev@cxf.apache.org
Subject: ProviderFactory singleton?
Been looking through the code, an
Been looking through the code, and why is ProviderFactory a singleton? I would
think it would be tied to a bus or a server. It differentiates by address, but
currently I'm working on something with two side-by-side CXF servlets that load
completely different CXF configurations. In this case,
eers, Sergey
-Original Message-
From: Tong, Gary (IDEAS) [mailto:gary.t...@morganstanley.com]
Sent: 24 February 2009 17:23
To: dev@cxf.apache.org
Subject: RE: CXF dual-servlet issues
As far as I can tell, this issue is caused by
RequestPreprocessor.handleExtensionMappings
private vo
week.
I'm about to complete the client api stuff for 2.2. and will dedicate the
remaining time to addressing the various issues raised recently
Cheers, Sergey
- Original Message -
From: "Tong, Gary (FID)"
To:
Sent: Friday, February 20, 2009 6:59 PM
Subject: CXF dual-ser
Will investigate more on Monday, but this is currently breaking in CXF 2.1.4:
context.xml:
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:jaxrs="http://cxf.apache.org/jaxrs";
xsi:schemaLocation="
http://www.springfr
gnored
too. Can you please explain a bit more ? Any links will be appreciated.
Likewise, few more samples with slightly different object graphs but showing
the same pattern in action would help us to come up with a new feature
enhancement request for Jettison
Thanks, Sergey
>
I think it's a limitation of the underlying JSON library. Something like:
@XmlRootElement
public class Foo {
@XmlElementWrapper(name="values")
@XmlElement(name="value")
private List values
}
Gives XML like:
foo
bar
And json like:
{foo: {values: {value: ["foo", "bar"]}}}
Hi guys,
I really like how CXF provides both JSON and XML out of the box. However,
after working with the JSON serializer a bit, it's obvious that the JAXB
annotations translate poorly to JSON, and that while you have great control
over XML via JAXB, JSON via JAXB definitely leaves something t
Hello,
There seem to be issues with @Context-injected fields in ExceptionMapper, where
it throws an NPE with this:
public class MyMapper implements ExceptionMapper {
@Context
private HttpServletRequest request;
public Response toResponse(Exception ex) {
System.out.println(request.getR
lem also be that you specified
> 1 for *both* the servlets defined,
> instead of giving them distinct values? Somehow I doubt that's the
> issue though.
>
> Glen
>
>
>
> Tong, Gary (FID) wrote:
>> Hello,
>>
>> I'm having issues with creating multi
Hello,
I'm having issues with creating multiple CXFServlets. I'm trying to insantiate
2 independent CXF servlets and deploy them at different URLs. The relevant
part of the web.xml looks like:
test
org.apache.cxf.transport.servlet.CXFServlet
1
config-location
/
22 matches
Mail list logo
