Hi Mark and Rob,
Thanks for the input. However, still it is not very clear to me the limitation/usage of these two types of datatypes.
Let me put my question with respect to a specific scenario here -
- I’m using WebMethods 6.0.1. and JDBC Adapter 6.0.3. The underlying JDK version is 1.3.1 (which supports till Unicode 3.0).
- Now in release notes of WebMethod Installet 6.0.1 what I found is it is complient till Unicode 1.2.8 (WebMethod 6.1 complies till Unicode 3.0).
- Also the same release notes says that ‘string’ and ‘char’ datatypes should be only used for Latin-1 (iso-8859-1) characters (for the backward compatibility purpose with older version of brokers) and in general instead unicode_char and unicode_string datatypes should be used.
Now with this information I’m having further queries like -
a) Though WebMethod is Java based, don’t the char and string datatypes support any characters beyond iso-8859-1 chars (which char and string datatype in Java do support) ?
b) Do the unicode_char and unicode_string datatype of WebMethod support only those characters of Unicode which are supported by the WebMethod supported Unicode (i.e. 2.1.8 in case of WebMethod 6.0.1) ? So in that case, though I’m running WebMethod 6.0.1 on JDK 1.3.1 (which supports Unicode 3.0) I eventually can support all characters till Unicode 2.1.8, (instead of all Unicode 3.0.0 characters).
It would be great help for me if I can get these two queries clarified.