Santiago Pericas-Geertsen wrote:
>
> On Jan 26, 2005, at 4:46 PM, Paul Sandoz wrote:
>
>> The PrimitiveTypeContentHandler and RestrictedCharacterContentHandler
>> are desgined to be abstracted from the details of Fast Infoset and
>> provide support for the built-in encoding algorithms and restricted
>> alphabets.
>
>
> In RestrictedCharacterContentHandler, don't you want to report the data
> as byte[] for the built-in restricted alphabets.
It is meant to return data as char[], the idea is the method just
identifies the set of restricted characters. This may be useful for XSD
validators or binders. However it this feature is not set the parser can
just return these characters as normal character events.
Note that 'hexadecimal' is an encoding algorithm, but it returns
characters (the reason is we wanted to ensure efficient for this one for
the case where 16 characters (power of two) is used).
> Also, what about the
> user-defined alphabets.
>
That is specified in the AlphabetAndAlgorithmContentHandler.
The PrimitiveTypeContentHandler and RestrictedCharacterContentHandler
are just for the built-in encoding algorithms and restricted alphabets
respectively.
> (I've only looked very quickly at the commit message - I may be missing
> something!)
>
No problem.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_fi.dev.java.net
For additional commands, e-mail: dev-help_at_fi.dev.java.net