[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Error 80004005 eof - Microsoft XML Parser (September Dro

Subject: RE: Error 80004005 eof - Microsoft XML Parser (September Drop)
From: Andrew Kimball <akimball@xxxxxxxxxxxxx>
Date: Tue, 24 Oct 2000 12:51:54 -0400 (EST)
80004005
Ben,

You wrote:

> <xsl:when test="parent[@class='nav']">

Actually, make that parent::node().  What you have is equivalent to
child::parent (get all child elements that have the name "parent").

> <xsl:when test="../../..[@class = 'vesselSpec'] or ../..[@class =
'vesselSpec']">

Should be <xsl:when
test="parent::node()/parent::node()/parent::node()[@class = 'vesselSpec'] or
parent::node()/parent::node()[@class = 'vesselSpec']">

~Andy Kimball
MSXSL Dev


-----Original Message-----
From: Ben Skelton [mailto:Ben_Skelton@xxxxxxxxxxxxx]
Sent: Saturday, October 21, 2000 5:11 PM
To: xsl-list@xxxxxxxxxxxxxxxx
Subject: Re: Error 80004005 eof - Microsoft XML Parser (September Drop)




Wendell,

Thanks again, it amazes me that someone would take the time to write out
such a
detailed reply - another question for you (or anyone who can answer it)..

I have fixed the following syntax:
<xsl:when test="..[@class='nav']">

to read:
<xsl:when test="parent[@class='nav']">

Which works great but my question is how would I modify the following
statement
to work with MSXML's tighter syntax requirements:

<xsl:when test="../../..[@class = 'vesselSpec'] or ../..[@class =
'vesselSpec']">

Thanks in advance!

_Ben

---------------------------------
Ben M. Skelton
Habanero Studios Limited

604.709.6201 ext. 107
bskelton@xxxxxxxxxxxxx
Visit us on the web: http://www.habaneros.com

Come visit us in the Microsoft booth at eWorld.
October 24-26, 2000
Vancouver Convention & Exhibition Centre


|--------+------------------------->
|        |          Wendell Piez   |
|        |          <wapiez@mulberr|
|        |          ytech.com>     |
|        |                         |
|        |          10/19/2000     |
|        |          10:12 AM       |
|        |          Please respond |
|        |          to xsl-list    |
|        |                         |
|--------+------------------------->
 
>---------------------------------------------------------------------------
-|
  |
|
  |       To:     xsl-list@xxxxxxxxxxxxxxxx
|
  |       cc:
|
  |       Subject:     Re: Error 80004005 eof - Microsoft XML Parser
(September|
  |       Drop)
|
 
>---------------------------------------------------------------------------
-|





Ben,

I can't speak to the MSXML, but....

.[ancestor::sidebar[1]] expands to

self::node()[ancestor::sidebar[1]]

which translates into English as

"Are you a node with an ancestor sidebar that's your first sidebar
ancestor?"

This could be simplified as

ancestor::sidebar[1]

which translates as

"Do you have an ancestor named sidebar that's the first sidebar ancestor?"

But of course, if there are any sidebar ancestors, there's a first one: why
not just ask

ancestor::sidebar "Do you have any sidebar ancestors?"

Now, you may actually mean

ancestor::*[1][self::sidebar]

which is XPath for

"Is your first ancestor element a sidebar?"

Or even better:

parent::sidebar

"Do you have a parent 'sidebar'?"

Yet, to my eye there's nothing syntactically wrong with
".[ancestor::sidebar[1]]". So MSXML may have a bug, even if it's easy to
avoid in this case.

Someone else may be able to speak to differences between the MSXML builds.

Hope that helps!
Wendell

At 01:55 PM 10/19/00 -0700, you wrote:
>I am having a problem with the September drop of the Microsoft Parser.
>...
>In the stylesheet I have the following code, which works fine with the July
>build of the parser but not the September build:
>...
><xsl:when test=".[ancestor::sidebar[1]]">
>     <xsl:choose>
>   <xsl:when test=".[ancestor::sect4
>[1]]">
>   <h4><xsl:apply-templates /></h4>
>   </xsl:when>
>Can anyone please let me know of the correct syntax to use and why this
>build is
>specifically choking on this piece of code. It would be great if anyone
could
>give me their experience with the stability of the two builds in a
production
>environment. (Yeah, I know it is Beta code, but still...)
>
>Thanks in advance,
>
>_Ben
>
>---------------------------------
>Ben M. Skelton
>Habanero Studios Limited
>
>604.709.6201 ext. 107
>bskelton@xxxxxxxxxxxxx
>Visit us on the web: http://www.habaneros.com
>
>Come visit us in the Microsoft booth at eWorld.
>October 24-26, 2000
>Vancouver Convention & Exhibition Centre
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


======================================================================
Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list




 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list




 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.