Sylvain Wallez wrote: > Hi folks, > > I just came across Jelly at > http://jakarta.apache.org/commons/sandbox/jelly/ > > A quick look at it gives me the impression it could be a killer to > develop custom transfomers. Anyone using it ? > > Sylvain >
It is very cool tool indeed. HOWEVER: Being so flexible and powerful is dangerous. I want to second Daniel Fagerström's concerns with continuations, and extend them with another perspective. I think that lately people are getting into the xml scripting hype and are forgoting the core values of Java as a programming language. Strongly typed, object oriented, simple and readable. There are excelent development tools and libraries for Java which are well thought out, proven to work and solid. Main problems I've had with JSPs, JSTL and other scripting solutions: 1) Hard to enforce good practices. 2) Over time these scripts become awfully complex and hard to maintain. 3) Debugging. JSPs are a BIG pain to debug. JSPException doesn't even have neted exception. 4) Typing. Loosely typed languages were invented many years ago, but they have not become practical. Mainly because their programs can become hard to read, debug and maintain as they grow in size. 5) Performance 6) Competing with World standards. For the same reasons that I don't like C# as an initiative, I don't like Sun's JSP extensions (JSTL) initiatives. XSLT, XPath and the like are endorced by the W3C. Why not promote them in the Java world and admit that JSPs are a failure? My view is that Cocoon should have a base library of well designed and powerfull transformers, possibly implementing W3C (or other) standards. The appropriate way to promote Cocoon is to teach people how to use these transformers to achieve what they need and avoid writing their own when possible. This is how good practices can emerge and common libraries and solutions will become available faster. -- -= Ivelin =- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
