It's not Java's strength, either.
I think you are talking development METHODOLOGY, not language functionality.
You shouldn't be comparing languages on methodology, you should be comparing methods.
Like MVC, or FuseBox.
But I will say there are more Java coders who understand useful methodologies (it's
part of their training) than cold fusion SCRIPTERS.
But well trained programmers will use tried-and-true methodologies for development
whatever the language and environment they are in.
Using completely separate development and delivery environments for each tier helps
force good n-tier development, but there is nothing that forces each tier to be
written diferently.
Just my 2 cents.
Jerry Johnson
>>> [EMAIL PROTECTED] 04/05/02 04:12AM >>>
You have to look at the problem in a slightly different way, the real
strength of three or n-tier applications is that they should offer
separation and independence between layers. So that you could for instance
change your data source completely and handle that change without affecting
your client tier. Or use it in a different business model and not have to
change the presentation or data access layers. But to be able to fully
achieve that as in J2EE the language itself needs to be structured in that
way:
The J2ee goes for 4 tier:
Presentation: Servlets -JSP's
Business : Session EJB's
Integration : Entity beans, JDBC
Data : Database or other datasource e.g. Legacy app
When these tiers are properly defined and adhered to then each layer will be
independent of the implementation of the other layers. What you actually put
in the business layer in a specific case is defined by what doesn't affect
the data integration layer and doesn't affect the presentation layer. For
example what records you select to go in a report as opposed to where you
get the data from and how you lay it out.
Seems to me that by it's very nature CF militates against the n-tier
framework. CF is built to offer rapid development.
I suppose you could achieve something like it in CF by separating the
logical tiers within your CF app. So have included pages or custom tags or
UDF's that handled for instance data acess or presentation or business rules
only. The sort of thing that comes more naturally in OO. I'm sure someone
will say we should be doing that anyway, but seems to me that's not CF's
strength.
-----Original Message-----
From: Kola Oyedeji [mailto:[EMAIL PROTECTED]]
Sent: 04 April 2002 20:02
To: CF-Talk
Subject: RE: Where is the best place to put business rules?
Sorry i should have better phrased my question what would you do in a third
tier that you wouldnt put in the database or in the client?
Kola
> >
> >What would happen if someone decided to update your database using Excel
> >ODBC connection? The stored procedure wouldn't run. But if you had your
> >business logic in the trigger, it would fired upon an insert, update, or
> >delete.
> >
> >
> >That man knows best. Since then I put all my business logic inside of
> >triggers.
> >
> >> >Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
