Steve,
   my story is very similar to yours, but I am happy ;)

I also moved from JWS to Apache/JServ and now (after Sun release the specs for
jsp1.0), GNUJsp. GNUJsp is not a released product (you may want JRun if you want
something "released"), but I am very happy with GNUJsp.

It is important that you revise the "specs" for jsp 1.0 (see
http://java.sun.com/products/jsp/index.html) because a lot of things changed from
0.9x version to 1.0.

On another note, I think you should avoid a lot of business logic on your jsp
pages, i.e. try to use jsp to display information only that were rendered by a Bean
e.g.

The only thing I can tell you is that if you are using GNUJSp, you should get a new
CVS update -every day- , since those guys are working around the clock to catch-up
with 1.0 and a release is put for download every 2hrs......

Did you try to run your pages against Sun's JSWDK1.0? I found very useful for
testing....

Good luck...

Rodrigo

Steve Gower wrote:

> Please read my sad story and convince me that JSP is a real development
> environment and not merely a worthless hack that looks good in press
> releases and white papers.
>
> When I played with JSP on JWS beta 3, when some of my JSP pages were
> rendered, it put in extra line feeds in random locations which screwed up
> the HTML. This problem was fixed by including this on each of my pages:
>
> <%@ page buffer="256kb" %>
>
> As we all know, Sun has decided to leave us JWS users high-n-dry by
> discontinuing this webserver.
> Sooooo.. we've already converted all of our JWS servers to Apache/Jserv.
> When I had looked, I was not able to locate any JSP 1.0 add-ons for Apache.
> Since then, one our our server dudes tells me that he found and installed
> JSP 1.0 suport (I don't know what the package is called or where he got it
> from I think it maybe something GNU).
>
> Now, some of my JSP pages that did work on JWS 2.0 are exhibiting bizarre
> behavior.
>
> Here's a sample from my JSP page (Note, it uses a database bean to display
> queried info):
>
>   <b>Date Menu:</b>
>   <select name="date">
>   <%while(db.next()) { %>
>      <option value="<%= db.get("cDate") %>"><%= db.get("cDate") %>
>   <%} // end of while loop %>
>   </select>
>
>   <b>Report Menu:</b>
>   <select name="reporttype">
>     <%if(req.getreporttype().equals("All")){%>
>       <option value="All" selected>All Reports
>     <%} else {  %>
>       <option value="All">All Reports
>     <%}%>
>       ...more options deleted
>   </select>
>
> Notice that there are 2 different html <select> object. Well when the page
> is rendered, here is the output:
>
>   <select name="date">
>   <option value="1999-09-22">1999-09-22
>   <option value="1999-09-23">1999-09-23
>   <option value="1999-09-24">1999-09-24
>   <option value="1999-09-25">1999-09-25
>   <option value="1999-09-26">1999-09-26
>   <option value="1999-09-27">1999-09-27
>   <option value="1999-09-28">1999-09-28
>   <option value="All" selected>All Reports
>   </select>
>
> These two <select>'s were combined into one!  Basically what I'm wondering
> is: What Gives?
> Has JSP matured past the Toy stage? Is it ready for Prime time?  Does anyone
> our there have any idea what is causing this problem and how I can work
> around this?
>
> We're considering using JSP to develop a number of different applications,
> but want to get a version that is stable and actually works properly.  Any
> help would be appreciated.
>
> Steve Gower
> 319.266.1009
> http://www.bottomdollar.com
> The Shopping Search Engine(TM)
>
> ===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
> FAQs on JSP can be found at:
>  http://java.sun.com/products/jsp/faq.html
>  http://www.esperanto.org.nz/jsp/jspfaq.html

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html

Reply via email to