We all want it to be the best it can be obviously. I think the
input/conversation is all good. :)
It all depends on how we categorize this philosophically I suppose. There are
definitely good reasons to have this code in the WS family. There are also
good reasons to have this code in the Beehive project.
The main reason IMO to keep this implementation in Beehive is because of the purpose of
Beehive. It is an integrated metadata-driven framework that leverages the latest from
Sun J2SE 5.0, especially the JSR-175 annotation style. It provides an easy-to-use
programming model for building webapps. It targets a user with fewer of the
"rockstar J2EE dev" skills, a user who is more of a business developer and
doesn't want to deal with all of the plumbing. And Beehive will also be extensible to
future subprojects that also leverage JSR-175 style metadata. JWS is an important brush
stroke on this canvas.
We do need to flush out the details of the implementation proposal obviously.
Once we have that in hand should we call a more formal vote or is now the time
to settle it?
-----Original Message-----
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 12, 2004 12:17 PM
To: Beehive Developers
Subject: Re: can i help
Please don't use "JWS" .. that's already used in Axis for Java Web
Services as you may know ...
I didn't realize this was an RI for a JSR. If so I'm even more confused why
its not a project on its own .. amongst the other various WS projects.
Oh well - its finally up to the developer community, of course. If you feel
comfortable with the situation then I withdraw my objection.
Sanjiva.
----- Original Message -----
From: ". Ias" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, August 13, 2004 12:57 AM
Subject: Re: can i help
Here's my understanding and opinion on this issue so far as a creator of
Axis WSM.
1. Beehive JWS, of which name is from its wiki page although I called it
Beehive WSM (I agree that JWS is better based on its history), is supposed
to implement JSR 181 as RI that BEA must provide because they lead the
spec
in JCP.
2. Beehive team has several committers (from BEA and Tmax) including the
spec lead of JSR 181 and me for the job.
3. As I proposed roughly before, Beehive JWS consists of two layers, a JSR
181 processor and a possible integration with a web services platform such
as Axis.
4. As far as I'm concerned, it would be good for Web Services project to
co-work on JSR 181 with BEA inside Beehive project. The reason is that JSR
181 belongs to web services technologies, but also is a practical
application of metadata newly introduced in J2SE 5.0. Beehive requires and
uses metadata a lot. We can expect help and guidance from Beehive
developers who are already very familiar with metadata.
5. Regarding the current situation that there's no code for Beehive JWS
contributed initially by BEA, I propose that JSR 181 API part should be
checked in as soon as possible to Beehive SVN repository and we should
keep
discussing how we will implement it and integrate it with Axis. I'll make
my proposal more detailed within a week, and probably talk about it in
Axis
2 Summit as well. In my humble opinion, we all have a nice chance to build
an open source implementation from the early stage of its targeted spec
with spec folks and impl folks :-) In other words, the two groups can
interact productively and progressively to make a JSR 181 implementation
robust in both technical and pragmatical sense.
Thank you all for your interest in JWS,
Ias
From: "Sanjiva Weerawarana" <[EMAIL PROTECTED]>
Reply-To: "Beehive Developers" <[email protected]>
To: "Beehive Developers"
<[email protected]>,<[EMAIL PROTECTED]>
Subject: Re: can i help
Date: Thu, 12 Aug 2004 21:05:49 +0600
+1 .. my personal pref is if the work is directly Web services
related it should be done under the WS PMC as much as possible.
In addition to the incubation related advantages Dims points
out I also think others will discover this work more easily
if its in the WS family.
Sanjiva.
----- Original Message -----
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: "Beehive Developers" <[email protected]>
Sent: Thursday, August 12, 2004 8:10 AM
Subject: Re: can i help
Heather,
My 2 cents, i don't really care where it is done, as long as it gets
done :) We can do this either under the Beehive PMC or WS PMC.
Objective definitely is to get this done quickly and not get stuck
because beehive is still in incubation. Especially since this is ALL
new code that needs to be written and there is NO existing code
contributed in the incubation phase from BEA, it would make sense to
do this under WS PMC (so that we can release really quickly w/o
waiting for beehive to get out of incubation). If you all want to do
that, then let me and sanjiva know...
thanks,
dims
On Wed, 11 Aug 2004 17:15:02 -0700, Heather Stephens
<[EMAIL PROTECTED]>
wrote:
Hi Sanjiva.
The web service part of this project is intended to be an
implementation
of annotation-based programming model for web services (JSR-181).
See mail threads for latest discussion (and feel free to give your
comments!) -->
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
r.apache.org&msgNo=145
and
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
r.apache.org&msgNo=155
JSR-181 info can be found here -->
http://jcp.org/en/jsr/detail?id=181
Latest thinking on how it might happen within Beehive is found in
this
proposal from Ias -->
http://www.apache.org/~ias/beehive-wsm-proposal-draft.txt
He and others already have prototype code in Axis that we can use
here.
I hope this helps.
H.
-----Original Message-----
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 8:20 PM
To: Beehive Developers
Subject: Re: can i help
If this project is a pure *Web service* project why would we do it
as a part of Beehive? I'd rather see it under ws.apache.org
somewhere. Maybe I misunderstood?
Sanjiva.
----- Original Message -----
From: "Mario Morgado" <[EMAIL PROTECTED]>
To: "Beehive Developers" <[email protected]>
Sent: Wednesday, August 11, 2004 6:50 AM
Subject: RE: can i help
Once I complete reading the documentation on the various sites, I
will
provide feedback once i have had some time to put it into context
Heather Stephens <[EMAIL PROTECTED]> wrote:
Hey gang. Mario is interested in helping out with the WS
implementation
for Beehive.
The first step is to review the document Ias sent out:
http://www.apache.org/~ias/beehive-wsm-proposal-draft.txt
(Ias - now that we have a wiki we can go ahead and post this URL
to
it.)
And then as the plan takes shape ways you can help would include:
1. Using the implementation done by committers and posting bugs,
asking
questions or sending on actual fixes to this alias.
2. Writing samples or docs.
3. Perhaps picking off a feature to implement and submitting to
this
alias for acceptance.
Any other ideas anyone?
-----Original Message-----
From: Mario Morgado [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 3:40 PM
To: Heather Stephens
Subject: RE: can i help
Hi Heather I have read the documentation, and would be happy to
assist
with the webservice implementation, seems very interesting having
been
architecting webservices for the last 2 years now, so I think I
may
be
of some use
I have downloaded SVN, what is next.
-----Original Message-----
From: Heather Stephens [mailto:[EMAIL PROTECTED]
Sent: Monday, August 09, 2004 12:51 PM
To: Mario Morgado
Subject: RE: can i help
Hi Mario. Sorry for the late reply.
What part of Beehive are you interested in? The part that will be
needing the most work, other than just using Beehive to build
pageflows/controls/etc., is the webservice implementation. I've
attached the last email from ias on that subject.
I hope this helps.
Heather
________________________________________
From: Mario Morgado [mailto:[EMAIL PROTECTED]
Sent: Friday, August 06, 2004 7:27 AM
To: Heather Stephens
Subject: can i help
Hi Heather I would really like to help if there is an opportunity
for
me
to participate, let me know what I can do, I have downloaded the
source tree.
I am just finishing up another project FPML which started much the
same
way as beehive.
Mario Morgado
Chief Systems Architect
RDM Corporation
519-746-8483 X339
416-576-2987 Mobile
Mario Morgado
Cheif Architect, Project Manager
RDM Corporation
519-746-8483 X339
416-576-2987 Mobile
--
Davanum Srinivas - http://webservices.apache.org/~dims/
_________________________________________________________________
ìììì ëë ìëê ëêíê ìêë... MSN ìëì ììê
http://vod.msn.co.kr
