Re: Fetch Specifications defined in the .eomodel *FIXED*
Re: Fetch Specifications defined in the .eomodel *FIXED*
- Subject: Re: Fetch Specifications defined in the .eomodel *FIXED*
- From: Florijan Stamenkovic <email@hidden>
- Date: Sat, 16 Feb 2008 11:22:32 -0400
[2008-02-15 16:53:14 EST] <WorkerThread0> Server exception: The
fetchSpecification <SNIP/> was not allowed to execute on the
server. If your application needs to execute this method, the
security needs to be relaxed by implementing the delegate method
distributionContextShouldFetchObjectsWithFetchSpecification
The original server-side calls for this were catching the error and
just returning null without putting anything in the log.
Interesting... Do you know exactly at which point in your code was
this error generated? Was in on the line where you try to retrieve
the fetch spec object from the model on the server side? When you try
to return that fetch spec over to the client?
The funny thing is that I can call this FetchSpecification using
the normal invokeRemoteMethod() method of EOCustomObject, but if I
try to use the invokeStatelessRemoteMethodWithKeyPath() method of
EODistributedObjectStore, then it throws the above error.
So, if I understand you well, now that you've removed the SQL from
the spec, you can use also stateless RMI to get it?
And before that you could only retrieve it with EO based RMI? This is
really weird. At first it seemed like a valid security precaution,
but the more I think about it, the less sense it makes...
F
_______________________________________________
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