The Dreaded Request failed - status=500 on AJAX in CForms

[Stewart, Gary]

Hi people, 

I'm using Cocoon 2.1.8 (which is obviously using a different AJAX version from 
the current one) and I've discovered that there is some way to get it so it 
constantly fails updating the AJAX stuff for all users across all pipelines. 
I'm not sure how it happened. I've seen it a couple of times during dev when I 
was updating the sitemap. A restart would fix the problem. However I only 
recently saw it on the production system. Has anyone seen anything like this?

It looks like, to go into more detail, that the results are processed as HTML 
rather than XML (if you display the returned error you see that this is the 
case) therefore presumably the bu:update part is failing as it is wrapped in 
HTML. It looks likely that AJAX Request is and causing the selector to evaluate 
false as my form processing pipelines have something like 

map:select type=ajax-request
 map:when test=true
  map:serialize type=xml/
 /map:when
 map:otherwise
   map:call resource=session-process /
   map:call resource=default-transform /
   map:serialize type=html/
 /map:otherwise
/map:select

I'd try swapping the logic (so it tests for false and defaults to returning 
XML) but as I can't recreate the bug I don't know if that'd work.

I'll go check the patches for later versions of Cocoon though I know we 
switched to DOJO so we might not be using the same logic at all (I had a couple 
of problems with DOJO in 2.1.9 so I left upgrading, might be worth trying again 
with 2.1.10 though).

Thanks,

Gary

*
The information contained in this message may be confidential or 
legally privileged and is intended for the addressee only. If you 
have received this message in error or there are any problems 
please notify the originator immediately. The unauthorised use, 
disclosure, copying or alteration of this message is 
strictly forbidden.
*


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Unique XSL transform error that only occurs with Cocoon and Java 1.5

[footh]

I am using this identity transformation under Cocoon
2.1.9 and Java 1.5:

  xsl:template match=*
   xsl:element name={name()}
namespace={namespace-uri()}
 xsl:apply-templates select=@*|node() /
   /xsl:element
  /xsl:template
  xsl:template match=@*
xsl:attribute name={name()}
namespace={namespace-uri()}
 xsl:value-of select=. /
/xsl:attribute
  /xsl:template

The template is designed to remove namespaces. 
Anyway, under Java 1.4, everything works fine. 
However, when I switched to Java 1.5, I receive a
TransformerException. 

I have verified that the template works fine with Java
1.5 and the xalan transformation engine.  For some
reason, when Cocoon is involved, the error occurs.

Does anyone have any suggestions about where I would
start looking to figure out what is going on?  Can
anyone with a similar environment run this template to
verify they have the same problem?

Regards,

JF



 

Any questions? Get answers on any topic at www.Answers.yahoo.com.  Try it now.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Unique XSL transform error that only occurs with Cocoon and Java 1.5

[Bertrand Delacretaz]

On 2/7/07, footh [EMAIL PROTECTED] wrote:


...Does anyone have any suggestions about where I would
start looking to figure out what is going on?...


If the exception gives no clue as to what's going wrong, I'd start
commenting out parts of the transform to see exactly what causes it to
fail.

-Bertrand

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cform in portal

[許議中]

Hi!

does anybody know how to put cform to portal in 2.1.10.

Best Regards

johnson

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]