[mapguide-internals] Ticket 1050 fix

[Tom Fukushima]

Ouch.

Can you preprocess the provider capabilities XML and do a global string replacement of 

FunctionDefinitionCollection -> FunctionDefinitionList
ArgumentDefinitionCollection -> ArgumentDefinitionList

before sending it to the part of the expression editor that uses this XML?

To be safe you may want to do the various combinations:
<FunctionDefinitionCollection>
</FunctionDefinitionCollection> 
<FunctionDefinitionCollection/>
And same for ArgumentDefinitionCollection.
And also make sure the server is a 2.1 or less server before doing the replacement.

Tom

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Saturday, April 17, 2010 9:06 AM
To: mapguide-internals at lists.osgeo.org
Subject: [mapguide-internals] Ticket 1050 fix


Hi All,

I notice that a fix was made to 1050 so that it returned provider
capabilities xml that matches the original xsd schema. 

Currently Maestro's Expression Editor relies on the provider capabilities
object to provide function lists and auto-completion. However this used the
incorrect xml elements because we didn't know at the time, that the server
was not generating the correct xml.

This presents a dilemma for me, I can update Maestro to use the *correct*
provider capabilities object, but in the process I would be breaking the
Expression Editor if it is used against versions of MapGuide < 2.2 as they
output the incorrect version of the capabilities xml.

I'm not quite sure how to handle this change.

- Jackie
-- 
View this message in context: http://n2.nabble.com/Ticket-1050-fix-tp4917831p4917831.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals