The samples, since we don't rebuild them and deploy them and such as part of the release process, use a version for cxf of "<cxf.version>[2,)</cxf.version>" and also don't include the snapshot repos by default.
Can you try running with: mvn -Pserver,snapshots -Dcxf.version=2.3.0-SNAPSHOT That should force it into using the latest 2.3.0-SNAPSHOTs and provide the repo for it to use. Most likely, with just "mvn -Pserver", it's grabbing 2.2.5 from central and using that. Dan On Tue December 22 2009 9:11:07 am Nguyen Tien Luong wrote: > Hi, > > I'm trying to run jms-spec-demo example in the snapshot version of CXF > (apache-cxf-2.3.0-SNAPSHOT-src) > I used maven for building. > > mvn install (this will build the demo) <--- It's OK > In separate command windows/shells: > mvn -Pjms.broker <--- It's OK > mvn -Pserver <--- error raises here > > > __________________________________________________________ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] An exception occured while executing the Java class. null > No DestinationFactory was found for the namespace > http://www.w3.org/2008/07/soap/bindings/JMS/. [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: An exception > occured while executing the Java class. null at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLi > fecycleExecutor.java:583) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecyc > le(DefaultLifecycleExecutor.java:499) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLif > ecycleExecutor.java:478) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFa > ilures(DefaultLifecycleExecutor.java:330) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(De > faultLifecycleExecutor.java:291) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecyc > leExecutor.java:142) at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at > org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > 39) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm > pl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at > org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at > org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: > org.apache.maven.plugin.MojoExecutionException: An exception occured while > executing the Java class. null at > org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:338) at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMana > ger.java:451) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLi > fecycleExecutor.java:558) ... 16 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > 39) at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm > pl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) > at java.lang.Thread.run(Thread.java:595) > Caused by: javax.xml.ws.WebServiceException: > org.apache.cxf.service.factory.ServiceConstructionException at > org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:275) at > org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209) at > org.apache.cxf.jaxws.spi.ProviderImpl.createAndPublishEndpoint(ProviderImp > l.java:84) at javax.xml.ws.Endpoint.publish(Endpoint.java:47) > at demo.jms_greeter.server.Server.<init>(Server.java:32) > at demo.jms_greeter.server.Server.main(Server.java:37) > ... 6 more > Caused by: org.apache.cxf.service.factory.ServiceConstructionException > at > org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:12 > 5) at > org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean. > java:167) at > org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346) at > org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259) ... 11 > more > Caused by: org.apache.cxf.BusException: No DestinationFactory was found for > the namespace http://www.w3.org/2008/07/soap/bindings/JMS/. at > org..apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFact > ory(DestinationFactoryManagerImpl.java:115) at > org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:85) at > org.apache.cxf.endpoint.ServerImpl.<init>(ServerImpl.java:69) at > org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:10 > 6) ... 14 more > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 12 seconds > [INFO] Finished at: Tue Dec 22 14:50:07 CET 2009 > [INFO] Final Memory: 38M/64M > [INFO] > ------------------------------------------------------------------------ > __________________________________________________________ > > > Because the SOAP over JMS specification feature described here is a new > feature under development for CXF 2.3, so I don't know this error relates > to the snapshot version or it's my configuration that cause this thing. > > Any help is appriciated > > Thanks > ========================================================================= > NGUYEN Tien Luong | M2PGI - UFRIMAG > 13 Rue Blanche MONIER | Tel : > 06.45.42.46.33 38000 GRENOBLE | > http://tienluong.info > -- Daniel Kulp [email protected] http://www.dankulp.com/blog
