[
https://issues.apache.org/jira/browse/TAP5-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thiago Henrique De Paula Figueiredo updated TAP5-2762:
------------------------------------------------------
Description:
When first implemented in 5.8.3, the file was hardwired to
{{tapestryComponentDependencies.json}} in the folder where the JVM is ran. This
can be a limitation if you're running more than webapp in the same servlet
container and, of course, it's nice to have it configurable.
This ticket introduces a new configuration symbol,
{{tapestry.component-dependency-file}}
({{SymbolConstants.COMPONENT_DEPENDENCY_FILE}}), with a default value of
{{tapestryComponentDependencies.json}} to keep the existing behavior, which
accepts a path that can be either absolute or relative to the folder where the
JVM is running.
In addition, this ticket adds logging about reading and writing the component
dependency file and tweaks {{PageCatalog}} a bit regarding what to show when
production mode is off.
was:
When first implemented in 5.8.3, the file was hardwired to
{{tapestryComponentDependencies.json}} in the folder where the JVM is ran. This
can be a limitation if you're running more than webapp in the same servlet
container and, of course, it's nice to have it configurable.
This ticket introduces a new configuration symbol,
{{tapestry.component-dependency-file}}
({{SymbolConstants.COMPONENT_DEPENDENCY_FILE}}, with a default value of
{{tapestryComponentDependencies.json}} to keep the existing behavior, which
accepts a path that can be either absolute or relative to the folder where the
JVM is running.
In addition, this ticket adds logging about reading and writing the component
dependency file and tweaks {{PageCatalog}} a bit regarding what to show when
production mode is off.
> New symbol for defining the path to the component dependencies file
> -------------------------------------------------------------------
>
> Key: TAP5-2762
> URL: https://issues.apache.org/jira/browse/TAP5-2762
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.8.3
> Reporter: Thiago Henrique De Paula Figueiredo
> Priority: Major
>
> When first implemented in 5.8.3, the file was hardwired to
> {{tapestryComponentDependencies.json}} in the folder where the JVM is ran.
> This can be a limitation if you're running more than webapp in the same
> servlet container and, of course, it's nice to have it configurable.
> This ticket introduces a new configuration symbol,
> {{tapestry.component-dependency-file}}
> ({{SymbolConstants.COMPONENT_DEPENDENCY_FILE}}), with a default value of
> {{tapestryComponentDependencies.json}} to keep the existing behavior, which
> accepts a path that can be either absolute or relative to the folder where
> the JVM is running.
> In addition, this ticket adds logging about reading and writing the component
> dependency file and tweaks {{PageCatalog}} a bit regarding what to show when
> production mode is off.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
