git commit: accomodate for cases where JAVA_HOME points to JDK root directory
Updated Branches:
refs/heads/master 35d9f22b2 -> fa76c7950
accomodate for cases where JAVA_HOME points to JDK root directory
Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/fa76c795
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/fa76c795
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/fa76c795
Branch: refs/heads/master
Commit: fa76c7950d2d40458acaf8828efe42ed8bdd7cae
Parents: 35d9f22
Author: Ulrich Staerk
Authored: Mon Jan 14 13:23:03 2013 +0100
Committer: Ulrich Staerk
Committed: Mon Jan 14 13:23:03 2013 +0100
--
tapestry-javadoc/build.gradle |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/fa76c795/tapestry-javadoc/build.gradle
--
diff --git a/tapestry-javadoc/build.gradle b/tapestry-javadoc/build.gradle
index e861f3e..278f209 100644
--- a/tapestry-javadoc/build.gradle
+++ b/tapestry-javadoc/build.gradle
@@ -7,9 +7,12 @@ dependencies {
/** Returns the tools.jar/classes.jar of the Java runtime. */
File getTools() {
- def relpath = isMacOSX_1_6() ? "../classes/classes.jar" : "../lib/tools.jar"
+ def jreRelpath = isMacOSX_1_6() ? "../classes/classes.jar" :
"../lib/tools.jar"
+ def jdkRelpath = isMacOSX_1_6() ? "classes/classes.jar" : "lib/tools.jar"
+
+ def javaHome = System.properties['java.home']
- return new File(System.properties['java.home'], relpath)
+ return new File(javaHome, jdkRelpath).exists() ? new File(javaHome,
jdkRelpath) : new File(javaHome, jreRelpath)
}
boolean isMacOSX_1_6() {
git commit: unbreak build for eclipse users
Updated Branches:
refs/heads/master fa76c7950 -> 4f70b71e8
unbreak build for eclipse users
Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/4f70b71e
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/4f70b71e
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/4f70b71e
Branch: refs/heads/master
Commit: 4f70b71e8dcd256dcfbc9bf0b9f3ddb350ce4c0b
Parents: fa76c79
Author: Ulrich Staerk
Authored: Mon Jan 14 13:30:31 2013 +0100
Committer: Ulrich Staerk
Committed: Mon Jan 14 13:30:31 2013 +0100
--
.../tapestry5/internal/services/SessionImpl.java |1 -
.../services/assets/StackAssetRequestHandler.java |1 -
.../ioc/internal/PerThreadOperationTracker.java|1 -
.../ioc/internal/QuietOperationTracker.java|1 -
.../internal/services/PerthreadManagerImpl.java|2 --
5 files changed, 0 insertions(+), 6 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/4f70b71e/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
--
diff --git
a/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
b/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
index 3a93045..33b38d9 100644
---
a/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
+++
b/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/SessionImpl.java
@@ -82,7 +82,6 @@ public class SessionImpl implements Session
perthreadManager.addThreadCleanupCallback(new Runnable()
{
-@Override
public void run()
{
lock.unlock();
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/4f70b71e/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/assets/StackAssetRequestHandler.java
--
diff --git
a/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/assets/StackAssetRequestHandler.java
b/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/assets/StackAssetRequestHandler.java
index fcdef02..987e8e5 100644
---
a/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/assets/StackAssetRequestHandler.java
+++
b/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/assets/StackAssetRequestHandler.java
@@ -98,7 +98,6 @@ public class StackAssetRequestHandler implements
AssetRequestHandler
tracker.perform(String.format("Streaming asset stack %s", extraPath),
new org.apache.tapestry5.ioc.IOOperation()
{
-@Override
public Void perform() throws IOException
{
boolean compress =
compressionAnalyzer.isGZipSupported();
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/4f70b71e/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/PerThreadOperationTracker.java
--
diff --git
a/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/PerThreadOperationTracker.java
b/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/PerThreadOperationTracker.java
index f1837ad..7674357 100644
---
a/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/PerThreadOperationTracker.java
+++
b/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/PerThreadOperationTracker.java
@@ -93,7 +93,6 @@ public class PerThreadOperationTracker implements
OperationTracker
}
}
-@Override
public T perform(String description, IOOperation operation) throws
IOException
{
try
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/4f70b71e/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/QuietOperationTracker.java
--
diff --git
a/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/QuietOperationTracker.java
b/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/QuietOperationTracker.java
index b470fb1..141397c 100644
---
a/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/QuietOperationTracker.java
+++
b/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/QuietOperationTracker.java
@@ -35,7 +35,6 @@ public class QuietOperationTracker implements OperationTracker
return operation.invoke();
}
-@Override
public T perform(String description, IOOperation operation) throws
IOException
{
return operation.perform();
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/4
[CONF] Apache Tapestry > Building Tapestry from Source
Building Tapestry from Source
Page edited by Ulrich Stärk
Comment:
document coffeescript compilation
Changes (3)
...
* Command-line git users:
| Non Committers: | git clone http://git-wip-us.apache.org/repos/asf/reponame.git http://git-wip-us.apache.org/repos/asf/tapestry-5.git |
| Committers: | git clone http://git-wip-us.apache.org/repos/asf/reponame.git https://git-wip-us.apache.org/repos/asf/tapestry-5.git |
* Eclipse EGit users: ** Switch to Git perspective; then copy one of the URLs above into paste buffer
...
** When it's finished, the antlr-generated classes (e.g. PropertyExpressionLexer.java) will be in created in $buildDir/generated-sources/antlr/, but Eclipse doesn't yet know about that path. To fix that, right click on the {{tapestry-core}} project > Properties > Java Build Path > Source > Add Folder > find {{tapestry-core/build/generated-sources/antlr}}and check the checkbox next to it, then click {{OK}}.
h3. CoffeeScript If you want to run tests from within Eclipse, Tapestry will complain that it won't find certain _javascript_ files that normally are generated during compile time from their Coffeescript sources. In order to generate the _javascript_ files you need to have Coffeescript installed and in your path. Simply install [Node.js|http://nodejs.org/download/] and afterwards run {{npm install -g coffee-script}}. The installation should take care of everything. * Eclipse Gradle IDE users: ** Right click on the {{build.gradle}} file within tapestry-core and click Run As > "Gradle build...", check *only* the tapestry-core:compileCoffeeScript and tapestry-core:compileTestCoffeeScript tasks, and change the "Name" field to something like "tapestry-core coffeescript", then click Apply and Run. ** When it's finished, the coffeescript-generated _javascript_ files (e.g. t5-core-dom-jquery.js) will be in created in $buildDir/generated-sources/compiled-coffeescript/ and $buildDir/generated-sources/compiled-test-coffeescript/, but Eclipse doesn't yet know about that path. To fix that, right click on the {{tapestry-core}} project > Properties > Java Build Path > Source > Add Folder > find {{tapestry-core/build/generated-sources/compiled-coffeescript}} and {{tapestry-core/build/generated-sources/compiled-test-coffeescript}} and check the checkbox next to it, then click {{OK}}. h3. Generate CoffeeScript and Antlr files automatically when changed If you want to have Eclipse compile the _javascript_ files and lexer classes from their Coffeescript sources and Antlr files automatically when they change, you can do that by configuring an additional builder for the {{tapestry-core}} project: * Eclipse Gradle IDE users: ** Right click on the {{tapestry-core}} project and select properties. ** Select the "Builders" entry from the list on the left and click "New.." in the right panel. ** Select "Program" and click "Ok". ** Give the program a meaningful name, e.g. "compile coffeescript and antlr". ** Switch to the "Main" tab. ** For "Location:" click "Browse Workspace..." and select {{gradlew.sh}} or {{gradlew.bat}} in the Tapestry root project. If the root project is called "tapestry-5" the entry should look similar to "$\{workspace_loc:/tapestry-5/gradlew.bat\}". ** For "Working Directory:" click "Browse Workspace..." and select the Tapestry root project. ** For "Arguments:" enter {{tapestry-core:generateGrammarSource tapestry-core:compileCoffeeScript tapestry-core:compileTestCoffeeScript}}. ** Switch to the "Build Options" tab. ** Make sure that only "Allocate Console", "After a "Clean"", "During manual builds", "During auto builds" and "Specify working set of relevant resources" are checked. ** Click "Specify Resources...". ** From the "tapestry-core" project select "src/main/antlr", "src/main/coffeescript", and "src/test/coffeescript". ** Click "Finish". ** Click "OK". ** Click "OK".
h3. Building
...
Full Content
This is a guide to building Tapestry itself from source code. This is primarily of interest to Tapestry contributors, rather than Tapestry users.
Although Tapestry users are free to use any build mechanism for their own projects (and first class Maven support is provided), to build Tapestry itself from source you will use Gradle.
Note: Both command line and Eclipse Gradle IDE/EGit instructions are given here. Generally you'll want to chose approach one or the other, rather than mixing them.
Prerequisites
Install a Java JDK (Sun/Oracle, not OpenJDK), version 1.6 (1.5 should also work).
Install an IDE (IDEA IntelliJ is recommended (and free to Tapestry committers), but Eclipse will also work. NetBeans is reported to work as
[jira] [Updated] (TAP5-679) Allow defining read-only fields inside bean-edit-form component
[ https://issues.apache.org/jira/browse/TAP5-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-679: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Allow defining read-only fields inside bean-edit-form component > --- > > Key: TAP5-679 > URL: https://issues.apache.org/jira/browse/TAP5-679 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-core >Affects Versions: 5.1 >Reporter: manuel aldana > Labels: bulk-close-candidate > > inside bean-edit form it would be cool to have a component parameter where > you define read-only fields. They should be closed for edition, still they > should be visible (thus @NonVisual is not an option). > I know it is hard to put all form requirements into one component (harder to > understand, harder to document). But having read-only fields inside a form is > a very common use case and in my view should be supported in the handy first > class form component of tapestry. > The syntax could look like: > > or even better, to let it control through page class: > > for discussion see also > http://www.nabble.com/-bean-edit-form--make-a-sub-set-of-parameters-visible-but-not-editable-td23111464.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-862) GridDataSource return object index
[ https://issues.apache.org/jira/browse/TAP5-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-862: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > GridDataSource return object index > -- > > Key: TAP5-862 > URL: https://issues.apache.org/jira/browse/TAP5-862 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Pedro Januário >Priority: Trivial > Labels: bulk-close-candidate > > Sometimes would be great to being possible to obtain the specific index of a > row. > This is common when we have grid ordered and we want to get the next row. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-669) All services related to the old ApplicationState concept should be renamed to use the new SessionState naming
[ https://issues.apache.org/jira/browse/TAP5-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-669: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > All services related to the old ApplicationState concept should be renamed to > use the new SessionState naming > - > > Key: TAP5-669 > URL: https://issues.apache.org/jira/browse/TAP5-669 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.4 >Reporter: Hugo Palma >Priority: Minor > Labels: bulk-close-candidate > > 5.1.0.4 introduced the renaming of ApplicationState to SessionState. But > there are some services that use the same naming and that were not renamed > leaving the concept and the service names in an inconsistent state. > From a quick search i could find the following: > - ApplicationStateAdapter > - ApplicationStateContribution > - ApplicationStateCreator > - ApplicationStateManager > - ApplicationStatePersistenceStrategy > - ApplicationStatePersistenceStrategySource > - ApplicationStateWorker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-902) GridDataSource does not allow performing less than 2 queries if returning results
[ https://issues.apache.org/jira/browse/TAP5-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-902: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > GridDataSource does not allow performing less than 2 queries if returning > results > - > > Key: TAP5-902 > URL: https://issues.apache.org/jira/browse/TAP5-902 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Dan Adams > Labels: bulk-close-candidate > > By having getAvailableRows() and prepare() separate, any implementation is > forced to perform 2 queries. Many systems allow getting the results of a > query and the total count in one query so that you don't have to perform 2 > queries. Getting around this requires some pretty gross hacks (unless you > just don't use grid at all which is unfortunate). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-740) Writeable property expressions accessing java.util.Map entries at final term (T4-style)
[
https://issues.apache.org/jira/browse/TAP5-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-740:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Writeable property expressions accessing java.util.Map entries at final term
> (T4-style)
> ---
>
> Key: TAP5-740
> URL: https://issues.apache.org/jira/browse/TAP5-740
> Project: Tapestry 5
> Issue Type: Wish
> Components: tapestry-core
>Affects Versions: 5.1.0.5
>Reporter: Igor Lobanov
> Labels: bulk-close-candidate
>
> Consider following situation. Say there is a page which displays list of
> products in some category. User must be able to add several products to
> shopping cart from this page with single operation. To accomplish this we
> place a textfield near each product to allow user to input desired quantity,
> and we place "Add to cart" submit button after the list.
> As "value" parameter of TextField is bidirectional, we need some writeable
> location to read initial zero from and to store entered quantity when form is
> submited. Thus we need to write boilerplate stub:
> public class ProductOrder {
> public Product product;
> public int quantity;
> }
> To be able to render and then process such a form, we need to create an
> instance of ProductOrder for each Product in category and bind TextField
> values to corresponding ProductOrder.quantity.
> In T4 days it could be accomplished a bit easier. We only needed to create
> page property of type java.util.Map (initialized to empty map) and use
> binding expression like "ognl:orderMap[product]". Then on page render all
> textfields' values would be set to "0", because binding expression yields
> null. On page rewinding OGNL created entries in orderMap for us automatically
> and fills entered values in.
> While such approach definitely lacks OOP-ness, it suired well in situations
> when there is no particular need in the "stub" class other than facilitate
> form operations. It would be great to be able to use it in T5 with property
> expressions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1063) exception is thrown if web-browser closes HTTP connection prematurely
[
https://issues.apache.org/jira/browse/TAP5-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-1063:
---
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> exception is thrown if web-browser closes HTTP connection prematurely
> -
>
> Key: TAP5-1063
> URL: https://issues.apache.org/jira/browse/TAP5-1063
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
>Affects Versions: 5.1.0.5
>Reporter: Neeme Praks
> Labels: bulk-close-candidate
>
> Sometimes we see exceptions such as below in our logs.
> I suspect this is due to the fact that client browser has closed HTTP
> connection (navigated to different page already or something like that) and
> jetty then throws exception as it cannot write the response out.
> I guess the best solution to this would be to add a configuration flag to
> suppress this kind of errors (just swallow them or log on DEBUG level).
> The stacktrace:
> {noformat}
> 2010-03-13 14:10:40,710 ERROR [btpool0-110]
> [tapestry.render.com.mycompany.zps.web.admin.pages.ViewPrivateZone]
> - Render queue error in BeginRender[ViewPrivateZone:layout.logoutlink]:
> Committed
> org.apache.tapestry5.ioc.internal.util.TapestryException: Committed [at
> classpath:com/mycompany/zps/web/admin/components/Layout.tml, line 24]
> at
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:948)
> at
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$400(ComponentPageElementImpl.java:49)
> at
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.callback(ComponentPageElementImpl.java:159)
> at
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl$BeginRenderPhase.render(ComponentPageElementImpl.java:211)
> at
> org.apache.tapestry5.internal.services.RenderQueueImpl.run(RenderQueueImpl.java:74)
> at
> org.apache.tapestry5.internal.services.PageRenderQueueImpl.render(PageRenderQueueImpl.java:121)
> at
> $PageRenderQueue_1275673a10e.render($PageRenderQueue_1275673a10e.java)
> at
> $PageRenderQueue_1275673a0f6.render($PageRenderQueue_1275673a0f6.java)
> at
> org.apache.tapestry5.internal.services.MarkupRendererTerminator.renderMarkup(MarkupRendererTerminator.java:37)
> at
> org.apache.tapestry5.services.TapestryModule$27.renderMarkup(TapestryModule.java:1748)
> at
> $MarkupRenderer_1275673a110.renderMarkup($MarkupRenderer_1275673a110.java)
> at
> org.apache.tapestry5.services.TapestryModule$26.renderMarkup(TapestryModule.java:1732)
> at
> $MarkupRenderer_1275673a110.renderMarkup($MarkupRenderer_1275673a110.java)
> at
> org.apache.tapestry5.services.TapestryModule$25.renderMarkup(TapestryModule.java:1714)
> at
> $MarkupRenderer_1275673a110.renderMarkup($MarkupRenderer_1275673a110.java)
> at
> org.apache.tapestry5.services.TapestryModule$24.renderMarkup(TapestryModule.java:1700)
> at
> $MarkupRenderer_1275673a110.renderMarkup($MarkupRenderer_1275673a110.java)
> at
> org.apache.tapestry5.services.TapestryModule$23.renderMarkup(TapestryModule.java:1681)
> at
> $MarkupRenderer_1275673a110.renderMarkup($MarkupRenderer_1275673a110.java)
> at
> org.apache.tapestry5.services.TapestryModule$22.renderMarkup(TapestryModule.java:1662)
> at
> $MarkupRenderer_1275673a110.renderMarkup($MarkupRenderer_1275673a110.java)
> at
> $MarkupRenderer_1275673a10d.renderMarkup($MarkupRenderer_1275673a10d.java)
> at
> org.apache.tapestry5.internal.services.PageMarkupRendererImpl.renderPageMarkup(PageMarkupRendererImpl.java:64)
> at
> $PageMarkupRenderer_1275673a10b.renderPageMarkup($PageMarkupRenderer_1275673a10b.java)
> at
> org.apache.tapestry5.internal.services.PageResponseRendererImpl.renderPageResponse(PageResponseRendererImpl.java:61)
> at
> $PageResponseRenderer_1275673a08e.renderPageResponse($PageResponseRenderer_1275673a08e.java)
> at
> org.apache.tapestry5.internal.services.PageRenderRequestHandlerImpl.handle(PageRenderRequestHandlerImpl.java:63)
> at
> org.apache.tapestry5.services.TapestryModule$33.handle(TapestryModule.java:194
[jira] [Updated] (TAP5-857) Exclude recursion detection during initial render on blocks that are used for zone updates.
[ https://issues.apache.org/jira/browse/TAP5-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-857: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Exclude recursion detection during initial render on blocks that are used for > zone updates. > --- > > Key: TAP5-857 > URL: https://issues.apache.org/jira/browse/TAP5-857 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-core >Affects Versions: 5.1 >Reporter: Seth Call > Labels: bulk-close-candidate > > Currently it is not possible to define a t:block that uses a particular > component when that component is already above in the hierarchy, because > Tapestry will detect this as a recursion. > However, if this recursion-causing block is only to be used as responses to a > zone update, then ideally it wouldn't cause a recursion to be detected. > Say for instance this were possible: > >... > > Where t:zoneBlock is identical to t:block except it can only be used as the > response to a zone update, and assembly of the page would know to exclude the > contents of that block when it's a normal full page render to avoid the > initial reason the recursion detection was added in the first place (runaway > rendering issues). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-681) Zone update href should be gathered from link href attribute
[ https://issues.apache.org/jira/browse/TAP5-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-681: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Zone update href should be gathered from link href attribute > > > Key: TAP5-681 > URL: https://issues.apache.org/jira/browse/TAP5-681 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.4 >Reporter: Nikita Koksharov > Labels: bulk-close-candidate > > Currently zone update url on actionlink defined in parameter of Tapestry.init > method, but it would be nice to gather url directly from href attribute of > link element. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1148) org.apache.tapestry5.internal.DefaultValidationDecorator sounld not be final
[ https://issues.apache.org/jira/browse/TAP5-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1148: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > org.apache.tapestry5.internal.DefaultValidationDecorator sounld not be final > > > Key: TAP5-1148 > URL: https://issues.apache.org/jira/browse/TAP5-1148 > Project: Tapestry 5 > Issue Type: Improvement >Affects Versions: 5.0.19 >Reporter: Michael Wyraz >Priority: Trivial > Labels: bulk-close-candidate > > The class contains usefull code which has to be copied for an own component > (bad practice). So either this code (e.g. inError(Field) should go to > BaseValidationDecorator or the clas should allowed to be a superclass. > These methods should also be protected, not private. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-960) Transform ValidationDecorator in a service to be more easily overridable
[ https://issues.apache.org/jira/browse/TAP5-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-960: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Transform ValidationDecorator in a service to be more easily overridable > > > Key: TAP5-960 > URL: https://issues.apache.org/jira/browse/TAP5-960 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Thiago H. de Paula Figueiredo > Labels: bulk-close-candidate > > Today, the ValidationDecorator implementation is hardwired in > TapestryModule.contributeMarkupRenderer(). We could transform it in a service > so it can be more easily overriden. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-809) Spring services should be decoratable
[ https://issues.apache.org/jira/browse/TAP5-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-809: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Spring services should be decoratable > - > > Key: TAP5-809 > URL: https://issues.apache.org/jira/browse/TAP5-809 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-spring >Affects Versions: 5.1.0.5 >Reporter: Carl Crowder > Labels: bulk-close-candidate > Attachments: spring_service_decoration.patch > > > SpringBeanServiceDef returns "true" for isPreventDecoration() which causes > any attempts to decorate services created in Spring to fail silently. > As far as I can tell there's no need for them to not be decoratable - I asked > on the mailing list and noone objected, and having changed it locally the > tests all run fine. > If there is a valid reason then at least the service builder should log a > warning rather than plunge on ignoring the decoration method. > I've attached a (very simple) patch to enable decoration of spring services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1301) Allow changing the ClassLoader Tapestry uses for loading classes and resources
[ https://issues.apache.org/jira/browse/TAP5-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1301: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Allow changing the ClassLoader Tapestry uses for loading classes and resources > -- > > Key: TAP5-1301 > URL: https://issues.apache.org/jira/browse/TAP5-1301 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-ioc >Affects Versions: 5.1.0.4 >Reporter: Dan Adams >Priority: Minor > Labels: bulk-close-candidate > > I have a situation where we want to extend the classloader used for the > application with additional classes in a non-container-specfic way. > TapestryFilter.provideExtraModuleDefs() appears to support this at first > except that there are many references throughout Tapestry to > Thread.currentThread().getContextClassLoader() which bypasses any classloader > you provide when creating the ModuleDef. Furthermore, there is a constructor > to RegistryBuilder that allows providing your own root classloader but even > if you can get that to work the above call make it's moot as it won't find > any of your page templates and such. This could be quite simple if: > - TapestryFilter and it's related classes allowed extending the ClassLoader > (by wrapping it in a URLClassLoader) for instance > - Using a definitive ClassLoader rather than > Thread.currentThread().getContextClassLoader() to get resources. > May affect more recent versions but I have not checked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1193) tapestry.js prevents using the back/forward browser cache
[
https://issues.apache.org/jira/browse/TAP5-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-1193:
---
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> tapestry.js prevents using the back/forward browser cache
> -
>
> Key: TAP5-1193
> URL: https://issues.apache.org/jira/browse/TAP5-1193
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
>Affects Versions: 5.1.0.4
>Reporter: Dan Adams
> Labels: bulk-close-candidate
>
> At the bottom of tapestry.js is the following:
> // Ajax code needs to know to do nothing after the window is unloaded.
> Event.observe(window, "beforeunload", function()
> {
> Tapestry.windowUnloaded = true;
> });
> Assume you have a page that does this:
> - loads in some initial state
> - user does something causing a ajax request that changes the DOM
> - user clicks a link to go to another page
> - user clicks back button
> rather than getting the state of the page before they left the user will get
> the original state of the page including the DOM and js state and the load
> handlers will be run. Using the hash method of maintaining ajax history (or
> maybe a cookie) is really not an option in this case because the DOM is out
> of date. You'd need to do an extra ajax request to the server to restore the
> state and the user experience would be really poor.
> There needs to be at least of the option of disabling this for pages that
> need this behavior.
> See
> http://stackoverflow.com/questions/158319/cross-browser-onload-event-and-the-back-button
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1305) Service decorations can fail if using the conventional naming
[
https://issues.apache.org/jira/browse/TAP5-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-1305:
---
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Service decorations can fail if using the conventional naming
> -
>
> Key: TAP5-1305
> URL: https://issues.apache.org/jira/browse/TAP5-1305
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
>Affects Versions: 5.1.0.4
>Reporter: Dan Adams
> Labels: bulk-close-candidate
>
> If you have a service FooBar and 2 modules that each have:
> public static FooBar decorateFooBar(FooBar delegate, ...)
> you will get a logging message like this:
> [WARN] com.example.services.BazModule.FooBar Could not add object with
> duplicate id 'FooBar'. The duplicate object has been ignored.
> which results in one of the contributions (you don't know which one) being
> dropped. This is because T5 uses an ordered contribution internally when
> collecting the contributions and bases the id of the contribution based on
> the method name (drops "decorate").
> It should either fail with an exception and a good error or support this
> behaviour. The problematic line is RegistryImpl.findDecoratorsForService
> (line 634).
> The work-around is to use @Match("FooBar") on the method and name it
> something different such as "decoratingWithMyThingy".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-716) Add translations for the Slovak (sk) locale
[ https://issues.apache.org/jira/browse/TAP5-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-716: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Add translations for the Slovak (sk) locale > --- > > Key: TAP5-716 > URL: https://issues.apache.org/jira/browse/TAP5-716 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.2, 5.1.0.5, 5.1 >Reporter: Radoslav Bielik >Priority: Trivial > Labels: bulk-close-candidate > Attachments: T51_Slovak.zip > > > I would like to contribute Slovak translations of the core Tapestry messages. > I have translated and tested the following files (see attached zip archive): > corelib\components\BeanEditForm_sk.properties > corelib\components\DateField_sk.properties > corelib\components\Errors_sk.properties > corelib\components\GridColumns_sk.properties > corelib\components\GridPager_sk.properties > corelib\components\Palette_sk.properties > corelib\components\ProgressiveDisplay_sk.properties > internal\ValidationMessages_sk.properties > All files are UTF-8 encoded. Please let me know if there's anything else that > needs to be translated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-289) Add a tip in the T5 cookbook for grid columns management
[
https://issues.apache.org/jira/browse/TAP5-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-289:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Add a tip in the T5 cookbook for grid columns management
>
>
> Key: TAP5-289
> URL: https://issues.apache.org/jira/browse/TAP5-289
> Project: Tapestry 5
> Issue Type: Wish
> Components: documentation
>Affects Versions: 5.0.15
>Reporter: David Galichet
> Labels: bulk-close-candidate
>
> I've recently encountered a difficulty when trying to do the following :
> I had a component with a nested Grid that is populated using a list of value
> objects (for example List)
> I've also added a column to this list that is computed in the component java
> class (public boolean isValidOk() ).
> My problem was that I would like to add a parameter on my component in order
> to display or hide the computed column. So I've added a @Parameter in my
> component Java class and tried to use a beanModel.add("validOk") in order to
> display the column when needed.
> In fact this doesn't work because I've performed a
> beanModelSource.create(MyVo.class, ...) in order to get the beanModel and T5
> told me that the "validOk" property wasn't an attribute of MyVo.class.
> So the only way I've found (in T5 Grid.java) to add my column was to use
> BeanModelUtils.modify(...)
> As it wasn't so obvious, I think that an entry in the cookbook could be a
> good idea ;)
> If you wan't I can write a part of this cookbook (just contact me by email or
> on irc).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-618) Provide more options to extend BeanModelImpl?
[ https://issues.apache.org/jira/browse/TAP5-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-618: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Provide more options to extend BeanModelImpl? > - > > Key: TAP5-618 > URL: https://issues.apache.org/jira/browse/TAP5-618 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.1 >Reporter: Alfie Kirkpatrick >Priority: Minor > Labels: bulk-close-candidate > > I recently wanted to provide a subclass of this class. It provides some > useful code to handle the reordering / including of properties from the bean > but I wanted to construct my own implementation of PropertyModel within it. I > could override the add(...) methods but the properties field is private so it > didn't get me very far. Simply making this protected or providing a getter / > setter would do it. > I ended up having to copy and paste the whole class which is kind of ok. I've > just done it for a JCR backend and now want to do it again for a dynamic > Hashmap backing class for a dynamic search form. > I realise this is in the internal package so you might not be happy to open > this up... > Regards, Alfie. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-732) When using the add parameter with Grid and adding in a @NonVisual property, you must currently supply the cell renderer, but it should be automatically provided
[
https://issues.apache.org/jira/browse/TAP5-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-732:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> When using the add parameter with Grid and adding in a @NonVisual property,
> you must currently supply the cell renderer, but it should be automatically
> provided
>
>
> Key: TAP5-732
> URL: https://issues.apache.org/jira/browse/TAP5-732
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
>Affects Versions: 5.1.0.5
>Reporter: Howard M. Lewis Ship
>Priority: Minor
> Labels: bulk-close-candidate
>
> To make it work you must:
> reorder="id,title,firstname,lastname">
> ${person.id}
>
> I don't think the should be necessary; the Grid should identify
> that id is a property of the bean and include a default renderer for it.
> Without , the Id column is simply blank.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1149) Make ValidationTracker.extraErrors visible in Interface
[ https://issues.apache.org/jira/browse/TAP5-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1149: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Make ValidationTracker.extraErrors visible in Interface > --- > > Key: TAP5-1149 > URL: https://issues.apache.org/jira/browse/TAP5-1149 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.0.19 >Reporter: Michael Wyraz >Priority: Trivial > Labels: bulk-close-candidate > > I tried to create a component that shows only extra errors (because all other > errors are shown at the field using a validation decorator). But it's not > possible (except using cast and/or reflection) to access it. > Please add something to the ValidationTracker Interface that gives > information about where an error belongs to. > Idea: > List getFieldsWithErrors(); // Returns names of fields which have > errors recorded > List getExtraErrors(); // REturns all errors not bound to a field -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-793) Ajax back button feature for zones
[ https://issues.apache.org/jira/browse/TAP5-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-793: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Ajax back button feature for zones > -- > > Key: TAP5-793 > URL: https://issues.apache.org/jira/browse/TAP5-793 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Jérôme VERITE > Labels: bulk-close-candidate > > some zones are used to ajax navigate in the same page. > These zones can update the document location and allow to use the browser > back button using rsh library http://code.google.com/p/reallysimplehistory/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-883) Regexp validator behaviour differs on client and server side
[
https://issues.apache.org/jira/browse/TAP5-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-883:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Regexp validator behaviour differs on client and server side
>
>
> Key: TAP5-883
> URL: https://issues.apache.org/jira/browse/TAP5-883
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
>Affects Versions: 5.1.0.5
>Reporter: Dirk Lattermann
>Priority: Minor
> Labels: bulk-close-candidate
>
> In some situations, a value can pass client side regexp validation and fail
> the server side validation. This should not be the case.
> The server regexp validator requires a value to match the regexp exactly from
> start to end which is not the case on the client (browser).
> For example, given a regexp of [a-z]{2}, a value of hu4 passes validation on
> the client and fails on the server.
> Workaround: use anchored regexps like ^[a-z]{2}$
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-727) PasswordField component should be configurable to allow outputing its value
[ https://issues.apache.org/jira/browse/TAP5-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-727: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > PasswordField component should be configurable to allow outputing its value > --- > > Key: TAP5-727 > URL: https://issues.apache.org/jira/browse/TAP5-727 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Hugo Palma >Priority: Minor > Labels: bulk-close-candidate > Attachments: TAP5-727.patch > > > It would be useful if the component provided this kind of flexibility. > I'm attaching a patch for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-820) Misleading error message if page misses a no-argument constructor
[ https://issues.apache.org/jira/browse/TAP5-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-820: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Misleading error message if page misses a no-argument constructor > - > > Key: TAP5-820 > URL: https://issues.apache.org/jira/browse/TAP5-820 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Sebastian Hennebrueder >Priority: Minor > Labels: bulk-close-candidate > > If a page has only constructores requiring parameters, then the following > error message is shown. > It should tell the user as well, that a no-argument constructor is missing. > 8:12:58,223 ERROR RequestExceptionHandler:62 - Processing of request failed > with uncaught exception: Class de.laliluna.bibabook.pages.Index was not > transformed for use as a component; this can happen if it is an interface, or > was not in a package subject to component transformation. > java.lang.RuntimeException: Class de.laliluna.bibabook.pages.Index was not > transformed for use as a component; this can happen if it is an interface, or > was not in a package subject to component transformation. > at > org.apache.tapestry5.internal.services.ComponentClassTransformerImpl.createInstantiator(ComponentClassTransformerImpl.java:190) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1005) The asset protection fails for some URLS in Tomcat
[
https://issues.apache.org/jira/browse/TAP5-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-1005:
---
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> The asset protection fails for some URLS in Tomcat
> --
>
> Key: TAP5-1005
> URL: https://issues.apache.org/jira/browse/TAP5-1005
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
>Affects Versions: 5.1.0.6, 5.1.0.7
>Reporter: Sebastian Hennebrueder
> Labels: bulk-close-candidate
>
> A URL like
> /mycontext/assets/de displays a file index on Tomcat 6 whereas
> /mycontext/assets/de/ denies access correctly.
> In fact any URL which is not a file and does not end with a / leeds to a
> directory index.
> I fixed this with a BlackListAuthorizer for my application.
> The URL /mycontext/assets/de leads to an empty 'someResourcePath' variable
> /mycontext/assets/de/foo leads to de/foo as variable value. My solution
> denies access for an empty resource path and in case that the last segment
> has no . I assume that in that case it is not a file like foo.jpg.
> Best Regards
> Sebastian Hennebrueder
> http://www.laliluna.de
> public class BlacklistAuthorizer implements AssetPathAuthorizer {
> final Logger logger =
> LoggerFactory.getLogger(BlacklistAuthorizer.class);
> private final Collection configuration;
> public BlacklistAuthorizer(final Collection configuration) {
> this.configuration = configuration;
> }
> public boolean accessAllowed(final String someResourcePath) {
> return true;
> }
> public boolean accessDenied(final String someResourcePath) {
> if (someResourcePath.endsWith("/")) {
> logger.debug("Denying access to {}", someResourcePath);
> return true;
> }
> if (someResourcePath.equals("")) {
> // this is mostly a bug fix for Tomcat for paths
> without trailing / like /assets/foo
> logger.debug("Denying access to empty resource path",
> someResourcePath);
> return true;
> }
> int pos = someResourcePath.lastIndexOf('/');
> if (pos < 0)
> pos = 0;
> String ending = someResourcePath.substring(pos);
> if (ending.indexOf('.') == -1) {
> // not a file like foo.pdf or foo.js
> logger.debug("Denying access to {}", someResourcePath);
> return true;
> }
> return false;
> }
> public List order() {
> return Arrays.asList(Order.DENY, Order.ALLOW);
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-757) Allow PageLink's "page" parameter to accept page instance or class instead of just logical name to add new type-safe way of render request generation
[ https://issues.apache.org/jira/browse/TAP5-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-757: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Allow PageLink's "page" parameter to accept page instance or class instead > of just logical name to add new type-safe way of render request generation > -- > > Key: TAP5-757 > URL: https://issues.apache.org/jira/browse/TAP5-757 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Vjeran Marcinko > Labels: bulk-close-candidate > > It's a bit overkill to use ActionLink only for render requests (when no > action is needed) just to use its ability to return target page instance from > handler methods, preconfigured with required context values. This type safety > comes at the expense of 2 HTTP requests. > If PageLink's "page" parameter could not only accept logical page name, but > also page instance, then it would be possible to achieve same type-safety > with only one HTTP request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-983) CLONE -NPE in BeanDisplay if used in a form with a default model
[ https://issues.apache.org/jira/browse/TAP5-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-983: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > CLONE -NPE in BeanDisplay if used in a form with a default model > > > Key: TAP5-983 > URL: https://issues.apache.org/jira/browse/TAP5-983 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.1.0.5, 5.0.15 > Environment: Ubuntu Linux, Apache Tomcat >Reporter: Stephan Windmüller >Priority: Minor > Labels: bulk-close-candidate > > Create something like this: > > > > and submit the form. You get a NPE in beandisplay. The workaround is to > create the model yourself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-672) Translation for Vietnamese
[ https://issues.apache.org/jira/browse/TAP5-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-672: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Translation for Vietnamese > -- > > Key: TAP5-672 > URL: https://issues.apache.org/jira/browse/TAP5-672 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5, 5.0.18 >Reporter: Tam Du > Labels: bulk-close-candidate > Attachments: org.zip > > > Files for translation of components in Vietnamese -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1358) GridPager links need to send page's request parameters
[ https://issues.apache.org/jira/browse/TAP5-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1358: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > GridPager links need to send page's request parameters > -- > > Key: TAP5-1358 > URL: https://issues.apache.org/jira/browse/TAP5-1358 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Geoff Callender > Labels: bulk-close-candidate > > GridPager uses EventLinks, but EventLink has a problem: even though it DOES > send the page's activation context (which is good), it DOESN'T send the > page's request parameters (which is bad)! > Does this happen in 5.2 too? > This is a real problem since I like to put search/filter criteria into > request parameters and not the context. The problem is that when I click on a > GridPager link I lose the search/filter criteria. Why do I use request > parameters for search/filter criteria? Because it is arguably more RESTful. > See > > http://jumpstart.doublenegative.com.au/jumpstart/examples/state/passingdatabetweenpages1 > > http://blpsilva.wordpress.com/2008/04/05/query-strings-in-restful-web-services/ > Example > A page has enterable search criteria fields (name, department, status). > Type in a name and submit the page. We redisplay with the Grid populated and > more than one grid page. > If the page puts the search criteria in the activation context then the > GridPager's link to page 2 looks fine - like this... > http://localhost/myapp/things/index.grid.pager/2?t:ac=jack/$N/ACTIVE > ...however if the page puts the search criteria in the request parameters, > then the GridPager's link to page 2 looks inadequate - like this... > https://localhost/myapp/things/index.grid.pager/2 > ...but to prevent losing the request parameters it should be like this... > > https://localhost/myapp/things/index.grid.pager/2?name=jack&status=ACTIVE > I wasted a lot of time figuring out this was what was going wrong, even > though I could see this what was happening, because I was refusing to believe > that request parameters weren't getting equal treatment in this situation! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1213) ComponentResources should give access to generic parameters of bound types
[ https://issues.apache.org/jira/browse/TAP5-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1213: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > ComponentResources should give access to generic parameters of bound types > -- > > Key: TAP5-1213 > URL: https://issues.apache.org/jira/browse/TAP5-1213 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.7 >Reporter: Michael Wyraz > Labels: bulk-close-candidate > > ComponentResources can tell which type is bound to a given parameter via > getBoundType(ParameterName). This is a great feature but only works for > non-generic types. If a generic type is bound, it's impossible to access the > generic parameters. > Example: > A component can bind to a Set of something. getBoundType returns > "java.util.Set" for this parameter. So it' not possible to coerce the entries > of this set to the target type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-873) BeanEditForm cannot be submitted via click by PageTester
[ https://issues.apache.org/jira/browse/TAP5-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-873: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > BeanEditForm cannot be submitted via click by PageTester > > > Key: TAP5-873 > URL: https://issues.apache.org/jira/browse/TAP5-873 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Kevin Menard >Priority: Minor > Labels: bulk-close-candidate > > PageTester was updated for Tapestry 5.1 to be more aggressive in its > clickSubmit check for a "name" parameter. In 5.0, if a "name" was missing > the "value" value was used. In 5.1, if the "name" parameter is missing, an > exception is thrown. BeanEditForm does not provide a "name" value for its > submit button. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-754) Introduce easier way to disable column sorting in Grid
[
https://issues.apache.org/jira/browse/TAP5-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-754:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Introduce easier way to disable column sorting in Grid
> --
>
> Key: TAP5-754
> URL: https://issues.apache.org/jira/browse/TAP5-754
> Project: Tapestry 5
> Issue Type: Improvement
>Affects Versions: 5.1.0.5
>Reporter: Vjeran Marcinko
> Labels: bulk-close-candidate
>
> I have seldom need for Grid sorting so I almost always turn it off. Currently
> this is a bit awkward procedure. I also rarely configure Grid with BeanModel
> created in my page class, because template way of configuring Grid is
> sufficient for me.
> I have to introduce 3 new objects just for this purpose in this class, and
> also do some coding in setupRender():
> @Property
> private BeanModel model;
> @Inject
> private BeanModelSource beanModelSource;
> @Inject
> private ComponentResources componentResources;
> void setupRender() {
>
> model = beanModelSource.createDisplayModel(Employee.class,
> componentResources.getMessages());
> List propertyNames = model.getPropertyNames();
> for (String propertyName : propertyNames) {
> model.get(propertyName).sortable(false);
> }
> }
> Tapestry 4 had simple way of using character "!" in template that achieved
> the same thing so I feel kinda nostalgic for it...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-795) Tapestry IoC should provide an OrderedConfiguration for EagerLoaded services
[
https://issues.apache.org/jira/browse/TAP5-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-795:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Tapestry IoC should provide an OrderedConfiguration for EagerLoaded services
>
>
> Key: TAP5-795
> URL: https://issues.apache.org/jira/browse/TAP5-795
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
>Affects Versions: 5.1
> Environment: Any
>Reporter: Peter Stavrinides
>Priority: Minor
> Labels: bulk-close-candidate
>
> It is mentioned in the documentation that the order in which services are
> created is not defined when using eagerLoad(). This is somewhat counter
> productive in a sense as you can get into serious trouble If ordering of
> eagerloaded services is important (and very often it is, as the very concept
> implies ordering and availability before other services), yet ordering is
> ignored for eagerloaded services?
> So by using :
> binder.bind(SomeService.class).eagerLoad(); you can produce a NPE or
> potentially work just fine and this IoC quirk goes undetected, which is a
> ticking time bomb. Perhaps this method should be renamed to
> eagerLoadUnordered() or better yet removed entirely, and another way of
> ordering these should be introduced.
> An illustrative example is given below with two eagerloaded services
> (SiteInitialise sets up database connections and the connection pool,
> ImageService loads a cache of image data, so implicitly ImageService requires
> SiteInitialise to be loaded first).
> //Example: The shell of the eagerloaded ImageService service
> public class ImageService {
> /** Cache to hold thumbnail images */
> private static ConcurrentHashMap
> imageCache_ = new ConcurrentHashMap();
>
> public void preloadImageCache() {
> DbConnection connection = null;
> try {
> //This can potentially turn into a Null Pointer
> Exception as the startup order is arbitrary
> connection =
> DatabaseConnection.getReadConnection();
> //database query
> } catch (Exception e) {
> //handle exception
> }
> }
> public static ImageService build() {
> return new ImageService();
> }
> public ImageService() {
> preloadImageCache();
> }
> }
> //Workaround: adding a dependency on the other eagerloaded service will solve
> it, but this is not a practical solution if there are many of these services
> public class ImageService {
> /** Cache to hold thumbnail images */
> private static ConcurrentHashMap
> imageCache_ = new ConcurrentHashMap();
>
> public void preloadImageCache() {
> DbConnection connection = null;
> try {
> connection =
> DatabaseConnection.getReadConnection();
> //database query
> } catch (Exception e) {
> //handle exception
> }
> }
> public static ImageService build(SiteInitialise
> siteInitialise) {
> return new ImageService(siteInitialise);
> }
> public ImageService(SiteInitialise siteInitialise) {
> if(siteInitialise.isConnectionOk())
> preloadImageCache();
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-676) Getting the page from a ProperyEditor
[ https://issues.apache.org/jira/browse/TAP5-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-676: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Getting the page from a ProperyEditor > - > > Key: TAP5-676 > URL: https://issues.apache.org/jira/browse/TAP5-676 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.0.18 >Reporter: José Paumard > Labels: bulk-close-candidate > > As of now, it is not possible to get a reference on the page served to the > client from a PropertyEditor component. The method componentResources.getPage > returns the page in which this PropertyEditor is declared, and so does the > container annotated with @InjectContainer. A side effect is that a method > annotated with @PageAttached / @PageDetached is never called in a > PropertyEditor component. > It would be nice to see those two improvments : > - componentResources.getPage returns the page sent to the client, or having > another way to get a reference to that page from a PropertyEditor > - @PageDetached / @PageAttached called in PropertyEditor components -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1010) Fix Finnish validation message translation - corrected file attached
[ https://issues.apache.org/jira/browse/TAP5-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1010: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Fix Finnish validation message translation - corrected file attached > > > Key: TAP5-1010 > URL: https://issues.apache.org/jira/browse/TAP5-1010 > Project: Tapestry 5 > Issue Type: Bug >Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, > 5.1.0.6, 5.1.0.7, 5.0.15, 5.0.16, 5.0.17, 5.0.18, 5.0.19 >Reporter: Ville Virtanen > Labels: bulk-close-candidate > Attachments: ValidationMessages_fi_FI.properties > > > The file in the distribution is borked in every release, the file has wrong > encodings on some letters. attached is correctly encoded file (UTF-8). Please > use this file, do NOT copy the contents to the old file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1151) Customization of Grid Pager
[ https://issues.apache.org/jira/browse/TAP5-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1151: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Customization of Grid Pager > --- > > Key: TAP5-1151 > URL: https://issues.apache.org/jira/browse/TAP5-1151 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.7 >Reporter: Nicolas Bouillon > Labels: bulk-close-candidate > Attachments: screenshot_021.png > > > I have had to customize the look & feel of the Grid pager, and i had no other > solution to make a full copy paste of Grid.java and GridPager.java in order > to change the pager. > It should be fine to be able to override the pager in a simpler way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-729) Tapestry IOC proxies have incorrect implementation when interface method uses a covariant return type (causes AbstractMethodError)
[
https://issues.apache.org/jira/browse/TAP5-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-729:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Tapestry IOC proxies have incorrect implementation when interface method uses
> a covariant return type (causes AbstractMethodError)
> --
>
> Key: TAP5-729
> URL: https://issues.apache.org/jira/browse/TAP5-729
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
>Affects Versions: 5.1.0.5
>Reporter: Paul Field
> Labels: bulk-close-candidate
>
> Here's a Junit 3 test case to demonstrate:
> import junit.framework.TestCase;
> import org.apache.tapestry5.ioc.Registry;
> import org.apache.tapestry5.ioc.RegistryBuilder;
> import org.apache.tapestry5.ioc.ServiceBinder;
> public class ProxyText extends TestCase {
> private Registry registry;
> @Override
> protected void setUp() throws Exception {
> RegistryBuilder builder = new RegistryBuilder();
> builder.add(AppModule.class);
> registry = builder.build();
> registry.performRegistryStartup();
> }
> public void testRegistryWorks() {
> assertEquals(new Integer(1),
> registry.getService(SuperIFace.class).get());
> }
> public static class AppModule {
> public static void bind(ServiceBinder binder) {
> binder.bind(IFace.class, Impl.class);
> }
> }
> public interface SuperIFace {
> Number get();
> }
> public interface IFace extends SuperIFace {
> Integer get();
> }
> public static class Impl implements IFace {
> public Integer get() {
> return 1;
> }
> }
> }
> -
> The result is:
> java.lang.AbstractMethodError: $IFace_1218d10684a.get()Ljava/lang/Number;
> Note that if you change SuperIFace to:
> public interface SuperIFace {
> Integer get();
> }
> the test works - demonstrating that the problem is to do with the use of a
> covariant return type in IFace.
> BTW, this has turned up in code for testing where I want to create
> sub-interfaces that provide additional testing facilities for fake services
> and I need to control the particular types that are returned by the fake
> implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-816) Add logs on reply script evaluation error
[
https://issues.apache.org/jira/browse/TAP5-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-816:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Add logs on reply script evaluation error
> -
>
> Key: TAP5-816
> URL: https://issues.apache.org/jira/browse/TAP5-816
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
>Affects Versions: 5.1.0.0
>Reporter: Denis Delangle
>Priority: Minor
> Labels: bulk-close-candidate
>
> On ajax queries, if the evaluation of the script part of the reply fails, no
> message is shown to the user. It is then tricky to solve issues. I only ask
> for logging of such errors.
> Here is a diff for tapestry.js file adding a call to Tapestry.error. I don't
> know if exception should be thrown back afterwards.
> Index: tapestry.js
> ===
> --- tapestry.js (revision 805422)
> +++ tapestry.js (working copy)
> @@ -307,7 +307,15 @@
> // evaluating the reply.script
> // and other final steps.
>
> -if (reply.script) eval(reply.script);
> +
> +if (reply.script) {
> + try {
> + eval(reply.script);
> + } catch(e) {
> + //We catch any exception that can occur during
> script evaluation and we log it
> +
> Tapestry.error(Tapestry.Messages.clientException + e);
> + }
> +}
>
> Tapestry.onDomLoadedCallback();
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-687) In a Tapestry template, mixing a Tapestry library namespace with a subpackage in the element name (a dot between the folder and the component name) fails
[
https://issues.apache.org/jira/browse/TAP5-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-687:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> In a Tapestry template, mixing a Tapestry library namespace with a subpackage
> in the element name (a dot between the folder and the component name) fails
> -
>
> Key: TAP5-687
> URL: https://issues.apache.org/jira/browse/TAP5-687
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
>Affects Versions: 5.1.0.4
>Reporter: Nguyen Ngoc Trung
>Priority: Minor
> Labels: bulk-close-candidate
>
> Steps to reproduce the exception:
> 1. Create library t5comp, and declare: configuration.add(new
> LibraryMapping("t5comp", "vn.pyco.demo.t5comp"));
> 2. Creare two components: vn.pyco.demo.t5comp.components.Comp1 and
> vn.pyco.demo.t5comp.components.sub.Comp2
> 3. Create webapp t5app, and using t5comp library.
> 4. Index.tml code:
> http://www.w3.org/1999/xhtml";
> xmlns:t="http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";
> xmlns:tc="tapestry-library:t5comp"
> xmlns:p="tapestry:parameter">
>
>
> T5 Demo
>
>
> (1)
> (2)
> (3)
>
>
> 5. Run webapp and get result:
> - (1), (2) OK
> - (3) throws an exception:
> Unable to resolve 't5comp/sub.Comp2' to a component class name. Available
> component types: ActionLink, AddRowLink, AjaxFormLoop, Any, BeanDisplay,
> BeanEditForm, BeanEditor, Checkbox, DateField, Delegate, Errors, EventLink,
> ExceptionDisplay, Form, FormFragment, FormInjector, Grid, GridCell,
> GridColumns, GridPager, GridRows, Hidden, If, Label, LinkSubmit, Loop,
> Output, OutputRaw, PageLink, Palette, PasswordField, ProgressiveDisplay,
> PropertyDisplay, PropertyEditor, Radio, RadioGroup, RemoveRowLink,
> RenderObject, Select, Submit, SubmitNotifier, TextArea, TextField,
> TextOutput, Unless, Zone, t5comp/Comp1, t5comp/sub/Comp2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1104) FieldTracker are not exposed and hence it is difficult to locate the field in error from ValidationTracker
[ https://issues.apache.org/jira/browse/TAP5-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1104: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > FieldTracker are not exposed and hence it is difficult to locate the field in > error from ValidationTracker > -- > > Key: TAP5-1104 > URL: https://issues.apache.org/jira/browse/TAP5-1104 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Jayesh > Labels: bulk-close-candidate > > I need to provide hyperlinks to the individual fields in errors at the top. > Tapestry4 had -> IFieldTracking field = > IValidationDelegate.getFieldTracking(); > I couldn't find any equivalent in tapestry5. > Tapestry 5 validator returns List getErrors(); But then there is no > way to link these error messages to the actual fields which are in error. > I need to follow company's web standards which mandates to provide > links to errornous fields, so clicking at the those error texts jumps the > user to appropriate label/field. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-854) add a package-level localization feature
[ https://issues.apache.org/jira/browse/TAP5-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-854: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > add a package-level localization feature > > > Key: TAP5-854 > URL: https://issues.apache.org/jira/browse/TAP5-854 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: cleverpig > Labels: bulk-close-candidate > > just like struts2 had done in > Localization:http://struts.apache.org/2.1.6/docs/localization.html > I mean when i develope some page class in the same package,i always meet some > same resource message defines for CRUD pages of one POJO.. > so i think it's effectual under this dev habit:create a package level > property file for this package(pages).. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1164) missing or misspelled tapestry xmlns causes "Embedded component(s) defined but not found error"
[ https://issues.apache.org/jira/browse/TAP5-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1164: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > missing or misspelled tapestry xmlns causes "Embedded component(s) defined > but not found error" > --- > > Key: TAP5-1164 > URL: https://issues.apache.org/jira/browse/TAP5-1164 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Josh Canfield >Priority: Minor > Labels: bulk-close-candidate > > It would be helpful if tapestry could point out when it's possible that the > xmlns is missing or misspelled. If there are components defined in the class > and there are no components found in the template it seems reasonable to add > a line to the error message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-730) Add setSecure() to TestableRequest
[ https://issues.apache.org/jira/browse/TAP5-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-730: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Add setSecure() to TestableRequest > -- > > Key: TAP5-730 > URL: https://issues.apache.org/jira/browse/TAP5-730 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Paul Field > Labels: bulk-close-candidate > > Please could you add: > setSecure(boolean) > to TestableRequest so it is possible to write tests where the behaviour is > different for secure vs insecure requests (for example testing alternative > implementations of RequestSecurityManager). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1142) Tapestry5 template name simplification
[ https://issues.apache.org/jira/browse/TAP5-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1142: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Tapestry5 template name simplification > -- > > Key: TAP5-1142 > URL: https://issues.apache.org/jira/browse/TAP5-1142 > Project: Tapestry 5 > Issue Type: Wish >Affects Versions: 5.1 >Reporter: sandeepraj singh > Labels: bulk-close-candidate > > Hi, > Based on discussion on > http://old.nabble.com/Tapestry5-template-name-simplification-to28508162.html#a28511105 > As per the tapestry5 documentation > " > In certain cases, Tapestry will simplify the the logical name of a page. For > example, the page class org.example.pages.address.Create Address will be > given a logical name of "address/Create" (the redundant "Address" is removed > as a suffix) " > It would be nice if this feature could be made configurable. > This is because One can easily overrule this by choosing a different naming > scheme for his pages e.g address/EmployeeCreateAddress > So as such, it does not work in a defined way for all the cases. > The feature as it stands today has a tendency to confuse people from JSP / > Servlet background(personal experience) find the strategy very "special" to > understand. > So i hope this can be made configurable > Thanks > Sandeep -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1388) GridPager should be able to display which items are displayed
[ https://issues.apache.org/jira/browse/TAP5-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1388: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > GridPager should be able to display which items are displayed > - > > Key: TAP5-1388 > URL: https://issues.apache.org/jira/browse/TAP5-1388 > Project: Tapestry 5 > Issue Type: Improvement >Affects Versions: 5.0.15 >Reporter: Nicolas Bouillon > Labels: bulk-close-candidate > > Would be nice if the Grid Pager could be able to display not just the page > number, but also that it's displaying « item 50 to 100 of 2161 ». -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-778) BeanDisplay should be able to display properties of type list, map, etc,
[ https://issues.apache.org/jira/browse/TAP5-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-778: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > BeanDisplay should be able to display properties of type list, map, etc, > > > Key: TAP5-778 > URL: https://issues.apache.org/jira/browse/TAP5-778 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.0 >Reporter: Igor Drobiazko >Priority: Minor > Labels: bulk-close-candidate > > Additional annotation is probably needed to indicate the maximal size of the > collection to display? > @MaxVisualSize(5) > private List foos; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-775) AjaxFormLoop should expose (via properties and/or a method on AjaxFormLoopContext) the id of the FormInjector or FormFragment that is rendering (to faciliate JavaScript gen
[ https://issues.apache.org/jira/browse/TAP5-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-775: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > AjaxFormLoop should expose (via properties and/or a method on > AjaxFormLoopContext) the id of the FormInjector or FormFragment that is > rendering (to faciliate JavaScript generation) > > > Key: TAP5-775 > URL: https://issues.apache.org/jira/browse/TAP5-775 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.0.19 >Reporter: Howard M. Lewis Ship > Labels: bulk-close-candidate > > Context: trying to make FormFragments within an AjaxFormLoop draggable (for > re-ordering purposes). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-782) Tapestry should demarcate, via documentation annotations, user-access-only vs. user-implementable interfaces
[ https://issues.apache.org/jira/browse/TAP5-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-782: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Tapestry should demarcate, via documentation annotations, user-access-only > vs. user-implementable interfaces > > > Key: TAP5-782 > URL: https://issues.apache.org/jira/browse/TAP5-782 > Project: Tapestry 5 > Issue Type: Improvement >Affects Versions: 5.1.0.5 >Reporter: Robert Zeigler >Priority: Minor > Labels: bulk-close-candidate > > It would be nice if there was a documenting annotation on interfaces to > inform users which interfaces can be used by user-code but never implemented, > verses those interfaces which may be implemented at some point by users. > Examples of the former include most of the interfaces in the > org.apache.tapestry5.model package. The Asset and Resource interfaces are > examples of the second class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-806) PipelineBuilder should fail fast (throw an exception) in the situations where it currently logs an error
[ https://issues.apache.org/jira/browse/TAP5-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-806: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > PipelineBuilder should fail fast (throw an exception) in the situations where > it currently logs an error > > > Key: TAP5-806 > URL: https://issues.apache.org/jira/browse/TAP5-806 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-ioc >Affects Versions: 5.1.0.5 >Reporter: Howard M. Lewis Ship >Priority: Minor > Labels: bulk-close-candidate > > In addition, the current APIs should be deprecated, in favor of new methods > that do not take a Logger as a parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-776) Tapestry.FormFragment (client side) should be refactored to be easier to modify
[ https://issues.apache.org/jira/browse/TAP5-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-776: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Tapestry.FormFragment (client side) should be refactored to be easier to > modify > --- > > Key: TAP5-776 > URL: https://issues.apache.org/jira/browse/TAP5-776 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Howard M. Lewis Ship > Labels: bulk-close-candidate > > It would be nice if: > a) The DOM element has a property pointing to the Tapestry.FormInjector > object. I.e. $T(div).formFragment. > b) Tapestry.FormFragment had methods for adding new content (ala > FormInjector) above or below the existing FormFragment. > c) implicit in above: mix and match of FormInjector and FormFragment, to > allow easier ability to build AjaxFormLoop with buttons to add new rows above > or below existing rows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-773) Select component renderer does not allow HTML entities
[ https://issues.apache.org/jira/browse/TAP5-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-773: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Select component renderer does not allow HTML entities > -- > > Key: TAP5-773 > URL: https://issues.apache.org/jira/browse/TAP5-773 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Andy Blower > Labels: bulk-close-candidate > > All ampersands that are returned from getLabel() in an OptionModel get > encoded to &. This makes it impossible to use any html entities (— > etc) within option labels in selects. This is not that uncommon and > should definitely be supported by Tapestry out of the box. > It can be fixed by changing line 60 of > org.apache.tapestry5.internal.util.SelectModelRender from > writer.write(optionModel.getLabel()); > to > writer.writeRaw(optionModel.getLabel()); > This would mean that ampersands will need to be encoded for option labels, > but this is at least possible for a developer to do. Currently it's not > possible to use entities without using a custom select component, you can't > even extend the T5 Select class and override the Render nested class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-286) Add the possibility (as an option) for all generated URL to include the domain and context
[ https://issues.apache.org/jira/browse/TAP5-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-286: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Add the possibility (as an option) for all generated URL to include the > domain and context > -- > > Key: TAP5-286 > URL: https://issues.apache.org/jira/browse/TAP5-286 > Project: Tapestry 5 > Issue Type: New Feature >Affects Versions: 5.0.16 >Reporter: Martin Papy > Labels: bulk-close-candidate > > Now that we have the possibility to access the Dom and manipulate it easily, > we can use Tapestry to generate email based on Page Rendering... But Tapestry > generate only absolute URL ( without http://mydomain.com/context/ ). > For the moment I do this in the cleanupRender phase : > String mailBody = writer.getDocument().getRootElement.toString(); > And I send the result by mail. > It would be very useful if we could tell Tapestry -maybe with a special > Annotation- that we want for a particular Page/Component all URL / Link to > pages / Link to Assets (and so on) to be fully qualified ( ie not > /assets//yyy.jpg but http(s)://domain.com/context/assets//yyy.jpg ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-627) Allow injection of named spring beans
[ https://issues.apache.org/jira/browse/TAP5-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-627: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Allow injection of named spring beans > - > > Key: TAP5-627 > URL: https://issues.apache.org/jira/browse/TAP5-627 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-spring >Affects Versions: 5.1.0.2 >Reporter: Paul Field > Labels: bulk-close-candidate > > Since 5.1 now handles Spring beans through the master object provider, it is > (I think) impossible to specify spring beans by name, which is a pain when > you have multiple spring beans implementing the same interface. > Could the Spring Object Provider take notice of an annotation that specifies > the bean name, please? (e.g. @Service or @Id) > It would be particularly nice if the same annotation specified the names of > Tapestry IOC services *and* spring beans, so that if we decide to move > services from Spring into Tapestry IOC we don't need to change any other code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-879) 404 is never raised automatically if the application has an index page.
[ https://issues.apache.org/jira/browse/TAP5-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-879: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > 404 is never raised automatically if the application has an index page. > --- > > Key: TAP5-879 > URL: https://issues.apache.org/jira/browse/TAP5-879 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Christophe Cordenier > Labels: bulk-close-candidate > Attachments: TAP5-879.txt, TAP5-986.txt > > > The default behavior of PageRenderDispatcher when a user access to a URL like > 'http://localhost/demo/blah' (where 'demo' is the application context and > 'blah' is a page that does not exist) is to translate to > 'http://localhost/demo/index/blah' if an index page exists even if it has no > activation method. > It could be a better solution to check if a the index page has an activation > method with the corresponding parameter number and type, and automatically > raise a http 404 if not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-825) Improve label messages for beaneditform
[ https://issues.apache.org/jira/browse/TAP5-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-825: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Improve label messages for beaneditform > --- > > Key: TAP5-825 > URL: https://issues.apache.org/jira/browse/TAP5-825 > Project: Tapestry 5 > Issue Type: Improvement >Affects Versions: 5.1.0.5 >Reporter: Erik Putrycz >Priority: Minor > Labels: bulk-close-candidate > > Currently labels for object properties are searched in messages by property > name "-label". > However an object property might need to be mapped to many different names > depending on the object type. > It would be nice if the message lookup could also perform > .-label lookup, the same way it works for enums. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-639) Inlcude a coercion from Hibernate's Criteria object to a GridDataSource
[ https://issues.apache.org/jira/browse/TAP5-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-639: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Inlcude a coercion from Hibernate's Criteria object to a GridDataSource > --- > > Key: TAP5-639 > URL: https://issues.apache.org/jira/browse/TAP5-639 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-hibernate >Affects Versions: 5.1.0.4 >Reporter: Howard M. Lewis Ship > Labels: bulk-close-candidate > > Seems like a wrapper around a base Criteria could (form there) add in sorting > and pagination quite seamlessly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-829) Provide metadata for beanviewers
[ https://issues.apache.org/jira/browse/TAP5-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-829: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Provide metadata for beanviewers > > > Key: TAP5-829 > URL: https://issues.apache.org/jira/browse/TAP5-829 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Erik Putrycz > Labels: bulk-close-candidate > > I tried to improve beanviewers by using annotations in the class displayed > but unfortunately this is not possible currently. > For editing, BeanEditContext is available, while for viewing only > PropertyOutputContext provides metadata about the object being edited. A > BeanDisplayContext would be a great addition for accessing the class being > edited and retrieve annotations for instance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-800) Server side error during provideCompletions event for Autocompleter mixin is not reported on the client side properly
[ https://issues.apache.org/jira/browse/TAP5-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-800: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Server side error during provideCompletions event for Autocompleter mixin is > not reported on the client side properly > - > > Key: TAP5-800 > URL: https://issues.apache.org/jira/browse/TAP5-800 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Howard M. Lewis Ship >Priority: Minor > Labels: bulk-close-candidate > > You would expect that the console would be raised to display the Ajax error > (as happens with, say, a Zone update) but instead you get no notification and > some wierd presentation oddities (I believe because the autocompleter is > expecting an markup snippet, and instead recieves the exception report > page!). > It may just be time to find a complete replacement for the > Scriptaculous.Autocompleter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-797) Using "tapestry.combine-scripts" with an EmptyClientInfrastructure still adds an empty JavaScript file
[ https://issues.apache.org/jira/browse/TAP5-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-797: -- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Using "tapestry.combine-scripts" with an EmptyClientInfrastructure still adds > an empty JavaScript file > -- > > Key: TAP5-797 > URL: https://issues.apache.org/jira/browse/TAP5-797 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Carl Crowder >Priority: Minor > Labels: bulk-close-candidate > Attachments: check_no_script_tag_if_no_scripts.diff > > > If you have "tapestry.combine-scripts" set to true, and override the > ClientInfrastructure service to not add any assets, the DocumentLinkerImpl > still inserts a SCRIPT tag into the document. The JavaScript it generates is > empty except for a call to the Tapestry JavaScript object, which isn't part > of the page anyway as no other JavaScript has been loaded. > This a) causes a JavaScript error and b) adds unecessary HTTP requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1162) Need a way to pass context with GridPager
[ https://issues.apache.org/jira/browse/TAP5-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-1162: --- Labels: bulk-close-candidate (was: ) This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Need a way to pass context with GridPager > - > > Key: TAP5-1162 > URL: https://issues.apache.org/jira/browse/TAP5-1162 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.1.0.5 >Reporter: Geoff Callender > Labels: bulk-close-candidate > > I need this so I can pass the ID of the grid row I am supposed to highlight > when the grid is "inplace". > An example: in > http://jumpstart.doublenegative.com.au/jumpstart/examples/ajaxfiltercrud > the currently displayed person is highlighted correctly no matter what you > do, until you use the "inplace" GridPager. The other operations preserve the > ID by passing it as a context which the event handler reads. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-931) Component Parameters not always persisted to the end of a Heartbeat
[
https://issues.apache.org/jira/browse/TAP5-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-931:
--
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 1.5 years ago, has no assignee,
affects an old version of Tapestry that is not actively developed anymore, and
is therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Component Parameters not always persisted to the end of a Heartbeat
> ---
>
> Key: TAP5-931
> URL: https://issues.apache.org/jira/browse/TAP5-931
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
>Affects Versions: 5.1.0.5
>Reporter: Leonard Lu
>Priority: Minor
> Labels: bulk-close-candidate
> Attachments: Test.java
>
>
> Odd bug. In the component class that I will attach after creating this Issue,
> a parameter of type JSONObject is bound and modified during page render, then
> deferred to the end of a Heartbeat. In some circumstances when the deferred
> command is run, the parameter is recreated from the bound property and the
> earlier changes are lost.
> Circumstances when an error occurs:
> 1) The parameter is bound to an empty JSONObject, either new JSONObject(), or
> new JSONObject("{}")
> 2) The parameter is given a default value of an empty JSONObject
> Circumstances when an error does not occur:
> 1) The parameter is bound to a populated JSONObject (e.g. new
> JSONObject("{property:'value'}"))
> 2) The parameter is bound to any literal that is coerced to a JSONObject
> 3) A reference to the parameter is saved in a different final variable that
> is passed into the Runnable command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-773) Select component renderer does not allow HTML entities
[ https://issues.apache.org/jira/browse/TAP5-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Blower updated TAP5-773: - Affects Version/s: 5.3.6 5.2.5 > Select component renderer does not allow HTML entities > -- > > Key: TAP5-773 > URL: https://issues.apache.org/jira/browse/TAP5-773 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.3.6, 5.2.5, 5.1.0.5 >Reporter: Andy Blower > Labels: bulk-close-candidate > > All ampersands that are returned from getLabel() in an OptionModel get > encoded to &. This makes it impossible to use any html entities (— > etc) within option labels in selects. This is not that uncommon and > should definitely be supported by Tapestry out of the box. > It can be fixed by changing line 60 of > org.apache.tapestry5.internal.util.SelectModelRender from > writer.write(optionModel.getLabel()); > to > writer.writeRaw(optionModel.getLabel()); > This would mean that ampersands will need to be encoded for option labels, > but this is at least possible for a developer to do. Currently it's not > possible to use entities without using a custom select component, you can't > even extend the T5 Select class and override the Render nested class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-983) CLONE -NPE in BeanDisplay if used in a form with a default model
[ https://issues.apache.org/jira/browse/TAP5-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552763#comment-13552763 ] Stephan Windmüller commented on TAP5-983: - This bug is still present in 5.3.6. I will test it with 5.4 as soon as it is released. > CLONE -NPE in BeanDisplay if used in a form with a default model > > > Key: TAP5-983 > URL: https://issues.apache.org/jira/browse/TAP5-983 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.3.6, 5.1.0.5, 5.0.15 > Environment: Ubuntu Linux, Apache Tomcat >Reporter: Stephan Windmüller >Priority: Minor > Labels: bulk-close-candidate > > Create something like this: > > > > and submit the form. You get a NPE in beandisplay. The workaround is to > create the model yourself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-983) CLONE -NPE in BeanDisplay if used in a form with a default model
[ https://issues.apache.org/jira/browse/TAP5-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Windmüller updated TAP5-983: Affects Version/s: 5.3.6 > CLONE -NPE in BeanDisplay if used in a form with a default model > > > Key: TAP5-983 > URL: https://issues.apache.org/jira/browse/TAP5-983 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.3.6, 5.1.0.5, 5.0.15 > Environment: Ubuntu Linux, Apache Tomcat >Reporter: Stephan Windmüller >Priority: Minor > Labels: bulk-close-candidate > > Create something like this: > > > > and submit the form. You get a NPE in beandisplay. The workaround is to > create the model yourself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-983) CLONE -NPE in BeanDisplay if used in a form with a default model
[ https://issues.apache.org/jira/browse/TAP5-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Windmüller updated TAP5-983: Labels: (was: bulk-close-candidate) > CLONE -NPE in BeanDisplay if used in a form with a default model > > > Key: TAP5-983 > URL: https://issues.apache.org/jira/browse/TAP5-983 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.3.6, 5.1.0.5, 5.0.15 > Environment: Ubuntu Linux, Apache Tomcat >Reporter: Stephan Windmüller >Priority: Minor > > Create something like this: > > > > and submit the form. You get a NPE in beandisplay. The workaround is to > create the model yourself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1151) Customization of Grid Pager
[ https://issues.apache.org/jira/browse/TAP5-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Bouillon updated TAP5-1151: --- Affects Version/s: 5.3.6 > Customization of Grid Pager > --- > > Key: TAP5-1151 > URL: https://issues.apache.org/jira/browse/TAP5-1151 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.3.6, 5.1.0.7 >Reporter: Nicolas Bouillon > Labels: bulk-close-candidate > Attachments: screenshot_021.png > > > I have had to customize the look & feel of the Grid pager, and i had no other > solution to make a full copy paste of Grid.java and GridPager.java in order > to change the pager. > It should be fine to be able to override the pager in a simpler way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-773) Select component renderer does not allow HTML entities
[ https://issues.apache.org/jira/browse/TAP5-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552775#comment-13552775 ] Ulrich Stärk commented on TAP5-773: --- Instead of changing it to writeRaw(), which would break behavior in existing apps, I'd add a new parameter to Select and Palette which would default to the current behavior and write out raw if set. > Select component renderer does not allow HTML entities > -- > > Key: TAP5-773 > URL: https://issues.apache.org/jira/browse/TAP5-773 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core >Affects Versions: 5.3.6, 5.2.5, 5.1.0.5 >Reporter: Andy Blower > Labels: bulk-close-candidate > > All ampersands that are returned from getLabel() in an OptionModel get > encoded to &. This makes it impossible to use any html entities (— > etc) within option labels in selects. This is not that uncommon and > should definitely be supported by Tapestry out of the box. > It can be fixed by changing line 60 of > org.apache.tapestry5.internal.util.SelectModelRender from > writer.write(optionModel.getLabel()); > to > writer.writeRaw(optionModel.getLabel()); > This would mean that ampersands will need to be encoded for option labels, > but this is at least possible for a developer to do. Currently it's not > possible to use entities without using a custom select component, you can't > even extend the T5 Select class and override the Render nested class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1388) GridPager should be able to display which items are displayed
[ https://issues.apache.org/jira/browse/TAP5-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Bouillon updated TAP5-1388: --- Affects Version/s: 5.3.6 > GridPager should be able to display which items are displayed > - > > Key: TAP5-1388 > URL: https://issues.apache.org/jira/browse/TAP5-1388 > Project: Tapestry 5 > Issue Type: Improvement >Affects Versions: 5.3.6, 5.0.15 >Reporter: Nicolas Bouillon > Labels: bulk-close-candidate > > Would be nice if the Grid Pager could be able to display not just the page > number, but also that it's displaying « item 50 to 100 of 2161 ». -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[1/3] git commit: Documentation typo
Documentation typo
Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/12b2c6aa
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/12b2c6aa
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/12b2c6aa
Branch: refs/heads/master
Commit: 12b2c6aa8e27d6cf66eeac14499fcb257f152b1e
Parents: 4f70b71
Author: Howard M. Lewis Ship
Authored: Mon Jan 14 09:03:10 2013 -0800
Committer: Howard M. Lewis Ship
Committed: Mon Jan 14 09:03:53 2013 -0800
--
.../apache/tapestry5/services/TapestryModule.java |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/12b2c6aa/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
--
diff --git
a/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
b/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
index 9991752..fa11481 100644
---
a/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
+++
b/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
@@ -2458,7 +2458,7 @@ public final class TapestryModule
* OperationTracker
* Omits stack frames related to {@link OperationTracker}
* Access
- * Omits tack frames used to provide with access to container class
private members
+ * Omits stack frames used to provide access to container class
private members
*
*
* @since 5.1.0.0
[2/3] git commit: Adjust the OperationTracker regular expression to include the new perform() method
Adjust the OperationTracker regular expression to include the new perform()
method
Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/d6399590
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/d6399590
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/d6399590
Branch: refs/heads/master
Commit: d639959010608e589777458d1dc74c7ba44162f5
Parents: 12b2c6a
Author: Howard M. Lewis Ship
Authored: Mon Jan 14 09:04:47 2013 -0800
Committer: Howard M. Lewis Ship
Committed: Mon Jan 14 09:04:47 2013 -0800
--
.../apache/tapestry5/services/TapestryModule.java |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/d6399590/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
--
diff --git
a/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
b/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
index fa11481..a5b720f 100644
---
a/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
+++
b/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
@@ -2471,7 +2471,7 @@ public final class TapestryModule
configuration.add("Synthetic", new
SyntheticStackTraceElementAnalyzer());
configuration.add("SunReflect", new
PrefixCheckStackTraceElementAnalyzer(
StackTraceElementClassConstants.OMITTED, "sun.reflect."));
-configuration.add("OperationTracker", new
RegexpStackTraceElementAnalyzer(Pattern.compile("internal\\.(RegistryImpl|PerThreadOperationTracker|OperationTrackerImpl).*(run|invoke)\\("),
StackTraceElementClassConstants.OMITTED));
+configuration.add("OperationTracker", new
RegexpStackTraceElementAnalyzer(Pattern.compile("internal\\.(RegistryImpl|PerThreadOperationTracker|OperationTrackerImpl).*(run|invoke|perform)\\("),
StackTraceElementClassConstants.OMITTED));
configuration.add("Access", new
RegexpStackTraceElementAnalyzer(Pattern.compile("\\.access\\$\\d+\\("),
StackTraceElementClassConstants.OMITTED));
configuration.addInstance("Application",
ApplicationStackTraceElementAnalyzer.class);
[3/3] git commit: Minor JavaDoc improvements
Updated Branches:
refs/heads/master 4f70b71e8 -> 9e40372c1
Minor JavaDoc improvements
Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/9e40372c
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/9e40372c
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/9e40372c
Branch: refs/heads/master
Commit: 9e40372c121637725edbf94a918502c25b09ba29
Parents: d639959
Author: Howard M. Lewis Ship
Authored: Mon Jan 14 10:57:31 2013 -0800
Committer: Howard M. Lewis Ship
Committed: Mon Jan 14 10:57:31 2013 -0800
--
.../java/org/apache/tapestry5/ValueEncoder.java|8 +---
.../annotations/ActivationRequestParameter.java|3 ++-
.../tapestry5/annotations/RequestParameter.java|7 ---
3 files changed, 11 insertions(+), 7 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/9e40372c/tapestry-core/src/main/java/org/apache/tapestry5/ValueEncoder.java
--
diff --git a/tapestry-core/src/main/java/org/apache/tapestry5/ValueEncoder.java
b/tapestry-core/src/main/java/org/apache/tapestry5/ValueEncoder.java
index f3e3f4d..c781be6 100644
--- a/tapestry-core/src/main/java/org/apache/tapestry5/ValueEncoder.java
+++ b/tapestry-core/src/main/java/org/apache/tapestry5/ValueEncoder.java
@@ -1,4 +1,4 @@
-// Copyright 2007, 2008, 2011 The Apache Software Foundation
+// Copyright 2007-2013 The Apache Software Foundation
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
@@ -29,8 +29,8 @@ package org.apache.tapestry5;
* Tapestry can automatically generate ValueEncoders for enums as well as
* Collections of any object types for which a coercion can be found from a
* formatted String, such as primitives, primitive wrappers, Dates, Calendars,
- * "name=value" strings, and any types for which a custom coercion has been
- * contributed.
+ * "name=value" strings, and any types for which a {@linkplain
org.apache.tapestry5.ioc.services.TypeCoercer
+ * custom type coercion} has been contributed.
*
* Custom ValueEncoder implementations will need to be supplied for entity type
* objects. In such cases the {@link #toClient(Object)} method typically
returns
@@ -60,6 +60,8 @@ package org.apache.tapestry5;
* @see org.apache.tapestry5.services.ValueEncoderSource
* @see org.apache.tapestry5.services.ValueEncoderFactory
* @see org.apache.tapestry5.annotations.PageActivationContext
+ * @see org.apache.tapestry5.annotations.RequestParameter
+ * @see org.apache.tapestry5.annotations.ActivationRequestParameter
*/
public interface ValueEncoder
{
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/9e40372c/tapestry-core/src/main/java/org/apache/tapestry5/annotations/ActivationRequestParameter.java
--
diff --git
a/tapestry-core/src/main/java/org/apache/tapestry5/annotations/ActivationRequestParameter.java
b/tapestry-core/src/main/java/org/apache/tapestry5/annotations/ActivationRequestParameter.java
index daf3725..d5f8086 100644
---
a/tapestry-core/src/main/java/org/apache/tapestry5/annotations/ActivationRequestParameter.java
+++
b/tapestry-core/src/main/java/org/apache/tapestry5/annotations/ActivationRequestParameter.java
@@ -1,4 +1,4 @@
-// Copyright 2010 The Apache Software Foundation
+// Copyright 2010, 2013 The Apache Software Foundation
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
@@ -49,6 +49,7 @@ import org.apache.tapestry5.services.ValueEncoderSource;
* not affect annotated fields, only assigning them back to null will.
*
* @see RequestParameter
+ * @see ValueEncoder
*/
@Target(
{ ElementType.FIELD })
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/9e40372c/tapestry-core/src/main/java/org/apache/tapestry5/annotations/RequestParameter.java
--
diff --git
a/tapestry-core/src/main/java/org/apache/tapestry5/annotations/RequestParameter.java
b/tapestry-core/src/main/java/org/apache/tapestry5/annotations/RequestParameter.java
index b3e1b0a..ac72f8a 100644
---
a/tapestry-core/src/main/java/org/apache/tapestry5/annotations/RequestParameter.java
+++
b/tapestry-core/src/main/java/org/apache/tapestry5/annotations/RequestParameter.java
@@ -1,4 +1,4 @@
-// Copyright 2010 The Apache Software Foundation
+// Copyright 2010, 2013 The Apache Software Foundation
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
@@ -32,7 +32,7 @@ import org.apache.tapestry5.service
git commit: FIXED - TAP5-1833: Merge functionality of Tynamo.org's tapestry-exceptionpage module with the built-in ExceptionHandler - add javadoc
Updated Branches:
refs/heads/master 9e40372c1 -> fb3fca8d0
FIXED - TAP5-1833: Merge functionality of Tynamo.org's
tapestry-exceptionpage module with the built-in ExceptionHandler
- add javadoc
Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/fb3fca8d
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/fb3fca8d
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/fb3fca8d
Branch: refs/heads/master
Commit: fb3fca8d0835843bcbb25613ceafd393485fe4d2
Parents: 9e40372
Author: Kalle Korhonen
Authored: Mon Jan 14 12:14:59 2013 -0800
Committer: Kalle Korhonen
Committed: Mon Jan 14 12:14:59 2013 -0800
--
.../services/DefaultRequestExceptionHandler.java | 46 ++-
1 files changed, 43 insertions(+), 3 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/fb3fca8d/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java
--
diff --git
a/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java
b/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java
index 969c756..c40c6a0 100644
---
a/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java
+++
b/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java
@@ -40,8 +40,18 @@ import java.util.Map;
import java.util.Map.Entry;
/**
- * Default implementation of {@link RequestExceptionHandler} that displays the
standard ExceptionReport page. The page
- * must implement the {@link ExceptionReporter} interface.
+ * Default implementation of {@link RequestExceptionHandler} that displays the
standard ExceptionReport page. Similarly to the
+ * servlet spec's standard error handling, the default exception handler
allows configuring handlers for specific types of
+ * exceptions. The error-page/exception-type configuration in web.xml does not
work in Tapestry application as errors are
+ * wrapped in Tapestry's exception types (see {@link OperationException} and
{@link ComponentEventException} ).
+ *
+ * Configurations are flexible. You can either contribute a {@link
ExceptionHandlerAssistant} to use arbitrary complex logic
+ * for error handling or a page class to render for the specific exception.
Additionally, exceptions can carry context for the
+ * error page. Exception context is formed either from the name of Exception
(e.g. SmtpNotRespondingException -> ServiceFailure mapping
+ * would render a page with URL /servicefailure/smtpnotresponding) or they can
implement {@link ContextAwareException} interface.
+ *
+ * If no configured exception type is found, the default exception page {@link
SymbolConstants.EXCEPTION_REPORT_PAGE} is rendered.
+ * This fallback exception page must implement the {@link ExceptionReporter}
interface.
*/
public class DefaultRequestExceptionHandler implements RequestExceptionHandler
{
@@ -64,6 +74,19 @@ public class DefaultRequestExceptionHandler implements
RequestExceptionHandler
// should be Class, Object but it's not allowed to
configure subtypes
private final Map configuration;
+/**
+ * @param pageCache
+ * @param renderer
+ * @param logger
+ * @param pageName
+ * @param request
+ * @param response
+ * @param componentClassResolver
+ * @param linkSource
+ * @param serviceResources
+ * @param configuration A map of Exception class and handler values. A
handler is either a page class or an ExceptionHandlerAssistant.
ExceptionHandlerAssistant can be a class
+ * in which case the instance is autobuilt.
+ */
@SuppressWarnings("rawtypes")
public DefaultRequestExceptionHandler(RequestPageCache pageCache,
PageResponseRenderer renderer, Logger logger,
@@ -105,9 +128,19 @@ public class DefaultRequestExceptionHandler implements
RequestExceptionHandler
this.configuration = configuration;
}
+/**
+ * Handles the exception thrown at some point the request was being
processed
+ *
+ * First checks if there was a specific exception handler/page configured
for this exception type, it's super class or super-super class.
+ * Renders the default exception page if none was configured.
+ *
+ * @param exception The exception that was thrown
+ *
+ */
+@SuppressWarnings({ "rawtypes", "unchecked" })
public void handleRequestException(Throwable exception) throws IOException
{
-// skip handling of known exceptions if there are none configured
+// skip handling of known exceptions if there are none configured
if (configur
[jira] [Commented] (TAP5-1833) Merge functionality of Tynamo.org's tapestry-exceptionpage module with the built-in ExceptionHandler
[ https://issues.apache.org/jira/browse/TAP5-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553089#comment-13553089 ] Hudson commented on TAP5-1833: -- Integrated in tapestry-trunk-freestyle #1008 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1008/]) FIXED - TAP5-1833: Merge functionality of Tynamo.org's (Revision fb3fca8d0835843bcbb25613ceafd393485fe4d2) Result = FAILURE kaosko : Files : * tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java > Merge functionality of Tynamo.org's tapestry-exceptionpage module with the > built-in ExceptionHandler > > > Key: TAP5-1833 > URL: https://issues.apache.org/jira/browse/TAP5-1833 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-core >Affects Versions: 5.3 >Reporter: Kalle Korhonen >Assignee: Kalle Korhonen > > As discussed on the dev list: > http://markmail.org/search/?q=Bringing+Tynamo%27s+tapestry-exceptionpage+into+the+core#query:Bringing%20Tynamo%27s%20tapestry-exceptionpage%20into%20the%20core+page:1+mid:wocbkhyqqe7a2tm7+state:results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-1833) Merge functionality of Tynamo.org's tapestry-exceptionpage module with the built-in ExceptionHandler
[ https://issues.apache.org/jira/browse/TAP5-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kalle Korhonen resolved TAP5-1833. -- Resolution: Fixed Fix Version/s: 5.4 > Merge functionality of Tynamo.org's tapestry-exceptionpage module with the > built-in ExceptionHandler > > > Key: TAP5-1833 > URL: https://issues.apache.org/jira/browse/TAP5-1833 > Project: Tapestry 5 > Issue Type: New Feature > Components: tapestry-core >Affects Versions: 5.3 >Reporter: Kalle Korhonen >Assignee: Kalle Korhonen > Fix For: 5.4 > > > As discussed on the dev list: > http://markmail.org/search/?q=Bringing+Tynamo%27s+tapestry-exceptionpage+into+the+core#query:Bringing%20Tynamo%27s%20tapestry-exceptionpage%20into%20the%20core+page:1+mid:wocbkhyqqe7a2tm7+state:results -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
