Sorry about the previous post.
No "id" attribute is needed actually...
"W. Jordan" <wmjordan@163.c omwrote in message
news:%230fvOF2n IHA.2160@TK2MSF TNGP06.phx.gbl. ..
No "id" attribute is needed actually...
"W. Jordan" <wmjordan@163.c omwrote in message
news:%230fvOF2n IHA.2160@TK2MSF TNGP06.phx.gbl. ..
Hey there,
You should do something to prevent this exception. You should do
replaces to the fragment to add an "id" attribute to the LogEntry
elements, mark the end of log, and let the fragment look like that.
>
<LogEntry id="1" AtrA="name2" AtrB="time" AtrC="location" />
<LogEntry id="2" AtrA="name3" AtrB="time" AtrC="location" />
<LogEntry id="3" AtrA="name4" AtrB="time" AtrC="location" />
<EndOfLog/>
>
You should do something to prevent this exception. You should do
replaces to the fragment to add an "id" attribute to the LogEntry
elements, mark the end of log, and let the fragment look like that.
>
<LogEntry id="1" AtrA="name2" AtrB="time" AtrC="location" />
<LogEntry id="2" AtrA="name3" AtrB="time" AtrC="location" />
<LogEntry id="3" AtrA="name4" AtrB="time" AtrC="location" />
<EndOfLog/>
>