New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSGi services are not supported #1693
Comments
Also, I have a DEBUG output as well. I can send that upon request. |
Looks like hibernate-ehcache added a blueprint.xml file somewhere between 4.2.2-FINAL and 4.3.6-FINAL which is causing a compatibility issue between hawtio and hibernate. |
Looks like we've control over what blueprint XML files are being loaded here -> So we could either only load hawtio blueprints or add method of filtering the resulting list via configuration. I vote the latter as it's possible we could discover any old blueprint file that could hit this problem. Though, one would think OSGI services could be loaded, maybe this is something that should be improved in blueprint-web. Thoughts? |
Forgot to mention, how we are using hawtio:
This brings up an interesting discussion point. We pull in the war file and do no configuration to hawtio. We use whatever defaults are set up. With that said, is it possible to set up both. Meaning, in the hawtio-default-offline, the configuration is to pull in only the hawtio blueprint files. However, hawtio has the ability to configure it as well? There may be times when an app using hawtio wants to pull in other blueprint files? I also think the blueprint developers should be contacted with this bug. There may be a fix on their end? Or maybe they have a way to set up the configuration? |
@gashcrumb yeah I think we should prefix all our blueprint xml files with hawtio-, and then only include those files in that filter. |
You can configure which blueprint files to load
|
I have a standalone application that creates an instance of the Jetty container within itself via Spring. Hawtio is deployed into the Jetty container via Jetty Handlers (WebAppContext to be specific). We are using the following versions:
Java 1.8.0_20
Spring 4.1.1.RELEASE
Hibernate (with ehcache) 4.3.6.Final
Jetty 8.1.15.v20140411
ActiveMQ 5.10.0.1-SNAPSHOT (we created a snapshot to fix a logging issue)
Camel 2.13.0
Hawtio 4.1.26
We have other dependencies I can include if need be. But I think these are the major players.
The following exception just started to happen when we upgraded some of our dependencies. I do not know where this is coming from. Not sure if this is a compatibility issue with Hawtio and Java 8; or some combination of dependencies. I did notice there is a blueprint.xml file coming from hibernate-ehcache.
The text was updated successfully, but these errors were encountered: