[fdo-users] OGR provider in 3.4.0

[Greg Boone]

If you still have the issue, send us the test and we can examine it to try and determine the issue.

Greg

-----Original Message-----
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
Sent: Friday, April 17, 2009 11:43 AM
To: FDO Users Mail List
Subject: Re: [fdo-users] OGR provider in 3.4.0

If GA means General Avalibility, and is the one posted on the website as 
the official one,
I have used that one with the same results.

The actual text is from a run with my own
build, which did not include the fix.
I will try to apply the fix monday and observe the outcome.

Thank you for the response.

Regards, Kenneth Skovhede, GEOGRAF A/S



Greg Boone skrev:
> This should be fixed in the 3.4.0 GA. Refer to:
>
> http://trac.osgeo.org/fdo/ticket/498
>
> Greg
>
> -----Original Message-----
> From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
> Sent: Friday, April 17, 2009 7:34 AM
> To: FDO Users Mail List
> Subject: [fdo-users] OGR provider in 3.4.0
>
> I am trying to use the OGR provider in MGE2010 and it fails with an 
> unclassified exception.
>
> Digging a little with a custom build of the OGR provider, I can see that 
> it creates the OgrConnection object
> through the CreateConnection API call.
>
> Then without calling any methods on the object, it disposes the object 
> and returns the
> unclassified exception.
>
> The mapguide debug log shows this for "TestConnection":
> Error: An unclassified exception occurred.
>  StackTrace:
>   - MgFeatureServiceHandler.ProcessOperation line 83 file 
> d:\build\testarossa_nightly\build_30.1\ent\os\server\src\services\feature\FeatureServiceHandler.cpp
>   - MgOpTestFeatureSourceConnection.Execute line 100 file 
> d:\build\testarossa_nightly\build_30.1\ent\os\server\src\services\feature\OpTestFeatureSourceConnection.cpp    
>
>
> And this for a preview:
> Error: An unclassified exception occurred.
>  StackTrace:
>   - MgFeatureServiceHandler.ProcessOperation line 83 file 
> d:\build\testarossa_nightly\build_30.1\ent\os\server\src\services\feature\FeatureServiceHandler.cpp
>   - MgOpGetClasses.Execute line 105 file 
> d:\build\testarossa_nightly\build_30.1\ent\os\server\src\services\feature\OpGetClasses.cpp
>   - MgServerDescribeSchema.GetClasses line 1527 file 
> d:\build\testarossa_nightly\build_30.1\ent\os\server\src\services\feature\ServerDescribeSchema.cpp    
>
>
>
> Since the DescribeSchema call fails without ever calling DescribeSchema 
> on the provider, I thought that the OGRProvider may be missing some 
> required methods.
> I suspect that Rfc23 might be the cause:
> http://trac.osgeo.org/fdo/wiki/FDORfc23
>
> This may be a MapGuide error, but I was hoping that someone from the FDO 
> team had tested the OGR provider with an application that uses
> the new schema functions, or could give a hint towards the problem.
>
> Thanks in advance.
>
>   
_______________________________________________
fdo-users mailing list
fdo-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-users