Re: clnt-struts request

Pierre,

>>
> Yes indeed. But I didn't find any way to overwrite the default code 
> from my application. So if I want to use some uptodate libraries like 
> JSTL 1.1...
>
> May be a solution would be to use some "flags": if "web1.user" is 
> defined, then look for "web1.xml" from user application. And as value 
> of the flag, some kind of path to get the file?
> Or an implicit way: if plugin.jelly finds any "web1.xml" in user 
> conf/client directory, then it uses it.
>
> So you don't have to maintain the code for each version or specific 
> user wish.
>
Good idea....we can use a variable on where to get the template web.xml 
components.  Much better than hard-coding support for specific 3rd party 
releases in the plugin.  Can you use a locally modified client-struts  
for now, we can do the enhancement with variables after the current 
spate of Maven changes are done.

>
>> and the positive thing is that it will work with not only Struts, but 
>> with any other view technology.
>
>
> Not Tiles?
>
I guess it will work with Tiles as well.  But Tiles and Sitemesh are 
both technologies to "decorate" your pages, without the pages knowing 
how/if they are being decorated...i.e they both serve the same 
purpose.   Sitemesh is more general, and from what I understand, a lot 
faster.

>
> May be it would  be the kick-off  I need to look at sitemesh...
>
I will check app-sitemesh in tonight.  Actually, with maven, it doesn't 
even include JARs anymore, just a project.xml so keel:maven can do it's 
job and some configuration.

Shash

http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com