Try adding the targetService or targetEnpoint attribute to the http:endpoint. In your case it would be targetService=" search:DocumentService". I believe this is why you are getting the "Unable to find requested resource" message.
Regards, Jeff -----Original Message----- From: Raghul Nandagopal [mailto:[EMAIL PROTECTED] Sent: Monday, November 06, 2006 11:48 AM To: [email protected] Subject: Re: HTTP EndPoint - response getting truncated. Here is the configuration <sm:container id="jbi" useMBeanServer="false" createMBeanServer="false" dumpStats="true" embedded="true" statsInterval="10"> <sm:activationSpecs> <sm:activationSpec> <sm:component> <http:component> <http:endpoints> <http:endpoint service="search:SearchService" endpoint="soap" soap="true" role="consumer" locationURI="http://localhost:8192/SearchService/ " defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; defaultOperation="doGoogleSearch"/> <http:endpoint service="search:DocumentService" endpoint="work" soap="true" role="consumer" locationURI=" http://localhost:8192/DocumentService/"; defaultMep="http://www.w3.org/2004/08/wsdl/in-out " defaultOperation="documentService"/> </http:endpoints> </http:component> </sm:component> </sm:activationSpec> <sm:activationSpec> <sm:component> <jsr181:component> <jsr181:endpoints> <jsr181:endpoint pojoClass="MyProcessor" wsdlResource="classpath:search.wsdl" style="document"/> <jsr181:endpoint pojoClass="MyService" annotations="none" service="search:DocumentService" endpoint="work" style="document"/> Raghul Nandagopal wrote: > > Hi Guillaume, > > I managed to expose the POJO in document style. > My only issue now is that i am not able to use the XFire Dynamic Client. > The reason i think is the automatically generated WSDL is not getting > out... > For example,http://localhost:8192/DocumentService/main.wsdl > or http://localhost:8192/DocumentService?wsdl > returns only > > Unable to find requested resource > > Please let me know what's really going wrong. please help me understand > this piece better. > > > All i want is use XFire dynamic client to access the service exposed by > the below given configuration. > > Is it possible? > > > gnodet wrote: >> >> You can design your WSDL first if you prefer. >> Take a look at the wsdl-first example in the distribution. >> >> On 11/1/06, Raghul Nandagopal <[EMAIL PROTECTED]> wrote: >>> >>> Hi Guillaume, >>> >>> I fixed the issue. >>> I configured a JSR 181 Pojo instead of ordinary and everything worked >>> fine. >>> >>> I have an issue with tight binding of method name to the request XML. >>> >>> For example, in the MyProcessor POJO configured below, there is a method >>> doSearch. >>> >>> If i need to invoke it, then i need to have a tag <doSearch> in the >>> request >>> XML. >>> This is a tight coupling with the method name. >>> >>> Please let me know if there is any other way of method invocation where >>> the >>> method name is not tightly coupled with the tags in XML. >>> >>> Please help us in this regard. >>> >>> here is the endpoint configuration >>> >>> <sm:activationSpec> >>> <sm:component> >>> <http:component> >>> <http:endpoints> >>> <http:endpoint >>> service="demo:MySoapClient" >>> endpoint="MySoapClient" >>> role="consumer" >>> soap="true" >>> >>> locationURI="http://localhost:8192/SoapService/"; >>> >>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; /> >>> </http:endpoints> >>> </http:component> >>> </sm:component> >>> </sm:activationSpec> >>> >>> <sm:activationSpec> >>> <sm:component> >>> <jsr181:component> >>> <jsr181:endpoints> >>> <jsr181:endpoint pojoClass="MyProcessor" >>> annotations="none" >>> service="demo:MySoapClient" >>> endpoint="MySoapClient" /> >>> </jsr181:endpoints> >>> </jsr181:component> >>> </sm:component> >>> </sm:activationSpec> >>> ------------------------------------------------------------------------ >>> >>> >>> >>> Raghul Nandagopal wrote: >>> > >>> > Please find the debug log. >>> > >>> > 2006-11-01 01:03:42,515 DEBUG [org.mortbay.jetty] REQUEST >>> /SoapService/ on >>> > [EMAIL PROTECTED] >>> > 2006-11-01 01:03:42,515 DEBUG [org.mortbay.jetty] servlet=jbiServlet >>> > 2006-11-01 01:03:42,515 DEBUG [org.mortbay.jetty] chain=null >>> > 2006-11-01 01:03:42,515 DEBUG [org.mortbay.jetty] servelet >>> > holder=jbiServlet >>> > 2006-11-01 01:03:42,515 DEBUG [org.mortbay.jetty] continuation >>> > [EMAIL PROTECTED] >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] >> "POST >>> > /SoapService/ HTTP/1.1[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] >> >>> "Content-Type: >>> > text/xml[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] >> >>> "Content-Length: >>> > 204[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] >> "User-Agent: >>> > Jakarta Commons-HttpClient/3.0[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] >> "Host: >>> > localhost:8192[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] >> "[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] >> "<?xml >>> > version='1.0' encoding='UTF-8'?><doGoogleSearch >>> > >>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><key>key</key><st art>0</start><maxResults>10</maxResults><filter>true</filter></doGoogleS earch>" >>> > 2006-11-01 01:03:42,531 DEBUG [org.mortbay.jetty] REQUEST >>> /SoapService/ on >>> > [EMAIL PROTECTED] >>> > 2006-11-01 01:03:42,531 DEBUG [org.mortbay.jetty] servlet=jbiServlet >>> > 2006-11-01 01:03:42,531 DEBUG [org.mortbay.jetty] chain=null >>> > 2006-11-01 01:03:42,531 DEBUG [org.mortbay.jetty] servelet >>> > holder=jbiServlet >>> > 2006-11-01 01:03:42,531 DEBUG [org.mortbay.jetty] RESPONSE >>> /SoapService/ >>> > 400 >>> > 2006-11-01 01:03:42,531 DEBUG [org.mortbay.jetty] continuation >>> > [EMAIL PROTECTED] >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] << "HTTP/1.1 >>> 400 >>> > Bad Request[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] << >>> "Content-Type: >>> > text/xml[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] << >>> > "Transfer-Encoding: chunked[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.header] << "Server: >>> > Jetty(6.0.0rc4)[\r][\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "1" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "9" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "6" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\r]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "<?xml >>> > version='1.0' encoding='UTF-8'?><env:Envelope >>> > >>> xmlns:env="http://www.w3.org/2003/05/soap-envelope";><env:Body><env:Fault ><env:Code><env:Value>env:Sender</env:Value><env:Subcode><env:Value>env: Sender</env:Value></env:Subcode></env:Code><env:Reason><env:Text >>> > xml:lang="en">Unrecognized element: doGoogleSearch at [1,39]. >>> Expecting >>> > >>> 'Envelope'.</env:Text></env:Reason></env:Fault></env:Body></env:Envelope >" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\r]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "0" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\r]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\n]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\r]" >>> > 2006-11-01 01:03:42,531 DEBUG [httpclient.wire.content] << "[\n]" >>> > 2006-11-01 01:03:42,531 ERROR >>> > [org.apache.servicemix.http.HttpSpringComponent] Error processing >>> exchange >>> > InOnly[ >>> > id: ID:ThunderBird-1519-1162319929984-19:2 >>> > status: Active >>> > role: provider >>> > service: MySoapServer >>> > endpoint: MySoapServer >>> > in: <?xml version="1.0" encoding="UTF-8"?> >>> > ] >>> > java.lang.Exception: Invalid status response: 400 >>> > at >>> > >>> org.apache.servicemix.http.processors.ProviderProcessor.process(Provider Processor.java:175) >>> > at >>> > >>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBas eLifeCycle.java:410) >>> > at >>> > >>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCyc le.java:43) >>> > at >>> > >>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(D eliveryChannelImpl.java:624) >>> > at >>> > >>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.j ava:169) >>> > at >>> > >>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java :177) >>> > at >>> > >>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:2 27) >>> > at >>> > >>> org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java: 291) >>> > at >>> > >>> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecuto r.java:748) >>> > at java.lang.Thread.run(Thread.java:595) >>> > >>> > >>> > gnodet wrote: >>> >> >>> >> Could you post a log file at debug level and >>> >> put a tcp monitor [1] to check the http request sent >>> >> by servicemix-http ? >>> >> >>> >> [1] >>> >> >>> http://ws.apache.org/axis/java/user-guide.html#AppendixUsingTheAxisTCPMo nitorTcpmon >>> >> >>> >> On 10/31/06, Raghul Nandagopal <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>> Hi, >>> >>> >>> >>> Here is my sm.xml configuration deployed in JBoss >>> >>> >>> >>> <sm:activationSpec> >>> >>> <sm:component> >>> >>> <http:component> >>> >>> <http:endpoints> >>> >>> <http:endpoint >>> >>> service="sterling:MySoapClient" >>> >>> endpoint="MySoapClient" >>> >>> targetService="form:SoapProcessor" >>> >>> role="consumer" >>> >>> soap="true" >>> >>> >>> >>> locationURI="http://localhost:8192/SoapService/"; >>> >>> >>> >>> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; /> >>> >>> <http:endpoint >>> >>> service="sterling:MySoapServer" >>> >>> endpoint="MySoapServer" >>> >>> role="provider" >>> >>> >>> >>> locationURI="http://localhost:8192/SoapService/"; /> >>> >>> </http:endpoints> >>> >>> </http:component> >>> >>> </sm:component> >>> >>> </sm:activationSpec> >>> >>> >>> >>> <sm:activationSpec componentName="SoapProcessor" >>> >>> service="form:SoapProcessor" >>> destinationService="sterling:MySoapServer"> >>> >>> <sm:component><bean class="MyProcessor" >>> >>> /></sm:component> >>> >>> </sm:activationSpec> >>> >>> >>> >>> --------------------- >>> >>> >>> >>> Here is the error message - what's going wrong - help :( >>> >>> >>> >>> 00:09:11,984 ERROR [HttpSpringComponent] Error processing exchange >>> >>> InOnly[ >>> >>> id: ID:ThunderBird-1519-1162319929984-19:0 >>> >>> status: Active >>> >>> role: provider >>> >>> service: MySoapServer >>> >>> endpoint: MySoapServer >>> >>> in: <?xml version="1.0" encoding="UTF-8"?> >>> >>> ] >>> >>> java.lang.Exception: Invalid status response: 400 >>> >>> at >>> >>> >>> org.apache.servicemix.http.processors.ProviderProcessor.process(Provider Processor.java:175) >>> >>> at >>> >>> >>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBas eLifeCycle.java:410) >>> >>> at >>> >>> >>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCyc le.java:43) >>> >>> at >>> >>> >>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(D eliveryChannelImpl.java:624) >>> >>> at >>> >>> >>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.j ava:169) >>> >>> at >>> >>> >>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java :177) >>> >>> at >>> >>> >>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:2 27) >>> >>> at >>> >>> >>> org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java: 291) >>> >>> at >>> >>> >>> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecuto r.java:743) >>> >>> at java.lang.Thread.run(Thread.java:595) >>> >>> 00:09:11,984 INFO [STDOUT] Completed Processing >>> >>> -- >>> >>> View this message in context: >>> >>> >>> http://www.nabble.com/HTTP-EndPoint---response-getting-truncated.-tf2547 553.html#a7099823 >>> >>> Sent from the ServiceMix - User mailing list archive at Nabble.com. >>> >>> >>> >>> >>> >> >>> >> >>> >> -- >>> >> Cheers, >>> >> Guillaume Nodet >>> >> >>> >> >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/HTTP-EndPoint---response-getting-truncated.-tf2547 553.html#a7115638 >>> Sent from the ServiceMix - User mailing list archive at Nabble.com. >>> >>> >> >> >> -- >> Cheers, >> Guillaume Nodet >> >> > > -- View this message in context: http://www.nabble.com/HTTP-EndPoint---response-getting-truncated.-tf2547 553s12049.html#a7202238 Sent from the ServiceMix - User mailing list archive at Nabble.com. This email (and any attachments) is intended only for the use of the individual or entity named above and may contain information that is privileged and confidential. If you are not the intended recipient, or have unauthorized access, you are hereby notified that copying, disseminating, distributing or taking any action in reliance on this email is strictly prohibited<br /> <br /> Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it.
