You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by cbowditch <bo...@hotmail.com> on 2008/01/24 18:44:57 UTC
unexpected SAX character event
I have some XML like:
<OtherRecord2000>
<AccountNumber>R000239125</AccountNumber>
<SaleOfDeclineCompany/>
<CustomerReferral>Y</CustomerReferral>
<CustomerReferralCode>07</CustomerReferralCode>
<CustomerReferralAction>10</CustomerReferralAction>
<DeclineReasonCode>D3</DeclineReasonCode>
<DeclineDate>12092006</DeclineDate>
<PendReasonCode/>
<CancelReasonCode/>
<NTUReasonCode/>
<RepaymentMethod>DD</RepaymentMethod>
<PaymentMethod>BA</PaymentMethod>
<EmploymentStatus>E</EmploymentStatus>
<ContraAccountNumber1>0000000088230347</ContraAccountNumber1>
<ContraAccountNumber2/>
<ContraAccountNumber3/>
<ContraAccountNumber4/>
<ContraAccountNumber5/>
</OtherRecord2000>
When the SAX parser parses this XML on Windows XP, Sun JDK 1.5.0_11, a
character event is generated inbetween the start and end element events for
ContraAccountNumber2 (and 3,4,5). The character events contains only CR+LF
but I don't expect this event here!!
I'm using Xerces-J 2.7.1. I had a quick search of the archives and JIRA but
didn't find anything similar. Has anyone seen anything like this before? The
other thing is that this behaviour doesn't occur on my machine just on 2 of
my colleagues machines which makes me think Xerces isn't to blame but I've
searched and searched for the solution to this problem in vain :(
--
View this message in context: http://www.nabble.com/unexpected-SAX-character-event-tp15070639p15070639.html
Sent from the Xerces - J - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Mukul Gandhi <ga...@gmail.com>.
On Jan 26, 2008 5:11 PM, Stanimir Stamenkov <s7...@netscape.net> wrote:
> You example is obviously wrong. You need to honor the 'start' and
> 'length' parameters passed to the 'characters' callback when
> constructing a String out of the given 'ch':
Thank you very much for correcting my mistake.
> Where do you see character callbacks in between the start and end
> element callbacks for the "pqr" and "uvw" elements?
With the XML document:
<root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
The program I posted (with your fix, new String(ch,start,length)),
produces the output:
-----start element-----
##
##
#root#
!-----start element-----!
------characters------
!------characters------!
-----start element-----
##
##
#abc#
!-----start element-----!
------characters------
hello
!------characters------!
------end element------
##
##
#abc#
!------end element------!
------characters------
!------characters------!
-----start element-----
##
##
#pqr#
!-----start element-----!
------end element------
##
##
#pqr#
!------end element------!
------characters------
!------characters------!
-----start element-----
##
##
#uvw#
!-----start element-----!
------end element------
##
##
#uvw#
!------end element------!
------characters------
!------characters------!
------end element------
##
##
#root#
!------end element------!
This looks perfectly ok to me.
(you wrote correctly that System.out.println(...) adds an extra newline).
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Stanimir Stamenkov <s7...@netscape.net>.
Sat, 26 Jan 2008 10:44:32 +0530, /Mukul Gandhi/:
[...]
> public void characters(char[] ch,
> int start,
> int length) {
> System.out.println("------characters------");
> System.out.println((new String(ch)).trim());
> System.out.println("!------characters------!");
> }
[...]
> When I run this program on the above XML file, I get following output:
[...]
> ------characters------
> root>
> <abc>hello</abc>
> <pqr/>
> <uvw/>
> </root>
[...]
> I am a bit perplexed by the following output from 'characters' event:
>
> root>
> <abc>hello</abc>
> <pqr/>
> <uvw/>
> </root>
You example is obviously wrong. You need to honor the 'start' and
'length' parameters passed to the 'characters' callback when
constructing a String out of the given 'ch':
new String(ch, start, length)
> Moreover, if I don't do trim() on the String object, I get lot of
> whitespaces in the output.
You use System.out.println(...) which adds a new-line to the output.
At the end, all you have shown does not indicate Xerces generates
'character' callbacks between the 'startElement' and 'endElement'
callbacks for empty elements. Just pay attention to your output
(now, after you know your 'character' callbacks output is wrong,
just ignore it):
startElement: root
characters: ...
startElement: abc
characters: ...
endElement: abc
characters: ...
startElement: pqr
endElement: pqr
startElement: uvw
endElement: uvw
characters: ...
endElement: root
Where do you see character callbacks in between the start and end
element callbacks for the "pqr" and "uvw" elements?
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Mukul Gandhi <ga...@gmail.com>.
Hi Michael,
I tried the following example with Xerces-J 2.9.1.
XML document is:
<root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
Source program is:
public class SAXempl extends DefaultHandler {
..............
..............
public static void main(String[] args) {
SAXParserFactory spf = SAXParserFactory.newInstance();
SAXParser parser = spf.newSAXParser();
parser.parse(new File(filename), this);
}
public void startElement(java.lang.String uri,
java.lang.String localName,
java.lang.String qName,
Attributes attributes) {
System.out.println("-----start element-----");
System.out.println("#"+uri+"#");
System.out.println("#"+localName+"#");
System.out.println("#"+qName+"#");
System.out.println("!-----start element-----!");
}
public void endElement(java.lang.String uri,
java.lang.String localName,
java.lang.String qName) {
System.out.println("------end element------");
System.out.println("#"+uri+"#");
System.out.println("#"+localName+"#");
System.out.println("#"+qName+"#");
System.out.println("!------end element------!");
}
public void characters(char[] ch,
int start,
int length) {
System.out.println("------characters------");
System.out.println((new String(ch)).trim());
System.out.println("!------characters------!");
}
I have omitted the imports and other class skeleton for brevity.
When I run this program on the above XML file, I get following output:
-----start element-----
##
##
#root#
!-----start element-----!
------characters------
root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
!------characters------!
-----start element-----
##
##
#abc#
!-----start element-----!
------characters------
root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
!------characters------!
------end element------
##
##
#abc#
!------end element------!
------characters------
root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
!------characters------!
-----start element-----
##
##
#pqr#
!-----start element-----!
------end element------
##
##
#pqr#
------characters------
root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
!------characters------!
-----start element-----
##
##
#uvw#
!-----start element-----!
------end element------
##
##
#uvw#
!------end element------!
------characters------
root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
!------characters------!
------end element------
##
##
#root#
!------end element------!
I am a bit perplexed by the following output from 'characters' event:
root>
<abc>hello</abc>
<pqr/>
<uvw/>
</root>
Moreover, if I don't do trim() on the String object, I get lot of
whitespaces in the output.
Could you kindly explain this behaviour by Xerces.
On Jan 26, 2008 12:27 AM, Michael Glavassevich <mr...@ca.ibm.com> wrote:
> I suppose the SAX spec doesn't forbid that but Xerces doesn't do that.
> You'll get a startElement() event followed by an endElement() event. The
> only exception to that is if you're doing schema validation and the
> validator inserted a default element value. Then you'll get a characters()
> event.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Mukul Gandhi <ga...@gmail.com>.
On Jan 26, 2008 5:16 PM, Stanimir Stamenkov <s7...@netscape.net> wrote:
> Your first statement is not true, at least for Xerces (see my other
> reply in this thread).
Thanks for clarifying this.
> Regarding you second statement "But the text content will be null.":
>
> void characters (char ch[], int start, int length)
>
> I think it is logical if the 'length' parameter to a character
> callback is > 0, 'ch' cannot be null, and if length == 0 then no
> character callback should be made, so 'ch' should never be null.
> This could also be deducted from the general principle if the
> contract doesn't explicitly state null values are permitted - they
> are not.
I agree to this. Thanks for the clarification.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Stanimir Stamenkov <s7...@netscape.net>.
Fri, 25 Jan 2008 14:29:58 +0530, /Mukul Gandhi/:
> Even for elements like <xxx/>, the SAX parser produces character
> events. But the text content will be null.
>
> I am presently not sure, what the SAX standard says. I'll leave it for
> others to comment.
Your first statement is not true, at least for Xerces (see my other
reply in this thread).
Regarding you second statement "But the text content will be null.":
void characters (char ch[], int start, int length)
I think it is logical if the 'length' parameter to a character
callback is > 0, 'ch' cannot be null, and if length == 0 then no
character callback should be made, so 'ch' should never be null.
This could also be deducted from the general principle if the
contract doesn't explicitly state null values are permitted - they
are not.
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
"Mukul Gandhi" <ga...@gmail.com> wrote on 01/25/2008 03:59:58 AM:
> > Can you explain why you think the character event should occurs
inbetween
> > start/end element event when the only text nodes are before and after
the
> > element? I'm sorry it just seems wrong to me.
>
> Even for elements like <xxx/>, the SAX parser produces character
> events. But the text content will be null.
I suppose the SAX spec doesn't forbid that but Xerces doesn't do that.
You'll get a startElement() event followed by an endElement() event. The
only exception to that is if you're doing schema validation and the
validator inserted a default element value. Then you'll get a characters()
event.
> I am presently not sure, what the SAX standard says. I'll leave it for
> others to comment.
>
> I'll try this scenario myself, and share my findings.
>
> --
> Regards,
> Mukul Gandhi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Mukul Gandhi <ga...@gmail.com>.
> Can you explain why you think the character event should occurs inbetween
> start/end element event when the only text nodes are before and after the
> element? I'm sorry it just seems wrong to me.
Even for elements like <xxx/>, the SAX parser produces character
events. But the text content will be null.
I am presently not sure, what the SAX standard says. I'll leave it for
others to comment.
I'll try this scenario myself, and share my findings.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by cbowditch <bo...@hotmail.com>.
Hi Mukul,
thanks for the reply.
Mukul Gandhi wrote:
>
>> When the SAX parser parses this XML on Windows XP, Sun JDK 1.5.0_11, a
>> character event is generated inbetween the start and end element events
>> for
>> ContraAccountNumber2 (and 3,4,5). The character events contains only
>> CR+LF
>> but I don't expect this event here!!
>
> I feel, this is a compliant behavior. There is a whitespace text node,
> at the places you have cited. So a SAX parser should report these
> nodes (even insignificant to you) to the application.
>
Can you explain why you think the character event should occurs inbetween
start/end element event when the only text nodes are before and after the
element? I'm sorry it just seems wrong to me.
--
View this message in context: http://www.nabble.com/unexpected-SAX-character-event-tp15070639p15083418.html
Sent from the Xerces - J - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Mukul Gandhi <ga...@gmail.com>.
> When the SAX parser parses this XML on Windows XP, Sun JDK 1.5.0_11, a
> character event is generated inbetween the start and end element events for
> ContraAccountNumber2 (and 3,4,5). The character events contains only CR+LF
> but I don't expect this event here!!
I feel, this is a compliant behavior. There is a whitespace text node,
at the places you have cited. So a SAX parser should report these
nodes (even insignificant to you) to the application.
If it meet's your requirement, you can ignore the whitespace text
nodes in your application.
I also suggest, please shift to Xerces-J 2.9.1 to have a better
compliance and performance.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by cbowditch <bo...@hotmail.com>.
Hi Jake,
thanks for the reply.
Jacob Kjome wrote:
>
> I'm not sure what the problem would be, but just to get clarification...
> You
> say you are using Xerces-2.7.1. Are you using it directly or via JAXP?
> If
> via JAXP, did you put Xerces.jar into JAVA_HOME/jre/lib/endorsed (or other
> endorsed dir)? If not, you are using Sun's internal version of Xerces
> which
> is well known to have bugs that Xerces never had and bugs that have long
> since
> been fixed in newer versions of Xerces.
>
> Jake
>
>
I am using JAXP and indeed my first thought was that the machines showing
the incorrect behaviour did not have xerces-2.7.1.jar in the lib\endorsed
directory. But I have searched every JVM on the machines with the erroneous
behaviour and all have xerces-2.7.1.jar in the lib\endorsed folder :-/
Thanks,
Chris
--
View this message in context: http://www.nabble.com/unexpected-SAX-character-event-tp15070639p15083462.html
Sent from the Xerces - J - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Prashant Reddy <pr...@pramati.com>.
If the JVM version used is JDK 1.5 [1], there is no need to put Xerces
2.7.1 in endorsed dir. Simply putting xerces (2.7.1) in the classpath
will make JAXP lookup process pick the implementation up. Only when JAXP
could not find a parser implementation in the classpath, does it fall
back on default com.sun.internal parser implementation.
You will need to use endorsed dirs mechanism, if you would like to use a
higher version of JAXP than what is supplied by the JDK. In this event,
both higher version of JAXP jars and the appropriate parser
implementation should be kept in the endorsed dir.
-Prashant
1.
http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html
On Thu, 2008-01-24 at 12:33 -0600, Jacob Kjome wrote:
> I'm not sure what the problem would be, but just to get clarification... You
> say you are using Xerces-2.7.1. Are you using it directly or via JAXP? If
> via JAXP, did you put Xerces.jar into JAVA_HOME/jre/lib/endorsed (or other
> endorsed dir)? If not, you are using Sun's internal version of Xerces which
> is well known to have bugs that Xerces never had and bugs that have long since
> been fixed in newer versions of Xerces.
>
> Jake
>
> On Thu, 24 Jan 2008 09:44:57 -0800 (PST)
> cbowditch <bo...@hotmail.com> wrote:
> >
> > I have some XML like:
> >
> > <OtherRecord2000>
> > <AccountNumber>R000239125</AccountNumber>
> > <SaleOfDeclineCompany/>
> > <CustomerReferral>Y</CustomerReferral>
> > <CustomerReferralCode>07</CustomerReferralCode>
> > <CustomerReferralAction>10</CustomerReferralAction>
> > <DeclineReasonCode>D3</DeclineReasonCode>
> > <DeclineDate>12092006</DeclineDate>
> > <PendReasonCode/>
> > <CancelReasonCode/>
> > <NTUReasonCode/>
> > <RepaymentMethod>DD</RepaymentMethod>
> > <PaymentMethod>BA</PaymentMethod>
> > <EmploymentStatus>E</EmploymentStatus>
> > <ContraAccountNumber1>0000000088230347</ContraAccountNumber1>
> > <ContraAccountNumber2/>
> > <ContraAccountNumber3/>
> > <ContraAccountNumber4/>
> > <ContraAccountNumber5/>
> > </OtherRecord2000>
> >
> > When the SAX parser parses this XML on Windows XP, Sun JDK 1.5.0_11, a
> > character event is generated inbetween the start and end element events for
> > ContraAccountNumber2 (and 3,4,5). The character events contains only CR+LF
> > but I don't expect this event here!!
> >
> > I'm using Xerces-J 2.7.1. I had a quick search of the archives and JIRA but
> > didn't find anything similar. Has anyone seen anything like this before? The
> > other thing is that this behaviour doesn't occur on my machine just on 2 of
> > my colleagues machines which makes me think Xerces isn't to blame but I've
> > searched and searched for the solution to this problem in vain :(
> > --
> > View this message in context:
> >http://www.nabble.com/unexpected-SAX-character-event-tp15070639p15070639.html
> > Sent from the Xerces - J - Users mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> >For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by Jacob Kjome <ho...@visi.com>.
I'm not sure what the problem would be, but just to get clarification... You
say you are using Xerces-2.7.1. Are you using it directly or via JAXP? If
via JAXP, did you put Xerces.jar into JAVA_HOME/jre/lib/endorsed (or other
endorsed dir)? If not, you are using Sun's internal version of Xerces which
is well known to have bugs that Xerces never had and bugs that have long since
been fixed in newer versions of Xerces.
Jake
On Thu, 24 Jan 2008 09:44:57 -0800 (PST)
cbowditch <bo...@hotmail.com> wrote:
>
> I have some XML like:
>
> <OtherRecord2000>
> <AccountNumber>R000239125</AccountNumber>
> <SaleOfDeclineCompany/>
> <CustomerReferral>Y</CustomerReferral>
> <CustomerReferralCode>07</CustomerReferralCode>
> <CustomerReferralAction>10</CustomerReferralAction>
> <DeclineReasonCode>D3</DeclineReasonCode>
> <DeclineDate>12092006</DeclineDate>
> <PendReasonCode/>
> <CancelReasonCode/>
> <NTUReasonCode/>
> <RepaymentMethod>DD</RepaymentMethod>
> <PaymentMethod>BA</PaymentMethod>
> <EmploymentStatus>E</EmploymentStatus>
> <ContraAccountNumber1>0000000088230347</ContraAccountNumber1>
> <ContraAccountNumber2/>
> <ContraAccountNumber3/>
> <ContraAccountNumber4/>
> <ContraAccountNumber5/>
> </OtherRecord2000>
>
> When the SAX parser parses this XML on Windows XP, Sun JDK 1.5.0_11, a
> character event is generated inbetween the start and end element events for
> ContraAccountNumber2 (and 3,4,5). The character events contains only CR+LF
> but I don't expect this event here!!
>
> I'm using Xerces-J 2.7.1. I had a quick search of the archives and JIRA but
> didn't find anything similar. Has anyone seen anything like this before? The
> other thing is that this behaviour doesn't occur on my machine just on 2 of
> my colleagues machines which makes me think Xerces isn't to blame but I've
> searched and searched for the solution to this problem in vain :(
> --
> View this message in context:
>http://www.nabble.com/unexpected-SAX-character-event-tp15070639p15070639.html
> Sent from the Xerces - J - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by cbowditch <bo...@hotmail.com>.
cbowditch wrote:
>
> Thanks for all the replies so far. I have upgraded to Xerces version
> 2.9.1. I downloaded the source and set the debug contants to true and
> re-compiled. I get loads of information on System.out so the right parser
> is definitely being used to parse the XML.
>
Looking at the code I'm not sure I have done enough to get debugging turned
on properly. I changed the contants DEBUG_SCANNER_STATE, DEBUG_DISPATCHER
and DEBUG_CONTENT_SCANNING in the class XMLDocumentFragmentScannerImpl.
However, I would expect to see lines like:
>>> scanStartElement()
in my logs but I don't see them. Any tips on understanding the code would be
most helpful in resolving the unwanted character event problem.
--
View this message in context: http://www.nabble.com/unexpected-SAX-character-event-tp15070639p15181869.html
Sent from the Xerces - J - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: unexpected SAX character event
Posted by cbowditch <bo...@hotmail.com>.
Thanks for all the replies so far. I have upgraded to Xerces version 2.9.1. I
downloaded the source and set the debug contants to true and re-compiled. I
get loads of information on System.out so the right parser is definitely
being used to parse the XML.
I have uploaded the full XML file (its not very big)
http://www.nabble.com/file/p15181527/case3789-obf.xml case3789-obf.xml
The debug output from Xerces is intermingled with that of my own application
and the key section is provided below. The non-null character event is
received where you see m_pcData= and just prior to that I see ###
setScannerState: SCANNER_STATE_CONTENT.
### setScannerState: SCANNER_STATE_START_OF_MARKUP
### setScannerState: SCANNER_STATE_CONTENT
10:54:11,219 ServiceTask:Job Processor data.BaseBusinessObject.characters >
152
10:54:11,219 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
1 characters=0000000088230347
30-Jan-2008 10:54:13[Job Processor] >
10:54:12,217 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
2 m_pcData=0000000088230347
10:54:12,217 ServiceTask:Job Processor data.BaseBusinessObject.characters <
### setScannerState: SCANNER_STATE_START_OF_MARKUP
### setScannerState: SCANNER_STATE_CONTENT
10:54:12,217 ServiceTask:Job Processor data.BaseBusinessObject.characters >
153
10:54:12,217 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
1 characters=
10:54:12,217 ServiceTask:Job Processor data.BaseBusinessObject.characters <
30-Jan-2008 10:54:14[Job Processor] >
### setScannerState: SCANNER_STATE_START_OF_MARKUP
### setScannerState: SCANNER_STATE_CONTENT
10:54:13,215 ServiceTask:Job Processor data.BaseBusinessObject.characters >
154
10:54:13,230 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
1 characters=
10:54:13,230 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
2 m_pcData=
10:54:13,230 ServiceTask:Job Processor data.BaseBusinessObject.characters <
### setScannerState: SCANNER_STATE_START_OF_MARKUP
### setScannerState:
30-Jan-2008 10:54:15[Job Processor] > SCANNER_STATE_CONTENT
10:54:14,213 ServiceTask:Job Processor data.BaseBusinessObject.characters >
155
10:54:14,213 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
1 characters=
10:54:14,213 ServiceTask:Job Processor data.BaseBusinessObject.characters <
### setScannerState: SCANNER_STATE_START_OF_MARKUP
### setScannerState: SCANNER_STATE_CONTENT
10:54:14,213 ServiceTask:Job Processor data.BaseBusinessObject.characters >
156
10:54:14,213 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
1 characters=
30-Jan-2008 10:54:16[Job Processor] >
10:54:15,211 ServiceTask:Job Processor data.BaseBusinessObject.characters ?
2 m_pcData=
10:54:15,226 ServiceTask:Job Processor data.BaseBusinessObject.characters <
### setScannerState: SCANNER_STATE_START_OF_MARKUP
### setScannerState: SCANNER_STATE_CONTENT
--
View this message in context: http://www.nabble.com/unexpected-SAX-character-event-tp15070639p15181527.html
Sent from the Xerces - J - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org