The UsbDevice Interface declares these three methods: to potentially
throw UnsupportedEncodingException:
public String getSerialNumberString() throws UsbException,
UnsupportedEncodingException, UsbDisconnectedException
public String getManufacturerString() throws UsbException,
UnsupportedEncodingException, UsbDisconnectedException
public String getProductString() throws UsbException,
UnsupportedEncodingException, UsbDisconnectedException
However all three strings are defined in the USB 2.0 spec to be UTF-16
little endian encoded. The USB 1.1 spec isn't as explicit but I believe
it's effectively the same in practice.
Since all conforming Java VMs are required to support the UTF-16
big-endian and little-endian encodings is there any real chance this
exception might be thrown? maybe in J2ME somewhere?
--
Elliotte Rusty Harold [EMAIL PROTECTED]
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
javax-usb-devel mailing list
javax-usb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
