This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Comment

While I don't want to fight with all manifest configuration for cxf, I took the cxf bundle from Servicemix 4 and try to install it to dm server....

The correct way of doing this, I think is to places it under repository/bundles/usr at dm server (at least from what I read from the documentation)...

And then I started the dm server with -clean parameter and I expected to see in osgi panel (installed but not resolved) a cxf bundle but after several attempts nothing is there....

I am sure this artifact is a OSGi Bundle because it deploys in Servicemix 4 and the manifest entries are there...

So my guess it is not deployed because of some missing dependencies but there is nothing in the logs, where should I look to understand what is going wrong? Should I have the increase log level somewhere....

If somebody like to see the artifact it is under fuse
system\org\apache\cxf\cxf-bundle\2.2.2.1-fuse
directory with the name
cxf-bundle-2.2.2.1-fuse.jar

Comment

dm Server provisions dependencies from its repository as they're needed. This means that it will only install a bundle from its repository if the bundle is depended upon by something else that's been deployed, e.g. another bundle that imports a CXF package or a plan that lists the CXF bundle as one of its dependencies.

If you want to see if the CXF bundle will install and start in dm Server, the easiest way is probably to drop it into the pickup directory.

Comment

I've done a project in DM Server with a web service, Hibernate and ActiveMQ connectivity. I tried to get CXF to work but failed. That is, it worked fine if I structured the web service component as a standard web application, but not if I structured it as an OSGI bundle, which is what I wanted to do. There were a lot of conflicts among the dependencies of these three components so that I ended up having to incorporate some of the dependencies as jars within the bundle rather than separate bundles in DM Server, but that seems to make the dependencies unavailable if you want to instantiate a service declaratively in the Spring files. Also, there was a configuration problem with CXF having to do with CXF having hyphens in package names (i.e., WEB-INF as a package in the jar) that made it impossible to do the Spring configuration of endpoints the way the CXF literature tells you to. So, I ended up using straight JAX-WS from Sun with the Spring jar from JAX-WS Commons instead. CXF does work well in Servicemix 4, but I've found DM Server hugely easier to work with, particularly because of its integration with Eclipse/STS and because it doesn't depend on doing everything with Maven, as seems to be the case with Servicemix.

I'm hoping the thing with CXF gets ironed out in DM Server 2.0, because it's a great package, and the Sun web site is one of the slowest and quirkiest I've ever had to work with.

Comment

This is the first that I've heard of problems with getting CXF running in dm Server. If you could provide us with some more info, or even just a pointer to the CXF bundle that you tried to use, we'd be happy to dig into it.

Thanks,
Andy

Comment

Unfortunately, I've overwritten everything and don't have the configuration files I used or the jars I tried. I know I tried the Fuse bundle version of CXF, the bundles that ship with Servicemix 4 and Fuse ESB 4, and the version of the CXF bundles that support OSGi Remote Services, and I also tried sticking the straight CXF jars into MODULE-INF/WEB-INF/lib. The project was done about six months ago on DM Server 1.0.2 before SR02. I'm pretty sure the hyphen problem had to do with the cxf.xml file.

I think a lot of the problems I've had with dependencies are because most of the bundles for things like CXF and ActiveMQ seem to favor importing packages rather than bundles, and when you use several of those components that all have their own dependencies, there ends up being a lot of package overlap among the bundles in the container, so that it has a hard time resolving package imports.