beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ias" <iasan...@hotmail.com>
Subject RE: [Apache Beehive Wiki] Updated: Jsr181Impl
Date Mon, 30 Aug 2004 16:37:46 GMT
> Hi Ias,
> 
> Good point about the javax.jws packages. They probably should 
> be in the api directory. I'll take care of this.
> 

I moved javax packages to src/api, so don't be surprised at the change :-)

Thanks,

Ias

> Cheers,
> 
> -michael
> 
> -----Original Message-----
> From: Ias [mailto:iasandcb@hotmail.com]
> Sent: Friday, August 27, 2004 12:26 AM
> To: 'Beehive Developers'
> Subject: RE: [Apache Beehive Wiki] Updated: Jsr181Impl
> 
> > Hi Ias and all,
> 
> Hi Michael,
> 
> > 
> > A first skeleton for the jsr-181 impl has just been checked in. It 
> > roughly conforms to your proposal for the directory structure. The 
> > reason why the actual structure is a bit different is that 
> it tries to 
> > parallel the controls and netui projects' structure; as we said 
> > earlier, going forward we can easily refactor pieces that we don't 
> > like or that appear impractical.
> > 
> 
> Thanks for your nice initial drops for WSM!
> It seems to me OK except annotation types in runtime. How 
> about moving javax.jws packages to src/api?
> 
> > The next step would probably be to define a bunch of test 
> cases, which 
> > we could then work from; there already is a couple of test cases in 
> > the skeleton.
> > 
> 
> I'm sure that we will enjoy building test cases :-)
> 
> Regards,
> 
> Ias
> 
> P.S. By the way, I saw the directory structure of control and 
> got curious of what was difference between test and 
> drt/tests. Is there any documentation for that, I mean, 
> Beehive standard directory structure. 
> 
> > Cheers,
> > 
> > -michael
> > 
> > PS: The check-in message does have a note that gives a 
> brief overview 
> > over how the skeleton is structured.
> > 
> > -----Original Message-----
> > From: Ias [mailto:iasandcb@hotmail.com]
> > 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();
> > }
> > 
> > 
> > 
> 
> 

Mime
View raw message