Hi Dave, would you be willing to share any information as to exactly how you've
divided the functionality between the items described below.
Another way to identify what goes where is to follow the natural
MVC boundaries: Model = Java, View = CF, Controller = either, but
probably CF. IMHO,
Sure. Business objects (i.e. the Model, e.g. Agent, Location,
Customer, User, Quotes, etc) all were Java. DAOs too as I recall
(I remember discovering that I could instantiate
coldfusion.sql.QueryTable objects in my Java DAOs). Everything
else (views, filters, listeners) was done in CF.
Does
This can, of course, be a vital tactic for job security :-)
On 8/26/06, Denny Valliant [EMAIL PROTECTED] wrote:
So you code away in FB, great that's just great, but the next programmer
to get your code doesn't know FB. Or any framework. And is expected
to maintain it. Ouch! Time to learn...
On 8/26/06, James Holmes [EMAIL PROTECTED] wrote:
This can, of course, be a vital tactic for job security :-)
See, that's where the Boogie Nights Effect come into play. [-=
When homecheese is showing his shlong for poops and titters,
it's almost funny. When he's doing it to support his
I've been recently exploring the use of Java within CF using the cfobject
tag...very handy indeed to expose all those built in classes.
Are there any guidelines as to when one should be porting parts of a Coldfusion
application directly to Java?
Since CFMX is compiled into Java anyway, would
Are there any guidelines as to when one should be porting parts of a ColdFusion
application directly to Java?
My first answer would be: Whenever you want!
My second answer would be: Whenever ColdFusion can't easily do what you need it
to, but Java can.
--
Ian Skinner
Web
Hi Ian, thanks for your input.
Here's another question.
what if CF can do (A), Java can do (A)
Is there any advantage to Java doing (A) over CF?
~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
Hi Ian, thanks for your input.
Here's another question.
what if CF can do (A), Java can do (A)
Is there any advantage to Java doing (A) over CF?
I always hear Java is better at heavy processing (like major number crucnhing)
than CF is.
Java has built-in packages that allow things like
Here's another question.
what if CF can do (A), Java can do (A)
Is there any advantage to Java doing (A) over CF?
Maybe, maybe not. My first thought is that I would not want to reinvent the
wheel. If I can do it using CF's usually simple syntax, I would prefer to do
it that way. I'm not
Since you can invoke Java objects into CF, you can leverage the data types
of Java and other methods to augment CF. This is not uncommon.
Why use CF over Java? Well, you don't compile the Java object after you
manipulate it in CF. You let the CF parser do that for you at run-time. CF
is
Another consideration, besides the optimization (*grin*), is
maintainability.
This is one I struggle with constantly, in my mind.
I can't help but use some of the nifty stuff that's out there. Maybe it's
java
cuz I need it fast or portable (, or there's a java wheel I need. ;-)
Maybe it's
Another way to identify what goes where is to follow the natural
MVC boundaries: Model = Java, View = CF, Controller = either, but
probably CF. IMHO, that allows each language to play to its
strengths. I followed this division of labor in a Mach-II app and
it worked great. But as Denny pointed
12 matches
Mail list logo
