[ http://issues.apache.org/jira/browse/BEEHIVE-199?page=history ]
Jeremiah Johnson updated BEEHIVE-199:
-------------------------------------
Summary: Cannot reference Tiles Definition files outside the current
page flow using relative paths. (was: Cannot reference Tiles Definition files
outside the current page flow.)
Description:
Cannot reference Tiles Definition files outside the current page flow when
using relative paths.
Example use-case 1 (nested page flow):
---------------------------------------
Reference a tiles definition file from within a nested page flow where the
tiles definition file lives in the parent page flow directory (one directory
above) like so:
@Jpf.Controller(
tilesDefinitionsConfigs = { "../tiles-defs.xml" },
simpleActions={
@Jpf.SimpleAction(name="begin", tilesDefinition="default.page")
}
)
Which does not work because the generated output would look like this:
<plug-in className="org.apache.struts.tiles.TilesPlugin">
<set-property property="definitions-config"
value="\nested/../tilesdefs.xml"/>
<set-property property="moduleAware" value="true"/>
</plug-in>
was:
Cannot reference Tiles Definition files outside the current page flow. This
goes for both nested page flows and inherited ones.
Example use-case 1 (nested page flow):
---------------------------------------
Reference a tiles definition file from within a nested page flow where the
tiles definition file lives in the parent page flow directory (one directory
above) like so:
@Jpf.Controller(
tilesDefinitionsConfigs = { "../tiles-defs.xml" },
simpleActions={
@Jpf.SimpleAction(name="begin", tilesDefinition="default.page")
}
)
Which does not work because the generated output would look like this:
<plug-in className="org.apache.struts.tiles.TilesPlugin">
<set-property property="definitions-config"
value="\nested/../tilesdefs.xml"/>
<set-property property="moduleAware" value="true"/>
</plug-in>
Example use-case 2 (inherited page flow):
------------------------------------------
ParentPageFlow.jpf:
@Jpf.Controller(
tilesDefinitionsConfigs = { "tiles-defs.xml" },
simpleActions={
@Jpf.SimpleAction(name="begin", tilesDefinition="default.page")
}
)
ChildPageFlow.jpf (extends ParentPageFlow):
ChildFlow1Controller.jpf:
@Jpf.Controller(
simpleActions={
@Jpf.SimpleAction(name="begin", tilesDefinition="default.page")
}
)
Generated struts-config output:
<plug-in className="org.apache.struts.tiles.TilesPlugin">
<set-property property="definitions-config"
value="\childFlow1/tiles-defs.xml"/>
<set-property property="moduleAware" value="true"/>
</plug-in>
Reference to tiles-defs.xml is incorrect. tiles-defs.xml lives in the
ParentPageFlow directory. ChildPageFlow should of inherited the correct path.
This currently limits how tiles can be set up within nested page flows or
inherited page flows. In other words, the current PF implementation doesn't
support sharing of one common tiles definition file (tiles-defs.xml) among
nested or inherited page flows. It requires multiple tiles definitions and JSP
tiles to live in different places within the same webapp.
> Cannot reference Tiles Definition files outside the current page flow using
> relative paths.
> -------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-199
> URL: http://issues.apache.org/jira/browse/BEEHIVE-199
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Environment: Running the usual components required by Beehive V1Beta on a
> Win32 box. Local test environment.
> Reporter: Nathan Jantz
> Assignee: carlin rogers
>
> Cannot reference Tiles Definition files outside the current page flow when
> using relative paths.
> Example use-case 1 (nested page flow):
> ---------------------------------------
> Reference a tiles definition file from within a nested page flow where the
> tiles definition file lives in the parent page flow directory (one directory
> above) like so:
> @Jpf.Controller(
> tilesDefinitionsConfigs = { "../tiles-defs.xml" },
> simpleActions={
> @Jpf.SimpleAction(name="begin", tilesDefinition="default.page")
> }
> )
> Which does not work because the generated output would look like this:
> <plug-in className="org.apache.struts.tiles.TilesPlugin">
> <set-property property="definitions-config"
> value="\nested/../tilesdefs.xml"/>
> <set-property property="moduleAware" value="true"/>
> </plug-in>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
