comment inline

Håkon Sagehaug wrote:
Hi

I've now got the service published with the message, unig 3.2.2 snapshot

INFO: Setting the server's publish address to be
http://0.0.0.0:8192/EchoService

But I can't get a response back from my web service, in the tomcat log I get
this

[ERROR] Servlet.service() for servlet AxisServlet threw exception
java.lang.NullPointerException
    at
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:395)
    at
org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:366)
    at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
    at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
    at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
    at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
    at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
    at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
    at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
    at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
    at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
    at java.lang.Thread.run(Thread.java:619)

I can invoke the fine when not going through service mix, is there some
error in the xbean hitting a service that for some reason is not there?
Pasted the xbean file agin

<cxfbc:consumer wsdl="classpath:service.wsdl"
                      endpoint="EchoService"
                      service="bccs:EchoService"
                      targetEndpoint="EchoServiceProxy"
                      targetService="bccs:EchoService"
                      targetInterface="bccs:EchoService"/>
according to your wsdl, targetInterface should be bccs:EchoServicePortType
 <cxfbc:provider wsdl="classpath:service.wsdl"
                      locationURI="
http://localhost:8080/axis2/services/EchoService/";
                      endpoint="EchoServiceProxy"
                      service="bccs:EchoService"
                      interfaceName="bccs:EchoService"/>



here interfaceName="bccs:EchoServicePortType"
2008/5/7 Freeman Fang <[EMAIL PROTECTED]>:

You should download from

http://people.apache.org/repo/m2-snapshot-repository/org/apache/servicemix/apache-servicemix/3.2.2-SNAPSHOT/

.zip for windows
.tar.gz for linux

Cheers

Freeman

Håkon Sagehaug wrote:

Hi

Wher can I get the snapshot went here but this link was empty


http://people.apache.org/repo/m2-snapshot-repository/org/apache/servicemix/apache-servicemix/3.2-SNAPSHOT/

I there a tar or something somewhere or sahould I get it from svn trunk?

cheers, Håkon

2008/5/7 Freeman Fang <[EMAIL PROTECTED]>:



No, you needn't specify the MEP.

Which servicemix version you are using, seems your version is quiet
old,
since
"javax.jbi.messaging.MessagingException: Out not supported" get fixed
a
while ago,

Could you try with the latest 3.2.2 snapshot?

Freeman
Håkon Sagehaug wrote:



Hi,

I now seems to work to some extend, I can see the wsdl if I go to
http://0.0.0.0/EchoService/?wsdl and I can send a message in, via
soapui.
But I cant get anything back, do I've got to say that this is
supposed
to be
a InOut?

Some of the stack

DEBUG - SedaQueue                      -
[EMAIL PROTECTED] dequeued
exchange: InOut[
 id: ID:129.177.20.77-119c225bd4e-17:0
 status: Done
 role: provider
 interface: {
http://www.bccs.uib.no/EchoService.wsdl}EchoServicePortType<http://www.bccs.uib.no/EchoService.wsdl%7DEchoServicePortType>
<http://www.bccs.uib.no/EchoService.wsdl%7DEchoServicePortType>
 service: 
{http://www.bccs.uib.no/EchoService.wsdl}EchoService<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService>
<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService>
 endpoint: EchoServiceProxy
 operation: 
{http://www.bccs.uib.no/EchoService.wsdl}SayHi<http://www.bccs.uib.no/EchoService.wsdl%7DSayHi>
<http://www.bccs.uib.no/EchoService.wsdl%7DSayHi>

 in: <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:jbi="
http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"; xmlns:msg="
http://www.bccs.uib.no/EchoService.wsdl"; name="SayHiRequestMsg"
type="msg:SayHiRequestMsg" version="1.0"><jbi:part><ech:SayHi
xmlns:ech="
http://www.bccs.uib.no/EchoService.wsdl";>
       <ech:Hi xmlns:ech="http://www.bccs.uib.no/EchoService.wsdl
">smx</ech:Hi>
    </ech:SayHi></jbi:part></jbi:message>
 out: null
]


Here is the last error I get
javax.jbi.messaging.MessagingException: Out not supported
      at


org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:357)
      at


org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageObserver.java:125)
      at


org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1932)
      at


org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1790)
      at


org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:166)
      at


org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
      at


org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
      at


org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
      at


org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
      at


org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
      at


org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167)
      at


org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
      at


java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
      at


java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
      at java.lang.Thread.run(Thread.java:619)

cheers, Håkon


cheers, Håkon
2008/5/7 Freeman Fang <[EMAIL PROTECTED]>:





Hi,

From the  log, I can't see your cxf consumer start correctly, if
you
consumer start correctly, the log should print out something like

