Re: Understanding Object Usage

James Perkins skrev:

EJB's will be avoided then ;-)

I do have a ConnectionBean I have created. It works in conjunction with a

Just refactor it, if you need to. If you do not know how, put the cursor on the identifier "ConnectionBean" and right-click, Refactor, Rename. This will rename the class, i.e. the java file, and all the places in the source where it is used.

A better name might be "FooBarConnection" where FooBar is the _system_ you need to connect to, not the machine or the operating system. This will also make it clearer in your mind what actually belongs in the class.

I just wanted to make sure to get all my ducks in a row before I start
deploying a bunch of Java stuff. When learning how to write JSP's I made
quite a mess at the last place I worked on an intranet site so I really want
to avoid that again. I would be embarrased for anyone to actually see some
of that code.

I believe that the reason JSP's are hard to write well, is the fact that you mix two languages - one for presentation and one for business logic - and that it is extremely easy to blend the two together, and THEN you have the mess.
I have found that it creates a reasonable code base to use taglibs only in JSP pages (hence move the presentation stuff in CSS), and use JavaServer Faces to do the work. It is however a bit uphill to get working properly.

(and your basic problem was you put your initial prototype in production ;-) )

Thank you all for your comments and suggestions. I'm glad to know for the
most part I wasn't too far off in my though pattern with this.

You are most welcome. Learning new programming paradigms is not easy on your own.

/Thorbjørn