BinaryLogicOpType maxOccurs="unbounded"

[Yewondwossen Assefa]

Hi There,

  I have seen the bug and I guess I missed the maxOccurs="unbounded"
during implemetation. I have seen a couple of slds built with mutilple
binary operations and always though that It was an SLD problem ;)

  I will try to adress this before the next release. The changes are not
very trivial in the current architecture.

  Later,

huub fleuren wrote:
> Hi List,
>
> Today i filed a bug concerning a wrong interpretation (afaik) of the
> <Filter /> specification of <BinaryLogicOpType />
>
> BinaryLogicOpType is defined as:
>
> <xsd:choice minOccurs="2" maxOccurs="unbounded">
>
> But mapserver doesn't work like this when it uses an SLD xml
> It wants every operartor to be binary which leads to awkward xml
> like this:
>
> <Filter>
> <Or>
>  <And>
>   <And>
>    <And>
>     <1.../>
>     <2.../>
>    </And>
>    <3.../>
>   </And>
>   <4.../>
>  </And>
>  <5.../>
> </Or>
> </Filter>
>
> the specification is intuitively more logical
>
> <Filter>
> <Or>
>  <And>
>   <1.../>
>   <2.../>
>   <3.../>
>   <4.../>
>  </And>
>  <5.../>
> </Or>
> </Filter>
>
> Mapserver won't crash (it just doesn't look at the third etc.
> critera), so... though it isn't strickly a bug, it bugs.
>
>
> http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1277
>
>
>  Regards, Huub
>
>
> --
>
>  huub
>

--
----------------------------------------------------------------
Assefa Yewondwossen
Software Analyst

Email: assefa at dmsolutions.ca
http://www.dmsolutions.ca/

Phone: (613) 565-5056 (ext 14)
Fax:   (613) 565-0925
----------------------------------------------------------------