Hi!
> We use XMLC lots instead of JSPs (means you can get your web designer
> to do all the HTML however and make it look funky and they don't need
> to know anything other than HTML). But we precompile our html using
> XMLC and deploy just the compiled classes, and don't use XMLC at
> runtime.
Just wanted to say that using JSP does *not* mean that you can't have
webbies that know nothing but HTML. I've designed a simple Model-2 framework
(for that OpenJoda contest) that uses JSP's with a custom taglib (i.e. no
Java code in JSP's) and that gives me
1) Clean MVC. Really! V uses M through C
2) Skinnable apps. I can apply several different Looks&feels to an app
without having to change the code.
3) AFAICT all other models either output XML which is XSLT'ed to HTML or
work on XML in code at some point (XMLC). No such thing here.
So, JSP != "Java code in HTML". Can be, but don't have to be.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
