The service object PROBABLY is calling getByAttributes() ... look at the gateway method. This returns an array. getByAttributesQuery returns a query.
I would remove the getByAttributes() method that returns an array. You don't need it. (use Peter Bell or Paul Marcotte's iterators /IBO for a more efficient way to get encapsualtion with performance benefits of a query). Also, on your service make sure you change getReleasess() to returntype of 'query' once you change it to use getByAttributesQuery() Alan ________________________________________ From: [email protected] [EMAIL PROTECTED] On Behalf Of Brian Kotek [EMAIL PROTECTED] Sent: 06 May 2008 13:59 To: [email protected] Subject: [CFCDEV] Re: Help in learning service objects: How to use It's returning an array of Release objects, not a query. To use this you'd have to loop over the array and call getStory() on each one. A better option is probably to use getByAttributesQuery() instead, which will give you back a query instead of an array of objects. On Tue, May 6, 2008 at 7:59 AM, wkolcz <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: 'The gateway has a getByAttributesQuery method. Use this for a query and change the service cfc to use this on your 'getreleasess()' method.' According to the getReleasess(), it does use that Gateway function. I can invoke it, pass in the instances of the Gateway and the DAO, but I am getting back an array of the same object. How do I use these to output the record of the column "story". My cfdump looks like this: 1 component medportal.apps.newsroom.model.releases.releases [short version] 2 component medportal.apps.newsroom.model.releases.releases [short version] 3 component medportal.apps.newsroom.model.releases.releases [short version] 4 component medportal.apps.newsroom.model.releases.releases [short version] 5 component medportal.apps.newsroom.model.releases.releases [short version] 6 component medportal.apps.newsroom.model.releases.releases [short version] 7 component medportal.apps.newsroom.model.releases.releases [short version] 8 component medportal.apps.newsroom.model.releases.releases [short version] 9 component medportal.apps.newsroom.model.releases.releases [short version] 10 component medportal.apps.newsroom.model.releases.releases [short version] 11 component medportal.apps.newsroom.model.releases.releases [short version] 12 component medportal.apps.newsroom.model.releases.releases [short version] 13 component medportal.apps.newsroom.model.releases.releases [short version] 14 component medportal.apps.newsroom.model.releases.releases [short version] 15 component medportal.apps.newsroom.model.releases.releases [short version] 16 component medportal.apps.newsroom.model.releases.releases [short version] 17 component medportal.apps.newsroom.model.releases.releases [short version] 18 component medportal.apps.newsroom.model.releases.releases [short version] 19 component medportal.apps.newsroom.model.releases.releases [short version] 20 component medportal.apps.newsroom.model.releases.releases [short version] 21 component medportal.apps.newsroom.model.releases.releases [short version] 22 component medportal.apps.newsroom.model.releases.releases [short version] 23 component medportal.apps.newsroom.model.releases.releases [short version] 24 component medportal.apps.newsroom.model.releases.releases [short version] 25 component medportal.apps.newsroom.model.releases.releases [short version] 26 component medportal.apps.newsroom.model.releases.releases [short version] 27 component medportal.apps.newsroom.model.releases.releases [short version] 28 component medportal.apps.newsroom.model.releases.releases [short version] 29 component medportal.apps.newsroom.model.releases.releases [short version] 30 component medportal.apps.newsroom.model.releases.releases [short version] 31 component medportal.apps.newsroom.model.releases.releases [short version] 32 component medportal.apps.newsroom.model.releases.releases [short version] 33 component medportal.apps.newsroom.model.releases.releases [short version] 34 component medportal.apps.newsroom.model.releases.releases [short version] 35 component medportal.apps.newsroom.model.releases.releases [short version] 36 component medportal.apps.newsroom.model.releases.releases [short version] 37 component medportal.apps.newsroom.model.releases.releases [short version] 38 component medportal.apps.newsroom.model.releases.releases [short version] 39 component medportal.apps.newsroom.model.releases.releases [short version] 40 component medportal.apps.newsroom.model.releases.releases [short version] 41 component medportal.apps.newsroom.model.releases.releases [short version] 42 component medportal.apps.newsroom.model.releases.releases [short version] 43 component medportal.apps.newsroom.model.releases.releases [short version] ________________________________ From: Alan Livie <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> Sent: Tuesday, May 06, 2008 4:45 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [CFCDEV] Re: Help in learning service objects: How to use The gateway has a getByAttributesQuery method. Use this for a query and change the service cfc to use this on your 'getreleasess()' method. To save yourself doing this all the time you can make customise the generator to generate the cfc's they way you want them. Also, a good tip .... these generated gateways and DAO's .... when you want to add more methods etc do it in a different cfc and subclass the generated ones with your custom ones. Then if you add or remove columns from the db table the gateways and DAO's are based on you can just regen the cfc's and overwrite without worrying about all your custom stuff. It doesn't work so well with services as my services are usually assosiated with more than one Gateway and DAO. Another option is Transfer (before someone recommends it :-) ) Alan ________________________________________ From: [email protected]<mailto:[email protected]> [EMAIL PROTECTED]<mailto:[email protected]>] On Behalf Of wkolcz [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: 06 May 2008 12:36 To: [email protected]<mailto:[email protected]> Subject: [CFCDEV] Help in learning service objects: How to use I downloaded and installed Brian Rinaldi's Illudium PU-36 Code Generator. It produced a DAO, a Gateway, a bean, and a service object. I am attempting to learn how a service object works, or, more imporantly, how to use the service object. It comes with the following functions. (mine happens to be releasesServices.cfc) init (takes an instance of the DAO and the Gateway) createreleases getreleases getreleasess savereleases deletereleases So basically, I am getting the DAO (create,get,save,delete) and a Gateway (getreleasess)? How can I call the gateway to return a list of records. Or, more important, how can I use the results on my view? Its returned as an array. What am I missing. I need the education :-) I can setting my controller to: Here is the full function: --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
