You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Sanjiva Weerawarana <sa...@watson.ibm.com> on 2000/11/02 16:07:09 UTC
PROPOSAL: Dug Davis for committer
I'd like to propose that Dug be made a committer to get the provider
type generalization done. Vahe, was the code you posted (which never
got committed) also doing the same thing? If so we need to unify
the two approaches. My recollection is that it was a pretty nifty
way of doing EJB integration. If you'd like to work on merging the
two things and getting it all in I'll be happy to nominate you for
committer status too.
Other comitters please ack/nack.
+1
Sanjiva.
Re: PROPOSAL: Dug Davis for committer
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
> Thank you for your proposition, we would be happy to join the team and
> contribute to the development of the tool.
Cool!
> As to our approach to EJB integration with the Apache-SOAP (Locator/URN
> Generator framework) - we discussed it broadly with Dug in our private
> correspondence for quite a long time and initially considered
> possibilities of cooperation in developing the unified infrastructure. I
> suppose Dug could take the leadership and we from our side will provide
> our design, code (which has been already validated in real-life
> applications) and any other assistance.
>
> Also, I would like to mention other extensions we've incorporated into
> Apache SOAP - namely XSLT transformers. As there's something similar now
> being proposed by Ryo Neyama (hooks) - I think here our methods can be
> also used now to come up with optimal unified approach. I'll discuss it
> in the related thread.
It sounds to me that both of these can be built on the provider type
generalization that Dug has implemented. If you agree I suggest that
Dug go ahead and commit that code and you guys build the specific
providers (XSLT scripts, EJBs, BSF scripts, good 'ol Java classes)
on top of that framework.
Sanjiva.
Re: PROPOSAL: Dug Davis for committer
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
> Thank you for your proposition, we would be happy to join the team and
> contribute to the development of the tool.
Cool!
> As to our approach to EJB integration with the Apache-SOAP (Locator/URN
> Generator framework) - we discussed it broadly with Dug in our private
> correspondence for quite a long time and initially considered
> possibilities of cooperation in developing the unified infrastructure. I
> suppose Dug could take the leadership and we from our side will provide
> our design, code (which has been already validated in real-life
> applications) and any other assistance.
>
> Also, I would like to mention other extensions we've incorporated into
> Apache SOAP - namely XSLT transformers. As there's something similar now
> being proposed by Ryo Neyama (hooks) - I think here our methods can be
> also used now to come up with optimal unified approach. I'll discuss it
> in the related thread.
It sounds to me that both of these can be built on the provider type
generalization that Dug has implemented. If you agree I suggest that
Dug go ahead and commit that code and you guys build the specific
providers (XSLT scripts, EJBs, BSF scripts, good 'ol Java classes)
on top of that framework.
Sanjiva.
Re: PROPOSAL: Dug Davis for committer
Posted by Vahe Amirbekyan <av...@techone.com>.
Hello,
Sanjiva Weerawarana wrote:
>
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
Thank you for your proposition, we would be happy to join the team and
contribute to the development of the tool.
As to our approach to EJB integration with the Apache-SOAP (Locator/URN
Generator framework) - we discussed it broadly with Dug in our private
correspondence for quite a long time and initially considered
possibilities of cooperation in developing the unified infrastructure. I
suppose Dug could take the leadership and we from our side will provide
our design, code (which has been already validated in real-life
applications) and any other assistance.
Also, I would like to mention other extensions we've incorporated into
Apache SOAP - namely XSLT transformers. As there's something similar now
being proposed by Ryo Neyama (hooks) - I think here our methods can be
also used now to come up with optimal unified approach. I'll discuss it
in the related thread.
With the best regards, Vahe
>
> Other comitters please ack/nack.
>
> +1
>
> Sanjiva.
--
(\______________________________________________________/)
__|_| Vahe AMIRBEKYAN, Senior Consultant |_|__
(___o) tel: (510) 729 6750 ext.375 (o___)
(__o) mailto:avahe@techone.com (o__)
(__o) http://www.techone.com (o__)
(_o)____________________________________________________(o_)
Re: PROPOSAL: Dug Davis for committer
Posted by Vahe Amirbekyan <av...@techone.com>.
Hello,
Sanjiva Weerawarana wrote:
>
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
Thank you for your proposition, we would be happy to join the team and
contribute to the development of the tool.
As to our approach to EJB integration with the Apache-SOAP (Locator/URN
Generator framework) - we discussed it broadly with Dug in our private
correspondence for quite a long time and initially considered
possibilities of cooperation in developing the unified infrastructure. I
suppose Dug could take the leadership and we from our side will provide
our design, code (which has been already validated in real-life
applications) and any other assistance.
Also, I would like to mention other extensions we've incorporated into
Apache SOAP - namely XSLT transformers. As there's something similar now
being proposed by Ryo Neyama (hooks) - I think here our methods can be
also used now to come up with optimal unified approach. I'll discuss it
in the related thread.
With the best regards, Vahe
>
> Other comitters please ack/nack.
>
> +1
>
> Sanjiva.
--
(\______________________________________________________/)
__|_| Vahe AMIRBEKYAN, Senior Consultant |_|__
(___o) tel: (510) 729 6750 ext.375 (o___)
(__o) mailto:avahe@techone.com (o__)
(__o) http://www.techone.com (o__)
(_o)____________________________________________________(o_)
Re: PROPOSAL: Dug Davis for committer
Posted by Ryo Neyama <ne...@trl.ibm.co.jp>.
+1 +1 for Dug and Vahe.
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
Subject: PROPOSAL: Dug Davis for committer
Date: Thu, 2 Nov 2000 10:07:09 -0500
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
>
> Other comitters please ack/nack.
>
> +1
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
Subject: PROPOSAL: Vahe Amirbekyan for committer
Date: Thu, 2 Nov 2000 16:04:45 -0500
> Committers: Please vote ack/nack. Vahe participated actively earlier
> on EJBs etc. and is willing to get his extension logic integrated into
> Paul's stuff and for the world to be a happier place.
>
> +1
Ryo Neyama @ IBM Research, Tokyo Research Laboratory
Internet Technology
neyama@trl.ibm.co.jp
Re: PROPOSAL: Dug Davis for committer
Posted by George I Matkovits <ma...@uswest.net>.
+1
Regards - George
Sanjiva Weerawarana wrote:
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
>
> Other comitters please ack/nack.
>
> +1
>
> Sanjiva.
Re: PROPOSAL: Dug Davis for committer
Posted by Ryo Neyama <ne...@trl.ibm.co.jp>.
+1 +1 for Dug and Vahe.
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
Subject: PROPOSAL: Dug Davis for committer
Date: Thu, 2 Nov 2000 10:07:09 -0500
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
>
> Other comitters please ack/nack.
>
> +1
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
Subject: PROPOSAL: Vahe Amirbekyan for committer
Date: Thu, 2 Nov 2000 16:04:45 -0500
> Committers: Please vote ack/nack. Vahe participated actively earlier
> on EJBs etc. and is willing to get his extension logic integrated into
> Paul's stuff and for the world to be a happier place.
>
> +1
Ryo Neyama @ IBM Research, Tokyo Research Laboratory
Internet Technology
neyama@trl.ibm.co.jp
Re: PROPOSAL: Dug Davis for committer
Posted by George I Matkovits <ma...@uswest.net>.
+1
Regards - George
Sanjiva Weerawarana wrote:
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
>
> Other comitters please ack/nack.
>
> +1
>
> Sanjiva.
Re: PROPOSAL: Dug Davis for committer
Posted by Jacek Kopecky <ja...@idoox.com>.
+1
Jacek Kopecky
Idoox s.r.o.
On Thu, 2 Nov 2000, Sanjiva Weerawarana wrote:
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
>
> Other comitters please ack/nack.
>
> +1
>
> Sanjiva.
>
Re: PROPOSAL: Dug Davis for committer
Posted by Jacek Kopecky <ja...@idoox.com>.
+1
Jacek Kopecky
Idoox s.r.o.
On Thu, 2 Nov 2000, Sanjiva Weerawarana wrote:
> I'd like to propose that Dug be made a committer to get the provider
> type generalization done. Vahe, was the code you posted (which never
> got committed) also doing the same thing? If so we need to unify
> the two approaches. My recollection is that it was a pretty nifty
> way of doing EJB integration. If you'd like to work on merging the
> two things and getting it all in I'll be happy to nominate you for
> committer status too.
>
> Other comitters please ack/nack.
>
> +1
>
> Sanjiva.
>