Sylvain Wallez wrote:
<instruction name="call"
targetNamespace="http://apache.org/cocoon/templates/jx/1.0";
class="org.apache.cocoon.template.jxtg.instruction.StartCall"/>
<instruction name="withParam"
targetNamespace="http://apache.org/cocoon/templates/jx/1.0";
class="org.apache.cocoon.template.jxtg.instruction.StartParameterInstance"/>
<instruction name="attribute"
targetNamespace="http://apache.org/cocoon/templates/jx/1.0";
class="org.apache.cocoon.template.jxtg.instruction.StartAttribute"/>
</component>
This exactly what I called "frightening". Imagine a newbie seeing this
in cocoon.xconf :-)
looks less frightening now (and is placed outside cocoon.xconf):
<instructions targetNamespace="http://apache.org/cocoon/templates/jx/1.0";>
<instruction name="template"
class="org.apache.cocoon.template.instruction.Template"/>
<instruction name="forEach"
class="org.apache.cocoon.template.instruction.ForEach"/>
<instruction name="if" class="org.apache.cocoon.template.instruction.If"/>
<instruction name="choose"
class="org.apache.cocoon.template.instruction.Choose"/>
<instruction name="when"
class="org.apache.cocoon.template.instruction.When"/>
<instruction name="otherwise"
class="org.apache.cocoon.template.instruction.Otherwise"/>
<instruction name="out" class="org.apache.cocoon.template.instruction.Out"/>
<instruction name="import"
class="org.apache.cocoon.template.instruction.Import"/>
<instruction name="set" class="org.apache.cocoon.template.instruction.Set"/>
<instruction name="macro"
class="org.apache.cocoon.template.instruction.Define"/>
<instruction name="evalBody"
class="org.apache.cocoon.template.instruction.EvalBody"/>
<instruction name="eval"
class="org.apache.cocoon.template.instruction.Eval"/>
<instruction name="parameter"
class="org.apache.cocoon.template.instruction.Parameter"/>
<instruction name="formatNumber"
class="org.apache.cocoon.template.instruction.FormatNumber"/>
<instruction name="formatDate"
class="org.apache.cocoon.template.instruction.FormatDate"/>
<instruction name="comment"
class="org.apache.cocoon.template.instruction.Comment"/>
<instruction name="call"
class="org.apache.cocoon.template.instruction.Call"/>
<instruction name="withParam"
class="org.apache.cocoon.template.instruction.ParameterInstance"/>
<instruction name="attribute"
class="org.apache.cocoon.template.instruction.Attribute"/>
</instructions>
Those evil tag libraries. Still Sylvain kicked forms presentation
rocket high (respect!) using jxtg and jx-macros.xml and IMO we should
replace macro file with java instructions - it's core functionality
and looks like cforms - jxtg mariage is tightening.
Hmm... their respective parents have to meet beforehand ;-)
This leads to a question: obviously, cforms-specific tags shouldn't be
defined in the template block, and so there should be a way for the
cforms block to provide the additional tag definitions to jxtg. How can
we do that? The return of XSP's taglib-per-namespace?
I am far too less experienced in this area to propose a solution I won't
be prosecuted for.
cformsDummy is because there's no <jx:call> to call arbitrary code
without JXTG SAXing the result.
If you decide to rewrite jx-macros, please either do it in a temporary
newjx-macros file, that will later replace the current one, or test
carefully form samples before committing!!
Of course. The main questions is still: am I allowed to? I'll start a
quick vote because there are strong emotions around this.
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
