I'll take a look at the XPath stuff in SDO and see if we can avoid the
annotations for the new assembly model schema. It may not be simple so we
may have to annotate the schema to start with and fix this later.
Cheers,
On 08/08/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
Not sure without looking at the code. Ed wrote the XPath stuff.
Cheers,
On 08/08/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> Pete Robbins wrote:
> > I think the problem is that you can define an elements in a type such
> as:
> >
> > <element name="myElem" type="xs:string" maxOccurs="unbounded">
> > <element name="myElem.1" type="xs:string">
> > This would lead to properties on the SDO type named "myElem" (which is
>
> > many-valued) and "myElem.1".
> >
> > So, when I code
> > xxxxxxx->getCString("myElem.1");
> > does that return value index 1 from "myElem" or the single valued
> > property "
> > myElem.1".
> >
> > I think that is why we decided to disallow dots in property names.
> >
> > Cheers,
> >
>
> Pete,
>
> I believe that an XPath implementation needs to support this, and this
> is actually independent of SDO as dots are allowed in XSD element names.
>
> You would just escape the dot, like this:
> xxxxxxx->getCString("myElem%2E1"). Would that work for SDO as well? How
> is our XPath support implemented?
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Pete
--
Pete
