CXF WS Proxy Hangs

I'm attempting to simply proxy an existing WS for version management,
etc. At this point all I'm trying to do is simply pass requests from
the new endpoint to the existing one. I've read this doc
(http://www.mulesource.org/display/MULE2USER/Proxying+Web+Services) on
how to do it, but it's not working out so well. My config is as
follows:


                <service name="service">

                        <inbound>
                       
                                <cxf:inbound-endpoint
                                        address="http://localhost:63081/service"
                                        proxy="true" />
                       
                        </inbound>
                       
                       
                        <outbound>
                               
                                <outbound-pass-through-router>
                               
                                        <cxf:outbound-endpoint
                                                address="http://localhost:8080/service/soap"
                                                proxy="true" />
                                       
                                </outbound-pass-through-router>
                               
                        </outbound>

                </service>


This appears to be inline with the doc. The first thing I noted is
that it's not presenting the proxied WSDL. The original WSDL at
http://localhost:8080/service/soap?wsdl is correct, but the WSDL at
http://localhost:63081/service?wsdl refers to the ProxyService and is
completely different. However, the client can still connect, so I'm
willing to live with this oddity if I can get this functional even
though it'd be nice to not have to.

The bigger issue is that when a client that was previously working
when configured to hit the original service address attempts to use
the new address it hangs, then times out. Looking at the stdout of
mule I see that it receives and passes on a request, but immediately
closing the HTTP connections. It hangs too until it times out. Upon
timing out, or maybe just before (it happens very quickly) something
is sent to the original address, but it appears as if no parameters
are sent. I get output on the stdout of the JBoss instance hosting the
original service that shows that the correct operation was called, but
with no arguments.

I've fiddled with all combinations of synchronous and asyncRemote with
no change.

This is day 2 of trying to solve this. I've already googled the crap
out of the issue and am officially tired. Any help is greatly
appreciated.

Thanks,
T

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email