I meant to include this other information in that previous email, but
hit the send button too quickly:
Here's the run-down on the 4 areas listed I should cover in proposing a
new taglib.
Motivation: This tag library solved my issue of not being able to debug
server-side JavaScript. When the server is accessed locally, it allows
me to debug my server-side JavaScript, which BSF does not allow me to do.
Overview: I use this in my JSP pages instead of Java scriptlets:
<js:script>
pageContext.setAttribute("someval", "somevar");
</js:script>
...
<js:script debug="true">
<!--
var somevar = pageContext.getAttribute("someval");
out.println(somevar);
for(i=0;i<somereqvar.length;i++){
out.println(somereqvar[i]);
}
//-->
</js:script>
All the request parameters are declared in the scope of the JavaScript,
so I don't need to do anything to access them, they're already
available. In the above example, "somereqvar" is coming in from the
query string.
Requirements: I built this using the latest Rhino 1.6, since I want to
try out E4X, but it should work fine with Rhino 1.5. I use JBoss 4 as my
application server, so I built on J2EE 1.4 and JSP 2.0. I'm not sure how
far back the taglib API I'm using goes back, but everything related to
J2EE is extremely simplistic, so there shouldn't be any problems there.
Commitment: I can be involved in maintaining this tag library, though my
time would probably be limited to an hour a week or so (I'm a
non-traditional college student finishing a Bachelor's).
Thanks!
--
Jon Brisbin
Webmaster
NPC International, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
