I had an Article class and a Publication class, in NewsML, this was
patterned after one NewsML file having references to multiple files, as per
Reuters use. This is a design question, and nothing to do with Rails per se,
I would say; except for the relationship between the DAO and the Business
object, which is identical to MVC in any object oriented programming
language, I would say.
I wanted to be standards based, that is, if in the future the customer
needed to translate a zillion articles to some new future standard, he would
be able to; I still don''t know if I wasn''t knocking my head
against the
wall. YAML???
Victor Kane
http://awebfactory.com.ar
Date: Mon, 20 Mar 2006 10:57:52 -0500> From: "Brent Johnson" <bljohnson@gmail.com>
> Subject: Re: [Rails] Newbie Question about Custom Classes
> To: rails@lists.rubyonrails.org
> Message-ID:
> <9a27dace0603200757r51a8d5d3o892f601ee43ed934@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Thanks for the response. I was just thinking of doing this. But
> here''s what I would normally do in Java. I''d create a
News class, and
> an Article class. The News class would read the XML and create an
> array of Article classes.
>
> So, should I create two models, one called News and one called
> Articles? Is every custom class considered a model? What about some
> utility class that really doesn''t fit as a model?
>
> Thanks again,
>
> - Brent
>
> On 3/20/06, Norman Timmler <lists@inlet-media.de> wrote:
> > I would suggest storing your Article model in the app/models directory
> > and adding a create_from_xml class method, or parse the xml in the
> > controller as you already do.
> >
> > --
> > Norman Timmler
> >
> > http://blog.inlet-media.de
> >
> > _______________________________________________
> > Rails mailing list
> > Rails@lists.rubyonrails.org
> > http://lists.rubyonrails.org/mailman/listinfo/rails
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060320/126f7a05/attachment.html
