Joe,

Thanks for the response, casting as Object was not the fix but it was very helpful illustrating the problem although I am at another blind alley.

The object that is being passed in is a DTMNodeIterator which is interesting because if I define the method signature to accept
DTMNodeIterator it won't work but Object will. I will assume that
MethodResolver does not correctly recognize interfaces.


Now if I inspect the DTMNodeIterator, I can see my object in the m_cdtm field which is implemented as a OneShotInterator
but from a coding standpoint, I can't get access too it.


If I try to grab the DTM using the following code
DTMIterator dtmi = nodei.getDTMIterator();
DTM dtm = dtmi.getDTM(dtmi.getCurrentNode());
Where nodei is the casted Object to DTMNodeIterator;


Xalan complains that I can't get the DTM because the DTM Manager has not been set.

My assumption here is that; My original call to pquery returns
a DTM, the extension handler converts this into a DTMNodeIterator
to be consumed by Xalan but the DTMManager is never set on the
DTMNodeIterator so subsequent calls to getDTM() fail.

Any ideas.

Thanks
John G

Joseph Kesselman wrote:




Haven't dug into this so I may be offbase, but here's a SWAG:


The #UNKNOWN suggests that we're treating that value as a non-XML
datatype... and if you're really passing a reference to a DTM rather than a
node, that's correct. Try writing the extension to accept that parameter as
an Object and cast it after recieving it?

______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to