> Thanks for the Reply Dave,
> I got the problem. I was trying to pass istream with default namespace.
> Now, I changed it and it works fine.
>
> using namespace std;
>
> //Result Target.
> XalnDOMString asTransformedOutput;
> DOMStringPrintWriter aDOMStrPrintWriter(asTransformedOutput);
> XSLTResultTarget theResultTarget(&aDOMStrPrintWriter);
>
> //InputParsed Source.
> std::istringstream is(a_sXMLStr);
> XSLTInputSource theInputSource (&is);
>
> // Do the transform.
> int theResult = theXalanTransformer.transform(theInputSource,
> m_pCompiledStylesheet, theResultTarget);
> std::cout << "theResult :" << theResult << endl;
>
> This code works. I have a question here.
> Will Xalan Code flushes the instream after using it or do I need to do
that.
> The reason for asking this is if I use istringstream 100 threads are
> failing.
> (but fine with 75 threads).
> But going through fine with XSLTInputSource("birds.xml").
>
I don't know what flushing an input stream means. We definitely flush the
output stream, but flushing the input stream doesn't make sense. Can you
explain what you mean by "flushing?"
This sounds like a bug/limitation in the compiler's library. Since you
don't say what "failing" means, it's pretty hard to diagnose this. Using a
system ID for the input file is a slightly different code path and doesn't
use iostreams.
> Another question I have is I have to convert output XalnDOMString to
> char*
> The code which previously worked for me is not working now.
>
> aOutputStream << a_srXalanDOMString;
I have no idea what "not working now" means. Does it compile? If not,
what's the error message? Do you just need to include the header file that
declares operator<<() for XalanDOMStrings? (DOMStringHelper.hpp)
If it compiles, is it crashing, or is there just no output?
Dave
