Thanks for the heads up, Wolfgang. Although that has an impact on the priorities (particularly w.r.t. becoming 181-compliant), I suggest to keep the work you've done as a custom extension. It's quite valueable for several reasons, for instance, we can use the annotations to test the object model for extensibility and it provides users with a way of configuring their security requirements when they use the Axis platform under Beehive. We can provide annotation support for other runtimes as well (in the future) and thus provide a "Beehive way" to restrict access to Web services. Any ideas, comments?
Cheers, -michael PS: Wolfgang, have you started working on the test cases already? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 06, 2004 10:19 AM To: Beehive Developers Subject: Re: @SecurityRole and @SecurityIdentity Only security annotations will be removed from the final draft of JSR-181, but not the others. I asked him over the yahoo messanger now. Cheers, Wolfgang
