Hi Elena,
I believe the ItemPSVI interface should have only one method that
returns an Object representing the actual value. Given that, you will
need to have bunch of instanceof checks in your code to be able to cast
to the internal Xerces representation, i.e. XDecimal, and then get a
Java decimal
Novice here, but how about setting a constant when the wrapper Object is
created such that one can call a function and get an integer constant which
represents the data type. For example
public static final int DOUBLE = 0, INT = 1, BOOLEAN = 2 ... etc;
protected int validatedValueType = -1;
publ
Hi Christian,
Thank you for your reply.
Christian Schuhegger wrote:
> Your proposal to expose the validated values in the ItemPSVI classes
> sounds like a very good idea to me. Perhaps it is possible to extend the
> internal data representation classes like the XDecimal to return actual
> Java o
Hello,
Elena Litani wrote:
Currently it is not possible to access actual values via any of the API.
Normally, you can access extra XML Schema information via PSVI API (e.g.
normalized value, element type, etc.) [1]**. The PSVI can be accessed
via DOM/SAX in Xerces.
We are thinking to add getActua
Hi Stefano,
Stefano Zacchiroli wrote:
> It seems to me that the following isn't possible with the xerces API, am
> I wrong?
>
> I would like, for example, to validate a document like:
>
> 1999-05-31-05:00
>
> against an XML Schema that states that the "date" element should have
> type xsd:dat
It seems to me that the following isn't possible with the xerces API, am
I wrong?
I would like, for example, to validate a document like:
1999-05-31-05:00
against an XML Schema that states that the "date" element should have
type xsd:date.
Validation works fine, but I would like to access the
