nonononono. that's not what i was trying to do. i was trying to
demonstrate that cf seems to treat them differently in terms of
pathing or some such thing. see, when i add the mapping for
web-inf.cftags into cfadmin, i get an appropriate error on that
createobject call... but when i try to create it outright, i get the
same "could not find..." error. I'm basically just trying to come at
this problem from as many angles as I can, trying to leave no stone
unturned. i can't figure out for the life of me why it can find
web-inf.cftags.component without me doing anything but it can't find
web-inf.cftags.interface unless I add the mapping. that's all.
sorry for the confusion.
marc
On Thu, May 8, 2008 at 6:03 PM, Mark Mandel <[EMAIL PROTECTED]> wrote:
>
> Dude.. you can't create interfaces... it's kinda.. well.. the point of
> interfaces.
>
> components implement interfaces.
>
> If you are having problems, with CFCs implementing interfaces, that is
> one thing, but what you're trying to do isn't designed to work.
>
> Mark
>
> On Thu, May 8, 2008 at 9:17 PM, Marc Esher <[EMAIL PROTECTED]> wrote:
>>
>> Well... that's where I started. Same thing. And that's what led me to
>> simply try viewing the interface itself (not something I do normally).
>>
>> So then I removed the web-inf mapping and tried this:
>>
>> <cfset obj = createObject("component","component")>
>> <cfdump var="#obj#">
>> <cfset obj = createObject("component","web-inf.cftags.interface")>
>> <cfdump var="#interface#">
>>
>> component was created fine, but for interface I got "could not
>> find....". if I add the mapping back, it finds "interface" but I get
>> a more reasonable error ("interface cannot extend itself").
>>
>> Now... if I try creating "web-inf.cftags.component", it doesn't find
>> it without the mapping. So it's as if, under the hood, "component" is
>> special in that CF just knows about it, but that interface isn't so
>> special. I can't createobject on it directly without the web-inf
>> stuff. for example:
>>
>> <cfset obj = createObject("component","component")>
>> <cfdump var="#obj#">
>> <cfset obj = createObject("component","interface")>
>>
>> that will create component just fine, but i get "could not find..."
>> for the interface one.
>>
>> Now, I only bring up all this malarky in an effort to figure out how
>> to get CF to recognize interface without the need for a mapping. As I
>> said, it's not that big a deal, it's just a setup/deployment problem
>> that I'd prefer not to contend with. In fact, probably the way I'll
>> deal with it is just put web-inf/cftags/interface.cfc into my webroot
>> at deployment, since that's just a once-and-done solution with ANT.
>> Still annoying, though.
>>
>> On 5/8/08, Mark Mandel <[EMAIL PROTECTED]> wrote:
>>>
>>> What happens if you try and create an object that implements the interface?
>>>
>>> It may just be a bug in the cfccomponent viewer that tries to
>>> createObject the interface, which, well - wouldn't work.
>>>
>>> Mark
>>>
>>> On Thu, May 8, 2008 at 7:40 PM, Marc Esher <[EMAIL PROTECTED]> wrote:
>>> >
>>> > @Barry: tried that brother! no dice.
>>> >
>>> > @Mark: that's the thing: there is no surrounding code. this happens
>>> > with the most basic interface:
>>> >
>>> > <cfinterface>
>>> > <cffunction name="hi" access="public" returntype="String"/>
>>> > </cfinterface>
>>> >
>>> > trying to view that cfc in the browser throws the error. And, like I
>>> > said, adding that mapping into cfadmin fixes the problem. but I know I
>>> > shouldn't need to do that.
>>> >
>>> > Now, I've gotten this error on 3 different machines so far. BUT, on my
>>> > home PC, which has an identical setup, filesystem-wise, I don't have
>>> > the problem.
>>> >
>>> > strange.
>>> >
>>> > marc
>>> >
>>> >
>>> >
>>> > On Wed, May 7, 2008 at 11:48 PM, Barry Beattie <[EMAIL PROTECTED]>
>>> wrote:
>>> > >
>>> > > and the other thing I encounted last week is the caching of compents,
>>> > > especially when you're still cooking them.
>>> > >
>>> > > I didn't end up tracking down exactly why it was happening, just
>>> > > survived the workaround of clearing the cache (in the CF admin) when I
>>> > > noticed it was happening.
>>> > >
>>> > > just a thought
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > On 5/8/08, Mark Mandel <[EMAIL PROTECTED]> wrote:
>>> > > >
>>> > > > Marc -
>>> > > >
>>> > > > What is the surrounding code you are using to create your component?
>>> > > >
>>> > > > Mark
>>> > > >
>>> > > > On Thu, May 8, 2008 at 2:21 AM, Marc Esher <[EMAIL PROTECTED]>
>>> wrote:
>>> > > > >
>>> > > > > Hey All,
>>> > > > > I'm hitting a weird problem when using cfinterface. the error
>>> is:
>>> > > > >
>>> > > > > The WEB-INF.cftags.interface ColdFusion component or interface
>>> name,
>>> > > > > used to extend or implement the blah.blah.blah component is
>>> invalid.
>>> > > > >
>>> > > > > what this is saying is that it can't find
>>> WEB-INF.cftags.interface isn't valid.
>>> > > > >
>>> > > > > In order to get this to work, I had to add a mapping into cfadmin
>>> to
>>> > > > > point /WEB-INF/cftags to c:\coldfusion8\wwwroot\WEB-INF\cftags
>>> > > > >
>>> > > > > What's weird is that I'd expect cfcomponents to fail, too, since
>>> the
>>> > > > > component.cfc is in the same place as the interface.cfc
>>> > > > >
>>> > > > > Anyone ever see this before? I'd prefer not to have to use the
>>> mapping
>>> > > > > since it creates just one more thing I need to worry about on
>>> > > > > multi-workstation and multi-server deployments.
>>> > > > >
>>> > > > > By the way, this is a run-of-the-mill CF8 install.
>>> > > > >
>>> > > > > Thanks.
>>> > > > >
>>> > > > > Marc
>>> > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > > E: [EMAIL PROTECTED]
>>> > > > W: www.compoundtheory.com
>>> > > >
>>> > > > >
>>> > > >
>>> > >
>>> > > >
>>> > >
>>> >
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> E: [EMAIL PROTECTED]
>>> W: www.compoundtheory.com
>>>
>>> >
>>>
>>
>> >
>>
>
>
>
> --
> E: [EMAIL PROTECTED]
> W: www.compoundtheory.com
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---
