Skip to content
Advertisement

Exception when creating Spring Context with JMS Service references

We have a Swing UI client which uses an Appclient which sets up a Spring framework context with CAMEL beans for talking to remote services in an OSGi server via JMS.

Here’s an example of one of the service references:

JavaScript

Recently we added ‘camel-http’ features to the OSGi (Karaf) server to allow the use of HTTP URI endpoints.

This inclusion on the server has started creating a warning when the client starts with the following Stacktrace:

JavaScript

This appears to indicate that when our existing JMS endpoints are being created, it is somehow finding a reference to the ‘RequestEntity’ class. There is no reference to this class in any of our code, so we’re not sure why this warning has started appearing.

Is there any way we can get more information about which bean it is trying to instantiate?

Advertisement

Answer

Eventually tracked it down to a third-hand dependency of the Karaf bundle that had the ‘camel-http’ added to it.

We didn’t have the ‘interface’ classes for the services in a separate bundle. Once we separated them out and only included that ‘api’ bundle with the interfaces, the error went away.

User contributions licensed under: CC BY-SA
5 People found this is helpful
Advertisement