Matthew,
This is a bug that will be fixed in the next WO update. In the
meantime, the workaround is to call:
public static void registerWebService(String webServiceName, Class
webServiceClass,String[] allowedMethods, boolean isRPC) and passing
'null' for the allowedMethods parameter.
On Feb 16, 2008, at 10:22 AM, Florijan Stamenkovic wrote:
[2008-02-15 16:53:14 EST] Server exception: The
fetchSpecification 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
[2008-02-15 16:53:14 EST] Server exception: The
fetchSpecification 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
One addition and a correction to my own post:
On Feb 16, 2008, at 3:36 AM, Juan Manuel Palacios wrote:
Here's an excerpt of my apache access log (I'm hosting the sandbox
for the new MacPorts website, among other personal things):
66.249.65.203 - - [12/Feb/2008:20:36:23 -0430] "GE
Good evening everyone! I'm subscribing to this list to inquire about
a problem I'm experiencing that has me startled and that I'm
unfortunately relating to the WebObjects 5.4.1 update, given what I've
found so far in my investigations. Now, don't get me wrong, I don't
want to come off ma
