JiBX

Namespace causing unmarshalling to fail

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: core
  • Labels:
    None
  • Environment:
    Windows 2000, JDK 1.4.2_06, Ant 1.6.5
  • Number of attachments :
    1

Description

A nested collection binding which works if namespaces are removed, fails during unmarshalling when namespaces are present in the source XML file and also in the binding.

The attached zip has the Java files, JiBX binding(s), source XML file and Ant build file to reproduce this issue. It was run against the current CVS version (RC1+).

The two Ant tasks of interest are:
test-ns (the default target) – shows error behaviour when NS are present
test-no-ns – shows the same bindings minus the NS do in fact work.

Just unpack the zip to a new directory and run 'ant' to see the error. Run 'ant test-no-ns' to see how it should work

Sorry, there is no JUnit test case, just a simple command line test file. Hopefully it will be sufficient to identify the problem.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Leif Stainsby added a comment -

And, of course, you may want to set the "jibx.home" variable in the build.xml file before attempting to build it.

Show
Leif Stainsby added a comment - And, of course, you may want to set the "jibx.home" variable in the build.xml file before attempting to build it.
Hide
Permalink
Leif Stainsby added a comment -

Hmmm, we are learning quite a bit about JiBX it seems.

Adding a namespace entry (as shown below) to the "keywords" mapping makes this problem go away.
<namespace uri="http://www.opengeospatial.net/ows" default="elements"/>

I might have assumed that a single namespace declaration in JiBX had similar effect to that in an XML entity. I was wrong. Defining a namespace on the root element in an XML document applies to all contained elements (absent further namespace declarations), but, in a JiBX it is entirely local to that one mapping definition.

This was purely my mistake. My apologies

Show
Leif Stainsby added a comment - Hmmm, we are learning quite a bit about JiBX it seems. Adding a namespace entry (as shown below) to the "keywords" mapping makes this problem go away. <namespace uri="http://www.opengeospatial.net/ows" default="elements"/> I might have assumed that a single namespace declaration in JiBX had similar effect to that in an XML entity. I was wrong. Defining a namespace on the root element in an XML document applies to all contained elements (absent further namespace declarations), but, in a JiBX it is entirely local to that one mapping definition. This was purely my mistake. My apologies
Hide
Permalink
Leif Stainsby added a comment -

Not a bug. Misunderstanding re namespace usage in binding file.

Show
Leif Stainsby added a comment - Not a bug. Misunderstanding re namespace usage in binding file.
Hide
Permalink
Dennis Sosnoski added a comment -

You can make a <namespace> apply to all the mappings, but need to move it out as a child of the <binding> element. If you nest it inside a particular <mapping>, the <namespace> only applies to the definitions within that <mapping>.

Show
Dennis Sosnoski added a comment - You can make a <namespace> apply to all the mappings, but need to move it out as a child of the <binding> element. If you nest it inside a particular <mapping>, the <namespace> only applies to the definitions within that <mapping>.

People

  • Assignee:
    Unassigned
    Reporter:
    Leif Stainsby
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: