thanx, but we are not using velocity... the other frameworks we use are sitemesh and jdo for the data access. for the "view" of the data a true EXPLORER like tree is required that folds in and out (like Win Explorer or any other common file manager) if possible everything has to remain on the server side otherwise JavaScripts would be accepted (IE as primary browser, but since I would like to keep it reusable nothing IE-specific should be there ;)
W -----Ursprüngliche Nachricht----- Von: Matt Ho [mailto:[EMAIL PROTECTED] Gesendet: Montag, 31. März 2003 13:31 An: [EMAIL PROTECTED] Betreff: Re: [OS-webwork] How to mark options as "selected" for webwork:select tag? > you new velocity template you write. It should exist in > /WEB-INF/classes/decorators/xhtml, I believe. You can place in a couple of paths, either /decorators/xhtml/... or /WEB- INF/classes/decorators/xhtml as velocity is configured to read both from the classpath as well as the web path. M ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
