Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#20 element name is a zero-length string

open
nobody
None
5
2012-10-08
2011-06-28
Anonymous
No

I am getting XTDE0820: Supplied element name is a zero-length string when i try to execute the <xsl:element name="{local-name()}">. Look like the element name does not allow to pass the parm. An Xslt i wote is works in XMLSpy but is it gives me bellow error message.

I wrote the xslt that extract the payload from the SOAP Message and remove the namespace from all elements.

Error Message

Error at xsl:element on line 8
XTDE0820: Supplied element name is a zero-length string
at xsl:for-each (#7)
processing /soapenv:Envelope/soapenv:Body[1]/text()[1]
at xsl:for-each (#6)
processing /soapenv:Envelope/soapenv:Body[1]
at xsl:for-each (#5)
processing /soapenv:Envelope
buildNumericErrorCode
keySA.ROUTE.ROUTE_CONTROLLER.index
location1.1.101.1
2011-06-27 17:53:52,147-0400 ERROR sdphost 1.1.101.1.1 SA ROUTE R

Discussion

  • Michael Kay
    Michael Kay
    2011-06-28

    This is quite the wrong place to post requests for Saxon help. Please in future use the saxon-help mailing list or forum. And please supply sufficient of your code to see what's going on.

    The stack trace here suggests strongly that at the point of failure the context item is a text node, in which case local-name() will indeed be a zero-length string. My guess is that it worked on Altova because they use the Microsoft XML parser which (unlike every other parser) strips whitespace-only text nodes by default.

     
  • Amit
    Amit
    2011-06-28

    This is not related to white-space issue, it is related to can't pass the parameter to Element name. i did send the detail information to saxon-help mail. If you need anymore info please let me know.

    Thank you in advance for your help!

     


Anonymous


Cancel   Add attachments