Actually I tried that as well - just copied the CFC to a new name,
"DPDataSource_BrandNewVersion" and tried calling it - same exact
behavior.


The root of the problem, I think, is that the call is being made with
the fully qualified name but the generic name is being returned: I've no
idea how this could happen. once I figure out how it might happen then I
can start working with the host to figure it.  But so far, nothing (I'm
probably going to destoy my dev server trying to set this up.)


Jim Davis


-----Original Message-----
From: Tom Kitta [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 11:20 PM
To: CF-Talk
Subject: Re: Wierd CFC Path Problem - Question on CFC types (HELP!!)


I think it could go away if you change a bit the name of the CFC in
question (if that is possible). A lot of problems can arise when there
is naming collision.

For example it is bad thing to have a variable and function named the
same way, I expect the same thing might happen with CFC. It was wired
for me to find out one day that my functions stopped to work ... then I
found a variable with the same name - variable takes higher preference
than function name. In another instance there was no variable but a
query .. same deal .. then in another instance there was no conflict at
all but it didn't work, renaming fixed it. I think the translation from
CF to java might not be perfect in all instances under all wired
circumstances.

Thus, try changing the CFC name and maybe even location (full path). I
bet it will solve the problem of CFC type but create another related to
a new name.

The idea of a mapping created by some user might be getting you closer
to the root of the problem, I don't know.

TK
  ----- Original Message -----
  From: Jim Davis
  To: CF-Talk
  Sent: Tuesday, October 28, 2003 10:10 PM
  Subject: RE: Wierd CFC Path Problem - Question on CFC types (HELP!!)

  Unfortunately I can't - the production server is hosted/shared
  (CrystalTech.com).  But I don't think this is the case anyway - it
just
  doesn't "feel" like a server issue.  I can create new CFCs, change
those
  I have, and everything works: I just get the wrong type back.

  They believe that this is coding issue (of course) and I beleive that
it
  must be a server issue (since it worked yesterday).  A new mapping or
  something COULD have messed thing up, but the behavior is very odd: it
  does find MY CFC (not another one or have trouble finding it as I
think
  a mapping problem would).  But the type of the CFC is the generic name
  only, not the fully qualified name - depsite the fact that I can only
  call the CFC with a fully qualified name.

  My CFCs are in "com.depressedpress." - what if another customer
created
  a mapping to "com"?  I would expect to have an error on
initialization,
  right?  Or could it somehow be finding my CFC in a different way and
  dropping the name as it found it?

  Should I be using "com.depressedpress" at all or maybe something more
  like "com_depressedpress" (so that "com" isn't the mapped folder...)?

  I'm going crazy on this one...

  Thanks,

  Jim Davis

  -----Original Message-----
  From: Tom Kitta [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, October 28, 2003 9:53 PM
  To: CF-Talk
  Subject: Re: Wierd CFC Path Problem - Question on CFC types (HELP!!)

  Have you tried restarting both servers? It solved many strange
problems
  for me like invisible templates etc.

  TK
    ----- Original Message -----
    From: Jim Davis
    To: CF-Talk
    Sent: Tuesday, October 28, 2003 8:42 PM
    Subject: RE: Wierd CFC Path Problem - Question on CFC types (HELP!!)

    Sorry - I'm starting to get frantic on this one.

    When I call:

    <cfdump var="#CreateObject('Component',
    'com.Depressedpress.DPDataSource')#">

    I get back a type of "DPDataSource" but I get an error if I try:

    <cfdump var="#CreateObject('Component', 'DPDataSource')#">

    How could this happen?  With the same code the problem only occurs
in
    production (hosted at CrystalTech.net) not on Develoment (I've tried
  to
    mimic the environments as closely as possible, both CFMX 6.1).  It
had
    worked on production until sometime yesterday.

    Any ideas at all one what could cause this?  Even crazy ones. I'm
  facing
    a nasty evening if I can't figure this out.

    Jim Davis

    -----Original Message-----
    From: Jim Davis [mailto:[EMAIL PROTECTED]
    Sent: Tuesday, October 28, 2003 6:24 PM
    To: CF-Talk
    Subject: RE: Wierd CFC Path Problem - Question on CFC types

    I'm now seeing my problem in most of my CFCs - but only on the
    production (hosted) server.

    For example if I call:

    <cfdump var="#CreateObject('Component',
    'com.Depressedpress.DPEvents.Festival')#">

    The resulting component is of type "Festival", not
    "com.Depressedpress.DPEvents.Festival"

    Since I'm specifying the full path in my create, how could it get
    truncated?  I would think that the only way to get truncated to the
  base
    name would be for a mapping to that specific folder to be in effect
-
  is
    that true?

    It seems that a mapping to the "com" folder wouldn't do it, for
  example.

    How can this occur (when I call a fully qualified type and it
returns
  an
    unqualified, generic type)?

    Jim Davis

      _____  

    _____  

  _____  


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to