OpenADK produced XML contains US namespace instead of UK namespace

[Jon Nicholson]

Well, I took the plunge and tried updating our application the the OpenADK. I replaced the following jars:
- sifworks-adk-uk.jar
- sdoall-uk.jar
with the one I managed to generate from the OpenADK source:
- adk-library-uk-1.0.0-SNAPSHOT.jar

I left the other dependencies (e.g. jetty) as is (I haven't checked if any local jar dependencies need updating with those that Maven brought down in the build process). No other changes have been made to the configuration of the ADK.

After reorganising all the imports it seemed to work... The application executed as normal, and I could connect to a zone, provision the zone for our application, send queries, etc. But, then we hit a brick wall.

When we receive data from the zone we inspect each data object in the given DataObjectInputStream, by calling readDataObject() and then toXML(). In the SIFWorks/EduStructures ADK this yielded XML with the expected (correct, UK) namespace attribute of:
- xmlns="http://www.sifinfo.org/uk/infrastructure/2.x"
however it appears that the OpenADK is presenting the following (incorrect, US) namespace:
- xmlns="http://www.sifinfo.org/infrastructure/2.x"

As far as I can tell I'm using the correct UK jar, and there appears to be no errors indicating I am missing a dependency/require any other generated jar files.

This issue has been found against our own production ZIS, and the EDUStructures test ZIS, both of which (still) work fine with our application when using the SIFWorks ADK.

I would hazard a guess that this bug also affects the AU version of the OpenADK.

[Jon Nicholson (jonicholson)]

If it helps at all, here is the jar I generated that experiences the problem.

[Brian Sneddon (brian-sneddon)]

Thanks Jon,

We are working on this bug and it looks like we've found the source of the
problem. We testing a fix that will remove this bug and hopefully simplify
the maven build process as well.

--
Brian Sneddon
Software Engineer
Pearson
801.565.3039

On 9/13/11 9:17 AM, "Jon Nicholson" <email address hidden> wrote:

> If it helps at all, here is the jar I generated that experiences the
> problem.
>
> ** Attachment added: "adk-library-uk-1.0.0-SNAPSHOT.jar"
>
> https://bugs.launchpad.net/open-adk-java/+bug/828735/+attachment/2397664/+file
> s/adk-library-uk-1.0.0-SNAPSHOT.jar

[Jon Nicholson (jonicholson)]

Thank you Brian, that sounds fantastic.

[Brian Sneddon (brian-sneddon)]

Jon,

We've updated the OpenADK with the namespace fix as well as a simplified
build process. There should be a readme file with the new maven build
instructions. A single maven command line compile will/should make an
eclipse ready project.

Let us know how it goes for you.

Thanks,

--
Brian Sneddon
Software Engineer
Pearson
801.565.3039

On 9/13/11 10:03 AM, "Jon Nicholson" <email address hidden> wrote:

> Thank you Brian, that sounds fantastic.

[Jon Nicholson (jonicholson)]

I've followed the new instructions. My thoughts on that are included as a comment to the appropriate bug report (https://bugs.launchpad.net/open-adk-java/+bug/804527).

The newly generated jar is now working with the correct namespace. Thank you very much! This bug can now be closed.