castor

Exception occurs during unmarshaling, when both idresolver is present and validation is set to true.

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.3.2
  • Fix Version/s: 1.3.4
  • Component/s: XML
  • Labels:
    None
  • Environment:
    Windows, Java 1.6
  • Testcase included:
    yes
  • Number of attachments :
    2

Description

An exception occurs when trying to unmarshall xml, when both validation is set to true and an idresolver is registered for the unmarshaller. Disabling the validation will cause the xml to be correctly unmarshalled.

Sample code that will cause an error:
Unmarshaller unmarshaller = createUnmarsahllerFromMapping(LIBRARY_MAPPING_FILE);
unmarshaller.setValidation(true);
unmarshaller.setIDResolver(idResolver);
Object result = unmarshal(unmarshaller, ID_REF_INPUT_STRING);

Stack trace:

org.exolab.castor.xml.MarshalException: ValidationException: ClassDescriptorResolver from context must not be null!{File: [not available]; line: 1; column: 272}
	at org.exolab.castor.xml.Unmarshaller.convertSAXExceptionToMarshalException(Unmarshaller.java:873)
	at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:770)
	at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:636)
	at org.exolab.castor.xml.TestUnmarshaller.unmarshal(TestUnmarshaller.java:600)
	at org.exolab.castor.xml.TestUnmarshaller.testIDResolver(TestUnmarshaller.java:533)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Atached patch will failing test.

  1. Text File
    CASTOR-3135.patch
    29/Jun/11 4:02 PM
    46 kB
    Jakub Narloch
  2. Text File
    Castor-3135-fix.patch
    01/Jul/11 2:19 PM
    5 kB
    Jakub Narloch

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. CASTOR-3133 XML Marshaller and Unmarshaller tests

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jakub Narloch added a comment -

Attached patch will failing test.

Show
Jakub Narloch added a comment - Attached patch will failing test.
Hide
Permalink
Jakub Narloch added a comment -

I believe that I understand, why this happens, when the object is validated in Validator class in effect the IdRefValidator is called and throws exception, but currently the IdValidator which is suppose to add the id to the test context is never invoked. Currently I don't yet know how correct this, but I will work on it.

Show
Jakub Narloch added a comment - I believe that I understand, why this happens, when the object is validated in Validator class in effect the IdRefValidator is called and throws exception, but currently the IdValidator which is suppose to add the id to the test context is never invoked. Currently I don't yet know how correct this, but I will work on it.
Hide
Permalink
Jakub Narloch added a comment - - edited

I attached the initial patch that will resolve the first test - the case where all ids are present in xml.

The second one - when the id is resolved from external source, that is the idresolver, the test will still fail, becouse the validator is not aware of the idresolver.

Show
Jakub Narloch added a comment - - edited I attached the initial patch that will resolve the first test - the case where all ids are present in xml. The second one - when the id is resolved from external source, that is the idresolver, the test will still fail, becouse the validator is not aware of the idresolver.

People

  • Assignee:
    Werner Guttmann
    Reporter:
    Jakub Narloch
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: