>> The default bindings handle things like xs:int and know enough to turn >> that into an Integer. The default binding for an a complex type (at least >> for an earlier version of the parser!) would produce a java.util.Map with >> the keys as the element name and the value as appropriate. > > I see! What about namespaces: they are part of the Map's key? > They could be :-) or we could use that compound name. Remember you can define the binding for complex in your configuration before you run the parser - so these questions should be explored and we can code in the most useful result as the default (providing Justin agrees).
>> The advantage here is anything that *can* be bound is punted into a java >> object - geometry; feature etc should show up ready to go. >> >> So this is the theory; Rob is running into the limits of what this default >> complex binding can do.... > > Ok. Last question: Having a String with the xml fragment won't help me? > Instead I have to build this Map based tree out of it as shown above? Um building the map based tree should happen without you doing anything. (providing it does not die on the "wrapper" schema you provided it). We only tested with the simple geometry wrappers provided by the WPS spec; nothing as fun as the example you provided... > Thanks again, Happy hacking, Jody ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
