Where to learn JSP

I am a Forms Designer (Adobe Acrobat) for a credit union, and I was just hired by our Lotus Notes Domino folks to develope forms using BEA AquaLogic. The hiring manager says that he wants me to start with working on the front end of things. He wants me to learn Java, but not right away. Instaed he wants me to begin with JSP pages. I hope he will allow me to have Dreamweaver as one of my tools for forms developemnt.

I have little programming experience even with the 200 or so Acrobat eFroms I have developed; which contain a fair amount of Javascript for added functionality. I am a graphic designer of sorts b/c I work with Quark Express, Adobe illustrator and Photoshop. So this will be quite a jump to the other side!

I looked on Amazon and they have "HTML & XHTML: The Definitive Guide (6th Edition) by O'reilly." What about a book like "Java for the Web with Servlets, JSP, and EJB: A Developer's Guide to J2EE Solution, by New Riders?" Would this be too advanced?

Michael

mikes1212a at 2007-7-29 14:10:32 >

Use online, the very best resource and develope your jsp using IBM Websphere/RAD tool. You will learn things very easily.

skp71a at 2007-7-29 14:10:32 >

Hi,

Refer Complete Reference basically and learn other books via online itself, lot of good books available for jsp ,

whatever it is, with out practical you cant improve your skills, so side by side do more on jsp

drvijayy2k2a at 2007-7-29 14:10:32 >

That roseindia article is funny. The introduction is OK, but when it comes to real code ...

public boolean connect() throws ClassNotFoundException,SQLException {

Class.forName(dbDriver);

dbCon = DriverManager.getConnection(dbURL);

return true;

}

When does it return false? What's the benefit of returning true?

public ResultSet execSQL(String sql) throws SQLException {}

Passing Statements or ResultSets around as parameters or return types is bad design.

The code also doesn't close the connection, the statement, nor the resultset in case of exceptions, which causes memory and resource leaks.

And this is also funny:return (r == null) ? null : r;

they explained it as:

What this statement does is that, if the value of r is null, it returns a null value and if it is a non null value, it returns the value of r. Though this statement seems redundant, it is useful for preventing any errors that might occur due to improper value being set in r.

So, if r is null, then return null .. What's the difference between null and null?

The same applies to:return (r == 0) ? 0 : r;

Further on there is no clear separation in the code. The "data tier" is spread over the "bean" and the scriptlets. Yes, scriptlets.

Bad article.

BalusCa at 2007-7-29 14:10:32 >

Agree, the books written by Bert Bates and Kathy Sierra are very pleased to read.

http://www.amazon.com/Head-First-Servlets-JSP-Certified/dp/0596005407

BalusCa at 2007-7-29 14:10:32 >