[jira] [Updated] (TAP5-1474) [GSoC] add out-of-the-box protection against cross-site request forgery (CSRF)
[ https://issues.apache.org/jira/browse/TAP5-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti updated TAP5-1474: -- Labels: (was: bulk-close-candidate) [GSoC] add out-of-the-box protection against cross-site request forgery (CSRF) -- Key: TAP5-1474 URL: https://issues.apache.org/jira/browse/TAP5-1474 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-core Affects Versions: 5.2 Reporter: Ulrich Stärk Assignee: Massimo Lusetti There are several approaches to protect against CSRF. A student working on this task will evaluate the possible solutions, discuss with the community which to implement and implement and test the chosen approach. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TAP5-1474) [GSoC] add out-of-the-box protection against cross-site request forgery (CSRF)
[ https://issues.apache.org/jira/browse/TAP5-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-1474: - Assignee: Massimo Lusetti [GSoC] add out-of-the-box protection against cross-site request forgery (CSRF) -- Key: TAP5-1474 URL: https://issues.apache.org/jira/browse/TAP5-1474 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-core Affects Versions: 5.2 Reporter: Ulrich Stärk Assignee: Massimo Lusetti There are several approaches to protect against CSRF. A student working on this task will evaluate the possible solutions, discuss with the community which to implement and implement and test the chosen approach. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TAP5-1474) [GSoC] add out-of-the-box protection against cross-site request forgery (CSRF)
[ https://issues.apache.org/jira/browse/TAP5-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281386#comment-14281386 ] Massimo Lusetti commented on TAP5-1474: --- I think this could get in in some form but: - malicious software can coerce the victim's browser to do GET requests and POST with specific type which if memory serve are: application/x-www-form-urlencoded, multipart/form-data and text/plain. - the rule of thumb is that GET requests are meant to be idempotent they are not normally protected against CSRF. - in Tapestry we don't have a full blown mechanism for serving REST requests and typically all requests are generated by Link (in a way or the other) and are therefore GET so is usual to have a link to a GET event handler to change something in the storage. So my take is this to be a overall filter/dispatcher which if activated is does the check on all requests coming in and not something that should be activated on a page-by-page or event-by-event handler. I guess the trade-off performance wise is irrelevant. Does it make sense? [GSoC] add out-of-the-box protection against cross-site request forgery (CSRF) -- Key: TAP5-1474 URL: https://issues.apache.org/jira/browse/TAP5-1474 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-core Affects Versions: 5.2 Reporter: Ulrich Stärk Labels: bulk-close-candidate There are several approaches to protect against CSRF. A student working on this task will evaluate the possible solutions, discuss with the community which to implement and implement and test the chosen approach. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TAP5-2245) select component: selected option is not listed in the model.
[
https://issues.apache.org/jira/browse/TAP5-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti resolved TAP5-2245.
---
Resolution: Cannot Reproduce
Fix Version/s: 5.4
Feel free to reopen with a demo project to demonstrate.
select component: selected option is not listed in the model.
-
Key: TAP5-2245
URL: https://issues.apache.org/jira/browse/TAP5-2245
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: Sven Homburg
Assignee: Massimo Lusetti
Labels: regression
Fix For: 5.4
Attachments: ScreenDump.pdf
@Component
private Zone previewZone;
@Component(parameters = {value=previewMonth, model=[1,3,6],
zone=previewZone})
private Select previewSelect;
@OnEvent(component = previewSelect, value = EventConstants.VALUE_CHANGED)
void onValueChangedFromPreviewSelect(long result)
{
if (selectedDate == null)
selectedDate = LocalDate.now();
selectedDate = selectedDate.plusMonths((int) (result - 1));
ajaxResponseRenderer.addRender(previewZone, previewZone);
}
After selecting a value in select component the following error message
occoures:
Selected option is not listed in the model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TAP5-2245) select component: selected option is not listed in the model.
[
https://issues.apache.org/jira/browse/TAP5-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195964#comment-14195964
]
Massimo Lusetti commented on TAP5-2245:
---
I've had a similar case in a recent app using beta-22 and it seems it's working
right.
Does anyone confirm this still valid issue?
select component: selected option is not listed in the model.
-
Key: TAP5-2245
URL: https://issues.apache.org/jira/browse/TAP5-2245
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: Sven Homburg
Labels: regression
Attachments: ScreenDump.pdf
@Component
private Zone previewZone;
@Component(parameters = {value=previewMonth, model=[1,3,6],
zone=previewZone})
private Select previewSelect;
@OnEvent(component = previewSelect, value = EventConstants.VALUE_CHANGED)
void onValueChangedFromPreviewSelect(long result)
{
if (selectedDate == null)
selectedDate = LocalDate.now();
selectedDate = selectedDate.plusMonths((int) (result - 1));
ajaxResponseRenderer.addRender(previewZone, previewZone);
}
After selecting a value in select component the following error message
occoures:
Selected option is not listed in the model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (TAP5-2245) select component: selected option is not listed in the model.
[
https://issues.apache.org/jira/browse/TAP5-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti reassigned TAP5-2245:
-
Assignee: Massimo Lusetti
select component: selected option is not listed in the model.
-
Key: TAP5-2245
URL: https://issues.apache.org/jira/browse/TAP5-2245
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: Sven Homburg
Assignee: Massimo Lusetti
Labels: regression
Attachments: ScreenDump.pdf
@Component
private Zone previewZone;
@Component(parameters = {value=previewMonth, model=[1,3,6],
zone=previewZone})
private Select previewSelect;
@OnEvent(component = previewSelect, value = EventConstants.VALUE_CHANGED)
void onValueChangedFromPreviewSelect(long result)
{
if (selectedDate == null)
selectedDate = LocalDate.now();
selectedDate = selectedDate.plusMonths((int) (result - 1));
ajaxResponseRenderer.addRender(previewZone, previewZone);
}
After selecting a value in select component the following error message
occoures:
Selected option is not listed in the model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TAP5-2280) [GSoC] New module to generate and compile component based on Facebook React framework
[ https://issues.apache.org/jira/browse/TAP5-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13955075#comment-13955075 ] Massimo Lusetti commented on TAP5-2280: --- Hi Vishal, that shouldn't have been difficult to find sinc you arrived here, anyway from here http://tapestry.apache.org/community.html you can see: User list at: users-subscr...@tapestry.apache.org Dev list at: dev-subscr...@tapestry.apache.org Cheers [GSoC] New module to generate and compile component based on Facebook React framework - Key: TAP5-2280 URL: https://issues.apache.org/jira/browse/TAP5-2280 Project: Tapestry 5 Issue Type: New Feature Reporter: Massimo Lusetti Labels: gsoc2014, java, javascript It would be great to leverage the power of Tapestry5 Asset pipeline and Request dispatcher to gracefully handle the build of Facebook React (http://facebook.github.io/react/index.html) based componets. The main objective for this new module would be to free the developer to build Facebook React components and have them naturally binded to Tapestry5 page events. Tapestry5 and Facebook React share the same component model and event delegation concepts, the Tapestry5 Asset pipeline can be enhanced to compile, compress and minify at runtime JSX files while the Request dispather coupled with the REST friendly generated URL can make this pretty easy to develop one page app within Tapestry5 leveraging all the performance (development and runtime) provided by the framework. I'm more then willing to mentor this project. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TAP5-2280) New module to generate and compile component based on ReactJS framework
Massimo Lusetti created TAP5-2280: - Summary: New module to generate and compile component based on ReactJS framework Key: TAP5-2280 URL: https://issues.apache.org/jira/browse/TAP5-2280 Project: Tapestry 5 Issue Type: New Feature Reporter: Massimo Lusetti It would be great to leverage the power of Tapestry5 Asset pipeline and Request dispatcher to gracefully handle the build of ReactJS (http://facebook.github.io/react/index.html) based componets. The main objective for this new module would be to free the developer to build ReactJS components and have them naturally binded to Tapestry5 page events. Tapestry5 and ReactJS share the same component model and event delegation concepts, the Tapestry5 Asset pipeline can be enhanced to compile, compress and minify at runtime JSX files while the Request dispather coupled with the REST friendly generated URL can make this pretty easy to develop one page app within Tapestry5 leveraging all the performance (development and runtime) provided by the framework. I'm more then willing to mentor this project. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (TAP5-1007) When Tapestry is loading templates or other files on case-insensitive OSs (Windows) it should trigger an error if the file name case is incorrect (which will result in a
[ https://issues.apache.org/jira/browse/TAP5-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13752298#comment-13752298 ] Massimo Lusetti commented on TAP5-1007: --- Yep, both are OS dependent. The check is valid only on case insensitive OS so the same apply for the test which check the code. When Tapestry is loading templates or other files on case-insensitive OSs (Windows) it should trigger an error if the file name case is incorrect (which will result in a runtime failure on case-sensitive OSs, such as Linux) --- Key: TAP5-1007 URL: https://issues.apache.org/jira/browse/TAP5-1007 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.2 Reporter: Howard M. Lewis Ship Assignee: Howard M. Lewis Ship Fix For: 5.4 In other words, on Windows you might find file myComponent.tml when it should be named MyComponent.tml (to match the name of the class, MyComponent). This is irritating to find in testing or production, and Tapestry should be able to add a check that the case of the file name does not match the expected case. -- 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-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti updated TAP5-2070:
--
Attachment: (was:
0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch)
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.4
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
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-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728515#comment-13728515
]
Massimo Lusetti commented on TAP5-2070:
---
The patch is outdated, I'll commit a new one based on a different implementation
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.4
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
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] [Created] (TAP5-2153) Adapt quickstart archetype generated sources to be bootstrap and 5.4 compatibile
Massimo Lusetti created TAP5-2153: - Summary: Adapt quickstart archetype generated sources to be bootstrap and 5.4 compatibile Key: TAP5-2153 URL: https://issues.apache.org/jira/browse/TAP5-2153 Project: Tapestry 5 Issue Type: Improvement Components: quickstart Affects Versions: 5.4 Reporter: Massimo Lusetti Current quickstart is based on an old HTML/CSS template which doesn't use bootstrap nor jquery. It would be nice to have the source code generated by the latest quickstart archetype to follow the choice from core -- 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-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725320#comment-13725320
]
Massimo Lusetti commented on TAP5-2070:
---
Any comment on this?!
Does we want to ship with the current behavior?
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
Attachments:
0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
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-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti updated TAP5-2070:
--
Affects Version/s: 5.4
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.4
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
Attachments:
0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
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-2131) Update Javadoc CSS to reflect changes in the html generate by JDK7
[ https://issues.apache.org/jira/browse/TAP5-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-2131. --- Resolution: Fixed Fix Version/s: 5.4 Update Javadoc CSS to reflect changes in the html generate by JDK7 -- Key: TAP5-2131 URL: https://issues.apache.org/jira/browse/TAP5-2131 Project: Tapestry 5 Issue Type: Improvement Reporter: Massimo Lusetti Assignee: Massimo Lusetti Fix For: 5.4 The current stylesheet is adapted for the JDK6 javadoc html output, we need a new stylesheet for customizing JDK7 javadoc output -- 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] [Created] (TAP5-2131) Update Javadoc CSS to reflect changes in the html generate by JDK7
Massimo Lusetti created TAP5-2131: - Summary: Update Javadoc CSS to reflect changes in the html generate by JDK7 Key: TAP5-2131 URL: https://issues.apache.org/jira/browse/TAP5-2131 Project: Tapestry 5 Issue Type: Improvement Reporter: Massimo Lusetti The current stylesheet is adapted for the JDK6 javadoc html output, we need a new stylesheet for customizing JDK7 javadoc output -- 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] [Assigned] (TAP5-2131) Update Javadoc CSS to reflect changes in the html generate by JDK7
[ https://issues.apache.org/jira/browse/TAP5-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-2131: - Assignee: Massimo Lusetti Update Javadoc CSS to reflect changes in the html generate by JDK7 -- Key: TAP5-2131 URL: https://issues.apache.org/jira/browse/TAP5-2131 Project: Tapestry 5 Issue Type: Improvement Reporter: Massimo Lusetti Assignee: Massimo Lusetti The current stylesheet is adapted for the JDK6 javadoc html output, we need a new stylesheet for customizing JDK7 javadoc output -- 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] [Created] (TAP5-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
Massimo Lusetti created TAP5-2070:
-
Summary: Respond with a HTTP 404 if the page is activated with an
activation context not explicitly supported by the page itself
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Reporter: Massimo Lusetti
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
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] [Assigned] (TAP5-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti reassigned TAP5-2070:
-
Assignee: Massimo Lusetti
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
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] [Closed] (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 ] Massimo Lusetti closed TAP5-879. Resolution: Won't Fix A new issue has been created to reflect what I would like to achieve. Here we are talking only about Index pages and I want all pages to behave the same so I ask you to follow TAP5-2070 which will implement this plus more. I you feel strong about this particular issue, please reopen. 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 Assignee: Massimo Lusetti 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-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti updated TAP5-2070:
--
Attachment: 0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
Patch that implement the new behavior but keep it disabled.
It can be enabled by a configuration symbol.
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
Attachments:
0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
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-2065) Introduce support for MongoDB access as a service
[ https://issues.apache.org/jira/browse/TAP5-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-2065. --- Resolution: Fixed Fix Version/s: 5.4 Introduce support for MongoDB access as a service - Key: TAP5-2065 URL: https://issues.apache.org/jira/browse/TAP5-2065 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-ioc Reporter: Massimo Lusetti Assignee: Massimo Lusetti Fix For: 5.4 Provide infrastructure services to be able to access a MongoDB instance through Tapestry5 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] [Created] (TAP5-2065) Introduce support for MongoDB access as a service
Massimo Lusetti created TAP5-2065: - Summary: Introduce support for MongoDB access as a service Key: TAP5-2065 URL: https://issues.apache.org/jira/browse/TAP5-2065 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-ioc Reporter: Massimo Lusetti Provide infrastructure services to be able to access a MongoDB instance through Tapestry5 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] [Assigned] (TAP5-2065) Introduce support for MongoDB access as a service
[ https://issues.apache.org/jira/browse/TAP5-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-2065: - Assignee: Massimo Lusetti Introduce support for MongoDB access as a service - Key: TAP5-2065 URL: https://issues.apache.org/jira/browse/TAP5-2065 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-ioc Reporter: Massimo Lusetti Assignee: Massimo Lusetti Provide infrastructure services to be able to access a MongoDB instance through Tapestry5 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-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 ] Massimo Lusetti updated TAP5-879: - Labels: (was: bulk-close-candidate) 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 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] [Assigned] (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 ] Massimo Lusetti reassigned TAP5-879: Assignee: Massimo Lusetti 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 Assignee: Massimo Lusetti 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] [Commented] (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:comment-tabpanelfocusedCommentId=13564295#comment-13564295 ] Massimo Lusetti commented on TAP5-879: -- I take this just to be sure it will not be closed in the bulk operation while discussion is ongoing on the dev list. 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 Assignee: Massimo Lusetti 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] [Created] (TAP5-2058) Support X-Forwarded-Proto to identify a Request secured (https)
Massimo Lusetti created TAP5-2058: - Summary: Support X-Forwarded-Proto to identify a Request secured (https) Key: TAP5-2058 URL: https://issues.apache.org/jira/browse/TAP5-2058 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Reporter: Massimo Lusetti The X-Forwarded-Proto is the de facto standard header used by reverse proxies to tell the original Request was secured or not with HTTPS. It can therefore be used to recognize the Request as secured. -- 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] [Assigned] (TAP5-2058) Support X-Forwarded-Proto to identify a Request secured (https)
[ https://issues.apache.org/jira/browse/TAP5-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-2058: - Assignee: Massimo Lusetti Support X-Forwarded-Proto to identify a Request secured (https) --- Key: TAP5-2058 URL: https://issues.apache.org/jira/browse/TAP5-2058 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Reporter: Massimo Lusetti Assignee: Massimo Lusetti The X-Forwarded-Proto is the de facto standard header used by reverse proxies to tell the original Request was secured or not with HTTPS. It can therefore be used to recognize the Request as secured. -- 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-2058) Support X-Forwarded-Proto to identify a Request secured (https)
[ https://issues.apache.org/jira/browse/TAP5-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-2058. --- Resolution: Fixed Fix Version/s: 5.4 Support X-Forwarded-Proto to identify a Request secured (https) --- Key: TAP5-2058 URL: https://issues.apache.org/jira/browse/TAP5-2058 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Reporter: Massimo Lusetti Assignee: Massimo Lusetti Fix For: 5.4 The X-Forwarded-Proto is the de facto standard header used by reverse proxies to tell the original Request was secured or not with HTTPS. It can therefore be used to recognize the Request as secured. -- 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-2014) Zone highlight leaves behind an explicit background-color which overrides css background-color
[
https://issues.apache.org/jira/browse/TAP5-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505355#comment-13505355
]
Massimo Lusetti commented on TAP5-2014:
---
I've came across this one lately and it's annoying indeed.
The fact is that it has been fixed in the 5.4 branch which by default does
nothing, so the question is: is a fix for 5.3 branch with the consequent
release necessary ?
Zone highlight leaves behind an explicit background-color which overrides css
background-color
--
Key: TAP5-2014
URL: https://issues.apache.org/jira/browse/TAP5-2014
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.3.6
Reporter: Geoff Callender
Zone highlighter (i.e. t:update=highlight) leaves behind an explicit
background-color that overrides the background-color specified in css.
Instead, I think it should finish by removing the style changes that it added.
An example consequence: it kills off my hover effect. I have a table row with
a hover effect, eg.
tr { background-color: #fff; }
tr:hover { background-color: #eee; }
and the row is also a zone with a highlight effect
tr t:type=Zone t:id=rowZone id=prop:currentRowZoneId
t:update=highlight
The hover effect works just fine until the zone updates, and then it no
longer works.
Here's the row before the zone updates:
tr class=even t-zone tapestry-zone id=rowZone_5
Here's the row after the zone updates:
tr class=even t-zone tapestry-zone id=rowZone_5
style=background-image: none; background-color: rgb(255, 255, 255);
The problem would go away if the zone update finished by leaving the row the
way that it found it:
tr class=even t-zone tapestry-zone id=rowZone_5
You can see the problem if you turn on Highlight zone updates in this
example:
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/eventlinksinaloop
--
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-1949) Alerts component does not show alerts added from a component that occurs later in the template
[ https://issues.apache.org/jira/browse/TAP5-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-1949. --- Resolution: Fixed Fix Version/s: 5.4 5.3.5 Thanks for the patch Joachen Kemnade Alerts component does not show alerts added from a component that occurs later in the template -- Key: TAP5-1949 URL: https://issues.apache.org/jira/browse/TAP5-1949 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.3, 5.3.4, 5.4 Reporter: Jochen Kemnade Assignee: Massimo Lusetti Priority: Minor Labels: patch Fix For: 5.3.5, 5.4 Attachments: 0001-defer-the-alerts-JS-initialization-to-allow-for-aler.patch Consider the following snippet: t:alerts / t:componentthataddsanalert / The alert will not be shown as the JS for the alerts is generated in the beginRender phase of the alerts component. and alerts that are added later are ignored until its next rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1949) Alerts component does not show alerts added from a component that occurs later in the template
[ https://issues.apache.org/jira/browse/TAP5-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13422250#comment-13422250 ] Massimo Lusetti commented on TAP5-1949: --- Would you mind to flag the patch as Apache licensed? Alerts component does not show alerts added from a component that occurs later in the template -- Key: TAP5-1949 URL: https://issues.apache.org/jira/browse/TAP5-1949 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.3, 5.3.4, 5.4 Reporter: Jochen Kemnade Priority: Minor Labels: patch Attachments: 0001-defer-the-alerts-JS-initialization-to-allow-for-aler.patch Consider the following snippet: t:alerts / t:componentthataddsanalert / The alert will not be shown as the JS for the alerts is generated in the beginRender phase of the alerts component. and alerts that are added later are ignored until its next rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1949) Alerts component does not show alerts added from a component that occurs later in the template
[ https://issues.apache.org/jira/browse/TAP5-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-1949: - Assignee: Massimo Lusetti Alerts component does not show alerts added from a component that occurs later in the template -- Key: TAP5-1949 URL: https://issues.apache.org/jira/browse/TAP5-1949 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.3, 5.3.4, 5.4 Reporter: Jochen Kemnade Assignee: Massimo Lusetti Priority: Minor Labels: patch Attachments: 0001-defer-the-alerts-JS-initialization-to-allow-for-aler.patch Consider the following snippet: t:alerts / t:componentthataddsanalert / The alert will not be shown as the JS for the alerts is generated in the beginRender phase of the alerts component. and alerts that are added later are ignored until its next rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1949) Alerts component does not show alerts added from a component that occurs later in the template
[ https://issues.apache.org/jira/browse/TAP5-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293433#comment-13293433 ] Massimo Lusetti commented on TAP5-1949: --- I like the proposed behavior. Did anyone see a draw back in this changes? Alerts component does not show alerts added from a component that occurs later in the template -- Key: TAP5-1949 URL: https://issues.apache.org/jira/browse/TAP5-1949 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.3, 5.4 Reporter: Jochen Kemnade Priority: Minor Labels: patch Attachments: 0001-defer-the-alerts-JS-initialization-to-allow-for-aler.patch Consider the following snippet: t:alerts / t:componentthataddsanalert / The alert will not be shown as the JS for the alerts is generated in the beginRender phase of the alerts component. and alerts that are added later are ignored until its next rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-147) Localization: Messages should be overwiteable by Container (.i.e. users) of the component
[ https://issues.apache.org/jira/browse/TAP5-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-147. -- Resolution: Duplicate Is has been fixed with TAP5-424 as now the ComponentMessagesSource accept and ordered configuration of catalogs (Resources) so order determine overrides. Localization: Messages should be overwiteable by Container (.i.e. users) of the component -- Key: TAP5-147 URL: https://issues.apache.org/jira/browse/TAP5-147 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.0.15 Reporter: Fritz Pröbstle Assignee: Massimo Lusetti Labels: tapestry5-review-for-closing Currently messages are *only* searched in the component and its subclasses catalogs. This means only the component provider suppies messages. Often a *User* of a componet ( ie. the container ) wants to override the messages. In a special case the container is the page which should have means to change *all* messages. I propose a path-like syntax to specify thew hierarchy.(means all messages are reachable if the container hierarchy is documented) I.e: page.properties --- firstContainerId.innerContainerId.name= overwriten message In the Message search for a component it the following search would appear: look in immediate container ... look in the moust outer container (page) the look upo in the componet and its subclasses. If a message is found stop the search and take the message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-147) Localization: Messages should be overwiteable by Container (.i.e. users) of the component
[ https://issues.apache.org/jira/browse/TAP5-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-147. Localization: Messages should be overwiteable by Container (.i.e. users) of the component -- Key: TAP5-147 URL: https://issues.apache.org/jira/browse/TAP5-147 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.0.15 Reporter: Fritz Pröbstle Assignee: Massimo Lusetti Labels: tapestry5-review-for-closing Currently messages are *only* searched in the component and its subclasses catalogs. This means only the component provider suppies messages. Often a *User* of a componet ( ie. the container ) wants to override the messages. In a special case the container is the page which should have means to change *all* messages. I propose a path-like syntax to specify thew hierarchy.(means all messages are reachable if the container hierarchy is documented) I.e: page.properties --- firstContainerId.innerContainerId.name= overwriten message In the Message search for a component it the following search would appear: look in immediate container ... look in the moust outer container (page) the look upo in the componet and its subclasses. If a message is found stop the search and take the message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE
[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-1616. - Resolution: Duplicate This has been addressed with TAP5-1637 PeriodicExecutor service prevents running T5.3 on GAE - Key: TAP5-1616 URL: https://issues.apache.org/jira/browse/TAP5-1616 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3 Reporter: Kalle Korhonen Labels: tapestry5-review-for-closing Since GAE doesn't allow user-created threads, constructing PeriodicExecutor service fails on GAE, preventing running the whole application on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-1485) Quickstart archetype should define a ProductionModeModule and DevelopmentModeModule with support inside web.xml
[ https://issues.apache.org/jira/browse/TAP5-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-1485. --- Resolution: Fixed Fix Version/s: 5.3 Quickstart archetype should define a ProductionModeModule and DevelopmentModeModule with support inside web.xml --- Key: TAP5-1485 URL: https://issues.apache.org/jira/browse/TAP5-1485 Project: Tapestry 5 Issue Type: Improvement Components: quickstart Affects Versions: 5.3 Reporter: Howard M. Lewis Ship Assignee: Massimo Lusetti Fix For: 5.3 Attachments: quickstart.patch It's a good practice to have a general AppModule, plus additional module(s) for setup restricted to actual production, and an alternate module for overrides needed during development and testing. The support for this, execution modes, was adding in 5.2. More documentation would be nice, as would an enhanced quickstart archetype that shows how those modes would operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-1609) Generate Maven archetype from within gradle builds
[ https://issues.apache.org/jira/browse/TAP5-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-1609. --- Resolution: Fixed Fix Version/s: 5.3 Generate Maven archetype from within gradle builds -- Key: TAP5-1609 URL: https://issues.apache.org/jira/browse/TAP5-1609 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.3 Reporter: Massimo Lusetti Assignee: Massimo Lusetti Fix For: 5.3 It would be nice to have (again) the Maven archetype produced by the build cycle. Maybe with a build.gradle script in it... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE
[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090809#comment-13090809 ] Massimo Lusetti commented on TAP5-1616: --- To me that would be an user error not a framework incompatibility. Maybe a note in Confluence showing this kind of issue, relative to GAE, is what is needed. PeriodicExecutor service prevents running T5.3 on GAE - Key: TAP5-1616 URL: https://issues.apache.org/jira/browse/TAP5-1616 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3 Reporter: Kalle Korhonen Since GAE doesn't allow user-created threads, constructing PeriodicExecutor service fails on GAE, preventing running the whole application on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE
[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091040#comment-13091040 ] Massimo Lusetti commented on TAP5-1616: --- Right now PageSourceImpl depends on it so a changes would be needed anyway. PeriodicExecutor service prevents running T5.3 on GAE - Key: TAP5-1616 URL: https://issues.apache.org/jira/browse/TAP5-1616 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3 Reporter: Kalle Korhonen Since GAE doesn't allow user-created threads, constructing PeriodicExecutor service fails on GAE, preventing running the whole application on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE
[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091057#comment-13091057 ] Massimo Lusetti commented on TAP5-1616: --- I'm not addicted to GAE actually... but I like Igor's proposal. PeriodicExecutor service prevents running T5.3 on GAE - Key: TAP5-1616 URL: https://issues.apache.org/jira/browse/TAP5-1616 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3 Reporter: Kalle Korhonen Since GAE doesn't allow user-created threads, constructing PeriodicExecutor service fails on GAE, preventing running the whole application on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE
[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091330#comment-13091330 ] Massimo Lusetti commented on TAP5-1616: --- The only argument I could see is that the SoftReference is owned directly by the GC while the current impl is somehow configurable by the user. I would like to see a comment from Howard in this regards and I would like to see a poll in the user and/or dev list to get if GAE support is really asked. What do you think? PeriodicExecutor service prevents running T5.3 on GAE - Key: TAP5-1616 URL: https://issues.apache.org/jira/browse/TAP5-1616 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3 Reporter: Kalle Korhonen Since GAE doesn't allow user-created threads, constructing PeriodicExecutor service fails on GAE, preventing running the whole application on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE
[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090355#comment-13090355 ] Massimo Lusetti commented on TAP5-1616: --- A simple patch would be to adapt the code to accept a PAGE_SOURCE_CHECK_INTERVAL of 0 which will disable the janitor of page instances ... which indeed will affect heap space usage and so forth the GC. Would that be acceptable ? PeriodicExecutor service prevents running T5.3 on GAE - Key: TAP5-1616 URL: https://issues.apache.org/jira/browse/TAP5-1616 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3 Reporter: Kalle Korhonen Since GAE doesn't allow user-created threads, constructing PeriodicExecutor service fails on GAE, preventing running the whole application on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1616) PeriodicExecutor service prevents running T5.3 on GAE
[ https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090455#comment-13090455 ] Massimo Lusetti commented on TAP5-1616: --- I'm not sure to follow you about making sure that failure in constructing the service doesn't prevent the app from loading PeriodicExecutor service prevents running T5.3 on GAE - Key: TAP5-1616 URL: https://issues.apache.org/jira/browse/TAP5-1616 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3 Reporter: Kalle Korhonen Since GAE doesn't allow user-created threads, constructing PeriodicExecutor service fails on GAE, preventing running the whole application on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-650) Enhance form autofocus to accept fieldname as a value
[
https://issues.apache.org/jira/browse/TAP5-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti closed TAP5-650.
Resolution: Fixed
Fix Version/s: 5.3
Applied as a mixin to the form component
Enhance form autofocus to accept fieldname as a value
-
Key: TAP5-650
URL: https://issues.apache.org/jira/browse/TAP5-650
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.1.0.3
Reporter: Kalle Korhonen
Assignee: Massimo Lusetti
Priority: Minor
Fix For: 5.3
It's not difficult to set autofocus=false and add $('myField').activate();
yourself, but I think it would address many of the issues people are having
with autofocus if the parameter would also accept a field name instead of
simply a boolean value so you can set the focus to field you like.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1485) Quickstart archetype should define a ProductionModeModule and DevelopmentModeModule with support inside web.xml
[ https://issues.apache.org/jira/browse/TAP5-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-1485: - Assignee: Massimo Lusetti Quickstart archetype should define a ProductionModeModule and DevelopmentModeModule with support inside web.xml --- Key: TAP5-1485 URL: https://issues.apache.org/jira/browse/TAP5-1485 Project: Tapestry 5 Issue Type: Improvement Components: quickstart Affects Versions: 5.3 Reporter: Howard M. Lewis Ship Assignee: Massimo Lusetti Attachments: quickstart.patch It's a good practice to have a general AppModule, plus additional module(s) for setup restricted to actual production, and an alternate module for overrides needed during development and testing. The support for this, execution modes, was adding in 5.2. More documentation would be nice, as would an enhanced quickstart archetype that shows how those modes would operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1609) Generate Maven archetype from within gradle builds
[ https://issues.apache.org/jira/browse/TAP5-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-1609: - Assignee: Massimo Lusetti Generate Maven archetype from within gradle builds -- Key: TAP5-1609 URL: https://issues.apache.org/jira/browse/TAP5-1609 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.3 Reporter: Massimo Lusetti Assignee: Massimo Lusetti It would be nice to have (again) the Maven archetype produced by the build cycle. Maybe with a build.gradle script in it... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TAP5-1609) Generate Maven archetype from within gradle builds
Generate Maven archetype from within gradle builds -- Key: TAP5-1609 URL: https://issues.apache.org/jira/browse/TAP5-1609 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.3 Reporter: Massimo Lusetti It would be nice to have (again) the Maven archetype produced by the build cycle. Maybe with a build.gradle script in it... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1609) Generate Maven archetype from within gradle builds
[ https://issues.apache.org/jira/browse/TAP5-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084707#comment-13084707 ] Massimo Lusetti commented on TAP5-1609: --- The base for this is in the trunk I'll wait some days before closing this hoping for some comments from users: To use this one you should: - build the quickstart as usual with gradle - install the archetype-catalog.xml in the build/quickstart-generated in the local catalog - install the .jar and the .pom produced by the build - test the archetype with the full command line of archetype:generate More tweak will certainly follow... Generate Maven archetype from within gradle builds -- Key: TAP5-1609 URL: https://issues.apache.org/jira/browse/TAP5-1609 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.3 Reporter: Massimo Lusetti Assignee: Massimo Lusetti It would be nice to have (again) the Maven archetype produced by the build cycle. Maybe with a build.gradle script in it... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-299) NPE in SelectModelRenderer when Palette used with mismatched values and model
[ https://issues.apache.org/jira/browse/TAP5-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-299. Resolution: Invalid Please open a new one for 5.3 if this still applicable and has relevance NPE in SelectModelRenderer when Palette used with mismatched values and model - Key: TAP5-299 URL: https://issues.apache.org/jira/browse/TAP5-299 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.0.15 Reporter: Dan Adams Create a model with A,B as the available options and set the palette value parameter to a list with C. You will get a NPE here: org.apache.tapestry5.internal.util.SelectModelRenderer.option(SelectModelRenderer.java:49) org.apache.tapestry5.corelib.components.Palette$SelectedRenderer.render(Palette.java:147) because valueToOptionModel in Palette doesn't contain a mapping for C. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-300) Autocompleter on scrollable pages scrolls whole page when ArrowUp is pressed
[
https://issues.apache.org/jira/browse/TAP5-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti closed TAP5-300.
Resolution: Won't Fix
Scriptaculous has been update and work has been done on the JS side to make it
more PrototypeJS agnostic (in future) so please reopen if still applicable in
5.3
Autocompleter on scrollable pages scrolls whole page when ArrowUp is pressed
Key: TAP5-300
URL: https://issues.apache.org/jira/browse/TAP5-300
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0.15
Reporter: Shymon
If you place autocompleter on a page longer than browser's window (page which
has a scrollbar) and press ArrowUp key after choice list is displayed whole
page is scrolled down such that highlighted option is on the top edge of
browser's window. If you press ArrowDown page is scrolled back to proper
position. Behaves the same in FF and IE.
Maybe this is the problem:
markPrevious: function() {
if(this.index 0) this.index--
else this.index = this.entryCount-1;
this.getEntry(this.index).scrollIntoView(true);
},
markNext: function() {
if(this.index this.entryCount-1) this.index++
else this.index = 0;
this.getEntry(this.index).scrollIntoView(false);
},
scrollIntoView true for previous and false for next?
It's very annoying, and makes autocompleter practically unusable on
production quality pages.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-315) Tapestry should be able to notice the creation of new templates or classes, rather than just updates to existing
[ https://issues.apache.org/jira/browse/TAP5-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-315. Resolution: Fixed Fix Version/s: 5.2.6 Tested against a clean webapp based on 5.2.6 and it has noticed the newly created and compiled class/page so I guess this is a leftover and maybe is due to the changes related to the pagepool mechanism Tapestry should be able to notice the creation of new templates or classes, rather than just updates to existing -- Key: TAP5-315 URL: https://issues.apache.org/jira/browse/TAP5-315 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.0.15 Reporter: Thiago H. de Paula Figueiredo Priority: Minor Fix For: 5.2.6 Tapestry does not pick new pages, components, mixins and templates after it is started. If this fact is reversed, we could develop an entire web interface without reloading the application. In addition, there is one other reason to implement this new feature: applications with static content. Every time I add a new page to my website, I have to restart the application, as it's written on T5. This is not an issue to my site, but can be to high traffic ones. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-338) Component report crashes in multiproject Maven build with many subdirectories
[ https://issues.apache.org/jira/browse/TAP5-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-338. Resolution: Won't Fix ComponentReport building is disabled since the switch to gradle and even tapestry-core now use a javadoc doclet to document components behavior. If you feel you can reopen. Component report crashes in multiproject Maven build with many subdirectories - Key: TAP5-338 URL: https://issues.apache.org/jira/browse/TAP5-338 Project: Tapestry 5 Issue Type: Bug Environment: Ubuntu 8.10, Java 1.6.0_07, Maven 2.0.9 Reporter: Martin Wagner Priority: Minor Attachments: tapestry-component-error.txt In a multiproject build, mvn site aborts with error INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: target/component-report-javadoc-arguments.txt (No such file or directory) The error happens only in the following setting (part of our nightly build and thus hard to change): dir subdir (with master pom.xml) subsubdir (with project pom.xml and definition of component-report in reporting section) If I call mvn site in subdir, things work fine. If I call mvn site in subsubdir, things work fine. If I call mvn -f subsubdir/pom.xml site in subdir, things work fine. If I call mvn -f subdir/pom.xml site in dir, error occurs. If I call mvn -f subdir/subsubdir/pom.xml site in dir, error occurs. I will attach the detailed output of mvn -X -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-368) Error messages in Errors component are misaligned in Internet Explorer 7 when strict doctype used
[ https://issues.apache.org/jira/browse/TAP5-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084040#comment-13084040 ] Massimo Lusetti commented on TAP5-368: -- To me it seems a very special case which could be addressed by the user with a patch, I've marked this for reviewing even if I would close it. Error messages in Errors component are misaligned in Internet Explorer 7 when strict doctype used - Key: TAP5-368 URL: https://issues.apache.org/jira/browse/TAP5-368 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.0.16 Reporter: Simon Hartley Priority: Trivial Labels: tapestr5-review-for-closing Error messages are misaligned in the Errors component in Internet Explorer 7 when I use the following doctype: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN http://www.w3.org/TR/html4/strict.dtd; The text appears shifted to the left, beginning outside of the box. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-411) A persistence strategy to provide page specific state
[ https://issues.apache.org/jira/browse/TAP5-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084047#comment-13084047 ] Massimo Lusetti commented on TAP5-411: -- There's been a lot of work in the session handling recently with new session attrbitue and so on, this is old and could be outdated. I would like to close this... please comment A persistence strategy to provide page specific state -- Key: TAP5-411 URL: https://issues.apache.org/jira/browse/TAP5-411 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-core Affects Versions: 5.1 Reporter: Peter Stavrinides Labels: tapestr5-review-for-closing Perhaps the most commonly reoccurring persistence pattern is 'per page', as opposed to session wide, or per request. Tapestry provides persistence strategies for the later of these, but there is no strategy that mirrors a pages 'implied' life-cycle. @Persist Persists a value for a page for the duration of a session: best used on primitives, a disadvantage is that its open for abuse by incorrect use which will clutter the session and increase its size thereby reducing scalability. @Persist(flash) A persisted object is removed after a post: - Not suited to all use cases that require 'page specific' persistence... render methods can sometimes prevent using flash persistence. Currently the most scalable pattern for simulating page state is using onActivate with onPassivate, and re-instantiating objects required for the page, generally from their identifiers. It requires more boilerplate code for checking that URL parameters are passed correctly, particularly for pages that have 'optional parameters'... the downside is more queries and having to use identifiers in URL parameters. @Persist(conversation) Seam provides this type of strategy, conversations provide a generally better persistence context, persistence is associated to a single window / tab, for which it retains state information between data requests/posts etc (whereas its relatives, which are other windows or tabs will be independent to the 'conversation') . Conversational state has been discussed in the past for Tapestry. @Persist(?) The proposed strategy is along the same lines as conversational state, but persisted values are retained for all instances of that page (regardless of tabs or windows, meaning in practice that all active instances of that page share an identifier), so closing all instances would remove associated persisted values. More on this in this thread here: http://www.nabble.com/Persistance-td20732003.html#a20732003 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-171) Filter out attributes with default value (from DTD) when parsing templates
[
https://issues.apache.org/jira/browse/TAP5-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti updated TAP5-171:
-
Affects Version/s: 5.2
Filter out attributes with default value (from DTD) when parsing templates
--
Key: TAP5-171
URL: https://issues.apache.org/jira/browse/TAP5-171
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2, 5.0.18
Environment: Sun JDK 1.5
Reporter: Folke Behrens
Priority: Minor
Labels: tapestr5-review-for-closing
Fix For: 5.3
Attachments: TAP5-171 5.2.4.patch, Test.html,
attributes2-dtd-default.patch
Consider testing for org.xml.sax.ext.Attributes2 and use
Attributes2.isSpecified(int) to check if the attribute is really specified or
just a default declaration.
With this you can e.g. test if a shape=rect is really set. Test for
http://xml.org/sax/features/use-attributes2; or just use instanceof:
if (attributes instanceof Attributes2) {
if (( (Attributes2)attributes ).isSpecified(i)) {
// do something
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (TAP5-171) Filter out attributes with default value (from DTD) when parsing templates
[
https://issues.apache.org/jira/browse/TAP5-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti reopened TAP5-171:
--
As per request from Martin Strand which has provided a patch against 5.2.4
Filter out attributes with default value (from DTD) when parsing templates
--
Key: TAP5-171
URL: https://issues.apache.org/jira/browse/TAP5-171
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2, 5.0.18
Environment: Sun JDK 1.5
Reporter: Folke Behrens
Priority: Minor
Labels: tapestr5-review-for-closing
Fix For: 5.3
Attachments: TAP5-171 5.2.4.patch, Test.html,
attributes2-dtd-default.patch
Consider testing for org.xml.sax.ext.Attributes2 and use
Attributes2.isSpecified(int) to check if the attribute is really specified or
just a default declaration.
With this you can e.g. test if a shape=rect is really set. Test for
http://xml.org/sax/features/use-attributes2; or just use instanceof:
if (attributes instanceof Attributes2) {
if (( (Attributes2)attributes ).isSpecified(i)) {
// do something
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-423) Implement a file-system Asset type
[ https://issues.apache.org/jira/browse/TAP5-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084072#comment-13084072 ] Massimo Lusetti commented on TAP5-423: -- Patch are probably outdated but is this of some interest now ? Implement a file-system Asset type -- Key: TAP5-423 URL: https://issues.apache.org/jira/browse/TAP5-423 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-core Affects Versions: 5.0.18 Reporter: manuel aldana Labels: tapestr5-review-for-closing Attachments: filesystem_asset1.0_TAP423.patch, filesystem_asset1.1_TAP423_withIntegrationTest.patch, filesystem_asset1.2_TAP423.patch currenty it is built in to retrieve assets from classpath and from webcontext. a file system asset type which can retrieve stuff directly from the filesystem (e.g. from /srv/statics/) makes also sense. something like: *ResourceFileSystem extends AbstractResource* and *FileSystemAssetFactory extends AssetFactory* -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-440) Translation for Simplified Chinese
[ https://issues.apache.org/jira/browse/TAP5-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084075#comment-13084075 ] Massimo Lusetti commented on TAP5-440: -- Please verify the latest source (ex kaptcha) and provide an unified version Translation for Simplified Chinese -- Key: TAP5-440 URL: https://issues.apache.org/jira/browse/TAP5-440 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.0.18 Reporter: JinFen Chen Priority: Trivial Attachments: message_zh_CN.zip Component message translation for Simplified Chinese. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-440) Translation for Simplified Chinese
[ https://issues.apache.org/jira/browse/TAP5-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-440. Resolution: Duplicate I'll fix with the other patch since they're newer Translation for Simplified Chinese -- Key: TAP5-440 URL: https://issues.apache.org/jira/browse/TAP5-440 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.0.18 Reporter: JinFen Chen Priority: Trivial Labels: tapestr5-review-for-closing Attachments: message_zh_CN.zip Component message translation for Simplified Chinese. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-939) Chinese localization for ValidationMessages_zh_CN
[ https://issues.apache.org/jira/browse/TAP5-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-939. Resolution: Fixed Fix Version/s: 5.3 Patch applied Chinese localization for ValidationMessages_zh_CN - Key: TAP5-939 URL: https://issues.apache.org/jira/browse/TAP5-939 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.1.0.5 Reporter: mindhawk Priority: Trivial Fix For: 5.3 Attachments: ValidationMessages_zh_CN.properties Chinese localization for ValidationMessages_zh_CN -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-941) Chinese localization for corelib components
[ https://issues.apache.org/jira/browse/TAP5-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-941. Resolution: Fixed Fix Version/s: 5.3 Patch applied Chinese localization for corelib components --- Key: TAP5-941 URL: https://issues.apache.org/jira/browse/TAP5-941 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.1.0.5 Reporter: mindhawk Priority: Minor Fix For: 5.3 Attachments: Chinese_localization_for_corelib_components .rar Chinese localization for corelib components -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-450) Add rel=nofollow to t:grid sort links
[ https://issues.apache.org/jira/browse/TAP5-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-450: Assignee: Massimo Lusetti Add rel=nofollow to t:grid sort links --- Key: TAP5-450 URL: https://issues.apache.org/jira/browse/TAP5-450 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.0.18 Reporter: James A. Hillyerd Assignee: Massimo Lusetti Priority: Minor Google is indexing the different sorted versions of my grid components. ie: http://simobjects.net/manufacturer/view.grid.columns:sort/aircraftType?t:ac=5 This makes it look like I have a bunch of pages with identical content, which google doesn't like. It also makes the site more brittle, because in some places I have renamed the grid, so the link returns an error. (The above link is an example of that) It seems like adding rel=nofollow to the sort links would be a good idea. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-455) Allow discarding of persistent field changes for specific strategy only
[ https://issues.apache.org/jira/browse/TAP5-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084103#comment-13084103 ] Massimo Lusetti commented on TAP5-455: -- Kalle does this still applicable ? Allow discarding of persistent field changes for specific strategy only --- Key: TAP5-455 URL: https://issues.apache.org/jira/browse/TAP5-455 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.0.18 Reporter: Kalle Korhonen Priority: Minor Discarding persistent field changes for specific strategies only would be useful for conversational persistent strategies. Currently PersistentFieldManager always iterates over all strategies when discardChanges() is called. Adding discardChanges(String strategyName, String pageName) operation to PersistentFieldManager would be enough. See more discussion at http://n2.nabble.com/Discard-persistent-field-changes-for-one-strategy-only--td2179942.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1525) More javascript events for zones
[ https://issues.apache.org/jira/browse/TAP5-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-1525. - Resolution: Duplicate More javascript events for zones Key: TAP5-1525 URL: https://issues.apache.org/jira/browse/TAP5-1525 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.2.0 Reporter: Joe Klecko It seems that time and time again for each T5 project (6 out of 7 so far) I find I need to override tapesty.js methods to add additional support for zones. Currently there is only 1 event fired from a zone (Tapestry.ZONE_UPDATED_EVENT), I'd like to suggest/request there be at least 4 events total (3 new ones): 1) ZONE_BEFORE_AJAX_REQUEST_EVENT: This would be fired before the ajax request is sent to the server. Listeners should be able to cancel the ajax request (similiar to the way tapestry allows a form submission to be canceled). Access to the options object to be passed to Tapestry.ajaxRequest should be accessible(read/write) from the event's memo property (or where ever, just accessible). 2) ZONE_BEFORE_UPDATE_EVENT: This would be fired after the ajax request returns and just before the zone is updated via the processReply() method. Again, listeners should be able to cancel the update. Access to the options object passed to Tapestry.ajaxRequest should be accessible from the event's memo property (or where ever, just accessible). 3) ZONE_UPDATED_EVENT: already and is listed here for completeness. 4) ZONE_AJAX_REQUEST_ERROR_EVENT: This would be fired if the ajax request errored out for the zone. (includes error data) references to mailing list: http://tapestry.1045711.n5.nabble.com/More-javscript-zone-events-please-td4401005.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-423) Implement a file-system Asset type
[ https://issues.apache.org/jira/browse/TAP5-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-423. Resolution: Duplicate This is somehow a special case for TAP5-1515 so please if you feel go there and vote there if interested Implement a file-system Asset type -- Key: TAP5-423 URL: https://issues.apache.org/jira/browse/TAP5-423 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-core Affects Versions: 5.0.18 Reporter: manuel aldana Attachments: filesystem_asset1.0_TAP423.patch, filesystem_asset1.1_TAP423_withIntegrationTest.patch, filesystem_asset1.2_TAP423.patch currenty it is built in to retrieve assets from classpath and from webcontext. a file system asset type which can retrieve stuff directly from the filesystem (e.g. from /srv/statics/) makes also sense. something like: *ResourceFileSystem extends AbstractResource* and *FileSystemAssetFactory extends AssetFactory* -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-450) Add rel=nofollow to t:grid sort links
[ https://issues.apache.org/jira/browse/TAP5-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-450. -- Resolution: Fixed Fix Version/s: 5.3 Add rel=nofollow to t:grid sort links --- Key: TAP5-450 URL: https://issues.apache.org/jira/browse/TAP5-450 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.0.18 Reporter: James A. Hillyerd Assignee: Massimo Lusetti Priority: Minor Fix For: 5.3 Google is indexing the different sorted versions of my grid components. ie: http://simobjects.net/manufacturer/view.grid.columns:sort/aircraftType?t:ac=5 This makes it look like I have a bunch of pages with identical content, which google doesn't like. It also makes the site more brittle, because in some places I have renamed the grid, so the link returns an error. (The above link is an example of that) It seems like adding rel=nofollow to the sort links would be a good idea. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-450) Add rel=nofollow to t:grid sort links
[ https://issues.apache.org/jira/browse/TAP5-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-450. Add rel=nofollow to t:grid sort links --- Key: TAP5-450 URL: https://issues.apache.org/jira/browse/TAP5-450 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.0.18 Reporter: James A. Hillyerd Assignee: Massimo Lusetti Priority: Minor Fix For: 5.3 Google is indexing the different sorted versions of my grid components. ie: http://simobjects.net/manufacturer/view.grid.columns:sort/aircraftType?t:ac=5 This makes it look like I have a bunch of pages with identical content, which google doesn't like. It also makes the site more brittle, because in some places I have renamed the grid, so the link returns an error. (The above link is an example of that) It seems like adding rel=nofollow to the sort links would be a good idea. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-460) ApplicationStateObject as a Hibernate entity (storing only the primary key in the session)
[ https://issues.apache.org/jira/browse/TAP5-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-460. Resolution: Duplicate This is duplicated by TAP5-790 which is already in the trunk ApplicationStateObject as a Hibernate entity (storing only the primary key in the session) -- Key: TAP5-460 URL: https://issues.apache.org/jira/browse/TAP5-460 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-hibernate Affects Versions: 5.1.0.0 Reporter: Howard M. Lewis Ship It would be very nice if there was a way of marking an entity as a session-persistent state object. The object's primary key would be stored in the session, rather than the object itself. This could be a specific persistence strategy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-514) Make Validation Bubbles easily customizable
[ https://issues.apache.org/jira/browse/TAP5-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-514. Resolution: Won't Fix I dare to close as the comments in it talks enough and cause the js part is changed lot so please open a new one for 5.3 if that's the case Make Validation Bubbles easily customizable --- Key: TAP5-514 URL: https://issues.apache.org/jira/browse/TAP5-514 Project: Tapestry 5 Issue Type: New Feature Components: tapestry-core Affects Versions: 5.0.19 Reporter: Borislav Ivanov Labels: tapestr5-review-for-closing To have a control over various parameters for the validation bubbles. Fade time, image, should they appear when you fade in to the input field , etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-526) VerifyError when a subclass uses @PageActivationContext but extends from a super-class that also uses @PageActivationContext
[ https://issues.apache.org/jira/browse/TAP5-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-526. Resolution: Invalid I've tested this with 5.2.6 and is no more the case. If you need a test case in the test suite please let me know. VerifyError when a subclass uses @PageActivationContext but extends from a super-class that also uses @PageActivationContext Key: TAP5-526 URL: https://issues.apache.org/jira/browse/TAP5-526 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.1.0.0 Reporter: Howard M. Lewis Ship java.lang.VerifyError class com.formos.tapestry.svnadmin.pages.RejectProject overrides final method . * java.lang.ClassLoader.defineClass1(Native Method) * java.lang.ClassLoader.defineClass(ClassLoader.java:675) * java.lang.ClassLoader.defineClass(ClassLoader.java:520) * javassist.Loader.findClass(Loader.java:379) * org.apache.tapestry5.internal.services.ComponentInstantiatorSourceImpl$PackageAwareLoader.findClass(ComponentInstantiatorSourceImpl.java:94) * javassist.Loader.loadClass(Loader.java:311) * java.lang.ClassLoader.loadClass(ClassLoader.java:251) * org.apache.tapestry5.internal.services.ComponentInstantiatorSourceImpl.findClass(ComponentInstantiatorSourceImpl.java:296) * org.apache.tapestry5.internal.services.ComponentInstantiatorSourceImpl.getInstantiator(ComponentInstantiatorSourceImpl.java:276) * $ComponentInstantiatorSource_11f8bfd139e.getInstantiator($ComponentInstantiatorSource_11f8bfd139e.java) * org.apache.tapestry5.internal.pageload.PageLoaderImpl.createAssembler(PageLoaderImpl.java:205) * org.apache.tapestry5.internal.pageload.PageLoaderImpl.getAssembler(PageLoaderImpl.java:195) * org.apache.tapestry5.internal.pageload.PageLoaderImpl.loadPage(PageLoaderImpl.java:169) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-569) add convenience js method: Tapestry.activateZone( zoneId, url ), maybe Tapesry.activateZones( url )
[
https://issues.apache.org/jira/browse/TAP5-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084197#comment-13084197
]
Massimo Lusetti commented on TAP5-569:
--
Does this still desirable?
Maybe when the new latest features and work dedicated to js in tapestry is
settled this could gain attention...
add convenience js method: Tapestry.activateZone( zoneId, url ), maybe
Tapesry.activateZones( url )
---
Key: TAP5-569
URL: https://issues.apache.org/jira/browse/TAP5-569
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.1.0.1
Reporter: Fernando Padilla
People keep asking for an easy way to activate zones from their own
javascript.
I have created such a function for our project, but this easy/small
convenience method should be in Tapestry core proper..
Tapestry.activateZone( zoneId, url )
and now with the multi-zone support, I wonder if zoneId if even required. It
could be null, or another method could be created too:
Tapestry.activateZones( url )
Below is the js that I added to my project:
Tapestry.activateZone = function ( zoneId, url ) {
var zoneManager = Tapestry.findZoneManagerByZoneId( zoneId );
if ( zoneManager != null ) {
zoneManager.updateFromURL( url );
}
};
Tapestry.findZoneManagerByZoneId = function( zoneId ) {
var zoneElement = $(zoneId);
if (!zoneElement) {
Tapestry.ajaxError(Unable to locate Ajax Zone '#{id}' for
dynamic update., { id:zoneId});
return null;
}
var manager = $T(zoneElement).zoneManager;
if (!manager) {
Tapestry.ajaxError(Ajax Zone '#{id}' does not have an
associated Tapestry.ZoneManager object., { id :zoneId });
return null;
}
return manager;
};
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-585) Some method names are not allowed in components and pages
[
https://issues.apache.org/jira/browse/TAP5-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti closed TAP5-585.
Resolution: Invalid
There are some conventions certainly please reopen this with a test case
attached if that's the case as I don't see this issue bubble up frequently on
the mailing list
Some method names are not allowed in components and pages
-
Key: TAP5-585
URL: https://issues.apache.org/jira/browse/TAP5-585
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.18
Reporter: Felix Gonschorek
Some method names in components and pages make tapestry throw an Exception:
StackMapTable format error: bad class index. Howard assumes this is a
naming conflict to methods tapestry adds to components and pages on the fly.
This is an example method, that throws the exception:
@BeginRender
boolean render(MarkupWriter writer) {
//blubb
return false;
}
When i rename the method to boolean blubb(MarkupWriter writer) for example,
everything is fine.
In the stack trace one can not see which method it is, or in which
page/component the naming conflict occurs. It would save one some time to
find the corresponding component if the stack trace or the exception message
would give one a hint.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-588) It should be much easier to set an initial sort column of a grid
[
https://issues.apache.org/jira/browse/TAP5-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084204#comment-13084204
]
Massimo Lusetti commented on TAP5-588:
--
There is the sortModel parameter which can help here... isn't this sufficient?
It should be much easier to set an initial sort column of a grid
Key: TAP5-588
URL: https://issues.apache.org/jira/browse/TAP5-588
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.1.0.2
Reporter: Hugo Palma
Priority: Minor
Labels: tapestr5-review-for-closing
Right now if you want to set an initial sort column for a grid you have to
code something like:
if (grid.getSortModel().getSortConstraints().isEmpty()) {
grid.getSortModel().updateSort(column);
}
for every grid in the page.
It would be great if an initialSortColumn or defaultSortColumn parameter
was added to the grid component that would receive the name of the column to
which the grid would be ordered by default.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-592) An error occurs when parsing a template with a Block component as root component.
[ https://issues.apache.org/jira/browse/TAP5-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-592. Resolution: Won't Fix The workaround seems pretty easy An error occurs when parsing a template with a Block component as root component. - Key: TAP5-592 URL: https://issues.apache.org/jira/browse/TAP5-592 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.0.18 Reporter: Briac Pilpré Priority: Minor When trying to parse a component description containing a single Block declaration, Tapestry throws an exception: org.apache.tapestry5.ioc.internal.util.TapestryException Failure parsing template classpath:my/app/components/HelloBlock.tml: Element block does not support an attribute named ''. The only allowed attribute name is 'id'. ?xml version=1.0? t:block xmlns:t=http://tapestry.apache.org/schema/tapestry_5_0_0.xsd; t:id=helloBlock Hello. /t:block The TemplateParserImpl.findSingleParameter allows only a single attribute but the xmlns:t attribute is taken into account. I guess we could patch this correct by skipping xmlns attributes (like the xml:space attribute is skipped). Partial Stack trace * org.apache.tapestry5.internal.services.TemplateParserImpl.findSingleParameter(TemplateParserImpl.java:500) * org.apache.tapestry5.internal.services.TemplateParserImpl.startBlock(TemplateParserImpl.java:445) * org.apache.tapestry5.internal.services.TemplateParserImpl.startTapestryElement(TemplateParserImpl.java:396) * org.apache.tapestry5.internal.services.TemplateParserImpl.startElement(TemplateParserImpl.java:352) * org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-606) Add Finnish translation to javascript messages (Translated messages attached.)
[ https://issues.apache.org/jira/browse/TAP5-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-606. Resolution: Fixed Fix Version/s: 5.3 Patch applied Add Finnish translation to javascript messages (Translated messages attached.) -- Key: TAP5-606 URL: https://issues.apache.org/jira/browse/TAP5-606 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.1.0.2 Reporter: Ville Virtanen Priority: Trivial Fix For: 5.3 Attachments: tapestry-messages_fi_FI.js Translation messages in finnish. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-620) Add ProgressListener support to Upload component
[ https://issues.apache.org/jira/browse/TAP5-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti updated TAP5-620: - Assignee: Massimo Lusetti Affects Version/s: 5.2 5.3 Add ProgressListener support to Upload component Key: TAP5-620 URL: https://issues.apache.org/jira/browse/TAP5-620 Project: Tapestry 5 Issue Type: Wish Components: tapestry-upload Affects Versions: 5.3, 5.2, 5.1.0.2 Reporter: Paudi Moriarty Assignee: Massimo Lusetti Would be great if Tapestry supported the ProgressListener interface out of the box. As it is, I'm going to have to override the MultipartDecoder service and implement a custom Upload component. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-638) Support for uploading files using AJAX
[ https://issues.apache.org/jira/browse/TAP5-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084219#comment-13084219 ] Massimo Lusetti commented on TAP5-638: -- I'm very interested in this one so I guess the question is: What a derivate work in the Java world acutally is? Support for uploading files using AJAX -- Key: TAP5-638 URL: https://issues.apache.org/jira/browse/TAP5-638 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-upload Reporter: Hugo Palma If the upload component is included on a form that does a partial update(has the zone parameter set) the value property isn't updated with the UploadedFile instance. So it seems that this component upload doesn't support ajax. It would be great if it was possible to upload a file using AJAX. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-650) Enhance form autofocus to accept fieldname as a value
[
https://issues.apache.org/jira/browse/TAP5-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti reassigned TAP5-650:
Assignee: Massimo Lusetti
Enhance form autofocus to accept fieldname as a value
-
Key: TAP5-650
URL: https://issues.apache.org/jira/browse/TAP5-650
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.1.0.3
Reporter: Kalle Korhonen
Assignee: Massimo Lusetti
Priority: Minor
It's not difficult to set autofocus=false and add $('myField').activate();
yourself, but I think it would address many of the issues people are having
with autofocus if the parameter would also accept a field name instead of
simply a boolean value so you can set the focus to field you like.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-142) HTML Button component with Form support
[ https://issues.apache.org/jira/browse/TAP5-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti reassigned TAP5-142: Assignee: Massimo Lusetti HTML Button component with Form support --- Key: TAP5-142 URL: https://issues.apache.org/jira/browse/TAP5-142 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.0.15 Environment: Anyone Reporter: Massimo Lusetti Assignee: Massimo Lusetti Attachments: patch This patch supply the component for HTML 4 button element (button) with Form support when the button type is submit which is the default and act as the Submit component. Button elements are preferable over Submit in terms of flexibility and CSS-awarness. The code needs to be cleaned an i happily do that if there's enough interest in it. The patch contain unit and integration tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-142) HTML Button component with Form support
[ https://issues.apache.org/jira/browse/TAP5-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083138#comment-13083138 ] Massimo Lusetti commented on TAP5-142: -- This is old and I've come out with my own solution. I'll close it and if anyone wants it please reopen or open a new one. HTML Button component with Form support --- Key: TAP5-142 URL: https://issues.apache.org/jira/browse/TAP5-142 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.0.15 Environment: Anyone Reporter: Massimo Lusetti Assignee: Massimo Lusetti Fix For: 5.3 Attachments: patch This patch supply the component for HTML 4 button element (button) with Form support when the button type is submit which is the default and act as the Submit component. Button elements are preferable over Submit in terms of flexibility and CSS-awarness. The code needs to be cleaned an i happily do that if there's enough interest in it. The patch contain unit and integration tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-142) HTML Button component with Form support
[ https://issues.apache.org/jira/browse/TAP5-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-142. -- Resolution: Won't Fix Fix Version/s: 5.3 The Form and event associated has evolved enough to make this obsolete HTML Button component with Form support --- Key: TAP5-142 URL: https://issues.apache.org/jira/browse/TAP5-142 Project: Tapestry 5 Issue Type: New Feature Affects Versions: 5.0.15 Environment: Anyone Reporter: Massimo Lusetti Assignee: Massimo Lusetti Fix For: 5.3 Attachments: patch This patch supply the component for HTML 4 button element (button) with Form support when the button type is submit which is the default and act as the Submit component. Button elements are preferable over Submit in terms of flexibility and CSS-awarness. The code needs to be cleaned an i happily do that if there's enough interest in it. The patch contain unit and integration tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-2) DateField customization
[ https://issues.apache.org/jira/browse/TAP5-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-2. -- DateField customization --- Key: TAP5-2 URL: https://issues.apache.org/jira/browse/TAP5-2 Project: Tapestry 5 Issue Type: Improvement Affects Versions: 5.0.15 Reporter: Skow Priority: Minor Fix For: 5.3 I'm unable to find a way to customize the underlying DatePicker that DateField uses. At the very least, one should be able to change the starting day of the week and attach the 'onchange' event on the text field so something can happen when a date is picked from the popup calendar. The only workaround I've come up with is to pull the datefield.js out of the Tapestry jar and hard-code the starting day of the week. I'm still working to getting the onchange event of the text field to fire. Perhaps there is an easy way to do this without actually needing a fix - if so, perhaps all that is needed is a quick wiki howto. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-2) DateField customization
[ https://issues.apache.org/jira/browse/TAP5-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-2. Resolution: Won't Fix Fix Version/s: 5.3 Is somehow too old to be current so close it, if you're interested please reopen DateField customization --- Key: TAP5-2 URL: https://issues.apache.org/jira/browse/TAP5-2 Project: Tapestry 5 Issue Type: Improvement Affects Versions: 5.0.15 Reporter: Skow Priority: Minor Fix For: 5.3 I'm unable to find a way to customize the underlying DatePicker that DateField uses. At the very least, one should be able to change the starting day of the week and attach the 'onchange' event on the text field so something can happen when a date is picked from the popup calendar. The only workaround I've come up with is to pull the datefield.js out of the Tapestry jar and hard-code the starting day of the week. I'm still working to getting the onchange event of the text field to fire. Perhaps there is an easy way to do this without actually needing a fix - if so, perhaps all that is needed is a quick wiki howto. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-5) Context lost in a form fragment in a property editor component
[
https://issues.apache.org/jira/browse/TAP5-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti resolved TAP5-5.
Resolution: Won't Fix
Fix Version/s: 5.3
5.0.x isn't supported anymore if you feel please open a new on 5.3
Context lost in a form fragment in a property editor component
--
Key: TAP5-5
URL: https://issues.apache.org/jira/browse/TAP5-5
Project: Tapestry 5
Issue Type: Bug
Affects Versions: 5.0.15
Reporter: José Paumard
Fix For: 5.3
Attachments: tapestry-form-fragment.patch
I created a PropertyEditor to edit a special class, which content spans over
one or more pair of String.
The TML for the PropertyEditor declaration is :
t:block t:id=myProp
t:editor.myPropEditor t:id=myPropEditor
propertyvalue=prop:context.propertyValue
propertyname=prop:context.label
messages=prop:context.containerMessages/
/t:block
The TML of the property editor itself is :
t:label for=s11/ t:textfield t:id=s12/ br/
t:label for=s21/ : t:textfield t:id=s22 / br/
t:checkbox t:id=showFragment1 t:mixins=triggerfragment
fragment=fragment1/
t:formfragment t:id=fragment1 visible=showFragment1
t:label for=t11/ t:textfield t:id=t12/ br/
t:label for=t21/ : t:textfield t:id=t22 / br/
/t:formfragment
With a basic POJO class associated to that, and the declaration of the
parameters :
public class MyPropertyEditor {
@Parameter(name=propertyValue,required=true)
private MyProperty myProperty ;
@Parameter(name=propertyName,required=true)
private String propertyName ;
@Parameter(name=messages,required=true)
private Messages messages ;
private String s11, s12, s21, s22, t11, t12, t21, t22 ;
...
}
If I try to read / update the myPropery parameter in that class :
- from the s11, s12, s21, s22 getter or setter - everything works ok, I can
read or update this parameter
- from the t11, t12, t21 or t22 getter or setter, I get the following stack
trace :
An unexpected application exception has occurred.
* org.apache.tapestry5.runtime.ComponentEventException
Failure writing parameter 'value' of component
AppPropertyEditBlocks:mypropertyeditor.content2: Failure reading parameter
'propertyValue' of component AppPropertyEditBlocks:mypropertyeditor: No
object of type org.apache.tapestry5.services.PropertyEditContext is available
from the Environment. Available types are
org.apache.tapestry5.ValidationTracker,
org.apache.tapestry5.services.ComponentEventResultProcessor,
org.apache.tapestry5.services.FormSupport,
org.apache.tapestry5.services.Heartbeat.
context
eventType
action
location
classpath:org/.../webapp/components/item/AbstractCreate.tml, line
6, column 24
1 t:container
xmlns:t=http://tapestry.apache.org/schema/tapestry_5_0_0.xsd;
2
3 ${message:title}
4 br/
5
6 t:form t:id=create
7 t:errors/
8 t:beaneditor t:id=createEditor object=item
exclude=prop:excludelist/
9 t:submit value=message:create/
10 /t:form
11
* org.apache.tapestry5.ioc.internal.util.TapestryException
Failure writing parameter 'value' of component
AppPropertyEditBlocks:mypropertyeditor.content2: Failure reading parameter
'propertyValue' of component AppPropertyEditBlocks:mypropertyeditor: No
object of type org.apache.tapestry5.services.PropertyEditContext is available
from the Environment. Available types are
org.apache.tapestry5.ValidationTracker,
org.apache.tapestry5.services.ComponentEventResultProcessor,
org.apache.tapestry5.services.FormSupport,
org.apache.tapestry5.services.Heartbeat.
location
classpath:org/.../webapp/components/editor/MyPropertyEditor.tml,
line 21, column 62
16 t:checkbox t:id=showFragment1 t:mixins=triggerfragment
fragment=fragment1/
17 t:label for=showFragment1/
18
19 t:formfragment t:id=fragment1 visible=showFragment1
20 t:label for=t11/ : t:textfield t:id=t12/
21 t:label for=t21/ : t:textfield t:id=t33 /
22 /t:formfragment
23
24
25 /td/tr
26 /table
* org.apache.tapestry5.ioc.internal.util.TapestryException
Failure reading parameter 'propertyValue' of component
AppPropertyEditBlocks:mypropertyeditor: No object of type
org.apache.tapestry5.services.PropertyEditContext is available from the
Environment. Available types are
[jira] [Closed] (TAP5-5) Context lost in a form fragment in a property editor component
[
https://issues.apache.org/jira/browse/TAP5-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti closed TAP5-5.
--
Context lost in a form fragment in a property editor component
--
Key: TAP5-5
URL: https://issues.apache.org/jira/browse/TAP5-5
Project: Tapestry 5
Issue Type: Bug
Affects Versions: 5.0.15
Reporter: José Paumard
Fix For: 5.3
Attachments: tapestry-form-fragment.patch
I created a PropertyEditor to edit a special class, which content spans over
one or more pair of String.
The TML for the PropertyEditor declaration is :
t:block t:id=myProp
t:editor.myPropEditor t:id=myPropEditor
propertyvalue=prop:context.propertyValue
propertyname=prop:context.label
messages=prop:context.containerMessages/
/t:block
The TML of the property editor itself is :
t:label for=s11/ t:textfield t:id=s12/ br/
t:label for=s21/ : t:textfield t:id=s22 / br/
t:checkbox t:id=showFragment1 t:mixins=triggerfragment
fragment=fragment1/
t:formfragment t:id=fragment1 visible=showFragment1
t:label for=t11/ t:textfield t:id=t12/ br/
t:label for=t21/ : t:textfield t:id=t22 / br/
/t:formfragment
With a basic POJO class associated to that, and the declaration of the
parameters :
public class MyPropertyEditor {
@Parameter(name=propertyValue,required=true)
private MyProperty myProperty ;
@Parameter(name=propertyName,required=true)
private String propertyName ;
@Parameter(name=messages,required=true)
private Messages messages ;
private String s11, s12, s21, s22, t11, t12, t21, t22 ;
...
}
If I try to read / update the myPropery parameter in that class :
- from the s11, s12, s21, s22 getter or setter - everything works ok, I can
read or update this parameter
- from the t11, t12, t21 or t22 getter or setter, I get the following stack
trace :
An unexpected application exception has occurred.
* org.apache.tapestry5.runtime.ComponentEventException
Failure writing parameter 'value' of component
AppPropertyEditBlocks:mypropertyeditor.content2: Failure reading parameter
'propertyValue' of component AppPropertyEditBlocks:mypropertyeditor: No
object of type org.apache.tapestry5.services.PropertyEditContext is available
from the Environment. Available types are
org.apache.tapestry5.ValidationTracker,
org.apache.tapestry5.services.ComponentEventResultProcessor,
org.apache.tapestry5.services.FormSupport,
org.apache.tapestry5.services.Heartbeat.
context
eventType
action
location
classpath:org/.../webapp/components/item/AbstractCreate.tml, line
6, column 24
1 t:container
xmlns:t=http://tapestry.apache.org/schema/tapestry_5_0_0.xsd;
2
3 ${message:title}
4 br/
5
6 t:form t:id=create
7 t:errors/
8 t:beaneditor t:id=createEditor object=item
exclude=prop:excludelist/
9 t:submit value=message:create/
10 /t:form
11
* org.apache.tapestry5.ioc.internal.util.TapestryException
Failure writing parameter 'value' of component
AppPropertyEditBlocks:mypropertyeditor.content2: Failure reading parameter
'propertyValue' of component AppPropertyEditBlocks:mypropertyeditor: No
object of type org.apache.tapestry5.services.PropertyEditContext is available
from the Environment. Available types are
org.apache.tapestry5.ValidationTracker,
org.apache.tapestry5.services.ComponentEventResultProcessor,
org.apache.tapestry5.services.FormSupport,
org.apache.tapestry5.services.Heartbeat.
location
classpath:org/.../webapp/components/editor/MyPropertyEditor.tml,
line 21, column 62
16 t:checkbox t:id=showFragment1 t:mixins=triggerfragment
fragment=fragment1/
17 t:label for=showFragment1/
18
19 t:formfragment t:id=fragment1 visible=showFragment1
20 t:label for=t11/ : t:textfield t:id=t12/
21 t:label for=t21/ : t:textfield t:id=t33 /
22 /t:formfragment
23
24
25 /td/tr
26 /table
* org.apache.tapestry5.ioc.internal.util.TapestryException
Failure reading parameter 'propertyValue' of component
AppPropertyEditBlocks:mypropertyeditor: No object of type
org.apache.tapestry5.services.PropertyEditContext is available from the
Environment. Available types are org.apache.tapestry5.ValidationTracker,
org.apache.tapestry5.services.ComponentEventResultProcessor,
org.apache.tapestry5.services.FormSupport,
[jira] [Resolved] (TAP5-7) Palette component error marker appears on the line below the component when validation fails.
[
https://issues.apache.org/jira/browse/TAP5-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti resolved TAP5-7.
Resolution: Won't Fix
Fix Version/s: 5.3
Please open a new one for 5.3 if this still applicable
Palette component error marker appears on the line below the component when
validation fails.
-
Key: TAP5-7
URL: https://issues.apache.org/jira/browse/TAP5-7
Project: Tapestry 5
Issue Type: Bug
Affects Versions: 5.0.15
Environment: Windows XP, IE 7.0.5730.13, FireFox 2.0.0.14, Tapestry
5.0.11, Eclipse 3.3.2 Maven 2.0.9, Run-Jetty-Run
Reporter: Daniel
Priority: Minor
Fix For: 5.3
I have overridden the following CSS classes to make the palette fields
smaller:
div.t-palette-available SELECT {
width: 100px;
float: left;
}
div.t-palette-selected SELECT {
width: 100px;
float: left;
clear: right;
}
The HTML for the palette displaying the error X icon on the next line looks
like:
div class=t-beaneditor-row
label class=t-error for=keywords
id=keywords:labelKeywords/label
input id=keywords:values name=keywords:values type=hidden
value=[]
div class=t-palette
div class=t-palette-available
div class=t-palette-titleAvailable/div
select id=keywords:avail multiple=multiple
name=keywords:avail size=7
option value=31word4
/select
/div
div class=t-palette-controls
button disabled=disabled id=keywords:select
img alt=Select gt;
src=assets/tapestry/corelib/components/select.png
/button
button disabled=disabled id=keywords:deselect
img alt=lt; Deselect
src=assets/tapestry/corelib/components/deselect.png
/button
/div
div class=t-palette-selected
div class=t-palette-titleSelected/div
select id=keywords multiple=multiple
name=keywords size=7select/
/div
div class=t-palette-spacer/div
/div
img alt=[Error] class=t-error-icon id=keywords:icon
src=assets/tapestry/field-error-marker.gif
/div
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-7) Palette component error marker appears on the line below the component when validation fails.
[
https://issues.apache.org/jira/browse/TAP5-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti closed TAP5-7.
--
Palette component error marker appears on the line below the component when
validation fails.
-
Key: TAP5-7
URL: https://issues.apache.org/jira/browse/TAP5-7
Project: Tapestry 5
Issue Type: Bug
Affects Versions: 5.0.15
Environment: Windows XP, IE 7.0.5730.13, FireFox 2.0.0.14, Tapestry
5.0.11, Eclipse 3.3.2 Maven 2.0.9, Run-Jetty-Run
Reporter: Daniel
Priority: Minor
Fix For: 5.3
I have overridden the following CSS classes to make the palette fields
smaller:
div.t-palette-available SELECT {
width: 100px;
float: left;
}
div.t-palette-selected SELECT {
width: 100px;
float: left;
clear: right;
}
The HTML for the palette displaying the error X icon on the next line looks
like:
div class=t-beaneditor-row
label class=t-error for=keywords
id=keywords:labelKeywords/label
input id=keywords:values name=keywords:values type=hidden
value=[]
div class=t-palette
div class=t-palette-available
div class=t-palette-titleAvailable/div
select id=keywords:avail multiple=multiple
name=keywords:avail size=7
option value=31word4
/select
/div
div class=t-palette-controls
button disabled=disabled id=keywords:select
img alt=Select gt;
src=assets/tapestry/corelib/components/select.png
/button
button disabled=disabled id=keywords:deselect
img alt=lt; Deselect
src=assets/tapestry/corelib/components/deselect.png
/button
/div
div class=t-palette-selected
div class=t-palette-titleSelected/div
select id=keywords multiple=multiple
name=keywords size=7select/
/div
div class=t-palette-spacer/div
/div
img alt=[Error] class=t-error-icon id=keywords:icon
src=assets/tapestry/field-error-marker.gif
/div
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-9) Component event requests that fail should still send a redirect (to the exception report page)
[ https://issues.apache.org/jira/browse/TAP5-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-9. Resolution: Won't Fix Fix Version/s: 5.3 Please open a new one for 5.3 if this still applicable Component event requests that fail should still send a redirect (to the exception report page) -- Key: TAP5-9 URL: https://issues.apache.org/jira/browse/TAP5-9 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Reporter: Howard M. Lewis Ship Fix For: 5.3 When a request, such as a form submission, fails with an exception, we currently render the exception report page within the same request. We should capture the necessary information (as client persistent properties, once implemented as TAPESTRY-1356), including request headers and session state *within the request which threw the exception*, then send a normal client-redirect to the exception page to present the data. If nothing else, this will be needed by the time we implement portlets, since you can't fudge the difference between action and render requests inside a portlet container. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-8) Application message catalog is only used when a not localized version is present
[ https://issues.apache.org/jira/browse/TAP5-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-8. Resolution: Won't Fix Fix Version/s: 5.3 Please open a new one for 5.3 if this still applicable Application message catalog is only used when a not localized version is present Key: TAP5-8 URL: https://issues.apache.org/jira/browse/TAP5-8 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Reporter: Hugo Palma Priority: Minor Fix For: 5.3 If i provide a MyApp_en.properties in the WEB-INF dir of my application the bundle is ignored. But if i add an empty MyApp.properties file the bundle is not longer ignored and works just fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-8) Application message catalog is only used when a not localized version is present
[ https://issues.apache.org/jira/browse/TAP5-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-8. -- Application message catalog is only used when a not localized version is present Key: TAP5-8 URL: https://issues.apache.org/jira/browse/TAP5-8 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Reporter: Hugo Palma Priority: Minor Fix For: 5.3 If i provide a MyApp_en.properties in the WEB-INF dir of my application the bundle is ignored. But if i add an empty MyApp.properties file the bundle is not longer ignored and works just fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-9) Component event requests that fail should still send a redirect (to the exception report page)
[ https://issues.apache.org/jira/browse/TAP5-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-9. -- Component event requests that fail should still send a redirect (to the exception report page) -- Key: TAP5-9 URL: https://issues.apache.org/jira/browse/TAP5-9 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Reporter: Howard M. Lewis Ship Fix For: 5.3 When a request, such as a form submission, fails with an exception, we currently render the exception report page within the same request. We should capture the necessary information (as client persistent properties, once implemented as TAPESTRY-1356), including request headers and session state *within the request which threw the exception*, then send a normal client-redirect to the exception page to present the data. If nothing else, this will be needed by the time we implement portlets, since you can't fudge the difference between action and render requests inside a portlet container. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-16) Error popups are not positioned well near the edges of the page
[ https://issues.apache.org/jira/browse/TAP5-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-16. --- Error popups are not positioned well near the edges of the page --- Key: TAP5-16 URL: https://issues.apache.org/jira/browse/TAP5-16 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Reporter: Howard M. Lewis Ship Fix For: 5.3 Attachments: screenshot-1.jpg When the error popup is too close to the edge of the page, the message inside gets truncated. I think the error popup should recognize when this happens and instead position itself differently, so that the message is not truncated, and the right edge of the bubble aligns with the right edge of the field. In addition, a different image should be used, one that doesn't include the nib (the triangular part that points at the field) ... or the nib should be moved to the opposite right side of the image. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-17) Null value in RadioGroup returns the string on
[ https://issues.apache.org/jira/browse/TAP5-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-17. - Resolution: Won't Fix Fix Version/s: 5.3 Please open a new one for 5.3 if this still applicable Null value in RadioGroup returns the string on Key: TAP5-17 URL: https://issues.apache.org/jira/browse/TAP5-17 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Environment: Linux 2.6.24 Sun JDK 6 Reporter: Dave Dombrosky Priority: Minor Fix For: 5.3 When using a null value on a radio button, or a value the gets ValueEncoded to null, the value gets submitted to the server as on. The value should come back null, or at least as an empty String. I have no idea how on is getting submitted instead of the correct value. To test: 1) Create radio group with a few radio components in it. 2) Make one of these radio buttons have value=null. 3) Submit form and watch as you get the String on returned instead of null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-17) Null value in RadioGroup returns the string on
[ https://issues.apache.org/jira/browse/TAP5-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti closed TAP5-17. --- Null value in RadioGroup returns the string on Key: TAP5-17 URL: https://issues.apache.org/jira/browse/TAP5-17 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Environment: Linux 2.6.24 Sun JDK 6 Reporter: Dave Dombrosky Priority: Minor Fix For: 5.3 When using a null value on a radio button, or a value the gets ValueEncoded to null, the value gets submitted to the server as on. The value should come back null, or at least as an empty String. I have no idea how on is getting submitted instead of the correct value. To test: 1) Create radio group with a few radio components in it. 2) Make one of these radio buttons have value=null. 3) Submit form and watch as you get the String on returned instead of null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-16) Error popups are not positioned well near the edges of the page
[ https://issues.apache.org/jira/browse/TAP5-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-16. - Resolution: Won't Fix Fix Version/s: 5.3 A lot has changed here so please reopen if needed Error popups are not positioned well near the edges of the page --- Key: TAP5-16 URL: https://issues.apache.org/jira/browse/TAP5-16 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Reporter: Howard M. Lewis Ship Fix For: 5.3 Attachments: screenshot-1.jpg When the error popup is too close to the edge of the page, the message inside gets truncated. I think the error popup should recognize when this happens and instead position itself differently, so that the message is not truncated, and the right edge of the bubble aligns with the right edge of the field. In addition, a different image should be used, one that doesn't include the nib (the triangular part that points at the field) ... or the nib should be moved to the opposite right side of the image. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TAP5-21) Misleading error message when a component sub-class invokes non-default constructor of parent component class
[ https://issues.apache.org/jira/browse/TAP5-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-21. - Resolution: Won't Fix Fix Version/s: 5.3 Please open a new one for 5.3 if this still applicable Misleading error message when a component sub-class invokes non-default constructor of parent component class - Key: TAP5-21 URL: https://issues.apache.org/jira/browse/TAP5-21 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Environment: Linux, Sun JDK 1.6 Reporter: Jens Pfau Priority: Minor Fix For: 5.3 Some of my pages inherit from a common abstract base class but even if I move this to root package.base, I receive the following application exception: Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: caught an exception while obtaining a class file for root package.pages.MyPage at org.apache.tapestry.internal.services.ComponentInstantiatorSourceImpl.findClass(ComponentInstantiatorSourceImpl.java:241) at org.apache.tapestry.internal.services.ComponentInstantiatorSourceImpl.findInstantiator(ComponentInstantiatorSourceImpl.java:223) at $ComponentInstantiatorSource_118ac384906.findInstantiator($ComponentInstantiatorSource_118ac384906.java) at org.apache.tapestry.internal.services.PageElementFactoryImpl.newRootComponentElement(PageElementFactoryImpl.java:257) at $PageElementFactory_118ac384934.newRootComponentElement($PageElementFactory_118ac384934.java) at org.apache.tapestry.internal.services.PageLoaderProcessor.loadRootComponent(PageLoaderProcessor.java:413) at org.apache.tapestry.internal.services.PageLoaderProcessor.loadPage(PageLoaderProcessor.java:391) at org.apache.tapestry.internal.services.PageLoaderImpl.loadPage(PageLoaderImpl.java:60) at $PageLoader_118ac384932.loadPage($PageLoader_118ac384932.java) at org.apache.tapestry.internal.services.PagePoolCache.checkout(PagePoolCache.java:188) at org.apache.tapestry.internal.services.PagePoolImpl.checkout(PagePoolImpl.java:107) at $PagePool_118ac384931.checkout($PagePool_118ac384931.java) at org.apache.tapestry.internal.services.RequestPageCacheImpl.get(RequestPageCacheImpl.java:43) at $RequestPageCache_118ac384930.get($RequestPageCache_118ac384930.java) at $RequestPageCache_118ac384903.get($RequestPageCache_118ac384903.java) at org.apache.tapestry.internal.services.LinkFactoryImpl.createPageLink(LinkFactoryImpl.java:239) at $LinkFactory_118ac384935.createPageLink($LinkFactory_118ac384935.java) at org.apache.tapestry.internal.structure.PageImpl.createPageLink(PageImpl.java:161) at org.apache.tapestry.internal.structure.InternalComponentResourcesImpl.createPageLink(InternalComponentResourcesImpl.java:128) at org.apache.tapestry.corelib.components.PageLink.beginRender(PageLink.java:73) at org.apache.tapestry.corelib.components.PageLink.beginRender(PageLink.java) at org.apache.tapestry.internal.structure.ComponentPageElementImpl$11$1.run(ComponentPageElementImpl.java:338) at org.apache.tapestry.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:874) ... 62 more Caused by: java.lang.ClassNotFoundException: caught an exception while obtaining a class file for root package.pages.MyPage at javassist.Loader.findClass(Loader.java:359) at org.apache.tapestry.internal.services.ComponentInstantiatorSourceImpl$PackageAwareLoader.findClass(ComponentInstantiatorSourceImpl.java:73) at javassist.Loader.loadClass(Loader.java:311) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.apache.tapestry.internal.services.ComponentInstantiatorSourceImpl.findClass(ComponentInstantiatorSourceImpl.java:237) ... 84 more Caused by: java.lang.RuntimeException: Base class root package.base.AbstractPage (super class of root package.pages.MyPage) is not in a controlled package and is therefore not valid. You should try moving the class to package root package.base. at org.apache.tapestry.internal.services.ComponentClassTransformerImpl.transformComponentClass(ComponentClassTransformerImpl.java:126) at $ComponentClassTransformer_118ac384913.transformComponentClass($ComponentClassTransformer_118ac384913.java) at org.apache.tapestry.internal.services.ComponentInstantiatorSourceImpl.onLoad(ComponentInstantiatorSourceImpl.java:162) at javassist.Loader.findClass(Loader.java:340) ... 88 more -- This message is automatically generated by JIRA. For more information on JIRA, see:
[jira] [Resolved] (TAP5-26) When @Validate(required) is applied to a field whose type is primitive, the client-side JavaScript includes two invocations of Tapestry.Validator.required
[ https://issues.apache.org/jira/browse/TAP5-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimo Lusetti resolved TAP5-26. - Resolution: Won't Fix Fix Version/s: 5.3 Please open a new one for 5.3 if this still applicable When @Validate(required) is applied to a field whose type is primitive, the client-side JavaScript includes two invocations of Tapestry.Validator.required Key: TAP5-26 URL: https://issues.apache.org/jira/browse/TAP5-26 Project: Tapestry 5 Issue Type: Bug Affects Versions: 5.0.15 Reporter: Howard M. Lewis Ship Priority: Minor Fix For: 5.3 Tapestry should recognize that the required validator was already indicated via @Validate and not re-add it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
