To clarify, the config metadata model doesn't seem to be enough to support this level of complexity.
On Tue, Oct 1, 2013 at 10:59 AM, Raymond Auge <[email protected]>wrote: > Hello everyone, > > I'm wondering the best approach for modelling hierarchically complex > configuration data in DS > > For example, Portlets (JSR-168/286) have rather complex configuration > http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd. > > If I wanted to model a Portlet as a DS component, I have a hard time > mapping the complexity. > > Any ideas how to model this? > > I could ref an XML resource or some other weirdness, but is there perhaps > a more elegant approach? > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect > *Liferay, Inc.* <http://www.liferay.com> (@Liferay) > > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay)
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
