> The great questions are:
> a) why does mbstowcs(..) fail on 4-STABLE bu not on 5.1 ?
> b) [more important] how to correctly recover from this error path ?
>I do not ocnsider it a FreeBSD specific problem but simply an
>unhandled error path in xalan.
It's strange that
> From: "Bjoern A. Zeeb"
> The great questions are:
> a) why does mbstowcs(..) fail on 4-STABLE bu not on 5.1 ?
> b) [more important] how to correctly recover from this error path ?
> I do not ocnsider it a FreeBSD specific problem but simply an
> unhandled error path in xalan.
Ran i
On Thu, 19 Jun 2003 [EMAIL PROTECTED] wrote:
Hi,
(hope you do not get it twice - something ate the first mail :(( )
> > There will be at least one problem with
> > xercesc_2_3::XMLTransService::makeNewTranscoderFor
>
> There have been numerous commits since 1.5 was released, and a fix fo
> "Colin" == Colin Paul Adams <[EMAIL PROTECTED]> writes:
Colin> If I add both -XD and -DOM it reproduces. Or just -DOM. Not
Colin> with -XD alone though.
Should I enter this in bugzilla? Do you want me to attach the source
document (c. 400KB) and stylesheet?
--
Colin Paul Adams
Pr
> >> The actual method being called is:
> >>
> >> int transform (const XalanParsedSource &theParsedXML, const
> >> XalanCompiledStylesheet *theCompiledStylesheet, const
> >> XSLTResultTarget > &theResultTarget)
> >>
> >> The compiled stylesheet was compiled from an X
> "david" == david n bertoni <[EMAIL PROTECTED]> writes:
david> OK, this is a bug, because we should not let a DOMException
david> through -- it should be caught by the wrapper code and
david> translated into a XalanDOMException.
>> The actual method being called is:
>>
> Agghhh!
> This reply-not-going-to-the-list business gets me every time!
>
> Well, by trial and error, I discovered it's a DOMException (code 14 -
> namespace error).
OK, this is a bug, because we should not let a DOMException through -- it
should be caught by the wrapper code and translated
Hi Thomas,
Yes, generic XSLT questions are best asked on the Mulberry list. Not only
will you get a faster response there, but you will likely get multiple
responses, which may help you figure out the best way to do something.
In XSLT 1.0, any xsl:variable element that contains content create
Agghhh!
This reply-not-going-to-the-list business gets me every time!
Well, by trial and error, I discovered it's a DOMException (code 14 -
namespace error).
Why I'm getting such an error, I'm not sure. There's certainly nothing
wrong with the namespace declarations in either the source document o
I'm willing to contribute what few spare cycles I have, too, as I've
already done some minimum work to get XML::Xalan working with Xalan C++
1.4 (and soon hope to have it working with 1.5).
I'm not a committer or anything, just an interested end-user and someone
who's tried to help get the ball ro
Thanks to all who pointed out the subtleties of the difference between
getting back a result tree fragment rather than true boolean output.
So here's my next question:
Is there a way to achieve the same effect (i.e., not getting a result
tree fragment) if you want to set a variable conditionally?
Hi Colin,
If you can reproduce it with an isolated test case, you can create a
Bugzilla report and attach the source document and stylesheet. These
things are much easier to debug on Windows because you can set the debugger
to break when an exception is thrown.
Otherwise, this will be very h
Hi Colin,
You should not get any exception from any of the
XalanTransformer::transform() member functions. If you are getting one,
it's not one we know about. What platform are you using? If it's Win32,
then access violations will come through as exceptions.
Dave
|-+
What types of exceptions might be thown by XalanTransformer's
transform method(s)?
I'm getting an exception - I can catch it with ... - but I'd like to
get something more specific, so i can get an error message from it.
--
Colin Paul Adams
Preston Lancashire
귀하의
허락없이 홍보성 전자 우편을 보내게 된 점 정중히 사과
드립니다. 본 메일은 정보통신망 이용촉진 및 정보보호
등에 관한 법률 50조에 의거한 [광고]메일입니다. 귀하의
전자우편주소는 인터넷 상의 공개된 장소에서
습득하였으며, 저희는 귀하의 전자우편 주소외 어떠한
Title: www
16 matches
Mail list logo
