Hi, thanks a lot, the namespace declaration was missing and this solved the problem.
Bye Lorenzo 2010/9/10 Freeman Fang <[email protected]> > Hi, > > Did you declare namespace for prefix "registry" you used in "service" > attribute as http://www.klever.it/kdv/registry/ws ? > > Freeman > > On 2010-9-9, at 下午11:42, Lorenzo Bolzani wrote: > > Hi, >> I'm trying to find the right parameters to configure a cxfse:proxy. >> >> I think that from the jconsole and with the xbeans.xml file I should be >> abie >> to configure everything. >> Is this correct? >> >> Should I check the Internal or the External endpoint? >> >> In the jconsole I see: >> >> endpointName: DocumentManagementServiceImplPort >> serviceName: { >> http://www.klever.it/kdv/registry/ws}DocumentManagementService<http://www.klever.it/kdv/registry/ws%7DDocumentManagementService> >> >> This is the proxy definition >> >> <cxfse:proxy >> service="registry:DocumentManagementService" >> >> type="it.klever.kdv.registry.ws.DocumentManagementPort" >> useJBIWrapper="false" /> >> >> >> and this is the error >> >> INFO - PhaseInterceptorChain - Interceptor has thrown exception, >> unwinding now Fault occured >> javax.jbi.messaging.MessagingException: Could not find route for exchange: >> InOut[ >> id: ID:127.0.1.1-12af6972c15-10:17 >> status: Active >> role: provider >> interface: >> {http://www.klever.it/kdv/registry/ws}DocumentManagementPort<http://www.klever.it/kdv/registry/ws%7DDocumentManagementPort> >> service: DocumentManagementService >> operation: >> {http://www.klever.it/kdv/registry/ws}findDocuments<http://www.klever.it/kdv/registry/ws%7DfindDocuments> >> in: <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap=" >> http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns2:findDocuments >> xmlns:ns2="http://www.klever.it/kdv/registry/ws"; xmlns:ns3=" >> http://www.klever.it/kdv/registry >> >> "><ns2:type-name>pec-mail</ns2:type-name><ns2:first-entity>0</ns2:first-entity><ns2:entity-count>2</ns2:entity-count><ns2:filter><ns3:filter-conditions><ns3:filter-condition><ns3:condition><ns3:attribute>x-riferimento-message-id</ns3:attribute><ns3:value>123</ns3:value></ns3:condition></ns3:filter-condition></ns3:filter-conditions></ns2:filter></ns2:findDocuments></soap:Body></soap:Envelope> >> >> I think the proxy should try to contact >> "DocumentManagementServiceImplPort" >> but looks like none of the parameters in the xml can be used to change the >> interface value. >> >> >> Thanks for any suggestions. >> >> >> Bye >> >> Lorenzo >> > > > -- > Freeman Fang > >
