Hi!
It's me again :)
I found out the same exeption in mail-list archive earlier.
So, it is recommended to use servicemix-3.2.2-SNAPSHOT.
But I work with 3.2.1 version (lastest release-version).
Is it possible to pass this issue on servicemix-3.2.1?
Thanks,
Ivan Pryvalov.
ivan пишет:
Sorry, I didn't change my bc-component...
Now I have following:
<stack-trace><![CDATA[javax.jbi.management.DeploymentException:
org.apache.cxf.BusException: No Dest
inationFactory was found for the namespace
http://cxf.apache.org/transport/jms.
at
org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:316)
at
org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
at
org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.jav
a:96)
at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:
88)
at
org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69
)
at
org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentSer
vice.java:508)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeplo
ymentService.java:350)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentSer
vice.java:253)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeployment
Service.java:647)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentServic
e.java:60)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.jav
a:611)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: org.apache.cxf.BusException: No DestinationFactory was found
for the namespace http://cxf
.apache.org/transport/jms.
at
org.apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactory(DestinationF
actoryManagerImpl.java:102)
at
org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:85)
at org.apache.cxf.endpoint.ServerImpl.<init>(ServerImpl.java:58)
at
org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:310)
... 13 more
]]></stack-trace>
WSDL:
...
<wsdl:binding name="MyServiceBindingJms" type="tns:MyService">
<soap:binding style="rpc"
transport="http://cxf.apache.org/transport/jms"/>
<wsdl:operation name="myService">
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
...
Truly yours,
Ivan Pryvalov.
ivan пишет:
Hi!
I have developed service-assembly like "cxf_wsdl_first" example. I
have my_service_cxf_se_su, my_service_cxf_bc_su and my_service_sa.
Difference is in wsdl where I have following:
<wsdl:service name="MyServiceDef">
<wsdl:port name="MyServicePortJms"
binding="tns:MyServiceBindingJms">
<jms:address destinationStyle="queue"
jndiConnectionFactoryName="java:comp/env/jms/OutputQueueConnectionFactory"
jndiDestinationName="java:comp/env/jms/OutputQueue">
</jms:address>
</wsdl:port>
</wsdl:service>
There is log from ServiceMix when deploying:
...
INFO - ServiceUnitLifeCycle - Starting service unit:
my-service-cxfse-su
26.06.2008 10:36:37
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
INFO: Creating Service {http://mycompany.com/services/}MyService from
class com.mycompany.services.MyServiceImpl
26.06.2008 10:36:38 org.apache.cxf.configuration.spring.ConfigurerImpl
getBeanName
INFO: Could not determine bean name for instance of class
org.apache.cxf.transport.jbi.JBIDestination.
..
and
...
INFO - jetty - jetty-6.1.6
INFO - jetty - Started
[EMAIL PROTECTED]:8092
...
How can I test my service?
In case HTML/SOAP I can use axis2 for creating client on java.
But what should I do if I have jms queue?
Thanks,
Truly yours,
Ivan Pryvalov.
