Hi Jeff,
Indeed, you're right. It's defined in the XSD as a String...
============================
<!-- ***** Request ID ***** -->
<xsd:simpleType name="RequestID">
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
============================
I think, at the time, I wanted to stick with the messageID policy of the
LDAP Protocol specs (RFC 4511 - ) which defines it as an integer.
====================================
MessageID ::= INTEGER (0 .. maxInt)
maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) --
====================================
My bad. Sorry about that.
I think it can be easily changed though.
Regards,
Pierre-Arnaud
On Thu, Jul 9, 2009 at 10:09 AM, Jeff MAURY <[email protected]> wrote:
> Hello,
>
> I am working on a SOAP implementation of a DSML gateway for ADS. So I
> discovered that studio has a DSML parser.
> However, I have the following question:
> the current DSML parser assumes RequestID should be numeric and should not
> be 0. I looked at the DSML v2 specs and RequestID is declared as a string
> extension but with no restrictions.
> I did not see in the specs any comments that restricts this value to be
> numeric and not 0. It is means as a correlation identifier but with no
> specific syntax.
> So my question is: does this restriction in the DSML parser comes from the
> fact that it has been mapped to an LDAP request ID that is numeric (I'm not
> sure but I guess it) ?
>
> Regards
> Jeff MAURY
>
> --
> La mélancolie c’est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n’est pas capitaliste
> C’est même gratuit pour les perdants
> La mélancolie c’est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c’est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.lastfm.fr/listen/user/jeffmaury/personal
>
