Powered by Squarespace

Popular articles:

What am I?

I'm a technology consultant, focused on enterprise collaborative applications. I'm based in North-east Scotland but work all over Europe, and sometimes I present at technology conferences using a mixture of deep-technology and humour to keep the audience awake.

I'm married with one grown-up daughter of whom I'm immensely proud, and have family members covering most significant time-zones. We took 'hide and seek' seriously.

Other interests include making excuses not to go to the gym, testing the tolerance of my peers with humour, and sometimes bringing my 20-year old ZZR 600 out of the garage to terrify myself with.

I've been blogging since it was called 'Talking cr@p on the internet' and at one stage hand-rolled my own blog. Fame and fortune for this minor technological greatness is still 'in the post'.

Enjoy my little outpost on the web and take cheer that it could be worse - I could be a Silverlight consultant...

How to get in touch?

I have a mobile phone number which has been unchanged in 15 years. Most folks have that. Or you can try eMailing me - look at the domain name and take a good guess which will work. Most things will. I'm on Linked-In for the business stuff, Facebook for the personal stuff, and Skype for the face to face stuff. 

I'm a freelance consultant, and I'm engaged by enterprise or government customers. Most of the work I do I cannot speak about, so excuse my somewhat clumsy evasions. 

« I tried to cancel my O2 home broadband today... | Main | Recovering... »
Monday
Feb152010

DXL and the Discovered Check bug...

We've got an application at Customer #1, and its a big application. During a critical phase as its hopping along its 'snakes and ladders' board of workflow stages, it'll make a complete backup of the relevant document using DXL. Literally, it'll do a java 'notesdocument.generateXML()' call.  This code was constructed in the R5/R6 timeframe, and this call is as old as the hills. That is, its been working reliably for 6+ years.

We originally tried to test this out on Domino 8.5.0, and generateXml() failed completely. Not good. We're now doing regression testing on 8.5.1, and have found to our pleasant surprise that generateXml() works well. At least, we thought so till we hit a document that had been through a particular gate in the process. We were getting a notes error: lotus.domino.NotesException: Error 4395, Not implemented

and a java dump, which included lines such as:

Caused by: javax.xml.transform.TransformerException: java.lang.RuntimeException: [ERR 0368] The string '%PARENT%' was used where a QName is required.

at com.ibm.xtq.xslt.jaxp.TransformerImpl.transform(Unknown Source)

and:

at GregorSamsa_Common_P0.GregorSamsa$0x24$main(<generated>)

And you think 'Who in gods name is Gregor Samsa'. And then you google and find this. Gregor Samsa is the central character of Kafka's 'The Metamorphasis'. Where a man turns into a bug. Hey - ten out of ten for humour here, but WTF?

Once you calm down and look at the source document. And find that there's a notesitem called '%PARENT% - which was put there by an errant piece of code from another process. And in fact, has always been there.

Its just that now DXL reports this instead of ignoring it. Hence the 'discovered check'. We fixed the item name so that it wasnt illegal, and it all works beautifully.

I guess the moral of the tale here is that if you see Gregor Samsa, you are truly in a maze of twisty little corridors, and you should investigate till your head hurts.

 

Reader Comments (1)

godss-well to-All things in their being are good for something.-Oris watch uk

August 3, 2011 | Unregistered CommenterOris watch uk

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>