Well, you can store the actual configuration somewhere else and use the current
mechanism to provide a pointer. Or just store it in XML/JSON in a string/byte[]
in the configuration?
Alternatively you can map the configuration of virtually an XML to properties
using nested property names and integers for elements
<a><b>3</b><b>1</b></a> -> a.1.b=1
We consciously prevented the complexity of XML Schemas to allow things like
Metatype (see Webconsole's editor) since we expected the configuration data to
be relatively simple. However, there are no limits to the byte[] length or
String length so this allows you to encode more complex data. Although this
will not give you the automatic UI.
Kind regards,
Peter Kriens
On 1 okt. 2013, at 16:59, 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é (@rotty3000)
> Senior Software Architect
> Liferay, Inc. (@Liferay)
>
>
>
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
