Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Date: Mon, 12 Feb 2001 12:55:58 +0100
To: cocoon-users@xml.apache.org
Subject: [C2] XSP without output (and namespace problem)
Message-ID: <20010212125558.A1736@funny.localnet>
Mail-Followup-To: Martin.Man@seznam.cz, cocoon-users@xml.apache.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.12i
From: Martin Man <Martin.Man@seznam.cz>

Hi,
	1) Anyone have any suggestions on how to write sort of servlet-like
generators using XSP, e.g., the generators that would do some things (SQL
update), will not produce any content except HTTP headers  and only
send redirect back to the client using <xsp-response:send-redirect/> according
to the result..., or if I reformulate the question, how is HTTP output stream
and XSP Generator's output stream related, e.g., do I need HTML serializer and
transformers when I know that my XSP is after applying logic-sheets totally
"logic-pure", 

	I know simple java servlet is good for this, but why not to use
XSP+logicsheets to do the task, to persist the uniformity, db access etc.
across various dynamic webpages...
	until now, I have a problem writing such, even simple pure XSP which
won't produce any content, at least it's still producing some whitespaces and
catching them by stylesheet doesn't seem to me as a very elegant sollution
(anyway I haven't got it even working yet :(())

	2) And the other question is:
	Do I need to declare all xmlns: napespaces in <xsp:page> starting 
element
even those that my XSP is not reffering to directly

example:
<xsp:page...
	xmlns:xsp="..."
	xmlns:mytaglib="..."
>

</xsp:page>

after applying my logicsheet, all my tags are transformed into <esql:, <log:,
<xsp-request:, <whatever-else:

I think that mytaglib.xsl should than take care of adding appropriate xmlns:
attributes into <xsp:page> tag when transforming my tags, e.g.,

example

after the application of my logicsheet the page should look like

<xsp:page...
	xmlns:xsp
	xmlns:esql
	xmlns:xsp-request
	...
	...
>

therefore saving the knowledge of the XSP developer to name all those
namespaces directly in the .xsp source, dont' even talking about that the
developer doesn't know them...

until now after looking at esql.xsl no such thing is being done, so the
question is, is this the transformer's task, or logicsheet's developer's task

sory for typing that much words,

cocoon enjoyer,
martin

-- 
-------------------------------------------------------------------------------
"Only dead fish swims with a stream"
gpg_key_fingerprint: 2CC0 4AF6 92DA 5CBF 5F09  7BCB 6202 7024 6E06 0223
home_page: http://home.zcu.cz/~mman