> Then there would be an outcry of "too much to configure.. waaah". :-)
Well I did say it wasn't perfect :-) However, there would be *nothing* to
configure if the user wasn't skinning their app. If they were skinning, then
I agree that the configuration in web.xml is still awkward. If you can think
of a cleaner solution for that problem I'm all for it.
> So those paths would then be duplicated in xwork.xml? Doesn't sound very
> appealing to me.
Not quite. I was thinking more along the lines of this in xwork.xml:
<skins>
<skin name="skin1"/>
<skin name="skin2"/>
...
</skins>
Plus that could be extended to perhaps specify a default set of UI
components for each skin or whatever. I think this sounds quite nice,
web.xml configuration aside.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
