Re: Fw:

In order of likelihood, I would guess (it's a bit of a blind guess):
  1) There is a problem with the context in which you are using the
     fragment I posted.  For example, you are looking up an attribute
     which doesn't exist in the map; there should really be more
     error-checking for such cases, probably involving breaking the big
     select down into several variable assignments and testing each step
     for success before proceeding.
  2) There is a bug in your JVM or XSL processor.  I tested with 
     XT 0.5 and Saxon 5.1 with IBM JDK 1.1.8 on Linux, and the
results        were correct given my test input.
  3) Something got garbled in transmission.  I'll e-mail you the test
     data I used and the XSL script as attachments off-list in case 
     that is what happened.
  4) (Just occurred to me) you are using an XSL processor which doesn't
     implement document('') correctly.

It's important always to say which XSL processor you are using when
asking questions on this list.

 Steve

mohamed wrote:
> 
> Thanks Steve, I like your solution a lot but for some reason it's giving me
> a
> java.net.MalformedURLException: : java.lang.StringIndexOutOfBoundsException:
> String index out of range: 0
> 
> at this line
> >       <xsl:element name="{document('')/*/xsl:template[@name='attr-map']
> >                           /map[@attr=name($attr-set[1])]/@elem}">
> 
> any ideas?

-- 
----------------------------------------------------------------------
Steve Tinney                                        Babylonian Section
                                 *   University of Pennsylvania Museum
stinney@xxxxxxxxxxxxx                          Phila, PA. 215-898-4047


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