Does a definition such as this have sense?
<definition name="myName" extends="myExtends" path="path.jsp">
...
</definition>
This is just because I have a problem with inheritance between multiple
files.
Say I have two files, where the second extends the first.
The first definition file contains:
<definition name="page.index" path="/layout/classic_layout.jsp">
<put name="top" value="/tiles/top.jsp"/>
<put name="left" value="/tiles/fourth.jsp"/>
<put name="body" value="/tiles/login.jsp" />
</definition>
The second file contains:
<definition name="page.index.bug" path="/layout/three_rows_layout.jsp" />
<definition name="page.index" extends="page.index.bug">
<put name="top" value="/tiles/top_pda.jsp"/>
<put name="left" value="/tiles/fourth.jsp"/>
<put name="body" value="/tiles/login.jsp" />
</definition>
When I use XmlDefinitionSet.extend method, the "page.index" definition
has both the "extends" (in fact "inherit") and "path" attributes! After
doing "resolveInheritances" it does not solve the problem.
I think the (possible) bug is in XmlDefinition.overload, where the
attributes are simply copied and not checked.
Thanks in advance
Antonio Petrelli
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
