What you need to understand is that Cocoon pipelines transport SAX events. An <xsp:expr> creates a character data event which will percolate down the pipeline. None of the standard transformers will try to parse these strings into XML again.
ok - thanks for that information.
You have to generate any XML tags as such already in the XSP:
<sql:query>
SELECT id FROM cmdb
WHERE bezeichnung='<sql:substitute-value sql:name="bezeichnung"/>' ...
</sql:query>
i experienced another problem here - on linux this works great but on mac os x the output is:
<sql:query> <sql:substitute-value sql:name=""/> </sql:query>
seems to be a different problem here. problems with a library?
But rather than using XSP-generator|SQL-transformer you should have a look at the esql logicsheet. That allows you to run the SQL inside the XSP and gives more control over conditional output and formatting.
Btw for serious applications I would recommend to use neither SQL-transformer nor ESQL-logicsheet for insert/update/delete operations. These should always be incapsulated in Java classes for proper transaction and exception handling.
i think we'll do it that way - thank you very much.
volker
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
