Stefan-

We actually had two issues. The first issue is that we had overridden
the EngineServiceLink (to include a check for https port 443) in a prior
release. Our version did not have the _stateful parameter. Once this
parameter was added I was able to remove our AjaxShellDelegate override
and the session appended to the path issue disappeared. 

The second issue (Could not load...) is that for some reason the context
tapestry/dojo paths just didn't work for us and neither did classpath. I
ended up moving our /dojo and /tapestry into /assets/static/ and used
tapestry's defaults for the paths.  

Below was what I removed from our Border. Changing it to classpath still
seemed to require our files to be in /assets/static so I just ended up
using the tapestry defaults.

        @Asset("context:/tapestry/")
        public abstract IAsset getTapestryPath();
        
        @Asset("context:/tapestry/core.js")
        public abstract IAsset getTapestrySource();
        
        @Asset("context:/dojo/dojo.js")
        public abstract IAsset getDojoSource();
        
        @Asset("context:/dojo/")
        public abstract IAsset getDojoPath();
        
        @Component(type = "Shell", bindings =
        { 
                .
                .
                .       
                "tapestryPath = asset:tapestryPath",
                "tapestrySource = asset:tapestrySource",
                "dojoSource = asset:dojoSource",
                "dojoPath = asset:dojoPath"             
        })
        public abstract IComponent getShell();  

These errors are gone now, but we still have an issue with our calendar
css paths appending the css file in front of images. Are you seeing this
as well? Hope the above helps.

Anna



-----Original Message-----
From: Stefan Esterer [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 04, 2007 3:08 AM
To: users@tapestry.apache.org
Subject: Re: Tapestry 4.1.1: incorrect dojoPath, tapestryPath - session
id is appended


I'm having the same problems with the snapshots..

Did you find the problem?

thx
stefan


Anna Vo wrote:
> 
> A little while ago I had posted this error, which occurs the first
time
> our site is loaded:
> 
> Could not load 'dojo.logging.Logger'; last tried '__package__.js'
> dojo.js;jsessioni... (line 14)
> Could not load 'tapestry.namespace'; last tried '/__package__.js'
> dojo.js;jsessioni... (line 14)
> [Exception... "'Error: Could not load 'tapestry.form'; last tried
> '/__package__.js'' when calling method:
> [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001c
> (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "<unknown>" data: no]
> 
> 
> Upon further investigation we found that these errors occurred because
> the paths were generated with the session appended to our path like
so:
> 
> <script type="text/javascript">
> dojo.registerModulePath("tapestry",
> "/assets/d431c0b6798a8384233a1c5202c55e26/tapestry");
> </script>
> 
> /assets/static/tapestry/;jsessionid=3ju0baj5pbt8g/namespace.js
> 
> 
> We traced it to the EngineServiceLink and this bit of code:
> 
> // TODO: This is somewhat questionable right now, was added in to
> support TAPESTRY-802
>         if (_cycle != null)
>             result = _cycle.encodeURL(result);        
>         return result;
> 
> 
> We searched around for a bit and found this link which seems very
> similar to our issue:
http://issues.apache.org/jira/browse/TAPESTRY-950
> 
> It looks like this issue was fixed. Just wondering if there is
something
> we are missing? We are using Tapestry 4.1.1. We worked around it by
> overriding the AjaxShellDelegate and specifying the dojoPath and
> tapestryPath. 
> 
> 
> Anna
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context:
http://www.nabble.com/Tapestry-4.1.1%3A-incorrect-dojoPath%2C-tapestryPa
th---session-id-is-appended-tf2914703.html#a8156015
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to