XFire

CharType generats xsd:char instead of xsd:string

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.2
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

xsd:char is an invalid xmlschema datatype.

Activity

Hide
Sean Truman added a comment -

Changed QName XSD_CHAR from 'char' to 'string', see attached patch.

Show
Sean Truman added a comment - Changed QName XSD_CHAR from 'char' to 'string', see attached patch.
Hide
Sean Truman added a comment -

Patch submit, I shouldn't have resolved. sorry

Show
Sean Truman added a comment - Patch submit, I shouldn't have resolved. sorry
Hide
Dan Diephouse added a comment -

I'm not sure what this would take - but I think it would be good if we specified that its a string with a length between 0 and 1 in the WSDL. Otherwise someone could send some giant string.

Show
Dan Diephouse added a comment - I'm not sure what this would take - but I think it would be good if we specified that its a string with a length between 0 and 1 in the WSDL. Otherwise someone could send some giant string.
Hide
Dan Diephouse added a comment -

I fixed our xsd;char generation and made it xsd:string. However, I think specifying a restriction of 1 character will take some added work so I'm schedulign this for 1.2, not 1.1.1.

Show
Dan Diephouse added a comment - I fixed our xsd;char generation and made it xsd:string. However, I think specifying a restriction of 1 character will take some added work so I'm schedulign this for 1.2, not 1.1.1.
Hide
Dan Diephouse added a comment -

Why is this reopened? I don't see any comments saying it isn't working and I believe we fixed it. Closing for now

Show
Dan Diephouse added a comment - Why is this reopened? I don't see any comments saying it isn't working and I believe we fixed it. Closing for now

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: