Hi Ias, The directory structure looks good, thanks much. (I am sure we'll change things around as we go :)
Regarding the TCK: being a newbie on this project, I thought that the final decision whether the TCK would be developed as part of the Beehive project was still with the JSR-181 expert group (see http://wiki.apache.org/beehive/Jsr181Impl, section 8 "Open Issues"). Under this assumption, should we focus more on tests and test cases in general than the TCK for the time being? Cheers, -michael -----Original Message----- From: Ias [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 1:47 PM To: 'Beehive Dev' Subject: RE: [Apache Beehive Wiki] Updated: Jsr181Impl > +== Directory Structure == > + > + * wsm > + * src > + * jsr181 > + * annotation - JSR 181 annotation types > + * processor > + * api - JSR 181 Processor API > + * components - Processor components > + * runtime > + * api - Runtime plug-ins APIs > + * plugins - Implementations of Beehive > + * test > + * tck > + * extra > > == Documentation == > > As a proposal on directory structure for WSM was added, I'd like to suggest: 1. Decide directory structure in a week. (During the time, import JSR 181 annotation types from JSR 181 ED or make a clean room annotation types for JSR 181.) 2. Develop TCK as tests for WSM. Thanks, Ias P.S. Here's an example of JSR 181 anntoation types for Beehive WSM. /* * Copyright 2001-2004 The Apache Software Foundation. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ package javax.jws; import java.lang.annotation.ElementType; import java.lang.annotation.Retention; import java.lang.annotation.RetentionPolicy; import java.lang.annotation.Target; /** * The <code>HandlerChain</code> annotation associates the Web Service * with an externally defined handler chain. This annotation is * typically used in scenarios where embedding the handler configuration * directly in the Java source is not appropriate; for example, where the * handler configuration needs to be shared across multiple Web Services. * * It is an error to combine this annotation with the * <code>SOAPMessageHandlers</code> annotation. * * @version 1.0. * */ @Retention(RetentionPolicy.RUNTIME) @Target({ElementType.TYPE}) public @interface HandlerChain { /** * Location of the handler chain file. The location is a URL, which * may be relative or absolute. Relative URLs are relative to * the location of the Java WS file at the time of processing. */ String location(); /** * The name of the handler chain within the file */ String name(); }
