You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org> on 2006/09/28 09:19:53 UTC
[jira] Created: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
----------------------------------------------------------------------------
Key: TAPESTRY-1099
URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
Project: Tapestry
Issue Type: Bug
Components: JavaScript
Affects Versions: 4.1
Environment: Internet Explorer 6
Reporter: Greg Woolsey
The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438601 ]
Jesse Kuhnert commented on TAPESTRY-1099:
-----------------------------------------
Yeah sorry about that.
I didn't release the "early release" of dojo into the snapshots yet because I had an outstanding issue with date validation.
Tom has definitely fixed the IE security warning issue so you should be all set in a day or two when I do another update - and hopefully this time a new snapshot.
BTW, to use your own dojo version you need to override the "ajaxDelegate" attribute of Shell...It's just a bean that happens to have a IRender interface on it is all.
Even though the @Shell allows overriding the default bundled version - it's certainly not guaranteed that the rest of system will work with that version.
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438568 ]
Greg Woolsey commented on TAPESTRY-1099:
----------------------------------------
Yes, I'm using 4.1.1 lastest snapshot (20060827.214823-24). It still includes an old dev build of DoJo, pre-0.3.x.
At this point I'm fine with requiring friendly URLs for assets to make it work with DoJo 0.3.1. My Tapestry issue is resolved with that configuration change. HTTPS still has problems with IE and background IFRAME objects due to a DoJo bug:
http://trac.dojotoolkit.org/ticket/548
The end result (long, long thread) setting the IFRAME src="javascript:false" is the correct solution, and works for me to avoid HTTPS mixed content warnings in IE6.
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438552 ]
Greg Woolsey commented on TAPESTRY-1099:
----------------------------------------
Found it. DoJo 0.3.1 has a different implementation for
dojo.uri.Uri()
which tries to ensure that URI components passed in end in forward slashes ("/") except for the last one. However, Tapestry 4.1 is outputting an Asset URL for the dojoPath with the slashes URL encoded. DoJo sees the base path doesn't end in "/", but in "%2F" instead, it's hex equivalent. It then walks back up the URI until it finds an unescaped "/" and just uses that portion.
The older DEV version of DoJo doesn't do that.
Since DoJo resides on the class path instead of web root for our project, the templates are not found. This error is not logged propery by Tapestry form validation, by the way. dojo.log.exception() doesn't report anything even when the DoJo log level is set to DEBUG.
So, next question - fiddle with Tapestry's Asset URI encoding or DoJo's baseURI processing?
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438602 ]
Jesse Kuhnert commented on TAPESTRY-1099:
-----------------------------------------
Oops...Almost forgot to answer the question about asset paths..
This is a "known issue" within dojo. I have my own version of dojo.uri.Uri that I include with Tapestry that correctly handles the path issues you saw.
I didn't have enough time to make the changes required for this fix in dojo directly for the 0.4 release (we're on feature freeze now) , but it'll definitely be in 0.5..
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
> Assigned To: Jesse Kuhnert
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Resolved: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=all ]
Jesse Kuhnert resolved TAPESTRY-1099.
-------------------------------------
Fix Version/s: 4.1.1
Resolution: Fixed
Awesome, I'm glad someone is liking the new way of things. There are probably still a few rough edges but I'm sure it'll get worked out soon enough.
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.1
>
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438634 ]
Greg Woolsey commented on TAPESTRY-1099:
----------------------------------------
I don't see anything in AjaxShellDelegate that would need modification for me - am I missing something? Unless I radically change (or use a snapshot of a major update to) the dojo API I don't think I need a new delegate. I just need to watch for behavioral changes like the base URL handling one.
As for the asset URL notation, that shouldn't be a big deal to people as long as it is noted somewhere prominent. I like the deprecation warnings the new Tapestry code generates to help me see what I need to update to migrate to 4.1.
I wouldn't have embarked on a 4.1.1 migration if I didn't think I could hack it as needed. Overall, I think it's well-crafted and a welcome replacement for the (closure leaking) JavaScript in T4.
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
> Assigned To: Jesse Kuhnert
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438555 ]
Greg Woolsey commented on TAPESTRY-1099:
----------------------------------------
Workaround for the URL problem: turn on friendly URLs for the Asset service:
http://tapestry.apache.org/tapestry4.1/UsersGuide/friendly-urls.html
This makes the base path look like a plain URL path with no parameters.
However, I'm still gettting mixed-content warnings from IE. I'll try a servlet filter to see what's coming through as HTTP instead of HTTPS.
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=all ]
Jesse Kuhnert reassigned TAPESTRY-1099:
---------------------------------------
Assignee: Jesse Kuhnert
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
> Assigned To: Jesse Kuhnert
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
Posted by "Andreas Andreou (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438560 ]
Andreas Andreou commented on TAPESTRY-1099:
-------------------------------------------
I think Jesse updated dojo a week ago to something-resembling a pre-0.4 version - don't know if that resolves things.
BTW, aren't you using 4.1.1-SNAPSHOT ? The maven repo is at http://people.apache.org/repo/m2-snapshot-repository
> Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-1099
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1099
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1
> Environment: Internet Explorer 6
> Reporter: Greg Woolsey
>
> The development version of DoJo included with the current packaged 4.1 release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE shows a mixed-content warning loading DoJo from a page accessed via HTTPS.
> DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate it.
> However, when I tried pointing my @Shell component to a DoJo source directory containing the dojo-0.3.1-widget package (and modifying the dojo.js to require packages not packaged in the T4.1 dojo.js), I get no widget prompt with validation errors on form submit. Form submit fails, and the dojo and tapestry JS objects appear to be defined and complete, but I get no feedback.
> When I leave the Shell component to it's default parameters, I get the IE warning, but if I OK the operation, then I see the validation errors prompt.
> If the packaged T4.1 build contains an updated DoJo, that should work with HTTPS, but I'm still trying to figure out what's up with my configuration to use a custom DoJo source and path with @Shell.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org