I have refactored JXTG recently so now instructions like jx:for, jx:if
are defined in separate file:
src/block/template/java/org/apache/cocoon/template/template-instructions.xml
Right now we are rendering forms in jxtg using a macro file which is
kind of ugly IMO - see yourself:
Leszek Gawron wrote:
I have refactored JXTG recently so now instructions like jx:for, jx:if
are defined in separate file:
src/block/template/java/org/apache/cocoon/template/template-instructions.xml
Right now we are rendering forms in jxtg using a macro file which is
kind of ugly IMO - see
Upayavira wrote:
Leszek Gawron wrote:
I have refactored JXTG recently so now instructions like jx:for, jx:if
are defined in separate file:
src/block/template/java/org/apache/cocoon/template/template-instructions.xml
Right now we are rendering forms in jxtg using a macro file which is
kind of
just for the record :)
[+1] Yes go for it.
[ ] It's a bad idea - leave jx-macros.xml untouched!
[ ] It's not jx-macros.xml fault. CForms should be changed if current
solution isn't right.
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager
Leszek Gawron wrote:
Upayavira wrote:
Leszek Gawron wrote:
I have refactored JXTG recently so now instructions like jx:for,
jx:if are defined in separate file:
src/block/template/java/org/apache/cocoon/template/template-instructions.xml
Right now we are rendering forms in jxtg using a macro
Leszek Gawron wrote:
I have refactored JXTG recently so now instructions like jx:for, jx:if
are defined in separate file:
src/block/template/java/org/apache/cocoon/template/template-instructions.xml
Right now we are rendering forms in jxtg using a macro file which is
kind of ugly IMO - see
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
I have refactored JXTG recently so now instructions like jx:for, jx:if
are defined in separate file:
src/block/template/java/org/apache/cocoon/template/template-instructions.xml
Right now we are rendering forms in jxtg using a macro file which is