[fdo-internals] RE: [mapguide-internals] FDO Provider naming change with King Oracle

[Greg Boone]

The name change may possibly have occurred when porting the trunk code back to the 3.4 branch. 

	Revision: 4457
	Author: gregboone
	Date: 6:07:10 PM, Thursday, March 19, 2009
	Message:
	Ticket #45: Ported Latest KingOracle Submission to 3.4 Branch

What is the name expected to be? We can revert this change and release a patch if needed.

Greg.


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Monday, July 27, 2009 5:20 AM
To: MapGuide Internals Mail List; FDO Internals Mail List
Subject: [fdo-internals] RE: [mapguide-internals] FDO Provider naming change with King Oracle

That kinda sucks for existing users...

I wonder if this was an intentional change in fdo, or an accidental rename in the template?  I'm tempted to revert to the old value in the MapGuide setup just to limit impact on our users.

Jason

-----Original Message-----
From: Jackie Ng
Sent: Monday, July 27, 2009 1:19 AM
Subject: RE: [mapguide-internals] FDO Provider naming change with King Oracle


/me thinks that this information is not actually used when building the FDO
distribution, seeing as the providers.xml template calls it OSGeo.KingOracle

http://trac.osgeo.org/fdo/browser/branches/3.4/providers.windows.template.xml

- Jackie


Jason Birch wrote:
> 
> Is that in the latest build only?
> 
> It looks like it's still called King.Oracle in the provider source, so I
> wonder if it's just an oversight in the installer.
> 
> http://trac.osgeo.org/fdo/browser/branches/3.4/Providers/KingOracle/src/Provider/KgOraProvider.h
> 
> Jason
> 
> -----Original Message-----
> From: Zac Spitzer
> Sent: Monday, July 27, 2009 12:46 AM
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] FDO Provider naming change with King Oracle
> 
> Just been playing with King Oracle and the 2.1 beta and discovered
> that the naming has changed from King.Oracle to OSGeo.KingOracle
> 
> which broke a lot of my feature sources, probably a good one for the
> release notes. a quick edit of the xml solved the problem
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals