Hey Ben,
First, I want to tell I'm amazed with the FeatureChaining stuff. It's like taking a deep breath compared to the old, eager fetching approach.
I managed to have a configuration for trunk with the MappedFeature config and a custom one I'm trying to set up. Both app-schema mappings work perfectly, and, though I'm able to see the nested attribute structure on the generated GML, I wonder why the simple attributes do not show up, though they're there in the Feature instances.
Are there any outstanding commits pending on the GML encoding front?
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Gabriel Roldan wrote:
First, I want to tell I'm amazed with the FeatureChaining stuff. It's like taking a deep breath compared to the old, eager fetching approach.
Yep, Rini did a great job. The most amazing thing is that you can even have nested properties coming from different databases.
I managed to have a configuration for trunk with the MappedFeature config and a custom one I'm trying to set up. Both app-schema mappings work perfectly, and, though I'm able to see the nested attribute structure on the generated GML, I wonder why the simple attributes do not show up, though they're there in the Feature instances.
Are there any outstanding commits pending on the GML encoding front?
Yes, I just got approval from Justin for GEOT-2474. This is the big one, and it fixes just about everything. I will commit it today. (Although it looks like Hudson is wedged.)
Let me know if this patch fixes the problems you see. Which attributes are missing?
Kind regards,
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia