Phew, I just converted a complete application to
jsp1.0. Much to my surpass it went rather smoothly.
I was initially worried about the lack of <includeif> et al.
and how nasty it might be to have to code my own
<% myBean.processRequest(request); %> at the top of
every page. But it really wasn't bad. I was initially
quite pleased...
I was very pleased with the clean nature of the
implementation and the speed (perhaps due to switching
to jdk1.2) that the server seems to run at.
After "renting" an additional 40 more meg of hard disk
space on my ISP so that I could move to jdk1.2 and
jsp1.0 I got everything copied up to the server and...
Hit a brick wall!!!!
It seems my 'home' on the ISP in a directory named
'/home/1/l/langley', which has never been a problem,
until now. (Spelled phonetically, that's
/home/one/el/langley).
It seems that the jsp1.0 wants to create classes whose
package names include the directory where they are created,
e.g. package home.1.l.langley.virtual_html.jsp1_0.examples.jsp.snp;
This is a REAL PROBLEM! Java DOES NOT LIKE raw numbers in
a package specification. Unfortunately, I have absolutely
no control over this directory specification. I'm currently
running on an ISP that has over 6000 web sites running in the
environment I've described, so it's more than a little
unlikely that I'll be able to convince them to change their
directory naming scheme.
The result. You can't use jsp1.0ea in an environment where
you have directories with named as numbers.
Now I know this may seem trivial... but after a 16 hour
day, I must say I'm more than a little disappointed to
get "shot dead" right at the finish line this way.
My environment is jdk1.2.1 on Solaris where uname -a
reports SunOs 5.5.1 Generic_103640-24 sun4u sparc SUNW etc.
And of course jsp1.0hhhh (my that hurts).
I tried moving the work directory via the default.cfg file
to /tmp/xyzzy/work... well it didn't work. No help there,
the package name in the generated code is dependent on
the location of the source. So even the samples, like
the .jsp version of snoop doesn't compile.
Any insight or ideas people could offer would be greatly
appreciated. (Just incase you're thinking... I tried
Jrun before investing the effort in converting to jsp1.0
and got "shot early" there because page redirections didn't
trigger .jsp page compilations. CallPage() seemed to help
some, but looked like it was running into nasty problems...)
Oh, and what's wrong with JspRef092?
With jdk1.1.8 and lower it leaves file descriptors open
when you interrupt page down loads, even just serving
.html pages. That's what prompted this whole excursion.
Jdk1.2.1 seems to have fixed this problem (I just learned).
So JspRef092 w/ Jdk1.2.1 is the only game in town for the
moment.
Sleepless in NH...
Langley.
===========================================================================
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".
