Have you used JavaServer Pages (JSPs) on a production site?
The following comments have been recorded for
Yes, and it went well
Back to Results
- 1 (16 Nov 2016 00:00)
- 1 (15 Jun 2016 00:00)
- http://autoinsurancen.pw/cheap-motor-insurance-india.html http://autoinsurancesm.top/auto-insurance-murfreesboro-tn.html http://autoinsurancen.pw/reviews-on-cure-auto-insurance.html http://carinsuranceten.info/affordable-auto-insurance-albuquerque.html http://autoinsurancesm.top/compare-insurance-quotes-online.html http://autoinsurancesm.top/the-best-cat-insurance.html http://carinsurancepu.top/progressive-rent-car.html http://carinsurancepu.top/the-evans-agency-insurance.html (26 Jan 2016 00:00)
- My preoblm was a wall until I read this, then I smashed it. (17 Oct 2015 00:00)
- nice post us website packers and movers bangalore Visti site:-
Packers and Movers Bangalore
Packers and Movers Delhi
Packers and Movers noida
Packers and Movers gugaon
Packers and Movers bangalore
(1 Aug 2015 00:00)
- We use it extensively on 888.com with WURFL and it went GOOD :) (16 Apr 2015 00:00)
- asd (14 Jun 2006 00:00)
- vf (22 Mar 2006 00:00)
- yes is best (16 Feb 2005 00:00)
- Makes my life easy. (1 Jul 2004 00:00)
- p (15 Jun 2004 00:00)
- good and i like it (9 Feb 2004 00:00)
- in production on a top ten Internet site (6 Apr 2003 00:00)
- I know alittle! (6 Nov 2002 00:00)
- Cool and EZ (12 Sep 2002 00:00)
- great! (28 Jun 2002 00:00)
- Who is Jebediah Crump??
This Guy Has. (13 May 2002 00:00)
- I have written JSP in production site but I am using MVC, JSP for rendering. This site is taking close to 100 request per second (13 Apr 2002 00:00)
- It is very hard to separate the code from the presentation. Maybe because it is page-centered? And it is difficult to create functionality if there is not an experienced Java programmer around. (21 Jan 2002 00:00)
- error are difficult to track! (15 Jan 2002 00:00)
- none (15 Jan 2002 00:00)
- We've built 5 production sites, two of them banks and have had great success. (31 Dec 2001 00:00)
- Very well... debugging was a little problematic. Moving to xml, xslt now... should be fun (22 Nov 2001 00:00)
- Only for the view component. (21 Nov 2001 00:00)
- very funny (20 Nov 2001 00:00)
- but now I use Velocity and it's even better! Tomcat4+Velocity+Ant rocks! (15 Nov 2001 00:00)
- Did it job. Similar to ASP coding style. Put my java code in javabeans. (15 Nov 2001 00:00)
- We made sure that we spent time understanding and designing up front which helped significantly. (14 Nov 2001 00:00)
- so easy to develop (13 Nov 2001 00:00)
- portable using WebLogic Entity Beans 2.0 (13 Nov 2001 00:00)
- Using model 2 with struts as framwork. (12 Nov 2001 00:00)
- It is the best web development technology around. (12 Nov 2001 00:00)
- Much more convenient than CGI.
Better than ASP because we were able to use OOP. (11 Nov 2001 00:00)
- Integration of HTML (including JSP code) and IDEs must be improved. Debugging of JSPs is tedious. (10 Nov 2001 00:00)
- Challenging but effective (9 Nov 2001 00:00)
- Before JSPs we were writing servlets mostly without beans. JSP has put us on the right track. Beans are great. (9 Nov 2001 00:00)
- It's a struggle to implement, but it works. (7 Nov 2001 00:00)
- Difficult to debug because we wren't using any sophisticated IDE.
In some case customers would not want to use them because of securtiy issues (autorecompilation of the source code).
But once they run, they run. (7 Nov 2001 00:00)
- using Jakarta Struts (6 Nov 2001 00:00)
- JSP is easy to use. (6 Nov 2001 00:00)
- Use it on all new and upcoming production sites. (6 Nov 2001 00:00)
- Yes it was terrific!!!
Amazed from the portability (6 Nov 2001 00:00)
- with and without EJB stateless and stateful sesion bean ( But Entity Beans are a headache ) (6 Nov 2001 00:00)
- However the challenge is keeping presentation separate from business logic. No clean solutions till now IMHO (6 Nov 2001 00:00)
- When compared to ASP (ie all programming in the page), JSP prepresents a more segmented, structured approach. (6 Nov 2001 00:00)
- yes it was far easier and quick implementing Programming in JSP. (5 Nov 2001 00:00)
- Much easier to use to implement web based solutions versus EJB. (5 Nov 2001 00:00)
- Also experimented with ASP for the same site, but it was hideous.
And to add value, running App server on a Linux box just gave me fantastic uptime and availability :)
(5 Nov 2001 00:00)
- but, understanding the limitations of jsp, I purposefully scoped the ui side of the project very thin. (5 Nov 2001 00:00)
- grestest (5 Nov 2001 00:00)
- taglibs are a dream! (5 Nov 2001 00:00)
- I only wish we had discovered architectures like Apache Struts sooner during the process of our JSP development. (5 Nov 2001 00:00)
- works well as the "view" for a model-view-controller architecture (5 Nov 2001 00:00)
- It is working very well, and is very protable between all Java Web Servlet Container and J2EE Server.
Use Servlet API 2.2, JSP 1.1 at tomcat 3.2.x, servletexec 3.x, bea weblogic 6.x, Jrun 3.x.
(5 Nov 2001 00:00)
- I still find other scripting languages easier to program in such as PHP and CFML. Also support for JSPs by ISPs could be better. (5 Nov 2001 00:00)
- Simple, transaparent model.
Wish it did more wrt to handling form input, validation, required fields, etc. (5 Nov 2001 00:00)
- Just started and planning to do much more. (PHP sucks) (5 Nov 2001 00:00)
- JSPs are great, but like any powerful, feature-rich technology, you have the ability to create elegant, well-functioning code as well as nightmare code. (5 Nov 2001 00:00)
- I was a major PITA to keep the jr. developers from making the source files 25 pages long. I think JSPs are horribly abused. (5 Nov 2001 00:00)
- To the puritans amongst programmers, these are not easy things to follow. It is really important to remember their forefathers (servlets) virtually everything clicks into place as long as you remember that. (5 Nov 2001 00:00)
- We are using the MVC model and are very happy with it. Our design pattern allows exaclty one bean for every JSP and the bean carries all the information needed to render that JSP. (5 Nov 2001 00:00)
- JSP rules (5 Nov 2001 00:00)
- I love JSP. I don't understand a lot of the crtiques, since largely they involve a failure of self-discipline and can be so easily resolved via the miracle of taglibs. David Geary like solutions in layout management, e.g., are terrific. (5 Nov 2001 00:00)
- I've used JSP's in my last 3 projects with great success. (5 Nov 2001 00:00)
- Can be a bit messy, with the ability to easily intermix java code and HTML (C and V of MCV), but once you get it down, it works very nicely. (5 Nov 2001 00:00)
- Good for simple layouts without much graphics. (5 Nov 2001 00:00)
- Always with great success. Have not found the best way to implement a good MVC architecture yet though - none of the ones available really do it well yet. We have our own process which works "well enough". (5 Nov 2001 00:00)
- jsps are great - definitely use them. (5 Nov 2001 00:00)
- To use HTML designer tools you must have your code inside your HTML like it is with JSP or ASP. A servlet, in the simplest case, puts the HTML inside the code where it is impossible for a designer to change. JSP has the added benefit that is is compiled on the fly. If you write it correctly you only have minimal code in your JSP.
(5 Nov 2001 00:00)
- But now we use XSLT (5 Nov 2001 00:00)
- But I've switched to Velocity and am loving it! (5 Nov 2001 00:00)
- Big production intranet site. Very potent technology especially when limited to custom tag libs. (5 Nov 2001 00:00)
- They work very well once they're debugged - but deugging has been a major hassle (I use JBuilder4 Ent.)
Also, some instances of keeping Java code out of JSP has been more difficult than it should be. (5 Nov 2001 00:00)
- Sorta- we precompile the jsps and just deploy the servlets. this way, we are not tied to any one jsp solution but just a generic servlet solution. (5 Nov 2001 00:00)
- Web Product: JSP/Servlets(JRUN), EJB (Stateless session beans using WebLogic) and Oracle. (5 Nov 2001 00:00)
- uses Tomcat 3.2.3 with apache 1.3, works great (5 Nov 2001 00:00)
- Don't code (too much) java into the JSP's, just put java method calls into the pages. (5 Nov 2001 00:00)
- it works great
(5 Nov 2001 00:00)
- I use them with great success primarily as the view in an mvc config. (5 Nov 2001 00:00)
- Site gets over a million hits a month.
No complaints thus far. (5 Nov 2001 00:00)
- Combined with XML this is a great solution. (5 Nov 2001 00:00)
- For a small site there is no reason to look for a middleware like EJB. Jsp with beans does it faster and simpler... (5 Nov 2001 00:00)
- Currently about 10 Sites
with up to 12000 requests
(jserv/gnujsp) (5 Nov 2001 00:00)
- We only used JSP for the View of an MVC architecture ... servlets were the controller. (5 Nov 2001 00:00)
- Model II worked very well for us. It seems like the clear choice. (5 Nov 2001 00:00)
- I am looking for something in between basic JDBC and EJB. I have created some of my own classes but it would be much nicer to have a real technology that many of us could contribute to. (5 Nov 2001 00:00)
- A production system should, almost always, use a combination of JSPs and Serwlets (5 Nov 2001 00:00)
- I love JSPs. Coz noone else in my organization likes it :-) (5 Nov 2001 00:00)
- You should have a Very Well category, and may be a GREAT one too ! (5 Nov 2001 00:00)
- JSPs Rock, together with Servlets as Controllers. (5 Nov 2001 00:00)
- Its cool ! (5 Nov 2001 00:00)
- Very good technology!
3 production sites: 2 with IIS on NT and 1 with Apache on Linux (5 Nov 2001 00:00)
- I implemented JSPs on three production sites (5 Nov 2001 00:00)
- I wonder why would anybody use ASP or PHP with the existence of the JSP, great technology! (5 Nov 2001 00:00)
- JSP's debugging is big problem otherwise its great! (5 Nov 2001 00:00)
- I used JSP on my first production site and it was kind of messy. I didn't quite get the MFV separation right. However, for my next site I'm going to have a bash at using Struts and see how that works. Looks good so far although possibly a bit expensive (overhead wise). (5 Nov 2001 00:00)
- Found it very quick and simple to develop JSP website using JBuilder and deploying onto JRun. (5 Nov 2001 00:00)
- Used Jrun and also JSP for the controller (MVC). No servlets at all.
Works fine :-) (5 Nov 2001 00:00)
- love it. quick & easy. (5 Nov 2001 00:00)
- We have three production sites running exclusively on JSP's (Apache + Tomcat). (5 Nov 2001 00:00)
- Ugly technology under the hood but too damn easy to ignore. (5 Nov 2001 00:00)
- Apache Struts rocks. (5 Nov 2001 00:00)
- It's uneasy howevver to dinf the right split between JSP, servlet, MVC model (5 Nov 2001 00:00)
- They are very easy for beginners to get started with, before learning sevlets properly (5 Nov 2001 00:00)
- Probably would have gone just as well without JSP though... :) (5 Nov 2001 00:00)
- The combination of servlets and JSP's (with Tomcat) is fantastic; it allows to separate the output layer from the application layer. (5 Nov 2001 00:00)
- Combination of java and servlets works very well here in CSC Norway. It is a bit complicated to set up the environment (IBMVAJava) but once you get it work, it is rather easy to build complex applications. (5 Nov 2001 00:00)
- It's easy, flexible and robust.
In combination with tag-lib it makes devlopment faster. Very well supported in the industry. Runs everywhere from my laptop to the Sun prod server with no change. (5 Nov 2001 00:00)
- Wonderful, you can achieve better performance than other technologies, but you have to do a very good project (5 Nov 2001 00:00)
- I use Servlets and JSPs on a production environment with Apache and Tomcat 3.3. The server receives over 15 million hits/month. I wish I could say Tomcat was more stable, but it tends to crash every couple of days ... I suppose this is abuse, and we should really move to a clustered architecture : ) (5 Nov 2001 00:00)
- MVC style fronted by servlet (5 Nov 2001 00:00)
- Portability (windows/UNIX), multiple implementations (Tomcat, ServletExec, Resin) makes life very easy. We feel very comfortable with all implementations and environments we used.
One soar point is that I haven't found a way to debug a JSP which is part of a complete Web Appliction (as defined with the whole WEB-INF/web.xml stuff) under JBuilder 4 Enterprise.
(5 Nov 2001 00:00)
- We used JSP's in the standard j2ee environment which went fine, though we could have spent a lot of time using the struts framework and achieved the same result, it's the question, whether to use your own code, or code on top of a nother framework. That's the confusing part (5 Nov 2001 00:00)
- We don't make use of any special features of JSP though. Our site could have been implemented using servlet alone. But using JSP makes things a little bit easier to maintain since you don't need to recompile the sources. (5 Nov 2001 00:00)
- We have successfully used JSP's in 3 production sites.
In the last two cases, we have generated the JSP's dynamically. (5 Nov 2001 00:00)