Re: ww:component (JSP) isn't outputting anything
tm_jee <[email protected]>
| Newsgroups | gmane.comp.java.open-symphony.webwork |
|---|---|
| Message-ID | <27575596.1150263365051.JavaMail.os-j2ee@opensymphony01.managed.contegix.com> |
> BTW, for whomever does the documentation for ww:component, I think it'd be helpful to >include a little note saying that JSP files can't get loaded from the classpath, and have to >tbe with the other JSP files. Thx for the feedback. I could work on it this weekend. I am supposed to work on the freemarker tutorial but can't find time last weekend, maybe i'll work on them together this weekend. > One related question: so I can put all my custom template files with all my other > JSPs, > but it looks like the theme.properties still has to be in the classpath, right? Do people > usually stick it directly into WEB-INF/classes, or do they jar it up with their source? > Neither one really seems quite right to me... theme properties are cached according to the template engine, eg. freemarker template engine could have a copy of xhtml theme properties and so can jsp template engine. Normally for templating on the fly like above, theme.properties shouldn't be necessary. Normally, i guess, templates and theme.properties are group together. With freemarker, the templates and theme.properties could lie in the classpath, making them jar-able. Jsp unfortunately don't have this advantage. This could comes in really handy when developing a product with lots of module. eg. by putting a forum module jar into the lib and adding a <package .. > in xwork.xml could make the webapp capable of serving a forum, ad a bloger jar file will make the webapp have a blog. Probably the webapp will have a admin module that will show the status of each module put in etc. just some of my 2 cents. hth --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=33869&messageID=66651#66651 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]