Thanks, Gert. I want to try http wsdl deployment, so it still need a service(just like jsr181-su(without wsdl file but have the java class(logic)) to run.
I will try it later. Now i have a new question. I use servicemix-jsr181-annotated-service-unit to make a su ,and i can generate a wsdl file on runtime(access http://localhost:8192/Service/?wsdl, i can see the wsdl file), can i generate wsdl file on compile ? (like: mvn generate-wsdl) I tried sometimes, still can't make it work. Gert Vanthienen wrote: > > L.S., > > > An HTTP consumer endpoint configuration creates an external endpoint. It > can be used to expose another endpoint to the outside world using > HTTP/SOAP. When you removed the JSR-181 SU, you removed the internal > endpoint that was being made available. If you now send an HTTP request > to the consumer endpoint, there no longer is a service on the ESB that is > able to do anything with the request. > > What exactly are you trying to achieve? > > > Gert > > > > hgkrt wrote: >> >> here is my service.wsdl file for more information.. >> i just add the jbi endpoint as described on the servicemix-http page. >> >> >> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <wsdl:definitions targetNamespace="http://www.ntts.co.jp/crm/samples"; >>> xmlns:tns="http://www.ntts.co.jp/crm/samples"; >>> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; name="service" >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >>> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; >>> xmlns:jbi="http://servicemix.org/wsdl/jbi/";> >>> >>> <wsdl:types> >>> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >>> attributeFormDefault="qualified" >>> elementFormDefault="qualified" >>> targetNamespace="http://www.ntts.co.jp/crm/samples";> >>> <xsd:element name="echoMethod"> >>> <xsd:complexType> >>> <xsd:sequence> >>> <xsd:element maxOccurs="1" minOccurs="1" name="value" nillable="true" >>> type="xsd:string"/> >>> </xsd:sequence> >>> </xsd:complexType> >>> </xsd:element> >>> <xsd:element name="echoMethodResponse"> >>> <xsd:complexType> >>> <xsd:sequence> >>> <xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" >>> type="xsd:string"/> >>> </xsd:sequence> >>> >>> </xsd:complexType> >>> </xsd:element> >>> </xsd:schema> >>> </wsdl:types> >>> <wsdl:message name="echoMethodResponse"> >>> <wsdl:part name="parameters" element="tns:echoMethodResponse"> >>> </wsdl:part> >>> </wsdl:message> >>> <wsdl:message name="echoMethodRequest"> >>> <wsdl:part name="parameters" element="tns:echoMethod"> >>> </wsdl:part> >>> </wsdl:message> >>> <wsdl:portType name="servicePortType"> >>> <wsdl:operation name="echoMethod"> >>> <wsdl:input name="echoMethodRequest" >>> message="tns:echoMethodRequest"> >>> </wsdl:input> >>> <wsdl:output name="echoMethodResponse" >>> message="tns:echoMethodResponse"> >>> </wsdl:output> >>> </wsdl:operation> >>> >>> </wsdl:portType> >>> <wsdl:binding name="serviceHttpBinding" type="tns:servicePortType"> >>> <wsdlsoap:binding style="document" >>> transport="http://schemas.xmlsoap.org/soap/http"/> >>> <wsdl:operation name="echoMethod"> >>> <wsdlsoap:operation soapAction=""/> >>> <wsdl:input name="echoMethodRequest"> >>> <wsdlsoap:body use="literal"/> >>> </wsdl:input> >>> <wsdl:output name="echoMethodResponse"> >>> <wsdlsoap:body use="literal"/> >>> </wsdl:output> >>> </wsdl:operation> >>> </wsdl:binding> >>> <wsdl:service name="Service"> >>> <wsdl:port name="endpoint1" binding="tns:serviceHttpBinding"> >>> <wsdlsoap:address location="http://localhost:8192/Service"/> >>> <jbi:endpoint role="consumer" defaultMep="in-out"/> >>> </wsdl:port> >>> </wsdl:service> >>> >>> </wsdl:definitions> >>> >> > > -- View this message in context: http://www.nabble.com/servicemix-http-with-wsdl-deployment-...-tf3938368s12049.html#a11188885 Sent from the ServiceMix - User mailing list archive at Nabble.com.
