xsl-list
[Top] [All Lists]

Re: [xsl] XML transformation based on parameters

2009-04-15 20:50:42
Yes, Michael. It uses xalan. I know it is a processor specific issue,
but my question is more general:
can XSLT 1.0 use extension functions? I tried with xalan:nodeset or
even with exslt one, but it continues
to return: "Invalid conversion from 'node-set' to..."

thanks,
e.



2009/4/16 Michael Kay <mike(_at_)saxonica(_dot_)com>:

It looks to me as if you are using Xalan as your XSLT processor. The kinds
of object you can pass as parameters depend on the processor you are using,
so you should check the processor-specific documentation (or on a
processor-specific help forum).

Passing a string when a node-set is expected definitely feels wrong; I
wouldn't expect a processor to parse the string by way of an automatic
conversion.


Michael Kay
http://www.saxonica.com/


-----Original Message-----
From: Emiliano Pecis [mailto:emiliano(_dot_)pecis(_at_)gmail(_dot_)com]
Sent: 15 April 2009 23:32
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] XML transformation based on parameters

Hi all,

I'm facing out a conversion issue: when I try to pass a XML
fragment as input parameter to XSLT, it returns the following error:

cannot convert from  'java.lang.String' to 'node-set'

If I try to pass it as xml object it fails with the following error:

cannot convert from
'org(_dot_)apache(_dot_)xmlbeans(_dot_)impl(_dot_)store(_dot_)Xobj$DocumentXobj(_at_)f0e06a'
 to
'node-set'

I have seen some suggestions regarding the use of "extension
functions" of processor, I but I didn't understand what
exactely I should do.

Thanks!
emiliano



2009/4/15 David Carlisle <davidc(_at_)nag(_dot_)co(_dot_)uk>:

Because it must be namespace agnostic! Is there an other way to
ignore namespace prefix?

others have suggested ways of doing this, but the real
answer is not
to be agnostic. The whole point of namespaces is to uniquely
distinguish elements that are in different namespaces.

There are always exceptions but a working assumption would be that
your input design would be better if the param element were
always in
the same namespace (or no namespace). If you have param elements in
different namespaces which must be treated identically, why
are they
in different namespaces?

David


______________________________________________________________________
__ The Numerical Algorithms Group Ltd is a company registered in
England and Wales with company number 1249803. The
registered office
is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The
service is
powered by MessageLabs.

______________________________________________________________________
__


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--