org/apache/xpath/objects/XObject incompatible with org/apache/xpath/objects/XNodeSet

[duduch_1er]

Hello i tried this code in my stylesheet :

xsl:variable name="items"
select="xsl-usexsl:getEleme ntsBySplitStrin g(.,'i')" />

whith the java function getElementsBySp litString
here the code :

public static Element getElementsBySp litString(Strin g aToSplit, String
aSeparator) throws UseXslException {

// Declaration
int intFound = 0;
// Trace
Log.debug(Const antes.CLE_METIE R, mClassName,
"getElementsByS plitString : DEBUT");

try {
Element items= new Element("ITEMS" );
if (aToSplit != null) {

intFound = aToSplit.indexO f(aSeparator);

while (intFound != -1) {
Element item = new Element("ITEM", aToSplit.substr ing(0,
intFound));
items.addConten t(item);

aToSplit = aToSplit.substr ing(intFound + 1);
intFound = aToSplit.indexO f(aSeparator);
}

if (aToSplit.lengt h() 0){
Element item = new Element("ITEM", aToSplit);
items.addConten t(item);

}
}
// Trace
Log.debug(Const antes.CLE_METIE R, mClassName,
"getElementsByS plitString : FIN");

return items;
} catch (Exception MyE) {
// Signalisation
Log.erreur(Cons tantes.CLE_METI ER, "split : " + MyE.getMessage( ));

// Propagation
throw new UseXslException ("Impossible de formater une chaine de
caractere en un Node");
}
}

and i get the following error :

org/apache/xpath/objects/XObject incompatible with
org/apache/xpath/objects/XNodeSet

Has someone anyidea for resolve this problem ?
thanks

[Joe Kesselman]

du********@hotm ail.com wrote:

org/apache/xpath/objects/XObject incompatible with
org/apache/xpath/objects/XNodeSet

Xalan will recognize objects which implement the DOM's Element interface
as nodes -- but that probably isn't what you're returning (given that
you're using new Element(), which isn't a DOM method.)

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry

[duduch_1er]

Joe Kesselman a écrit :

du********@hotm ail.com wrote:

org/apache/xpath/objects/XObject incompatible with
org/apache/xpath/objects/XNodeSet

Xalan will recognize objects which implement the DOM's Element interface
as nodes -- but that probably isn't what you're returning (given that
you're using new Element(), which isn't a DOM method.)

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry

Thanks for your answer
I used an other solution for resolving my problem, i use a template
instead of java class

i found the following template :

<?xml version="1.0"?>
<xsl:styleshe et version="1.0"
xmlns:xsl="http ://www.w3.org/1999/XSL/Transform"
xmlns:str="http ://exslt.org/strings"
extension-element-prefixes="str">

<xsl:template name="str:split ">
<xsl:param name="string" select="''" />
<xsl:param name="pattern" select="' '" />
<xsl:choose>
<xsl:when test="not($stri ng)" />
<xsl:when test="not($patt ern)">
<xsl:call-template name="str:_spli t-characters">
<xsl:with-param name="string" select="$string " />
</xsl:call-template>
</xsl:when>
<xsl:otherwis e>
<xsl:call-template name="str:_spli t-pattern">
<xsl:with-param name="string" select="$string " />
<xsl:with-param name="pattern" select="$patter n" />
</xsl:call-template>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

<xsl:template name="str:_spli t-characters">
<xsl:param name="string" />
<xsl:if test="$string">
<token><xsl:val ue-of select="substri ng($string, 1, 1)" /></token>
<xsl:call-template name="str:_spli t-characters">
<xsl:with-param name="string" select="substri ng($string, 2)" />
</xsl:call-template>
</xsl:if>
</xsl:template>

<xsl:template name="str:_spli t-pattern">
<xsl:param name="string" />
<xsl:param name="pattern" />
<xsl:choose>
<xsl:when test="contains( $string, $pattern)">
<xsl:if test="not(start s-with($string, $pattern))">
<token><xsl:val ue-of select="substri ng-before($string,
$pattern)" /></token>
</xsl:if>
<xsl:call-template name="str:_spli t-pattern">
<xsl:with-param name="string" select="substri ng-after($string,
$pattern)" />
<xsl:with-param name="pattern" select="$patter n" />
</xsl:call-template>
</xsl:when>
<xsl:otherwis e>
<token><xsl:val ue-of select="$string " /></token>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

</xsl:stylesheet>

and then you can use it in your xsl stylesheet like this :

first we have a treeResult

<xsl:variable name="rtfSplits ">
<xsl:call-template name="split" <xsl:with-param name="string"
select="string( .)" />
<xsl:with-param name="pattern" select="string( ';')" />
</xsl:call-template>
</xsl:variable>

after tranform in nodeset
<xsl:variable name="vSplits" select="xalan:n odeset($rtfSpli ts)"/>

and after we can parse

<xsl:value-of select="$vSplit s/token[1]"/>
<xsl:value-of select="$vSplit s/token[2]"/>
<xsl:value-of select="$vSplit s/token[3]"/>

[Joseph Kesselman]

du********@hotm ail.com wrote:

I used an other solution for resolving my problem, i use a template
instead of java class

That works too. Named templates are often a reasonable substitute for
function calls. XSLT 2.0 makes that easier by adding the ability to
write XSLT code that can be invoked using function-call syntax.

--
Joe Kesselman / Beware the fury of a patient man. -- John Dryden

[Joseph Kesselman]

(I should have added that one major advantage of doing it all in XSLT is
that your stylesheet is, obviously, more portable this way.)