Erik Hatcher wrote:
>
> JavaScript does not itself have a way to print that I know of - it relies on
> provided objects to do so ('alert' in web browsers to pop up a dialog box).
> I believe (and please correct me if I'm wrong) that to do a
> System.out.println from JavaScript you'd have to get a handle to the System
> object.java.lang.System.out.println "Hello World" > What functionality do you see <script> providing? I view it as a way to > write a Task without having to create a Java class, compile it, and > <taskdef> it. I view it simply as the implementation of the execute() > method of Task, and in that light I think it should be able to have clean > access to the Task object. +1 By the way, here is an example: http://virtuals.intalio.com/cgi-bin/cvsweb.cgi/~checkout~/openjms/src/build.xml?cvsroot=openjms Could it have been done in Java? Absolutely. > Others probably have a view of it creating other Tasks, and other more > esoteric things. But the capability to get crazy with <script> already > exists, I just am arguing for it to be execute(). Nah, that was just me showing off. > I've never seen so much discussion over one line of code before! :) Erik, meet Peter. Peter, Erik. OK, now that you have been introduced. ;-) - Sam Ruby
