On Tue, Mar 3, 2015 at 10:32 AM, Jan Willem Janssen < [email protected]> wrote:
> Hi Raymond, > > > On 03 Mar 2015, at 16:24, Raymond Auge <[email protected]> wrote: > > […] > > However, a metatype implementation change would be required but ONLY for > > access to said new "hints" information. This would require: > > > > 1) reading the extra schema info while parsing the metatype xml > > 2) providing API access to the information > > > > Implementing > > 1) is simple, just need to enhance the parser with the fields we decide > > 2) I was thinking of something like the following: > > […] > > IIRC, the MetaType spec already allows for optional attributes to be > defined > on ADs, Attributes, OCDs and Objects. I believe that this would already > cover > most of these requirements, not? > Sure! However, the need to read the metatype again is painful when metatype is already reading it. Furthermore, this doesn't work for MetatypeProviders. - Ray > > -- > Met vriendelijke groeten | Kind regards > > Jan Willem Janssen | Software Architect > +31 631 765 814 > > My world is revolving around INAETICS and Amdatu > > Luminis Technologies B.V. > Churchillplein 1 > 7314 BZ Apeldoorn > +31 88 586 46 00 > > http://www.luminis-technologies.com > http://www.luminis.eu > > KvK (CoC) 09 16 28 93 > BTW (VAT) NL8169.78.566.B.01 > > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
