castor

XSD is outdated

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.3.1
  • Fix Version/s: 1.3.2
  • Component/s: Core
  • Labels:
    None
  • Number of attachments :
    0

Description

Similiar to CASTOR-2981 the XSD is also outdated at least w.r.t. field-handler element.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. CASTOR-3040 XSD declaration causes elements to be marshalled into http://castor.exolab.org/ namespace

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Werner Guttmann added a comment -

Jakub, I just figured that there was a small hickup during deployment of release 1.3.1. I just copied mapping.xsd and mapping.dtd manually to the correct folders, and everything should work now. Can you please re-check on your side ?

Show
Werner Guttmann added a comment - Jakub, I just figured that there was a small hickup during deployment of release 1.3.1. I just copied mapping.xsd and mapping.dtd manually to the correct folders, and everything should work now. Can you please re-check on your side ?
Hide
Permalink
Jakub Bochenski added a comment -

Validation with DTD says the document is valid now, but at the same time the current XSD schema makes the same document fail validation.

Show
Jakub Bochenski added a comment - Validation with DTD says the document is valid now, but at the same time the current XSD schema makes the same document fail validation.
Hide
Permalink
Jakub Bochenski added a comment - - edited

Sapmle, XSD fails at the "class" element

<mapping>

	<field-handler name="dateHandler"
		class="package.FormatDateHandler">
		<param name="date-format" value="yyyy-MM-dd" />
	</field-handler>

	<class name="package.Entries">
		<field name="revisionNo" type="long">
			<bind-xml node="attribute" />
		</field> 
	</class>

</mapping>
Show
Jakub Bochenski added a comment - - edited Sapmle, XSD fails at the "class" element <mapping> <field-handler name= "dateHandler" class= " package .FormatDateHandler" > <param name= "date-format" value= "yyyy-MM-dd" /> </field-handler> <class name= " package .Entries" > <field name= "revisionNo" type= " long " > <bind-xml node= "attribute" /> </field> </class> </mapping>
Hide
Permalink
Werner Guttmann added a comment -

Jakub, can you please attach the mapping file you are trying to validate against the XML schema ?

Show
Werner Guttmann added a comment - Jakub, can you please attach the mapping file you are trying to validate against the XML schema ?
Hide
Permalink
Werner Guttmann added a comment -

Oops, no need anymore to attach the XML schema anymore .. ;-(. I just found the problem.

Show
Werner Guttmann added a comment - Oops, no need anymore to attach the XML schema anymore .. ;-(. I just found the problem.
Hide
Permalink
Werner Guttmann added a comment -

Just uploaded the fixed XML schema and cross-checked. Now the field-handler is at the correct location (before the class element).

Show
Werner Guttmann added a comment - Just uploaded the fixed XML schema and cross-checked. Now the field-handler is at the correct location (before the class element).

People

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

Dates

  • Created:
    Updated:
    Resolved: