<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:10pt"><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">> Oh, and if we have somehow become dependent upon a third-party tool<br>> (JIBX) that's so difficult to locate and has such a low commitment to<br>> interface stability, then perhaps we should reconsider that and use a<br>> different tool.<br><br>The decision to remove this tool from the version control, yet still to continue depending on it during the build time is indeed a little puzzling. Obviously the time is scarce and the tasks are many, but how difficult would it be to remove the dependency on JiBX altogether? Unless Nimbus designer is very close to public release *and* it heavily depends on JiBX, what's the compelling reason to keep having this
dependency. And if i understand correctly (from either Richard or Jasper), the XMLs generated by Nimbus designer were tweaked manually afterwards.<br><br>Thanks<br>Kirill<br><br></div></div></div><br>
</body></html>