Tapestry 5.1 has an asset protection scheme that requires some
configuration to allow access to asset files on the classpath; even
innocuous things such as stylesheet files. Unless you understand the
configuration, you'll see Assets exported as URLs that result in a
404. As you saw, moving them t
Thanks for the tips!
I resolved the issue by moving the component from my external component
.jar file (which is included in my application) into my actual
application, where it worked without any problems. It was the same code
but everything worked there.
Thanks again,
Elisabeth
On 25.04.2
Hi,
This indicates there is a problem in your css file and is not related
to tapestry. Sometimes a shift refresh fixes the problem. Copy and
paste the asset url into your browser and have a look at it. Might be
related to a file encoding problem.
Cheers,
Joost
On 24 apr 2010, at 23:14, E
Elisabeth,
when you include the stylesheet in the way you show, it should show up as
an
element in the section of the document that is produced. Can you
show the resulting rendered output ?
I do recall that there was some discussion in the past that if the tml being
rendered was not an HTML
Hi there,
I am building my own tapestry component (TabSet) which I want to give a
certain style. The problem is that the CSS is somehow not applied, even
though it looks like it finds it (if I change the path in the code where
I include the stylesheet, it complains it can't find the file, so i
