Re: Apache JDBC utils

From:

Lew <lewbloch@gmail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 2 May 2012 16:18:23 -0700 (PDT)

Message-ID:

<31980135.2149.1336000704354.JavaMail.geo-discussion-forums@pbcvn7>

On Wednesday, May 2, 2012 3:03:57 PM UTC-7, Jan Burse wrote:

Lew schrieb:

Scriptlet in JSP is an antipattern.

No,
Java EE 6 calls it even "deprecated".

But advantage of JSP is that it is readily
available. And its actually very old, already
around 1990. But you will not hear some praise
of it from me.

That "but" has nothing to do with the inadvisability of putting scriptlet in JSP.

Nor do the advantages or disadvantages JSP have anything to do with the advisability of scriptlet therein.

The age of JSP is even less relevant. Java is older than JSP and no one is suggesting we not use Java, either.

It has more been a conceptual issue in
matula how to generate XXXBean. But you
can of course plug-in your preffered
template language in the below flow:

+--------+ +-------------+
| DB | | .properties |
+--------+ +-------------+
     | |
     ------ -----
          | |
          v v
         +--------+
         |>>Here<<|
         +--------+
              |
              v
        +------------+
        | XXXBean |
        +------------+

Now I am waiting for a post that says
.properties files are an anti pattern.
Which I can also agree upon. So the
point of the .properties files here is
to provide annotation of the DB schema.

Of course one can also use here anything
else than .properties files that allows
for peristence or input of some
annotations. So the flow is basically
as follows:

+--------+ +-------------+
| DB | | >> Here 2 <<|
+--------+ +-------------+
     | |
     ------ -----
          | |
          v v
        +-----------+
        |>>Here 1 <<|
        +-----------+
              |
              v
        +------------+
        | XXXBean |
        +------------+

Why in the world would someone consider properties files an antipattern?

Don't use scriptlet in JSPs.

--
Lew