Make org.apache.tapestry.renderTags work at a library level
-----------------------------------------------------------
Key: TAPESTRY-2154
URL: https://issues.apache.org/jira/browse/TAPESTRY-2154
Project: Tapestry
Issue Type: Improvement
Components: Framework
Affects Versions: 4.1.5, 4.1.3, 4.1.2, 4.1.1
Reporter: Robert J. Walker
Priority: Minor
As it currently stands in released versions of Tapestry,
org.apache.tapestry.renderTags affects the entire application and all libraries
used in it. Because of this, in order to make portable components and
libraries, you must always specify the renderTag attribute in page and
component templates. Otherwise, you may get results you were not anticipating
if the org.apache.tapestry.renderTags setting is different.
For example, because of this problem, the Exception page was messed up if you
set org.apache.tapestry.renderTags to false in your application, because the
page assumes that it is true. (Bug #1431) The renderTags attribute had to be
specified everywhere in the template in order to counter this problem.
It needs to be possible to set org.apache.tapestry.renderTags at the library
level, without being overridden by the application-level settings. This makes
it possible to build libraries that assume (for example) that
org.apache.tapestry.renderTags is true, and use them in applications which have
it set to false.
Once this is implemented, org.apache.tapestry.renderTags should be set in the
core components and contrib libraries.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
