Return-Path: <kevin@webslingerz.com>
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 31122 invoked from network); 22 Nov 2000 14:19:02 -0000
Received: from unknown (HELO midgard.darkcanvas.com) (root@216.27.72.102)
  by locus.apache.org with SMTP; 22 Nov 2000 14:19:02 -0000
Received: from snorlax.webslingerZ.com (IDENT:root@[216.27.72.106])
	by midgard.darkcanvas.com (8.9.3/8.8.7) with ESMTP id JAA07335
	for <cocoon-users@xml.apache.org>; Wed, 22 Nov 2000 09:01:19 -0500
Received: from localhost (IDENT:kevin@localhost [127.0.0.1])
	by snorlax.webslingerZ.com (8.9.3/8.8.7) with ESMTP id JAA01739
	for <cocoon-users@xml.apache.org>; Wed, 22 Nov 2000 09:18:26 -0500
Date: Wed, 22 Nov 2000 09:18:26 -0500 (EST)
From: Kevin Sonney <kevin@webslingerz.com>
X-Sender: kevin@localhost
To: cocoon-users@xml.apache.org
Subject: Re: logic in esql:no-results tag
In-Reply-To: <20001122122945.6495.qmail@web2006.mail.yahoo.com>
Message-ID: <Pine.LNX.4.21.0011220913290.1366-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

On Wed, 22 Nov 2000, Drasko Kokic wrote:
> I got that ... thanks ... I just have problem getting
> some logic inside. My sample looks like:

Unless the <xsp:expr> code is returning a string, they are probabyl better
handled with <xsp:logic> tags.

> Is this okay?  It should work on any Oracle db.

I'd replace the xsp:expr tags with xsp:logic, as xsp:expr expects some
sort of data return to put into the docuemnt. Since the calls you make
seem to indicate loggin, these are probabyl best handled with xsp:logic.

> What is &connection_params; in your code

When I have *LOTS* of docuements that use the same database connection
code, I put all the connection details into an external doc, then map that
to an entity, like so :

<!DOCTYPE xsl:stylesheet [
<!ENTITY connection_params SYSTEM "db_defs.xml">
]>

That way, I only have to type 

&connection_params; 

when I need the username, password, jdbc url, etc.

This also has the advantage of allowing you to put the connection
definitions document in a secure place, that only apache/jserv or
apache/tomcat can access - keeping the users out of the database
connection information.

-- 
+-------------------------------------------+
| Kevin Sonney        kevin@webslingerZ.com |
| Systems Programmer    www.webslingerZ.com |
+-------------------------------------------+

"The weakest link in any civil rights case is always the
defendant. Imagine being a lawyer and getting a call from me. That's why I
try to, uh, behave myself." - Hunter S. Thompson