[#MULE-3931] Axis servlet binding doesn't associate full path with the service

Mule

Axis servlet binding doesn't associate full path with the service

Created: 05/Nov/08 03:03 AM Updated: 19/Nov/08 08:37 AM

Component/s:

Transport: Axis

Affects Version/s:

None

Fix Version/s:

2.x Product Backlog

Time Tracking:

Not Specified

Labels:
User impact:	Medium
Affects Docs:	Yes
Migration Impact:	If we made this change we'd need to document how configure this correctly

Description

« Hide

Currently, when using the servlet binding with access (and probably CXF) the service endpoint config does not get the full service path, which means a runtime we have to jump through hoops to figure out the correct config. In this example:

<servlet:connector name="servlet" servletUrl="http://localhost:62088/services"/>

    <model name="test">
        <service name="mycomponent">
            <inbound>
                <axis:inbound-endpoint address="servlet://mycomponent" synchronous="true"/>
            </inbound>
            <test:web-service-component/>
        </service>
    </model>

the service mycomponent will be bound to http://localhost:62088/services/mycomponent, combining the servletUrl and the endpoint path. A better solution may be to require that the servletURL contains no path information and configure the path on the servlet:// endpoint. i.e.

<servlet:connector name="servlet" servletUrl="http://localhost:62088"/>

    <model name="test">
        <service name="mycomponent">
            <inbound>
                <axis:inbound-endpoint address="servlet://services/mycomponent" synchronous="true"/>
            </inbound>
            <test:web-service-component/>
        </service>
    </model>

This would resolve a few issues that make the internals of this more complex than it should be.

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Ross Mason added a comment - 18/Nov/08 04:38 PM

FWIW This also applies to CXF