Re: resources not showing via dashboard

[Adam Tuttle]

Hi Gary,

Sorry it took so long to get this message approved, I only got the moderation notification from google groups today.

The reason your resources aren't showing up in the dashboard is that there's a syntax error somewhere in them that prevents Taffy from successfully instantiating and caching them.

Say your CFC would be found at foo.com/resources/fooCollection.cfc (not the REST uri that you specify, but the actual cfc file itself). If you open that URL in your browser, CF will redirect you to the "Component Explorer", but will run into the same error that Taffy had, and will display that error to you (helps to have robust exception info turned on).

This issue is slated to be fixed in whatever version of Taffy comes out after 1.3 (be it 1.4 or 2.0) -- instantiation errors will be displayed in the dashboard -- but for now, that should be an easy-ish way to work around it.

Sorry for the trouble!

Adam

garence wrote:

Hi all ...

Working with Taffy and REST for the first time, and I am having
problems with getting my resources to show. My "collection" and
"member" CFCs are stored in a "resources" directory that is located in
the webroot, and both CFCs contain get functions as well as the
requisite "extends" and "taffy_uri" attributes.

I do have a "taffy" mapping (via CF Admin) to the "taffy-master"
directory that was contained within the zip archive.

The "Getting Started" page from the Taffy wiki has been my guide.

Not surprisingly, I'd guess, I get a HTTP 404 error when attempting to
use an address such as http://myurl.com/api/index.cfm/teams

Any thoughts on what I may be overlooking? Much thanks for any help here.

Gary H-S

--
You received this message because you are subscribed to the Google
Groups "Taffy Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to taffy-users...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[garence]

Much thanks for your reply, Adam! I did manage to get this issue solved; neglected to realize I was using taffy:uri instead of taffy_uri in my script-based CFC resources. Now, my resources show in the dashboard and respond with 200s (!) when running a get.

Though I'm not completely out of the woods ...When attempting a get (via cfhttp) I receive a "400 Your default mime type is not implemented" status code. Could you share or point me to some info that would help me address this issue? Or let me know if more info is needed from me.

Again, thanks for chiming in here.

Gary

[Adam Tuttle]

That's a known issue... It should be fixed in the latest code from the 1.3-dev branch.

If you can't upgrade to that code, you can work around it by either:

* specifying an Accept header with your desired return format (application/json)
* or append the "file type" of your desired return format to the request URL (/api/index.cfm/foo/bar.json)

Adam

garence wrote:

Much thanks for your reply, Adam! I did manage to get this issue
solved; neglected to realize I was using taffy:uri instead of
taffy_uri in my script-based CFC resources. Now, my resources show in
the dashboard and respond with 200s (!) when running a get.

Though I'm not completely out of the woods ...When attempting a get
(via cfhttp) I receive a "400 Your default mime type is not
implemented" status code. Could you share or point me to some info
that would help me address this issue? Or let me know if more info is
needed from me.

Again, thanks for chiming in here.

Gary

On Tuesday, April 2, 2013 8:57:53 AM UTC-5, Adam Tuttle wrote:

    Hi Gary,

    Sorry it took so long to get this message approved, I only got the
    moderation notification from google groups today.

    The reason your resources aren't showing up in the dashboard is
    that there's a syntax error somewhere in them that prevents Taffy
    from successfully instantiating and caching them.

    Say your CFC would be found at foo.com/resources/fooCollection.cfc

    <http://foo.com/resources/fooCollection.cfc> (not the REST uri

    an email to taffy-users...@googlegroups.com <javascript:>.

    For more options, visit https://groups.google.com/groups/opt_out

    <https://groups.google.com/groups/opt_out>.

[garence]

Terrific! I've got things working now.

Thank you thank you.

Gary

On Tuesday, April 2, 2013 8:57:53 AM UTC-5, Adam Tuttle wrote: