OK, I got reading in place. Starting from org.apache.cxf.jaxrs.provider.AegisElementProviderTest you can see the whole business. Note that I did not put a cache into the no-namespace provider, and that the modularity of the abstract provider does not allow you to take control of this part of the business and let it have a cache. So you'll need your own.
On Mon, Oct 4, 2010 at 9:39 PM, Benson Margulies <[email protected]> wrote: > How about: > > <?xml version='1.0' encoding='UTF-8'?><AegisTestBean > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:type="AegisTestBean"><boolValue>true</boolValue><strValue>hovercraft</strValue></AegisTestBean> > > I'm about to check in a demo of how to make that work. Warning: I've > only tested the 'write' side so far. > > On Mon, Oct 4, 2010 at 8:59 PM, Benson Margulies <[email protected]> > wrote: >> I bet that this isn't good enough for you due to the namespace on the >> top level element. >> >> rt/frontend/jaxrs/src/test/java/org/apache/cxf/jaxrs/provider/NoNamespaceAegisElementProvider.java >> >> did this much. >> >> I will next look into where that top namespace comes from and what it >> would take to get rid of it. I think we are now talking about type >> mapping, and we'll need a custom type mapping to fix THAT. >> >> On Mon, Oct 4, 2010 at 8:53 PM, Benson Margulies <[email protected]> >> wrote: >>> >>> I created a test case for this, and it seemed to work. >>> >>> <?xml version='1.0' encoding='UTF-8'?><ns1:AegisTestBean >>> xmlns:ns1="http://fortest.jaxrs.cxf.apache.org"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xsi:type="ns1:AegisTestBean"><boolValue>true</boolValue><strValue>hovercraft</strValue></ns1:AegisTestBean> >>> >>> I'm going to check it in so you can easily see it. >>> >>> >>> >>> -- >>> View this message in context: >>> http://cxf.547215.n5.nabble.com/Aegis-Binding-without-namespaces-tp2880205p3198672.html >>> Sent from the cxf-user mailing list archive at Nabble.com. >>> >> >
