I know this is sort of sidestepping the problem, but you could do
something with your own code, maybe in an initializer block for your servlet
class?
        rivate static Boolean fInitialized = false;
        private void initialize(ServletConfig config) {
                String temp = config.getServletContext().getRealPath("img");
                fImgDirectory = temp;
                // foreach asset
                        // if (!fImageDirectory.fileExists(asset))
                                // copy into fImageDirectory.
        }

        public void init(ServletConfig config) throws ServletException {
                synchronized (fInitialized) {
                        if (!fInitialized)
                                initialize(config);
                        fInitialized = Boolean.TRUE;
                }
                super.init(config);             

        }

> -----Original Message-----
> From: Alan Chandler [mailto:[EMAIL PROTECTED]
> Sent: Saturday, August 27, 2005 10:36 AM
> To: [email protected]
> Subject: Getting Assets on to a path for static serving (in particular my
> .css file)
> 
> I have asked this question several times before but never received an
> answer.
> Now I have got to the point where all my work-arounds don't seem to hack
> it,
> so I NEED to ask again.
> 
> How do I get assets pushed into the correct path so that they can be
> served
> statically by my web server.  There used to be two tapestry configuration
> parameters  (org.apache.tapestry.asset.dir, org.apache.tapestry.asset.URL)
> to do this, but they seem to have disappeared in the latest version of the
> usersguide. (And I couldn't find out how to use these either!).
> 
> 
> 
> 
> --
> 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]

Reply via email to