The challenge with DWFs is that they are actually compressed directories of files and that have a unique id and an xml that references the unique id.
Each time a DWF is created, it creates a unique ID. This information is referenced in MapGuide. The Load Procedures deal with this. Without using load procedures, you could probably manually edit the Data Source in MapGuide to reflect that. Obviously that is not really an optimal solution so the best way would probably be to write some code to automatically do it I imagine that using Jackie's Maestro API would give you all the functionality on the MG side, but you'd probably have to rip through the DWF too, and note that different versions of DWF have different directory structures/files included so that can cause issues too. Hope that helps, and sorry there's no easy solution. I have patches of gray hair as a result ;) Jonathon On Wed, Aug 24, 2011 at 8:50 AM, frosty1_4me <[email protected]> wrote: > I too would like to know how this all works and if updating the dwfs in > this > manner avoids the Load Procedure and update issues I"m currently dealing > with. My issue is that since I can't just the Load Procedures manually, my > only other option is to update the dwfs that reside in the actualy library > repository which I would like to avoid. > > However, if an alias can be setup and the layers/datasources changed to use > those alias's then this would hopefully make updating those dwf's much > easier. > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/Alias-to-external-DWF-files-tp5992002p6720702.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users >
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
