the stuff Coquelicot does when it thinks it is at work

Monday, October 17, 2005

TIE'05 and SSR problems

It is beginning of 2nd week of TIE and I haven't written anything that was going on, mostly because of lack of time (and spirit...). Anyways, today was a very long and exhausting day (again) but I managed to get some more understanding on how the XML communication works. The plan was to get the JBother's SSR plugin talk to other systems. NORCCIS was one of them, and I noticed that the data was not comming through - they were claiming that the SSR are not appearing there.

First of all, I took a look at the XML SSR plugin was generating - thanks to Ronald's piece of code I was able to run the schema accordance test and discovered that some elements were plainly wrong: nillable instead of non-nillable, using wrong units ('kilometers' vs. 'meters'), wrong string for ID tags (apparently, they cannot start with a numeral). After making sure that the XML code we were generating was OK, I took a look at XML sent by other system. It turned out that they were using namespaces "embedded" with tags - not presented in the "header" of the file. This, in connection to XmlPullParser hack we are now using to, basically, copy over the XML for XMLBeans to do the parsing itself, resulted in wrong namespaces when parsing. This has been corrected, however - it did not help the fact that NORCCIS was not seeing the stuff from us.

I've worked some time on whitespace issue - right now the plugin sends XML without it, to satisfy the NORCCIS guys - but I don't think this is good. Whitespace shouldn't matter with XML. Well, we'll leave it to after-exercise, esp. because there will be cross-cueing test tomorrow.

In the process, we've discovered a bug in NORCCIS code: whenever it was sending acknowledgements, they were presented as regular request (this has been verified by ethereal's snooping on the network). JBother resulted in displaying improper window in this situation. When JBother was sending ack's, NORCCIS reported to see them correctly.


Post a Comment

<< Home