No, both org.apache.tapestry.asset.dir and org.apache.tapestry.asset.URL are
still used, as of Beta 3 anyways.
----- Original Message -----
From: "Alan Chandler" <[EMAIL PROTECTED]>
To: <tapestry-user@jakarta.apache.org>
Sent: Monday, August 15, 2005 3:54 PM
Subject: Re: Confused about asset prefix
On Monday 15 Aug 2005 18:05, Kent Tong wrote:
l...
Try:
class MyComponent {
@Asset("classpath:images/001.gif")
public abstract IAsset getMyAsset();
Thanks, I usderstand the syntax now - although it appears (from what is
currently happening in my test app) that classpath is the default.
I presume this means that I could specify INSIDE A LIBRARY COMPONENT
@Asset("context:styles/sitestyle.css")
public abstract IAsset getSiteStyle();
and then expect the user (MyApp) of the component to supply the style
sheet
at /MyApp/styles/sitestyle.css
As I said in the original post from this thread, I have a longer term
desire
to cause these assets to be served up by apache rather than tomcat. I
note
the latest userguide says that
org.apache.tapestry.asset.dir and org.apache.tapestry.asset.URL
are no longer needed. So how do I do it now? And where do "private"
assets
come into it?
--
Alan Chandler
http://www.chandlerfamily.org.uk
---------------------------------------------------------------------
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]
