Hi all,
this problem is very nice solved in c:url JSP tag. When the URL is absolute
(starting with /) then the context is added
before (request.getContextPath()) otherwise the URL is relative and leaved the
same as it was.
I think it shouldn't be problem to create component solving this proble
Maybe I'm not fully grasping the problem... what's wrong with using a
context asset?
Instead of saying , why not do:
.java:
@Inject("context:default.css")
private Asset _stylesheet;
//note: tapestry will coerce the stylesheet appropriately into the
client url string
public Asset getStyles
Will be a Shell component that makes possible to add css as assets ?
On 3/14/07, Todd Orr <[EMAIL PROTECTED]> wrote:
Realistically, the context is not always known during development.
Business folk could easily come back after the entire QA cycle and say
that it needs to be changed for marketin
Realistically, the context is not always known during development.
Business folk could easily come back after the entire QA cycle and say
that it needs to be changed for marketing reasons. This would require
a code change that may force an entire round of QA again. There should
be some way to refe
This is a conscious decision, that you will know early on what the
context path will be.
The effort to avoid this in T4, using a tag, caused far more
problems than it solved.
A solution using query parameters is likewise: it makes your site
off-limits to any kind of search engine, and it tends
I've never had to operate out of a context other than root, so I've just
hardcoded it to "/mystyle.css" or whatever...
On 3/12/07, Bogdan Calmac <[EMAIL PROTECTED]> wrote:
Consider a UserDetail page that has an URL like
"http://server/context/UserDetail/jdoe";. Here I'm using the tapestry
styl
Consider a UserDetail page that has an URL like
"http://server/context/UserDetail/jdoe";. Here I'm using the tapestry
style of passing parameters, as part of the context. The problem here
is that if you have a styleset link to "mystyle.css", it will try to
look for "http"://server/context/userdeta
