Cocoon 2.1.11 and XSLTC

[Laurent Medioni <lm...@odyssey-group.com>]

Hi,

is it reasonable to set the default xslt processor to XSLTC in
cocoon.xconf ?

It seams to provoke some weird side effects in my case...

Would it be a "common" change of the standard configuration ?

(or is this why the standard xconf does not propose it ;))

 

Thanks.


____________________________________________________________

� This email and any files transmitted with it are CONFIDENTIAL and intended
  solely for the use of the individual or entity to which they are addressed.
� Any unauthorized copying, disclosure, or distribution of the material within
  this email is strictly forbidden.
� Any views or opinions presented within this e-mail are solely those of the
  author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
� An electronic message is not binding on its sender. Any message referring to
  a binding engagement must be confirmed in writing and duly signed.
� If you have received this email in error, please notify the sender immediately
  and delete the original.

RE: Cocoon 2.1.11 and XSLTC

[Alfred Nathaniel <an...@apache.org>]

On 2008/08/29 at 09:32 "Laurent Medioni" <lm...@odyssey-group.com> wrote:

> is it reasonable to set the default xslt processor to XSLTC in
> cocoon.xconf ?
> It seams to provoke some weird side effects in my case*
> Would it be a *common* change of the standard configuration ?
> (or is this why the standard xconf does not propose it ;))

I can confirm that XSLTC can be used with Cocoon 2.1.x.  However, you
first have to check your stylesheets for XSLTC compatibility.  The XSLTC
engine and interpreted Xalan have little more in common than being part
of the same Apache project.

XSLTC flags a number of XSLT constructs are errors, which pass through
Xalan without problems.  One example is to call a non-existing template
name from a template which is never executed.

First you should use the command line tool "xalan -xsltc" to check that
your stylesheets compile without error, and then try again with Cocoon.

HTH, Alfred.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

RE: Cocoon 2.1.11 and XSLTC

[Derek Hohls <DH...@csir.co.za>]

Maybe not so common... but if you want a response from the
developers - who are very active on this list - you may need to
post something more specific (preferably with error logs) than
"seams to provoke some weird side effects".

>>> On 2008/08/29 at 09:32, in message
<19...@mail4.oams.com>, "Laurent
Medioni" <lm...@odyssey-group.com> wrote:

Hi,
Should I transfer this question to the Cocoon developers list ?
I thought I could get some answers from user experiences* I cannot
believe everybody uses the default configuration ;)
Or is it so a dumb question* ? ;)
Thanks.
 


From:Laurent Medioni [mailto:lmedioni@odyssey-group.com] 
Sent: mardi, 26. août 2008 11:08
To: users@cocoon.apache.org 
Subject: Cocoon 2.1.11 and XSLTC

 

Hi,
is it reasonable to set the default xslt processor to XSLTC in
cocoon.xconf ?
It seams to provoke some weird side effects in my case*
Would it be a *common* change of the standard configuration ?
(or is this why the standard xconf does not propose it ;))
 
Thanks.


-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

RE: Cocoon 2.1.11 and XSLTC

[Laurent Medioni <lm...@odyssey-group.com>]

Hi,

Should I transfer this question to the Cocoon developers list ?

I thought I could get some answers from user experiences... I cannot believe everybody uses the default configuration ;)

Or is it so a dumb question... ? ;)

Thanks.

 

________________________________

From: Laurent Medioni [mailto:lmedioni@odyssey-group.com] 
Sent: mardi, 26. août 2008 11:08
To: users@cocoon.apache.org
Subject: Cocoon 2.1.11 and XSLTC

 

Hi,

is it reasonable to set the default xslt processor to XSLTC in cocoon.xconf ?

It seams to provoke some weird side effects in my case...

Would it be a "common" change of the standard configuration ?

(or is this why the standard xconf does not propose it ;))

 

Thanks.


____________________________________________________________

* This email and any files transmitted with it are CONFIDENTIAL and intended
solely for the use of the individual or entity to which they are addressed.
* Any unauthorized copying, disclosure, or distribution of the material within
this email is strictly forbidden.
* Any views or opinions presented within this e-mail are solely those of the
author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
* An electronic message is not binding on its sender. Any message referring to
a binding engagement must be confirmed in writing and duly signed.
* If you have received this email in error, please notify the sender immediately
and delete the original.


____________________________________________________________

• This email and any files transmitted with it are CONFIDENTIAL and intended
  solely for the use of the individual or entity to which they are addressed.
• Any unauthorized copying, disclosure, or distribution of the material within
  this email is strictly forbidden.
• Any views or opinions presented within this e-mail are solely those of the
  author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
• An electronic message is not binding on its sender. Any message referring to
  a binding engagement must be confirmed in writing and duly signed.
• If you have received this email in error, please notify the sender immediately
  and delete the original.