hmm, let me try this a different way
-on the server side i want to specify the input beans I want the
client side to have
-the jsp would instantiate the beans using 0.92 behavior on the server
but the bean executes on the client [0.92 says if its java the SCRIPT
cannot specify anything but server execution, so I can't even get
tricky that way]
-I want the client side input beans to act as if they are in a giant
(full page - not window, size applet) where the HTML shows through
-the applet's layout and sizing type of behavior is actually derived
from the html positioning of the components in the jsp page
-if I want to put a toolbar in this window I want the window to behave
as if it is an applet with borderlayout (north/south docking). My
toolbars include textfields!
-I still want the components to all share the same logical or actual
applet container, maybe even across frames
-I want tags that support focus order traversal and other generalized
behaviors - font? color scheme? to be high level and part of the spec
-I'd expect that business logic behavior (data entry validation,
component disabling) should be easy to script
I guess in summary, I want to jsp page to build the applet, leveraging
html for layout and display, swing components to be
specified/initialized on the server but actually instantiated on the
client [save a lot on download time and put the work where it is done
best].
I want the jsp page to allow the specification of client side data
entry validation, masked edits[you gotta compete with ASP], focus
traversal, etc. I want html coders to be able to specify business
logic on the page, where it is all localized and not spread across
html files, java source files, jsp page files.
I can see some of this ability is in the spec using java scriptlets
[but that does the work on the server]
It seems like it makes sense to want to do the above, with the work
distributed between client and server as I tried to describe.
---Abhishek Chauhan <[EMAIL PROTECTED]> wrote:
>
> Steve,
>
> With the advent of extensible tags in JSP such features get out of the
> scope of the JSP spec, and into that of extensible tags. JSP would
> come with a set of standard tags that would be available on all JSP
> implementations.
>
> Extensible tags will allow JSP users / Tag Library Providers to
> provide custom tags that look and feel just like regular JSP tags.
> The tag provider would be able to implement whatever behaviour they
> want out of the tag. In particular, I think it is possible to
> implement your suggestion as a custom tag.
>
> -abhishek
>
> steve barrett wrote:
> > I would like to something that provided the following features:
> > 1) Swing components could be placed within the page using something
> > like <input .. BEAN TYPE="JTable">
> >
> > 2) These components shared an applet context so any behavior you
could
> > get from an applet could be coded (scripted would be too good to be
> > true)
> > a) data validation logic where emptiness, or date
> > validation, or amount checking could be done
> > b) business logic - examples:
> > 1. where components would be disabled because
> > a radio button was not selected
> > 2. if there was a zip code then city/state could
> > be set
> > 3. if some field held the int value 9 then some
> > other field had to be blank or perhaps an
> > int value 1-5
> >
> > 3) some kind of application bean that could provide access to
session
> > beans from multiple browser windows
> >
> > Can any of this already be done?
>
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
===========================================================================
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".
