Re: [Reactor For CF] Reactor R&D

[Kurt Wiersma]

That is is true Matt, but what we have found with our sample application is that we are to abstract the rest of the Reactor API easily through our service layer. The getXyzRecord() is the main method name that held us back. We figure we should propose changing it. It certainly won't be the end of the world if this change doesn't happen but we thought it was something for the community to consider.

I am going to continue work on example to show how we are doing our abstraction. I am going going to need the weekend to complete it. :)

--Kurt

On 3/23/06, Matt Woodward <[EMAIL PROTECTED]> wrote:

On 3/23/06, Kurt Wiersma <[EMAIL PROTECTED]> wrote:
> I maybe trying to hard to compare things to the java world here. In the Java
> world I can swap out Hibernate, Castor, and now even EJB3 just by adjusting
> my DAOs. I can do this because both those frameworks support the standard
> java bean naming conventions.

Naming conventions are part of the picture, but remember that
something like Hibernate works on a different philosophy.  Reactor is
an active record type model in which all your beans extend a base
class in Reactor.  Hibernate doesn't require this because rather than
calling save() directly on your beans, for example, you pass your
beans to Hibernate and it does the work.  Just pointing out that this
isn't exactly an apples to apples comparison.

Matt
--
Matt Woodward
[EMAIL PROTECTED]
http://www.mattwoodward.com



-- Reactor for ColdFusion Mailing List -- reactor@doughughes.net
-- Archives at http://www.mail-archive.com/reactor%40doughughes.net/

-- Reactor for ColdFusion Mailing List -- reactor@doughughes.net -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/