Jeff,
I solved the problem by removing the validation from the QName constructor.
It was superfluous anyway, as the XPath compiler performs the necessary
lexical checks prior to instantiation of a QName.
Thanks for reporting this issue.
- Dmitri
----- Original Message -----
From: "Jeff Lansing" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 07, 2003 4:17 PM
Subject: [JXPATH] @name feature
> Hi,
>
> The @name feature for accessing Map entries has a problem. This works
> fine for the simple names used in the example, such as
> getValue("[EMAIL PROTECTED]'home']/zipCode"), and there is even a note
> that says: "Note: At this point JXPath only supports Maps that use
> strings for keys."
>
> The problem is that a HashMap key can be any String, including one that
> contains the character ':'. But the @name feature tries to turn this
> string into the local part of a QName, and if there is a ':', the QName
> constructor throws an exception.
>
> So this feature doesn't work when keys are URL's, which is actually a
> very common thing to do.
>
> Thanks,
>
> Jeff
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
