On Thu, Oct 25, 2012 at 12:45 AM, Justin Deoliveira <[email protected]> wrote: > Hey Andrea, > > SO yeah, the way the encoder delegate works now is if an object to be > encoded doesn't match a binding, it is checked as an instance of > EncoderDelegate. And if so the encoder control is passed off to it. So > indeed one option would be to add something like: > > List<Object> getExtendedCapabilities() > > To the EMF model. And if those objects implement EncoderDelegate I think it > would just work.
Turns out I was a bit confused, and the extended caps that I was looking for is in OperationsMetadataType, which already had it as a field (but as an Object, not as a List<Object>). However it was breaking because there was code in the impl package trying to cast it to an EObject. After some research turned out to be EMF proxy handling, which I disabled in the ecore file manually for that property (tried to do so by annotations, but could not find a reference containing directions on how to do so). Then added a test in the xsd-csw module, and it worked just peachy. Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
