This approach will render your WS non interoperable, because it is well defined how a date should be put on the wire. Checkout the JAXRPC spech for other allowed xs types, like gYear gMonth etc.
If you have special needs you can of course use xs:string and transport any date signature. Your clients wont be able to unmarshall this as date, but they won't be able to do this if you use a custom serializer either.
Well the format is a perfectly valid xs:date according to http://www.w3.org/TR/xmlschema-2/#dateTime
SOAPScope has no problems with such dates e.g.
Is it mandated in the JAXRPC spec that dates mist be sent as UTC - I doubt that this is the case??
I did solve the problem by sending the timezone seperately but I still curious why JBoss ignored the serializer.
In anycase I solved the problem
Thanks for the reply
From what I read in the XMLSchema spec, you are definitely right - the time zone maybe part of xs:date. The jaxrpc spec only mandates xs:date and does afaik not make additional constraints.
I filed a bug with sourceforge: