Java.lang.Character and primitive char could be mapped to WSDL file better
--------------------------------------------------------------------------
Key: XFIRE-369
URL: http://jira.codehaus.org/browse/XFIRE-369
Project: XFire
Type: Improvement
Components: Core
Environment: Using Spring wiring with XFire
Reporter: David Greiman
Assigned to: Dan Diephouse
Priority: Minor
Unless I am doing something wrong, it seems that java.lang.Character and the
primitive "char" are not mapping to a one character xsd:string in the WSDL
file. I believe this is the solution from other web service tools. Instead, it
is mapped to a complex type that seems to be xFire specific (e.g., namespace
java.lang.Character). When using Xfire for both client and server, the char
does not map on the client side. Any ideas on how to make char/Character work?
Until then, I'll use an unbounded String.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
