If you know the CFX tag will be deployed with your site - then I don't
see a big deal with invoking a component within your CFC.

As you say no sense in reinventing the wheel.  CF provides the ability
to invoke these objects, this object does something you need to do, so
- to me - it seems wasteful not to use it.

I suppose you could build a CFC wrapper around that CFX tag if you
really wanted to so that if you ever wanted to not use the CFX tag in
the future you would only have to update the code that is dependant on
it in one place.

Bill



On 11/16/05, Seth Johnson (KW) <[EMAIL PROTECTED]> wrote:
> I'm working on a CFC method that accepts a block of text, performs some
> processing on it and returns a struct containing elements from the text.
>
> It occurred to me that I could use CFX_CSVtoQuery to simplify my task a
> great deal, since it provides an easy means of parsing the file, dealing
> with malformed rows, etc.
>
> I'm a bit leery about calling a CFX tag from a CFC since it introduces a
> dependency between the two pieces of code.  On the other hand, I hate
> re-inventing the wheel when I don't have to.
>
> What would you guys do?
>
> Thanks,
> Seth
>
>
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email to 
> [email protected] with the words 'unsubscribe cfcdev' as the subject of the 
> email.
>
> CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
> (www.cfxhosting.com).
>
> An archive of the CFCDev list is available at 
> www.mail-archive.com/[email protected]
>
>
>


--
[EMAIL PROTECTED]
http://blog.rawlinson.us

If you want Gmail - just ask.


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to