Older blog entries for mglazer (starting at number 200)

21 Aug 2002 »

Why use servlets and not beans?

Don't ask me. I use Beans and not servlets.

Servlets and beans are both java Classes. Beans follow a strict class structure.

As far as I can tell Servlets are cool CGI but still have the CGIs secondary nature. In other words you can not easily include a servlet and thus its output in the middle of a JSP page, you would have to use a load expensive SSI call and page.

Beans on the other hand are much more modern and code friendly, meaning no output with code. It allows JSP to be a true web scripting langauge by the pure and true separation of code and design.

Th availability of code within output is smart and useful but also not wise to always be on.

Of course people should be allowed to mix the two but it should be an option that can be turned off for production and live environments.

20 Aug 2002 »

Sun has a great quick start guide to using JSP:

http://java.sun.com/products/jsp/docs.html

Next: Beans Versus Servlets:

Why, Where, Who, Which, and of course When...

20 Aug 2002 »

The Difference:

Paranoia is not the fact that people are looking at or talking about you.

Instead, paranoia is being scared by the truth or untruth that people are looking at or talking about you.

You see, a non-paranoid person is not scared if people are looking or talking at or about them, only a truly paranoid person is.

20 Aug 2002 »

Complete Java Bean; Hello World:

BEAN:

package com.taglib.wdjsp.fundamentals;
public class HelloBean implements java.io.Serializable {
  String name;

   public HelloBean () {
    this.name = "World";
  }
  public String getName () {
    return name;
  }
  public void setName (String name) {
    this.name = name;
  }
}

JSP:

<HTML>
<BODY>
<jsp:useBean id="hello" class="com.taglib.wdjsp.fundamentals.HelloBean"/>
<jsp:setProperty name="hello" property="name" param="name"/>
Hello, <jsp:getProperty name="hello" property="name"/>!
</BODY>
</HTML>

20 Aug 2002 »

A search engine result that displays only the links in the results of your query you have already visited.

20 Aug 2002 »

The complete JSP tutorial

20 Aug 2002 »

Examples from Java Servlet Programming, 2nd Edition (Online)

Via ~ http://www.servlets.com/

Oh and also free Java Web Hosting

I just got my account:

http://www.mycgiserver.com/~jlog/

20 Aug 2002 »

Java Bean and SQL example with JSP page:

http://www.roseindia.net/jsp/usingbeansinjsp.htm

20 Aug 2002 (updated 20 Aug 2002 at 13:09 UTC) »

Java/JSP templating Engine:

http://javaby.sourceforge.net/

19 Aug 2002 »

A resume should have no Objective, Skills, Interests.

It should only contain, besides the standard header and footer, a Descening dated list of relatable previous employment history to the Job you are sending the resume (with a detailed and specific cover letter) to.

Each related Employment history item should only contain 4 bullets. The bullet categories must be:

1. Hardware used (i.e Windows NT Workstation and UNIX Apache Web Server).

2. Software Used (i.e. Widnows Office Programs, Java, jhtml, JSP, Servlets, Beans, PHP, MySQL, javaScript, Html, CSS, XML)

3. Responsibilites: (i.e. Job title and its requirements e.g. Html Production Specialist: in charge of mass producing hundreds of co-branded and vortal style architecture websites).

4. Accomplishments (i.e. High points of interest; Created a business wide single template creation engine for all Vortal replicated websites to be built upon saving thousands of work hours).

Lastly, but not as important, a short parapgraph for this job history item summarizing your experience as a whole.

The number of resume pages do not matter nor does anything else, except the above mentioned, matter for computer programmers.

191 older entries...