The nsjk2 module misses the point of what Java support in AOLserver means to the projects here at BNA. We use AOLserver and Tcl (and now XOTcl) as the core of our newer web sites. We are happy with ADP processing and calling Tcl from ADP pages and have built an entire UI around this model. (The usability of the programming model is fantastic.)
We would have liked to call certain Java classes from this ADP code base as if they were Tcl/XOTcl objects. We do not care about and do not want to use JSP for the specific applications that we have been told to figure out. As useful as nsjk2 is to many people it is not useful to many others. Do you have any plans to provide a means for standard AOLserver applications to include calls to a JVM inside AOLserver ADP and Tcl procs? Or will we still need to put another Java socket server somewhere and call that from our ADP/Tcl code? [EMAIL PROTECTED] wrote: > > > Actualy usefull would be simply a JVM you can make calls into, Tcl Blend > > style. This way I could write (or re-use) code that isn't well suited to > > Tcl and can more easily be done in a OO enviroment and seemlesly use it > > with AOLserver doing the presentation layer. (I hate JSP...) > > I don't see any downside to supporting Java, Java Servlets and JSP > better within AOLserver, and folks who do use Java-based technologies > have a lot to gain. > > As long as Java support in AOLserver stays as an optional module, what's > the risk? It allows more people to use AOLserver, and that's a win-win > for everyone. > > -- Dossy -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
