axis2 configuration fine tuning: Local Transport and transportReceiver

[Gennady Shumakher <gs...@gmail.com>]

Hi,

I am fine tuning axis2 configuration for our use cases which are stateless
web services available over http(s) only. Now I wonder regarding relevance
of Local Transport settings in our scenario. Unfortunately I couldn't fine
the documentation on that topic, but I suppose it is optimized for calls
within the same web application?

Additionally we embed axis2 within our web application. I successfully
tested that in this case the default <transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">  can be removed so
ports and other parameters are defined by web application connection. But I
wonder how that works if I don't have any explicit configuration for
<transportReceiver>, are there some defaults?

Thanks,
Gennady

Re: axis2 configuration fine tuning: Local Transport and transportReceiver

[Andreas Veithen <an...@gmail.com>]

On Mon, Dec 28, 2009 at 07:36, Gennady Shumakher <gs...@gmail.com> wrote:
> Hi,
>
> I am fine tuning axis2 configuration for our use cases which are stateless
> web services available over http(s) only. Now I wonder regarding relevance
> of Local Transport settings in our scenario. Unfortunately I couldn't fine
> the documentation on that topic, but I suppose it is optimized for calls
> within the same web application?

The local transport is primarily used in unit tests. Not sure if it is
usable in a production environment.

> Additionally we embed axis2 within our web application. I successfully
> tested that in this case the default <transportReceiver name="http"
> class="org.apache.axis2.transport.http.SimpleHTTPServer">  can be removed so
> ports and other parameters are defined by web application connection. But I
> wonder how that works if I don't have any explicit configuration for
> <transportReceiver>, are there some defaults?

The issue AXIS2-4465 sheds some light on how transport receivers
are/were managed by AxisServlet.

> Thanks,
> Gennady
>
>
>

Re: axis2 configuration fine tuning: Local Transport and transportReceiver

[gshum <gs...@gmail.com>]

I managed to configure axis2.xml with 'hostname' parameter that substitute
server part of EPR.

But I wonder is there a way to configure axis2 to use http 'host' header as
part of generated EPR? Host value should contain the server name as it 's
seen by the service consumer, which, I believe, is exactly what is desired
in the most of scenarios (BTW, that's how axis 1 handled EPR generation).
 
Thanks,
Gennady


Andreas Veithen-2 wrote:
> 
> Gennady,
> 
> AxisServlet will always process requests received through the servlet
> container, and the transportReceiver settings in axis2.xml have no
> impact on this. These settings are only used to generate the proper
> endpoint URIs in the WSDL (original or generated). Note that this is
> only true for the servlet transport. For other transports, the
> transportReceiver settings also determine how the transport receives
> requests.
> 
> Andreas
> 
> On Tue, Dec 29, 2009 at 12:16, Gennady Shumakher <gs...@gmail.com>
> wrote:
>> Andreas,
>> thanks for clarification.
>>
>> According to AXIS2-4465 the documentation is on its way, but I'd like to
>> be
>> sure we configure that properly.
>> I am running on 1.5.1 and would like to support both http, https and we
>> use
>> useOriginalwsdl=true (so wsdl is served as is, no generation).
>>
>>
>> As I see from the code the AxisServlet does implements TransportListener
>> directly that mentioned as problematic in AXIS2-4465...
>>
>> Anyhow the current behavior I face that if no explicit transportReceiver
>> defined in axis2.xml the services
>>
>> both via http and https work as expected via the ports defined for web
>> application and ?wsdl returns wsdl document.
>>
>> But if axis2.xml is configured as:
>> <transportReceiver name="default"
>> class="org.apache.axis2.transport.http.AxisServlet" />
>>
>>
>> the services http/s work well, but ?wsdl request fails with null
>> exception.
>> Do I miss something in configuration to make it work?
>>
>> Thanks,
>> Gennady
>>
>>
>> On Mon, Dec 28, 2009 at 07:36, wrote:
>>> Hi,
>>
>>>
>>> I am fine tuning axis2 configuration for our use cases which are
>>> stateless
>>> web services available over http(s) only. Now I wonder regarding
>>> relevance
>>> of Local Transport settings in our scenario. Unfortunately I couldn't
>>> fine
>>
>>> the documentation on that topic, but I suppose it is optimized for calls
>>> within the same web application?
>>
>> The local transport is primarily used in unit tests. Not sure if it is
>> usable in a production environment.
>>
>>
>>> Additionally we embed axis2 within our web application. I successfully
>>> tested that in this case the default <transportReceiver name="http"
>>> class="org.apache.axis2.transport.http.SimpleHTTPServer">  can be
>>> removed
>>> so
>>
>>> ports and other parameters are defined by web application connection.
>>> But
>>> I
>>> wonder how that works if I don't have any explicit configuration for
>>> <transportReceiver>, are there some defaults?
>>
>>
>> The issue AXIS2-4465 sheds some light on how transport receivers
>> are/were managed by AxisServlet.
>>
>>> Thanks,
>>> Gennady
>>>
>>>
>>>
>>
> 
> 

-- 
View this message in context: http://old.nabble.com/axis2-configuration-fine-tuning%3A-Local-Transport-and--transportReceiver-tp26940227p27421714.html
Sent from the Axis - User mailing list archive at Nabble.com.