El mar, 14-02-2006 a las 13:50 -0500, [EMAIL PROTECTED] escribió: > On 2/14/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > > I tried today an example found at > > http://cocoon.apache.org/2.1/userdocs/flow/jxtemplate.html > > in an usecase view. > > > > I added: > > <jx:macro name="d"> > > <tr><td></td></tr> > > </jx:macro> > > > > and then > > <d/> > > > > to the uscase view but it will not transformed like described in above URL. > > > > Did somebody used jx:macro with success? > > We may need more information to understand. Please add a stripped > example that reproduces the issue. >
Just add the above to *any* usecase in 1.4. > When I used JX with Flow, I discovered (what I consider a design flaw) > that Cocoon's JX finishes by serializing with a transformation so all > angle brackets are converted to "<" and ">". That sounds really weird, did you report that to cocoon-dev? > This made it very > difficult to return XML and HTML from JX. If it happens before > another transformation, the ruined tags could be ignored. In the jx-generator or transformer or both? > Add a > "copy everything" match to your XSL, or add a breakpoint immmediately > after the JX, to test if what you expect to be XML is being processed > as ugly text. Actually jx should interpret the <d/> element as call for the macro not xsl. Thanks for your thoughts. salu2 > solprovider > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
