Hi Wolfgang, Thanks for the update. If there is an endpoint interface, the implementation bean is *not* required to have @WebMethod annotations. [The methods in the endpoint interface isn't required to have @WebMethod annotations either.] So there shouldn't be an exception in this case. It's correct, though, to throw an exception if the signature in the endpoint interface doesn't match the one in the implementation bean, or if there are methods that are specified in the endpoint interface and that are not implemented by the bean. Does that make sense?
Cheers, -michael -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 9:52 AM To: Beehive Developers Subject: Re: @SecurityIdentity, @SecurityRoles Hi Michael, Thank you very much for the detail explanation. > Do your latest patches comply with this ? Yes, exactly. My implementation validates two things on this. The first one checks whether the service implementation bean implements all methods in the endpoint interface. If it does, okay. Otherwise, the processor will throw an exception. The second one checks whether those methods in the service implementation bean are annotated with @WebMethod. If they do, okay. Otherwise, the processor will throw an exception. >(sorry, haven't had a chance to look at them yet)? No, not at all. Plz take your time. I know u r busy. :) Thanks in advance. Wolfgang
