I have a deployed web service that speaks SOAP. This works just fine with the
service hosted in WebLogic and using the SOAP test feature of the oxygen XML
tool. I send a request and get a response. I have a wsdl file for this
service as well.

As a learning experience, I want to do something that should be trivial, but
is giving this novice user fits. I would like to proxy a request for this
service through ServiceMix.

I think that I need to write no code to accomplish this -- just write some
xbean.xml definitions for the http and eip installer ServiceMix components,
write a simple jbi.xml and wrap it all up in a service assembly with the
right nested zip structure.

I can't seem to come up with the right contents for the http xbean. I am
trying something like:

  <classpath>
    <location>.</location>
  </classpath>

    <!--
    These are the basic endpoints
    -->
    <http:endpoint
            service="arces:arces-router"
            endpoint="arces-router"
            role="consumer"
            locationURI="http://10.5.10.52:8192/Bye/";
            defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; />

    <http:endpoint
            service="arces:arces-service"
            endpoint="arces-service"
            role="provider"
            locationURI="http://b-0384-qa0006:8001/byeservice/Bye"; 
            wsdlResource="classpath:bye.wsdl"/>

My service mix instance is running on the 10.5.10.52 machine. The original
web service is on a local machine with the URI as indicated in the provider
endpoint. The original wsdl for my web service is bye.wsdl and I am
including it in the http su zip in my maven build.

My eip xbean looks like:

    <!--
    routing slip used in basic routing
    -->
    <eip:static-routing-slip service="arces:arces-router"
endpoint="endpoint">
        <eip:targets>
            <eip:exchange-target service="arces:arces-service"/>
        </eip:targets>
    </eip:static-routing-slip>

But when I put it alltogether and deploy my service assembly to servicemix,
and try to access the service using the consumer endpoint, I get a SOAP
fault complaining about that there should be only one content-type
MimeHeader.

I think this must be some trivial error I am making but after several hours
of attempts, I can't get it to work.

I would appreciate any advice anyone can give.

Jim

-- 
View this message in context: 
http://www.nabble.com/Using-http-and-eip-installer-zips-together-with-SOAP-tf2187193.html#a6050701
Sent from the ServiceMix - User forum at Nabble.com.

Reply via email to