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
b
I think I'm beginning to get the idea of what I'm trying to complain about.
An AegisDatabinding object has input configuration and it has state.
As it goes along, it constructs mappings for types.
I'm having trouble swallowing a situation in which each individual
JAX-RS item does this independent
On Jul 31, 2008, at 1:51 PM, Benson Margulies wrote:
Proposal:
The service configuration will obtain the data binding from the
service factory. If it is Aegis, it will extract the desired
customizations. If it is not Aegis, it will do nothing. It will NOT
independently pull in and parse the X
On Jul 29, 2008, at 6:07 PM, Rao, Sameer V wrote:
Hi,
Wanted to check when is the JiBX support planned for release. Also, is
it possible for users to user a message binding (work with the xml
stream) and internally use JiBX (a stop-gap arrangement until jibx is
natively support for webservice
