Forward:
        I truely believe that JSP and Beans are central in dynamic content creation.  
They
        are crutial to the development of the next wave of internet applications.  SUN 
must
        continue to invest in this truely object oriented technology.  I have written 
several
        web application frameworks myself, and see the grace and utility of JSP.  JSP 
seperates
        interface creation from the application logic while incorperating session and
        application management.  JSP allows designers to design and engineers to 
engineer.
        I am dedicated to its success.

Problem:
        JSP is becoming too complex.
                The current vision as discussed emphasizes "model 2".  Servlets talk 
to the
                application instantiate beans and forward requests which contain 
session
                information and request information.  This will scare many away and 
limit
                the usability of object oriented graphic tools for automatic page 
creation.

        Suggestion:
                Increase the awareness of JSP Aware Beans.  Make Beans a central 
concept
                in the design of JSP.

        Method:
                Add execution cycle specification and additional bean environment 
passing
                to JSP1.0
                a) through introspection call setSession, setServletContext,
                        setRequest, setResponse to bean execution cycle.
                b) add set-each-request parameter (called "set")  model to
                        JSP1.0 (as apposed to setoncreate or setfromrequest)
                c) implement and add to spec an execution cycle as follows
                        1. setoncreate called (during initial creation only)
                        2. setSession, setServletContext, setRequest,
                                setResponse are called
                        3. set (described in "b" above) called
                        4. setfromrequest called
                        5. processRequest called (work of page done here)
                        6. getXXX called by JSP
                d) elminate attempt at an additional programming language as seen in 
0.92
                        Use scriptlets.  Do not overcomplicate the interface use JAVA 
and
                        scriptlets instead of creating a tangent language.
                        1. remove "LOOP" use <%for(xxxx){%> html <%}%>
                        2. remove "property" concept in favor of <%=beanname.getXXXX%>
                e) GET ON THE BEAN BANDWAGON!!!!  ditch crowbars and make beans central
                        to the server function.  Anything short of this will kill JSP 
(imho)

That's about as much time as I have right now.  If there is any interest in my opinion
I will comment on my other concerns (such as application, session, and request 
function)
Hope I helped.

-jason

Jason Bright
Pres., BrighTech Inc.
212 3rd Ave N #435
Minneapolis, MN 55401
(612) 317-0737
[EMAIL PROTECTED]

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to