Re: Fetch and Direct to WebServices
Re: Fetch and Direct to WebServices
- Subject: Re: Fetch and Direct to WebServices
- From: email@hidden
- Date: Thu, 14 Jun 2007 01:26:54 -0400
Philippe thanks for the response,
I am completely baffled by what I may be doing wrong and am hoping a
detailed explination of the process I am following may highlight where
I am at making a mistake and you may be willing to send me an answer
that indicates this.
I've tried what you suggest but remain frustrated. Here is some more
detail:
I am using EOModeler 5.3.4, WO 5.3.3 on Mac OSX. I am selecting the
entity in EOModeler for the FetchSpec, creating the fetch, naming it
and resaving the model. I then start a Direct to WebServices project
and create a New Service and make public the entity with the FetchSpec.
From there I create the New Operation, associated it with the service,
select the entity with the FetchSpec, select Search and give it the
same name as the FetchSpec. When the entity opens, all properties are
available and nothing retated to the FetchSpec is available. I tried
your recommendation for cloning but nothing.
Is there anything in my process that looks wrong? Any suggestions?
Thanks again,
--Mat
Hi,
I had some troubles like yours when I created fetschpecs with WOLips.
For me, it only works when I create with EOModeler.
By the way, I encoutered some issues when I wanted to associate an
operation based on a fetchspec to another webservice. The name of the
operation has to be unique and if the operation's name is different
from the fectschpec's name, it does not work (all objects of the
entity are fetched).
The solution : clone the operation, associate to another web service,
remove the entity from the DefaultWebService, rename the operation
correctly and it works fine.
Config : WO 5.3.3 on Mac OS X
---------------------------------------------------------------
Philippe Rabier - SOPHIACOM
38 rue des Mathurins
F-75008 Paris
Téléphone : 33 1 41 40 05 80
Télécopie : 33 1 41 40 05 89
Web : http://www.sophiacom.fr
---------------------------------------------------------------
On 13 juin 07, at 11:51, email@hidden wrote:
Date: Wed, 13 Jun 2007 14:44:55 -0400
From: email@hidden
Subject: Fetch and Direct to WebServices
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset="us-ascii"; format=flowed
I can't seem to get any fetch spec to show up in the WebService
Assistant of Direct to WebServices. I've asked this before and am
hoping the second try will catch the eye of someone helpful in the
know.
The Apple documentation on this is:
----------------------------------------------------------------
"When you make public an entity with fetch specifications in the Web
Services Assistant, the Assistant creates operations corresponding to
those fetch specifications. You can see the arguments the operations
require and the return values in the Arguments pane and the Return
Values panes, respectively.
To modify an operation that is based on a fetch specification from a
data model, you must edit the fetch specification in the model and
rebuild the application."
----------------------------------------------------------------
I can't seem to make this true. Would anyone who knows how to make
this
true please explain how they do it? Is it possible to do a fetch
derived from a stored procedure? I would be excited just to see ANY
type of fetch become visible in the Service Assistant.
Thanks,
--Mat
________________________________________________________________________
AOL now offers free email to everyone. Find out more about what's free
from AOL at AOL.com.
=0
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden