Feature Joins totally broken

[jng]

I migrated one of our datasets to MGOS 2.0.0 RC1 and noticed the layers that are joined to an external database failed to render, where it previously rendered fine under v1.2.0

As a test I did a simple join of the Sheboygan parcels and its parcel database in MapGuide Studio 2009 beta (from the sample data), created a layer that is themed from one of the joined attributes (RTYPE) and noticed that it too failed to render.

I repeated the same process in MapGuide Studio 2008 (MGOS 1.2.0), and the joined parcels did render as expected.

Looking at the error logs, I found lots of these messages...

<2008-01-29T17:40:35> Administrator

Error: Failed to stylize layer: LayerDefinition3

An unclassified exception occurred.

StackTrace:

• MgMappingUtil.StylizeLayers line 781 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_19.3\mgdev\server\src\services\mapping\MappingUtil.cpp Failed to stylize layer: LayerDefinition3

An unclassified exception occurred.

[jng]

Steps to reproduce.

In MapGuide Studio 2008 (MGOS 1.2.0)

1. Load Parcels.shp from the MapGuide Studio sample data via load procedure. Create both feature source and layer.

2. Create an ODBC connection to parcels.mdb in the sample data. Upload the database as part of the resource data.

3. Create a feature join between the Parcels (shp) and the Parcels (mdb) on the "ID" property. I used "Joined" as the name prefix.

4. Create a layer from the Parcels(shp) feature source. Use the extended feature class. Create a polygon theme on the property "Joined_RTYPE".

5. Preview the layer, and the joined parcels are rendered correctly.

In MapGuide Studio 2009 beta. (MGOS 2.0.0 RC1)

Repeat the above steps. The joined parcels will not render when you reach the 5th step.

[jng]

This problem still persists in MGOS 2.0.0RC2

[brucedechant]

I have attached 2 pictures showing both the preview of the above joined feature sources and a map using this layer. However, I did notice that it took a considerable amount of time for the image to actually appear (several minutes). So I believe joins are working correctly just that in this case performance is slow.

A new defect to address the performance issue should be created.