Hi,
I'm getting into trouble here now that I'm debugging a test case.
readFrom takes ClassObject, not Class?. I don't see how the JAXB
code could work, as it will try to obtain a type for 'Object.class',
Unfortunately Class? does not compile. Plain Class is passed in to it from above and it
The RI/required section of the 1.0 FR calls for a MessageBodyReader
that delivers JAXBElements! In other words, they aren't really
thinking about delivering arbitrary Java objects. Since putting
@Provider on a generic class is likely to prove chaotic (or maybe it
just works), I'm not quite sure
Hi,
First the good news - I heroically :-) fixed the AegisTest by adding a plain old cast when passing AegisTestBean.class and your
provider works perfectly well. This is how it works for JAXB too.
The RI/required section of the 1.0 FR calls for a MessageBodyReader
that delivers
Hi
Do you participate in the JSR Process for this thing? As the FR
stands, @Provider seems to be required.
I don't participate - I started working with our JAX-RS impl at the time it was
at 0.5 or 0.4 level.
I'm asking questions though periodically.
@Provider is needed only if a CXF user
OK, here's the problem. I don't know how providers actually get used
in the real code. I guess it's time to clone the systest and see how
it comes out.
You won't see then in the actual system tests. Actually, there're custom providers there, but they're registered from Spring and
that's the
The question lurking here is the official API of the
MessageBodyReader. How does the interceptor choose the right class to
pass to it?
On Tue, Oct 21, 2008 at 1:26 PM, Sergey Beryozkin
[EMAIL PROTECTED] wrote:
OK, here's the problem. I don't know how providers actually get used
in the real
I'm getting into trouble here now that I'm debugging a test case.
readFrom takes ClassObject, not Class?. I don't see how the JAXB
code could work, as it will try to obtain a type for 'Object.class',
which is the only thing in the world of type ClassObject, AFAIK. My
code certainly won't work. I
I also note that even the systest never calls the JAXB 'readFrom'
routine. You really need a test for that.
On Mon, Oct 20, 2008 at 8:20 PM, Benson Margulies [EMAIL PROTECTED] wrote:
I'm getting into trouble here now that I'm debugging a test case.
readFrom takes ClassObject, not Class?. I
Hi Benson
I missed your merge email to the jax-rs module, the one introducing the AegisProvider. Even though there might still be some work
left to do there, this is great nonetheless, thanks. Perhaps Aegis fans such as Dan Diephouse will notice it too :-). In CXF JAX-RS
we can support 3 data
; Daniel Kulp
Subject: Re: Aegis versus jaxrs
OK, now we reach the crux of the matter. JAX-RS creates lots of
JAXBContexts, where 'normal' CXF manages to share one through an
entire service. Am I getting the idea that this is just an inescapable
aspect of the architecture? It could get slow.
Aegis
precedence over the default JAXB provider which handles
application/xml...
Cheers, Sergey
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: 14 October 2008 12:50
To: dev@cxf.apache.org
Subject: Re: Aegis versus jaxrs
I appreciate the cache. However, the minimum
@cxf.apache.org
Subject: Re: Aegis versus jaxrs
I think I finally have a sensible question by analogy with JAXB.
JAXBContext objects have a variety of options and properties. The
JAXBDataBinding allows the CXF app to control these items. The user
can make their own context and inject it into the data
about the one from javax.xml.validation
?
I just added it recently to support the optional schema validation...
Cheers, Sergey
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: 12 October 2008 12:13
To: dev@cxf.apache.org
Subject: Re: Aegis versus jaxrs
I
Hi
When a CXF service offers JAX-RS, some CXF-specific configuration is
involved, no? So, could we not have some properties at the service level
which the ProviderFactory consumes-if-provided? Aegis in particular has a
set of configuration options, it would be very cumbersome to force those to
When a CXF service offers JAX-RS, some CXF-specific configuration is
involved, no? So, could we not have some properties at the service level
which the ProviderFactory consumes-if-provided? Aegis in particular has a
set of configuration options, it would be very cumbersome to force those to
be
15 matches
Mail list logo
