Hi,
Another solution to this XMLSpy caused problem is to disable output
formatting for these elements.
Tools/Options:
- from file tab, add an entry to the No output formatting -field:
xsp:attribute
You might also want to include xsl:attribute to this.
---
Mika Fonsén *
Thank you very much for your help, again.
At this point I chose to use XSP action approach as I had already
written one XSP script for the task.
I also updated modules for beginners article on the Wiki to summarize
what I had learned from doing this (last three paragraphs inside Input
Modules
So one could write a proxy action to allow direct
usage of output modules from sitemap?
I wrote a small Wiki-document on modules, that would
have helped me a lot a month back
(http://wiki.cocoondev.org/Wiki.jsp?page=Modules). Is
the information on this page correct? If so, I could
try to work it
Hi,
As far as I know, output modules work only from
modular database actions (set in the descriptor
files). I asked this few messages back and got
confirmation to this. This would be a great feature,
tough :)
I guess I could write a small wiki article on modular
datababase actions and output
Question: What's the best way to pass parameters from
sitemap to mod-db-action? Could output modules be used
to do this?
Case (simplest I could think of): I need to mark a
database row locked when a user in a multi-user
environment wants to edit contents of this row. When
user requests an edit
