We are using JSP for a portal application that will go live with
hundreds of users in the next couple of months. Like Brian, I'm very
bullish on JSP. Like Brian, we are also using it *very*
conservatively.
This is driven by instability in the spec and the fact that we
have short deadlines and don't want to have to spend a lot of time
debugging JSP engines (or having to switch in a hurry while trying
to get features out).
I'm also of the opinion that JSP is here to stay, mostly because
of the fact it gets you from HTML easily into Java, which is
what we use to code application logic and transaction processing.
ASP just does not compete on Java support; IIS is also a very
difficult environment to manage. Even at the 0.91 level (GNU JSP),
JSP has already shown itself as the right choice. We've used
both on this project and have ended up rewriting all ASP into JSP.
Robert Hodges
Tilden Park Software
Brian Burridge wrote:
>
> I understand your desire to recieve the final spec, but keep in mind a few
> things. First, there never really is a final spec. Take HTML or Perl as an
> example. Second, although the final spec is not yet released, the current spec
> functions just fine. We are using it on live projects already, and we are
> simply ecstatic with JSP as a development environment. I look forward to spec
> 1, but don't know that it is going to mean any difference to our development
> whatsoever. Everything we need to do can be done, and is being done.
>
> One difference that might be making you more nervous is in how we are using
> JSP. I know that most people on this list seem to be very excited that JSP will
> be similiar to Cold Fusion. Whereas, my excitement about JSP is that it is
> nothing like Cold Fusion. Here at Val-Pak/Cox Target Media, we use only two
> tags in all our code: <%...%> and <usebean>. That's it. No other tags are used.
> The beauty of JSP (to me) is that it does inline Java. Java is stable and well
> supported, and what spec of JSP I'm using will not affect my Java code. I know
> this goes against some of the spec design and much of the discussion on this
> list, but the ability to inline Java, call db beans, and packages that we can
> download and/or purchase, is just amazing. The Java programming is much faster
> and easier to code than trying to build full servlets and compile them, and yet
> the speed is the same.
>
> My main point, is, that at least to us, the next spec will make zero difference
> in anything we do here. We aren't going to have to recode anything, we aren't
> going to gain any functionality (because we already have the full functionality
> of Java), and it isn't going to get any more stable (haven't had one case of
> server crash, or any other instability since we installed New Atlanta 3 months
> ago.)
>
> Hang in there, and don't worry about the future of JSP. As long as Java has a
> future, so does JSP.
>
> Brian N. Burridge
> Web Specialist
> Val-Pak/Cox Target Media
>
> Judd Salisbury wrote:
>
> > It is almost the end of the first quarter and I believe JavaSoft
> > committed to have the spec completed. I have been using JSP since July
> > 1998 when the spec was in version .90 and call me naive but I always
> > thought the final spec was just another month or two away. With each
> > month that pasts it becomes harder and harder for me to justify the use
> > of JSP. I have in the past been a great supporter of JSP in my
> > organization and have developed hundreds of pages using JSP, but I am
> > losing my political strength to defend the use of JSP in my
> > organization. I hate to say it but if the spec does not go gold in a
> > week or two I will have to recommend to my company to standardize on ASP
> > instead. I can no longer afford to defend a specification that can not
> > seem to make it out of the .9 something category. Could someone at
> > JavaSoft confirm that they will not be going to be hitting their own 1Q
> > deadline. And an explanation of what is holding them. At least then I
> > could tell my employer why the JSP spec will not be done by the first
> > quarter as I said it would be.
> >
> > Thanks,
> >
> > Judd
> >
> > ===========================================================================
> > 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".
>
> ===========================================================================
> 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".
===========================================================================
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".
