Closed Thread Icon

Topic awaiting preservation: fundamental JSP questions! (Page 1 of 1) Pages that link to <a href="" title="Pages that link to Topic awaiting preservation: fundamental JSP questions! (Page 1 of 1)" rel="nofollow" >Topic awaiting preservation: fundamental JSP questions! <span class="small">(Page 1 of 1)</span>\

Perfect Thunder
Paranoid (IV) Inmate

From: Milwaukee
Insane since: Oct 2001

posted posted 11-14-2003 12:52

Got a client. The client wants a fairly minor web app made. Their customers enter some data, upload a picture, we generate a PDF proof to them, they okay it, a print-ready PDF goes to our prepress guys, end of story. I could do this in a day with PHP.

Trouble is, they're a heavy Mac house, and one thing about Macs is that if you run a Mac shop, you have to use FileMaker. And if you have to use FileMaker, you immediately buy into a bunch of other stuff, including the Lasso server-side scripting language.

They're using FileMaker -- that's a non-negotiable -- and they're serving everything from WebStar -- also non-negotiable. That means I'm limited to things which play nicely with both of those, which means Lasso or Java/JSP. Tough choice, huh?

So my question is this -- should I stick with your basic JSP, servlets, Tomcat, all that... or should I start with J2EE from the get-go? If this simple application convinces the bigwigs, we might end up embarking on a big project where customers would be able to do a great deal online, even to the point of custom-designing entire products via the web app. Java seems like the obvious choice, since if I run into something that can't happen via JSP, I can put in a whole Java applet and do virtually anything.

Oh, and I've already checked the FAQ link to Sitepoint's Java section, and it's already helped a lot, but if anyone has further links, roll 'em in! This could become a full-time job if I look enough like I know what I'm doing.

Cell 1250 :: :: Illustrator tips

Nervous Wreck (II) Inmate

From: Indianapolis, In USA
Insane since: Jan 2002

posted posted 11-14-2003 14:19

Walk before you run.
Start with the basic jsp stuff. If you have any previous scripting experience it''s a piece of cake.

Few problems in life can't be solved by chocolate

Tyberius Prime
Paranoid (IV) Mad Scientist with Finglongers

From: Germany
Insane since: Sep 2001

posted posted 11-14-2003 14:59

all I can say is that J2EE is big... it's got a whole methodolgy attached to it, and will take time to learn.

Bipolar (III) Inmate

From: New Jersey, USA
Insane since: Jul 2003

posted posted 11-14-2003 15:40

It is funny that you say J2EE is big. J2EE encompasses alot like EJB but a full blown J2EE application can be just JSP.

Yes, JSP...Tomcat would be great. Java is fairly easy to learn and will offer alot of opportunities to scale and expand the application.

Perfect Thunder
Paranoid (IV) Inmate

From: Milwaukee
Insane since: Oct 2001

posted posted 11-14-2003 23:03

Thanks for the info so far... what Rhino and TP said fits in with what little I've learned so far, that although J2EE is a framework which requires its own methodology, a basic J2EE app can be plain ol' JSP.

Even though I'm starting small, I already have Java experience and server-side scripting experience, and this project could balloon into some serious stuff. I'm going to go with J2EE from the get-go, just in case.

Cell 1250 :: :: Illustrator tips

« BackwardsOnwards »

Show Forum Drop Down Menu