If your problem is to put two (or more) SUs for the same component into 1 SA, I believe that's a limitation in smx 3.0. Possibly this will be fixed in smx 3.1. To be correct, smx is not the real problem here. The problem is in the maven plugin. So if you're up to it, you can manually create all you jbi.xml files (which the maven plugin does for you) and it should work with smx 3.0 as well.
A work around is to put the consumer and the provider in one single SU and it will work just fine. That's what we do. /Anders beyond30lyc wrote: > > Thank you very much for your reply. The two are packeged in separate SUs > and i can not deploy them to the same assembly but separately is OK. > And another problem occurs. My external service is from .NET plateform and > its WSDL file is > <?xml version="1.0" encoding="utf-8" ?> > <definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:s="http://www.w3.org/2001/XMLSchema"; > xmlns:s0="http://tempuri.org/"; > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"; > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; > targetNamespace="http://tempuri.org/"; > xmlns="http://schemas.xmlsoap.org/wsdl/";> > <types> > <s:schema elementFormDefault="qualified" > targetNamespace="http://tempuri.org/";> > <s:element name="HelloWorld"> > <s:complexType /> > </s:element> > <s:element name="HelloWorldResponse"> > <s:complexType> > <s:sequence> > <s:element minOccurs="0" maxOccurs="1" name="HelloWorldResult" > type="s:string" /> > </s:sequence> > </s:complexType> > </s:element> > <s:element name="Adder"> > <s:complexType> > <s:sequence> > <s:element minOccurs="1" maxOccurs="1" name="a" type="s:int" /> > <s:element minOccurs="1" maxOccurs="1" name="b" type="s:int" /> > </s:sequence> > </s:complexType> > </s:element> > <s:element name="AdderResponse"> > <s:complexType> > <s:sequence> > <s:element minOccurs="1" maxOccurs="1" name="AdderResult" type="s:int" > /> > </s:sequence> > </s:complexType> > </s:element> > <s:element name="string" nillable="true" type="s:string" /> > <s:element name="int" type="s:int" /> > </s:schema> > </types> > <message name="HelloWorldSoapIn"> > <part name="parameters" element="s0:HelloWorld" /> > </message> > <message name="HelloWorldSoapOut"> > <part name="parameters" element="s0:HelloWorldResponse" /> > </message> > <message name="AdderSoapIn"> > <part name="parameters" element="s0:Adder" /> > </message> > <message name="AdderSoapOut"> > <part name="parameters" element="s0:AdderResponse" /> > </message> > <message name="HelloWorldHttpGetIn" /> > <message name="HelloWorldHttpGetOut"> > <part name="Body" element="s0:string" /> > </message> > <message name="AdderHttpGetIn"> > <part name="a" type="s:string" /> > <part name="b" type="s:string" /> > </message> > <message name="AdderHttpGetOut"> > <part name="Body" element="s0:int" /> > </message> > <message name="HelloWorldHttpPostIn" /> > <message name="HelloWorldHttpPostOut"> > <part name="Body" element="s0:string" /> > </message> > <message name="AdderHttpPostIn"> > <part name="a" type="s:string" /> > <part name="b" type="s:string" /> > </message> > <message name="AdderHttpPostOut"> > <part name="Body" element="s0:int" /> > </message> > <portType name="Service1Soap"> > <operation name="HelloWorld"> > <input message="s0:HelloWorldSoapIn" /> > <output message="s0:HelloWorldSoapOut" /> > </operation> > <operation name="Adder"> > <input message="s0:AdderSoapIn" /> > <output message="s0:AdderSoapOut" /> > </operation> > </portType> > <portType name="Service1HttpGet"> > <operation name="HelloWorld"> > <input message="s0:HelloWorldHttpGetIn" /> > <output message="s0:HelloWorldHttpGetOut" /> > </operation> > <operation name="Adder"> > <input message="s0:AdderHttpGetIn" /> > <output message="s0:AdderHttpGetOut" /> > </operation> > </portType> > <portType name="Service1HttpPost"> > <operation name="HelloWorld"> > <input message="s0:HelloWorldHttpPostIn" /> > <output message="s0:HelloWorldHttpPostOut" /> > </operation> > <operation name="Adder"> > <input message="s0:AdderHttpPostIn" /> > <output message="s0:AdderHttpPostOut" /> > </operation> > </portType> > <binding name="Service1Soap" type="s0:Service1Soap"> > <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; > style="document" /> > <operation name="HelloWorld"> > <soap:operation soapAction="http://tempuri.org/HelloWorld"; > style="document" /> > <input> > <soap:body use="literal" /> > </input> > <output> > <soap:body use="literal" /> > </output> > </operation> > <operation name="Adder"> > <soap:operation soapAction="http://tempuri.org/Adder"; style="document" > /> > <input> > <soap:body use="literal" /> > </input> > <output> > <soap:body use="literal" /> > </output> > </operation> > </binding> > <binding name="Service1HttpGet" type="s0:Service1HttpGet"> > <http:binding verb="GET" /> > <operation name="HelloWorld"> > <http:operation location="/HelloWorld" /> > <input> > <http:urlEncoded /> > </input> > <output> > <mime:mimeXml part="Body" /> > </output> > </operation> > <operation name="Adder"> > <http:operation location="/Adder" /> > <input> > <http:urlEncoded /> > </input> > <output> > <mime:mimeXml part="Body" /> > </output> > </operation> > </binding> > <binding name="Service1HttpPost" type="s0:Service1HttpPost"> > <http:binding verb="POST" /> > <operation name="HelloWorld"> > <http:operation location="/HelloWorld" /> > <input> > <mime:content type="application/x-www-form-urlencoded" /> > </input> > <output> > <mime:mimeXml part="Body" /> > </output> > </operation> > <operation name="Adder"> > <http:operation location="/Adder" /> > <input> > <mime:content type="application/x-www-form-urlencoded" /> > </input> > <output> > <mime:mimeXml part="Body" /> > </output> > </operation> > </binding> > <service name="Service1"> > <port name="Service1Soap" binding="s0:Service1Soap"> > <soap:address location="http://202.118.22.189/Adder/Service1.asmx"; /> > </port> > <port name="Service1HttpGet" binding="s0:Service1HttpGet"> > <http:address location="http://202.118.22.189/Adder/Service1.asmx"; /> > </port> > <port name="Service1HttpPost" binding="s0:Service1HttpPost"> > <http:address location="http://202.118.22.189/Adder/Service1.asmx"; /> > </port> > </service> > </definitions> > > The xbean.xml of my provider is > <beans xmlns:http="http://servicemix.apache.org/http/1.0"; > xmlns:external="http://tempuri.org";> > > <http:endpoint service="external:Service1" > endpoint="Service1Soap" > role="provider" > locationURI="http://202.118.22.189/Adder/Service1.asmx"; > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; > > wsdlResource="http://202.118.22.189/Adder/Service1.asmx?wsdl"; > soap="true" /> > </beans> > the service ,endpoint ,locationURI,wsdlResource are from the wsdl > The xbean.xml of my consumer is > > <http:endpoint service="consumer" > endpoint="soap" > targetService="external:Service1" > role="consumer" > locationURI="http://localhost:8192/example/"; > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; > soap="true" /> > > the targetService is from the service element of the provider xbean.xml > > Then i use the client proxy html page to test it, i add > http://localhost:8192/example/ to the end points. but an exception occurs > which tells me that internal 500 error occurs > > Waiting for your reply, thank you!!! > > > bsnyder wrote: >> >> On 1/16/07, beyond30lyc <[EMAIL PROTECTED]> wrote: >>> >>> I know that,but i can deploy the consumer and provider into different >>> assemblies,but i can deploy them to one assembly,I do not know why??? >> >> Are the consumer and the provider projects packaged in separate SUs or >> are they packaged in a single SU? JBI allows the flexibility to deploy >> SUs in separate SAs or the same SA so that you can do what's best in >> your environment. If you deploy two SUs in a single SA, are you OK >> with undeploying both SUs just to make changes to one of them? >> >> The flexibility of JBI packaging is similar to the packaging >> flexibility of J2EE when wrapping JARs in WARs and WARs in EARs. J2EE >> allows you to choose the best packaging and deployment strategy for >> your environment. JBI works in a similar manner. >> >> Bruce >> -- >> perl -e 'print >> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >> );' >> >> Apache Geronimo - http://geronimo.apache.org/ >> Apache ActiveMQ - http://activemq.org/ >> Apache ServiceMix - http://servicemix.org/ >> Castor - http://castor.org/ >> >> > > -- View this message in context: http://www.nabble.com/Can-i-assembly-the-httpconsumer-and-httpprovider-separately-tf3020634s12049.html#a8427126 Sent from the ServiceMix - User mailing list archive at Nabble.com.
