Return-Path: Mailing-List: contact soap-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-dev@xml.apache.org Received: (qmail 28469 invoked from network); 11 Aug 2000 18:17:39 -0000 Received: from host127.vignette.com (HELO hard.vignette.com) (207.8.7.254) by locus.apache.org with SMTP; 11 Aug 2000 18:17:39 -0000 Received: from vignette.com (hq2519.vignette.com [10.17.60.223]) by hard.vignette.com (8.10.1/8.10.1) with ESMTP id e7BIGu226306 for ; Fri, 11 Aug 2000 13:16:56 -0500 Message-ID: <39944398.6FB2E84@vignette.com> Date: Fri, 11 Aug 2000 13:19:04 -0500 From: Rich Johns X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: soap-dev@xml.apache.org Subject: Re: SOAPEngine / EnvelopeProcessor - Am I way off ? References: Content-Type: multipart/alternative; boundary="------------7055483AF79AB4972FB05BA5" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N --------------7055483AF79AB4972FB05BA5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sorry, didn't mean to ignore it. I plan to look at it as soon as I can, but right now I'm swamped. I like the concept (based on your explanations) of refactoring the code so that it is more reusable and that the architecture will become more flexible. I must admit that I have been looking at everything with an "http eye" although I do understand the need to generalize for other transports. I want to retain the idea of a servlet for http rpc and that we have the ability to register properly scoped service provider classses, so I doubt I will scream too much as long as this architectural option is available. Within that architecure, though, there are some improvements that would be nice, like the ability to register multiple providers in one deployment descriptor. thanks Jean-Noel Gadreau wrote: > > > Hi all. > > I am sending this quick e-mail because I did not get any feedback on the patch/enhancement that I > sent to the list a couple days ago on an implementation of what I called "SOAPEngine" and > "EnvelopeProcessors". As I did not see any discussion on the list, I am wondering if my approach > is completely off the scope of Apache-SOAP, or if I am not considering the problem correctly, if > nobody cares or if you don't have time to look at it. > > I need to keep working on this project for my company, but we also want to contribute to > Apache-SOAP if possible. So should I just keep working on it as it is and post updates ? Do you > see changes that I would need to roll in now ? > > If you could let me know what's your views on this, I would really appreciate. > > Thanks a lot > > Jean-Noel > > ============= > Jean-Noel GADREAU > Software Engineer, ActivCard Inc.(http://www.activcard.com ) > E-mail: jngadreau@activcard.com > Tel (main): 510-574-0100 > Tel (direct): 510-574-1736 --------------7055483AF79AB4972FB05BA5 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Sorry, didn't mean to ignore it. I plan to look at it as soon as I can, but
right now I'm swamped. I like the concept (based on your explanations) of
refactoring the code so that it is more reusable and that the architecture will
become more flexible. I must admit that I have been looking at everything
with an "http eye" although I do understand the need to generalize for
other transports.

I want to retain the idea of a servlet for http rpc and that we have the
ability to register properly scoped service provider classses, so I doubt
I will scream too much as long as this architectural option is available.
Within that architecure, though, there are some improvements that
would be nice, like the ability to register multiple providers in one
deployment descriptor.

thanks

Jean-Noel Gadreau wrote:

 

Hi all.

I am sending this quick e-mail because I did not get any feedback on the patch/enhancement that I sent to the list a couple days ago on an implementation of what I called "SOAPEngine" and "EnvelopeProcessors". As I did not see any discussion on the list, I am wondering if my approach is completely off the scope of Apache-SOAP, or if I am not considering the problem correctly, if nobody cares or if you don't have time to look at it.

I need to keep working on this project for my company, but we also want to contribute to Apache-SOAP if possible. So should I just keep working on it as it is and post updates ? Do you see changes that I would need to roll in now ?

If you could let me know what's your views on this, I would really appreciate.

Thanks a lot

Jean-Noel

=============
Jean-Noel GADREAU
Software Engineer, ActivCard Inc.(http://www.activcard.com )
E-mail: jngadreau@activcard.com
Tel (main): 510-574-0100
Tel (direct): 510-574-1736

--------------7055483AF79AB4972FB05BA5--