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 22:59:50 UTC
[jira] Commented: (TAPESTRY-1099) Current snapshot of 4.1 has HTTPS
DoJo problem, having trouble updating DoJo
[ 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