beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob Danner" <jac...@bea.com>
Subject RE: [proposal] wsm breakout
Date Thu, 25 May 2006 14:52:11 GMT
+1 (non-binding, just agree it's a good idea)

-----Original Message-----
From: Kenneth Tam [mailto:kentaminator@gmail.com] 
Sent: Wednesday, May 24, 2006 5:23 PM
To: Beehive Developers; dims@apache.org
Subject: Re: [proposal] wsm breakout

+1

FWIW, last time I talked to Eddie, the latest rev of the WSM code only
works on Axis1, but that port shouldn't be a big deal.

On 5/23/06, Davanum Srinivas <davanum@gmail.com> wrote:
> Awesome! +1 from me. We could then use/ship WSM jars as part of Axis2
> for JSR 181 support (with some additional glue code on the Axis2
> side).
>
> -- dims
>
> On 5/23/06, Eddie O'Neil <ekoneil@gmail.com> wrote:
> > All--
> >
> >   I'd like to propose that the WSM sub-directory in beehive/trunk be
> > converted into a sub-project of Beehive.  This makes it
significantly
> > easier to ship WSM independently of the rest of Beehive as it would
be
> > self-contained and wrapped in its own packaging.
> >
> >   The motivation for this is a desire to make Beehive less
monolithic
> > in structure so that separable parts like WSM can evolve without
being
> > tied to the other pieces and to deliver on the obvious interest in
> > JSR-181 in this TSS thread:
> >
> >   http://www.theserverside.com/news/thread.tss?thread_id=40280
> >
> > The next step would be to release a real beta of WSM before the TCK
work starts.
> >
> >   Thoughts / comments / flames?
> >
> > Eddie
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Mime
View raw message