You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Anna Vo <AV...@widen.com> on 2006/12/29 00:28:28 UTC
relative css image path references?
We have the same issue described here with our calendar looking funny
due to the CSS path references:
http://jira.codehaus.org/browse/JETTY-178
Example:
.calendarBodyContainer
{
url(/dojo/src/widget/templates/DatePicker.cssimages/dpBg.gif)
}
We are running Tapestry 4.1.1, Tomcat for our testing servers, and Jetty
locally. Happens locally and on testing servers on IE Win, FF Win and OS
X, and Safari OS X.
Is there anymore information on this? What is the best way to fix it?
Thanks in advance.
Anna
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: relative css image path references?
Posted by Jesse Kuhnert <jk...@gmail.com>.
p.s. If you're not putting this into your root classpath be sure to
add the appropriate regexp rules to "unprotect" your paths. (Tapestry
can't do it for you by default as it would be too easy for people to
allow security flaws into their apps)
http://tapestry.apache.org/tapestry4.1/tapestry-framework/hivedoc/module/tapestry.asset.html
On 12/28/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> Upon further reflection I think it may actually be my fault after all.
> In the case of content being served from a context path vs internal
> tapestry library it ~would~ make sense to give dojo base relative
> instead of absolute (sort of? ) path...
>
> Hmm.. .The easiest temporary solution is to make sure the dojoPath
> given to the Shell/ScritpIncludes component is one that will cause the
> tapestry asset service to manage it instead of the servlet container.
> (you probably want this to happen anyways as I'm pretty sure no
> servlet container/filter floating around does as much good for assets
> as the tapestry asset service can )
>
> I guess you can stick your version of dojo somewhere in your classpath
> - not context path - and give that path to the component. (ie
> classpath:/path/to/dojo instead of context:/js/dojo )
>
> On 12/28/06, Anna Vo <AV...@widen.com> wrote:
> > We have the same issue described here with our calendar looking funny
> > due to the CSS path references:
> > http://jira.codehaus.org/browse/JETTY-178
> >
> > Example:
> > .calendarBodyContainer
> > {
> > url(/dojo/src/widget/templates/DatePicker.cssimages/dpBg.gif)
> > }
> >
> > We are running Tapestry 4.1.1, Tomcat for our testing servers, and Jetty
> > locally. Happens locally and on testing servers on IE Win, FF Win and OS
> > X, and Safari OS X.
> >
> > Is there anymore information on this? What is the best way to fix it?
> > Thanks in advance.
> >
> > Anna
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: relative css image path references?
Posted by Jesse Kuhnert <jk...@gmail.com>.
Upon further reflection I think it may actually be my fault after all.
In the case of content being served from a context path vs internal
tapestry library it ~would~ make sense to give dojo base relative
instead of absolute (sort of? ) path...
Hmm.. .The easiest temporary solution is to make sure the dojoPath
given to the Shell/ScritpIncludes component is one that will cause the
tapestry asset service to manage it instead of the servlet container.
(you probably want this to happen anyways as I'm pretty sure no
servlet container/filter floating around does as much good for assets
as the tapestry asset service can )
I guess you can stick your version of dojo somewhere in your classpath
- not context path - and give that path to the component. (ie
classpath:/path/to/dojo instead of context:/js/dojo )
On 12/28/06, Anna Vo <AV...@widen.com> wrote:
> We have the same issue described here with our calendar looking funny
> due to the CSS path references:
> http://jira.codehaus.org/browse/JETTY-178
>
> Example:
> .calendarBodyContainer
> {
> url(/dojo/src/widget/templates/DatePicker.cssimages/dpBg.gif)
> }
>
> We are running Tapestry 4.1.1, Tomcat for our testing servers, and Jetty
> locally. Happens locally and on testing servers on IE Win, FF Win and OS
> X, and Safari OS X.
>
> Is there anymore information on this? What is the best way to fix it?
> Thanks in advance.
>
> Anna
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org