Dutertry, Nicolas wrote:
Hi,
I'm trying to use the "skin" attribute to control the behaviour of a
decorator but it is not very practical because the defaulting doesn't work.
We also use the skin attribute in the Jetspeed Desktop to select which
desktop theme is displayed on the page.
The "skin" attribute can be defined in a folder or in a page (in the
<defaults> element) or in a portlet fragment.
I thought that the skin of a fragment inherited from the <defaults> of the
page (or folder) if it was not defined but it is not the case.
Why put such an attribute in the <defaults> element if it is not used as a
default?
Well, its just not used in the /portal. Perhaps we should have done this
differently, but the "skin" is only used to store the desktop theme for
a page. So if you are not planning on using the Jetspeed desktop, you
can overload this attribute but be aware that it will conflict with the
/desktop
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
