[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-dev
Subject:    Re: question about relation between soap engine and transport listene	r
From:       "Doug Davis" <dug () us ! ibm ! com>
Date:       2001-02-27 20:38:41
[Download RAW message or body]

That is very possible to do and I suspect that some people will want to do
just
that.  Most of the pieces of Axis will be pluggable so that people can (and
will)
write their own versions.  What we ship though needs to handle most cases
and since right now Axis only talks HTTP what's there makes the most sense.
As we add more Transport Listeners I think we might do exactly what you're
suggesting.
-Dug

Dirk Reinshagen_C <DReinshagen_C@zaplet.com> on 02/27/2001 03:23:20 PM

Please respond to axis-dev@xml.apache.org

To:   "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
cc:
Subject:  question about relation between soap engine and transport listene
      r



This may have been covered already, if so feel free to ignore...

I had question regarding the relationship between the transport
listeners and the soap engine.  It seems like in the current
soap implementation and all of the proposed new implementations
have the engine constructed in the transport listener.

For instance, in the AxisServlet it constructs a SimpleAxisEngine
if one does not already exist.  The question I had is why the
engine is not a singleton?  It seems like you would want to share
the same engine, therefore the same registry among all of the
different transport listeners.

In this scenario something like the following would occur in
each transport listener:

SimpleAxisEngine engine = SimpleAxisEngine.getInstance();
engine.invoke(msgContext);


Dirk

[prev in list] [next in list] [prev in thread] [next in thread]