axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Davis" <...@us.ibm.com>
Subject Re: cvs commit: xml-axis/java/src/org/apache/axis/client AdminClient.java ServiceClient.java
Date Mon, 13 Aug 2001 16:48:00 GMT
I was wondering about that - but what if you want the functionality of
that transport object (ie. the stuff in transport object's constructor) but
want to use a different chain?  Or is that just plain silly?
-Dug

"Glen Daniels" <gdaniels@macromedia.com> on 08/13/2001 12:34:31 PM

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

To:   <axis-dev@xml.apache.org>
cc:
Subject:  Re: cvs commit: xml-axis/java/src/org/apache/axis/client
      AdminClient.java ServiceClient.java



Hi Doug:

>   Index: ServiceClient.java
>   ===================================================================
>   RCS file:
/home/cvs/xml-axis/java/src/org/apache/axis/client/ServiceClient.java,v
>   retrieving revision 1.39
>   retrieving revision 1.40
>   diff -u -r1.39 -r1.40
>   --- ServiceClient.java 2001/08/11 20:19:04 1.39
>   +++ ServiceClient.java 2001/08/13 16:21:39 1.40
>   @@ -174,6 +174,7 @@
>
>        // Our Transport, if any
>        private Transport transport;
>   +    private String    transportName ;
>
>        /**
>         * Basic, no-argument constructor.
>   @@ -259,6 +260,13 @@
>                e.printStackTrace();
>            }
>        }
>   +
>   +    /**
>   +     * Set the name of the transport chain to use.
>   +     */
>   +    public void setTransportName(String name) {
>   +      transportName = name ;
>   +    }
>
>     /** Get the Transport registered for the given protocol.
>         *
>   @@ -538,6 +546,9 @@
>            if (transport != null) {
>                transport.setupMessageContext(msgContext, this,
this.engine);
>            }
>   +        // Pass along the transport chain name if given
>   +        if ( transportName != null )
>   +          msgContext.setTransportName( transportName );

You might want this to be an either/or situation - Transports typically set
the MessageContext transportName in their setupMessageContext() method, so
doing it this way would set up everything else, but let transportName get
overridden by the option.  That seems like it might get confusing.

--Glen





Mime
View raw message