> We have a lot of legacy systems at my latest gig that all use and output
XML data.
I remember building a few data-driven webpages completely in XML and XSLT
--- and I clearly remember thinking it was the _future_! :-)
I must admit up front that I'm not sure which general approach would be
best ... but some naive thoughts: it seems like you might be able to
leverage an XML to JSON conversion as JSON may be a bit more malleable in
Objective-C space.
Or, depending on the complexity of your project and the maturity of the
following - consider something like
http://code.google.com/p/xsd2cocoa/
or, write one and contribute it back to the community? :-)
On Tue, Mar 25, 2014 at 2:15 PM, Alex Zavatone <z...@mac.com> wrote:
> We have a lot of legacy systems at my latest gig that all use and output
> XML data.
>
> For the purpose of consuming server based XML files, we're looking for a
> method to automate creation of objective c classes that represent the
> internal XML data structure.
>
> Is there any compelling reason not to deserialize into dictionaries
> instead?
>
> Which approach do you guys use?
>
> Thanks in advance.
>
> - Alex Zavatone
> _______________________________________________
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/lutherbaker%40gmail.com
>
> This email sent to lutherba...@gmail.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
