t; exist).
>>
>>
>> Error: Unable to locate asset
>> 'classpath:ctx/91328db67ddf7725/yaml/core/base.css' (the file does not
>> exist).
>>
>>
>>
>> or for images, it's a straight 404 w/o any further response.
>>
>> 3.
06:23, schrieb Alex Kotchnev:
> > >> > > >
> > >> > > > I spent some more time looking at this and I ended up removing
> > the
> > >> > usage
> > >> > > >> of
> > >> > > >> the ${asset:context:css/foobar
gt; >> (w/o
> >> > > using
> >> > > >> the asset:context binding prefixes), I continued having the same
> >> > > >> intermittent access issues for assets that are served from a
> >> > component.
> >> > > >&g
good as serving from a
>> CDN,
>> > > >> I'll
>> > > >> probably just stick to static files.
>> > > >>
>> > > >> Anyway, I thought this might be useful to someone el
However, this results in a very unreliable
> > > >>> rendering
> > > >>> of the pages - at times (if the app happens to be "warm"), the
> pages
> > > >>> render
> > > >>> just fine; at other times, I have to r
foo.css or
> something
> > >>> similar), instead of just using the "naked" (e.g. /css/foo.css w/o a
> > >>> context: prefix) path to the css in the layout; as a result, all of
> the
> > >>> "other" css (using yaml for layout) and the images r
t; http://zadachite-dev.appspot.com/assets/ctx/91328db67ddf7725/images/layout_v2/footer.jpg
> >>> )
> >>> instead of just being loaded as static files. I was thinking that
> >>> switching
> >>> the reference to the main stylesheet to not be a context: ref
unlikely to be warm right now)
>>>
>>> 2. Upon the initial loading of the pages, some of the graphics (more or
>>> less
>>> randomly) or stylesheets don't return as they get 404s:
>>>
>>>
>>>
>>> 404 Unable to locate asse
les aren't handled by the Asset Dispatcher anymore,
> instead the request handler for static files does the work
>
> >
> > Original-Nachricht
> > Datum: Tue, 13 Apr 2010 00:23:57 -0400
> > Von: Alex Kotchnev
> > An: Tapestry users
>
t 404 w/o any further response.
3. Browse to some of the other pages of the site - one by one, the
"missing"
assets start showing up one by one and eventually the layout renders
correctly. After the app is "warmed up" now, even if you refresh the page
including the initially c
2010 00:23:57 -0400
> Von: Alex Kotchnev
> An: Tapestry users
> Betreff: Re: Asset service issues in GAE
>
> I spent some more time looking at this and I ended up
> removing the usage of
> the ${asset:context:css/foobar.css} from the main templates. After doing
Unable to locate asset
> 'classpath:ctx/91328db67ddf7725/yaml/core/base.css' (the file does not
> exist).
>
>
>
> or for images, it's a straight 404 w/o any further response.
>
> 3. Browse to some of the other pages of the site - one by one, the
> "missin
ng up one by one and eventually the layout renders
correctly. After the app is "warmed up" now, even if you refresh the page
including the initially cached assets, they load fine.
--
View this message in context:
http://old.nabble.com/Asset-s
13 matches
Mail list logo