Opened 15 years ago

Closed 15 years ago

Last modified 14 years ago

#1325 closed defect (fixed)

Fdo Provider Capabilities xml fix

Reported by: jng Owned by: jng
Priority: low Milestone: Maestro-3.0
Component: Maestro Version: 2.1.0
Severity: trivial Keywords:
Cc: External ID:

Description (last modified by jng)

The fix to #1050 has revealed that Maestro has been working with incorrect provider capabilities xml for quite some time. As a result, features which rely on this xml output, such as the Expression Editor may not function properly against > 2.1 servers in its current form.

However, changing the deserialization logic to match the output from > 2.1 servers will simultaneously break <= 2.1 servers (as they are still outputting the incorrect xml)

The solution as suggested by Tom Fukushima, is to transform the xml into its pre-2.2 form before deserialization only if we're connecting to a <= 2.1 server.

Change History (3)

comment:1 by jng, 15 years ago

Description: modified (diff)

comment:2 by jng, 15 years ago

Resolution: fixed
Status: newclosed

Fixed in r4803.

comment:3 by jng, 14 years ago

Milestone: Maestro-2.1Maestro-3.0

Milestone Maestro-2.1 deleted

Note: See TracTickets for help on using tickets.