May 7, 2008 11:53:08 AM org.apache.cxf.endpoint.ServerImpl
initDestination
INFO: Setting the server's publish address to be
http://localhost:8192/EchoService

Could you decribe how you package your SUs and SA? Any chance you
append
the jbi.xml for your SA?

Freeman


Håkon Sagehaug wrote:





Hi,

See inline

2008/5/6 Freeman Fang <[EMAIL PROTECTED]>:







Hi,

The info
INFO - WSDL1Processor - EndpointServiceEndpoint[service={



http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
           <


http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
      <



http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy




]has




a service description, but no matching endpoint found in
is print out when start cxf bc provider, this is normal when
start
cxf
bc
provider which specify endpoint name is different with the
port
name
in wsdl
and this info will not prevent you to see the wsdl from
http://0.0.0.0:8192/EchoService/?wsdl, since cxf consumer
publish
this
wsdl.
From your info I can't tell what's the problem with your
consumer,
could
you use some command like
netstat -nap|grep 8192






Here is the result of netstat -nap|grep 8192

tcp        0      0 :::8192                     :::*
LISTEN      22734/java







to see if port 8192 is on of your localhost?
Or would you append you full log when deploy the SA






Here is what output I get when I deploy it

INFO  - AutoDeploymentService          - Directory: hotdeploy:
Archive
changed: processing cxf-tutorial-sa-1.0-SNAPSHOT.jar ...
DEBUG - AutoDeploymentService          - Unpacked archive



/Home/bccs/hakont/apache-servicemix-3.2.1/hotdeploy/cxf-tutorial-sa-1.0-SNAPSHOT.jar
to



/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/tmp/cxf-tutorial-sa-1.0-SNAPSHOT.0.tmp
DEBUG - SedaFlow                       - Called Flow suspend
DEBUG - JMSFlow                        - Called Flow suspend
DEBUG - JCAFlow                        - Called Flow suspend
DEBUG - AutoDeploymentService          - SA dependencies:
[servicemix-cxf-bc]
DEBUG - DeploymentService              - Moving



/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/tmp/cxf-tutorial-sa-1.0-SNAPSHOT.0.tmp
to



/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/install
DEBUG - DeploymentService              - Unpack service unit
archive



/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/install/tutorial-cxf-provider-su-1.0-SNAPSHOT.zip
to



/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/sus/servicemix-cxf-bc/tutorial-cxf-provider-su
DEBUG - CxfBcComponent                 - Deploying service unit
DEBUG - CxfBcComponent                 - Looking for



/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/sus/servicemix-cxf-bc/tutorial-cxf-provider-su/xbean.xml:
true
DEBUG - CxfBcComponent                 - Service unit deployed
INFO  - ServiceAssemblyLifeCycle       - Starting service
assembly:
cxf-tutorial-sa
INFO  - ServiceUnitLifeCycle           - Initializing service
unit:
tutorial-cxf-provider-su
DEBUG - CxfBcComponent                 - Initializing service
unit
DEBUG - CxfBcComponent                 - Service unit
initialized
INFO  - ServiceUnitLifeCycle           - Starting service unit:
tutorial-cxf-provider-su
DEBUG - CxfBcComponent                 - Starting service unit
DEBUG - ComponentContextImpl           - Component:
servicemix-cxf-bc
activated endpoint: {
http://www.bccs.uib.no/EchoService.wsdl}EchoService<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService>
<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService>
<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService>:
EchoServiceProxy
DEBUG - CxfBcComponent                 - Querying service
description
for
ServiceEndpoint[service={



http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
         ]
INFO  - WSDL1Processor                 - Endpoint
ServiceEndpoint[service={



http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
         ]
has a service description, but no matching endpoint found in
[EchoServiceLocal]
DEBUG - CxfBcComponent                 - Querying service
description
for
ServiceEndpoint[service={



http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
         ]
DEBUG - WSDL2Processor                 - Endpoint
ServiceEndpoint[service={



http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
         ]
has a non WSDL2 service description
DEBUG - JCAFlow                        - ServiceMix:
broadcasting
info
for



org.apache.servicemix.jbi.event.EndpointEvent[source=ServiceEndpoint[service={



http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
         ]]
DEBUG - JMSFlow                        - ServiceMix:
broadcasting
info
for



org.apache.servicemix.jbi.event.EndpointEvent[source=ServiceEndpoint[service={



http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
         ]]
DEBUG - CxfBcComponent                 - Service unit started
DEBUG - SedaFlow                       - Called Flow resume
DEBUG - JMSFlow                        - Called Flow resume
DEBUG - JCAFlow                        - Called Flow resume
INFO  - AutoDeploymentService          - Directory: hotdeploy:
Finished
installation of archive:  cxf-tutorial-sa-1.0-SNAPSHOT.jar

Thanks for the help, I've banged my head against the desk now
for a
couple
of hours








Freeman


Håkon Sagehaug wrote:







---------- Forwarded message ----------
From: Håkon Sagehaug <[EMAIL PROTECTED]>
Date: 2008/5/6
Subject: Re: Using cxf consumer and provider
To: [email protected]


hi

I got the same error, any other tips, I think I've also most
tried
everything suggested in the lists.

cheers, Håkon

2008/5/6 Freeman Fang <[EMAIL PROTECTED]>:

Hi,








Add
endpoint="EchoService"
service="bccs:EchoService"

for your consumer, this should work

Freeman


Håkon Sagehaug wrote:









Hi

I've got a as it seems a known problem, looked at the
mailing
list,
but
have
not managed to solve my problem.

The setup is like this. I've got a external web service
that
I
want
to
call
through service mix using cxf consumer and provider.
I've
got
one
cxf su
that contains a xbean.xml file like this

<beans xmlns:cxfbc="
http://servicemix.apache.org/cxfbc/1.0";
 xmlns:bccs="http://www.bccs.uib.no/EchoService.wsdl";


<cxfbc:consumer wsdl="classpath:service.wsdl"

                 targetEndpoint="EchoServiceProxy"
                 targetService="bccs:EchoService"

targetInterface="bccs:EchoServicePortType"/>

 <cxfbc:provider wsdl="classpath:service.wsdl"
                 locationURI="
http://localhost:8080/axis2/services/EchoService/";
                 endpoint="EchoServiceProxy"
                 service="bccs:EchoService"

interfaceName="bccs:EchoServicePortType"
 />

</beans>

And a wsdl file in the same folder like this

<?xml version="1.0" encoding="UTF-8"?>
<definitions name="EchoService" targetNamespace="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns="
http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema"; xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/";>
 <types>
 <xsd:schema elementFormDefault="qualified"
targetNamespace="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns:tns="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema";>
       <xsd:element name="SayHi">
           <xsd:complexType>
               <xsd:sequence>
                   <xsd:element name="Hi"
type="xsd:string"/>
               </xsd:sequence>
           </xsd:complexType>
       </xsd:element>
       <xsd:element name="SayHiResponse">
           <xsd:complexType>
               <xsd:sequence>
                   <xsd:element name="HiResponse"
type="xsd:string"/>
               </xsd:sequence>
           </xsd:complexType>
       </xsd:element>
   </xsd:schema>
 </types>
 <message name="SayHiRequestMsg">
 <part name="parameters" element="tns:SayHi">
 </part>
 </message>
 <message name="SayHiResponseMsg">
 <part name="parameters" element="tns:SayHiResponse">
 </part>
 </message>
 <portType name="EchoServicePortType">
 <operation name="SayHi">
<documentation>Just a simple echo operation that returns
the
same
string
that is given to it.</documentation>
 <input message="tns:SayHiRequestMsg">
 </input>
 <output message="tns:SayHiResponseMsg">
 </output>
 </operation>
 </portType>
 <binding name="EchoServiceBinding"
type="tns:EchoServicePortType">
 <soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"/>
 <operation name="SayHi">
 <soap:operation soapAction="
http://www.bccs.uib.no/EchoService.wsdl/SayHi"/>
 <input>
   <soap:body use="literal"/>
 </input>
 <output>
   <soap:body use="literal"/>
 </output>
 </operation>
 </binding>
 <service name="EchoService">
<documentation>This WSDL file describes a simple Echo
Service
that
echoes a
string sendt to it. This service is intended primarily
for
testing
purposes.</documentation>
 <port name="EchoService"
binding="tns:EchoServiceBinding">
 <soap:address location="http://0.0.0.0:8192/EchoService
"/>
 </port>
 </service>
</definitions>

But when I deploy the service assembly  get this

INFO  - WSDL1Processor                 - Endpoint
ServiceEndpoint[service={





http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
<

http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
                 <


http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
            <



http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy
       ]
has a service description, but no matching endpoint
found in
[EchoService]

and when I go to http://0.0.0.0:8192/EchoService/?wsdl i
don't
get
any
wsdl,
just HttpError:404

I'm sure the error is easy to fix, but have not been
able to
solve
it,
any
tips out there??

Also the location of the ws in the wsdl is on servicemix
port,
this
is
correct right, and in the provider the locationURI will
overwrite
this
value
and send it to the appropriate











yes, it's correct

 cheers, Håkon























Reply via email to