We are maintaining an application using GraphDB as a backend service. This application is built on spring-boot, and we are testing the application with a test-dependency to graphdb-runtime. It seems like GDB relies on an old version of Dropwizard (3.x), which had it's last release many years ago. Version 3.2.6 seems to be the last 3.x version.
This old version dependency clashes with the spring-boot dependency management (4.x), and these Dropwizard dependencies are managed manually. This is something we would like to avoid. Are there any plans to lift the Dropwizard dependency in GDB to version 4.x?
Unfortunately upgrading the version of dropwizard isn’t straightforward because of major differences between dropwizard 3.x and 4.x but we’ll see if we can plan this for a future GraphDB version.
Related
I am planning to use MapStruct in my project. Using JDK11, Spring boot 2.7.x has my current version but soon planning to upgrade it to JDK17 and Spring Boot 3.0. Based on documentation, latest library will support JDK8 onwards. Would like to know, whether library will support for above said specification. And also would like to know, how actively the project is going to support in near future?
I'm using WebSphere 9.0.5.3 and after migrating CXF-core lib from 3.1.x to 3.2.x I'm facing this problem :
AbstractJAXRS E No resource classes found
with CXF 3.1.x everything works fine my server is working and my rest services are working as well.
ps1: I have already disabled JAXRSEngine of WebSphere and working with my own libraries ( in the shared isolated package ) and as I said it was working fine with the previous version
ps2: I have already modified the class loader policy ( Multiple -
single )
with some debugging, I figured out that WebSphere is not even loading my classes ( annotated with #path)
ps3: have already upgraded jaxrs-ws-rs to 2.1.1 because CXF 3.2.x
supports JAX-RS latest 2.1 spec even though this spec is backward
compatible with jaxrs 2.0
and i have already upgraded also all the CXF JAXRS related jars and still have
the same problem
PS4: my application is working fine with tomcat 8 and Wildfly/JBoss so
i don't think i have a problem with my resources classes
PS5: in the same jar, the other classes are loaded so WebSphere is filtering the resources classes and not loading them
the main problem here is why websphere is not loading my resouruce classes i have just upgraded the jar and I kept the old configurations ?
The IBM WebSphere Application Server does not provide direct support for JAXRS 2.1. However, what you are attempting may still be possible. Beyond setting the "com.ibm.websphere.jaxrs.server.DisableIBMJAXRS20Engine" property to "true" you should also set the JAXRS provider to "2.0 spec" via the command prompt or administrative console, see the following for details: https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/rwbs_jaxrs_coexist.html
Beyond this, if you need the JAX-RS 2.1 APIs, then you will need to package the APIs with your application. You might also need to use parent-last classloading or package them in an isolated shared library associated with your application. Either approach poses some classloading risk.
I am using grails 2.3.0 and wanted to know which version of mongodb GORM is compatible with it.
The latest version of mongodb GORM requires 2.3.2 > http://grails.org/plugin/mongodb
My mongodb version currently is 2.6.0 but that should not matter I suppose.
It would be great If I could also know the gorm datastore dependencies version for grails 2.3.0 and mongodb gorm. Below are the ones for the latest mongo gorm.
dependencies {
…
compile 'org.grails:grails-datastore-gorm:3.1.0.RELEASE'
compile 'org.grails:grails-datastore-core:3.1.0.RELEASE'
test 'org.grails:grails-datastore-simple:3.1.0.RELEASE'
}
I also tried to go thru all the releases for mongodb gorm here: https://github.com/grails/grails-data-mapping/releases but did not get much of help.
In my Grails 2.3.11 app I'm using
compile ':mongodb:3.0.2'
before upgrade from 2.2.x to 2.3.x I was using :mongodb:3.0.1.
In another Grails 1.3.7 app I'm using :mongodb:1.0.0.RC4 with some hacks to enable aggregation.
I tried to find a version of plugin in between to match my Grails version best, but it's not trivial. The branch names in github have nothing to do with released plugin versions.
BTW,
early versions of Grails 2.3.0 has severe problems (don't remember which ones exactly, but they made the upgrade from 2.2.x impossible). So, I'd recommend to upgrade your Grails to the most recent 2.3.11
We are using tree cache in jboss 4.2.x, we are planning to switch to jboss6.x, will jboss 6.x supports tree cache?
From the JBoss Wiki:
As of version 6.0.0.CR1, Infinispan replaced JBoss Cache as the distributed caching technology upon which JBoss AS clustering services are built.
Now, it's possible that you may be able to package a downloaded copy of JBossCache 1.4 (which is the version that comes with JBossAS 4.2) inside your application and deploy it on JBossAS 6.x, but I suspect this is unlikely to work - JBossCache 1.4 relies on some very old shared JBoss libraries.
I think you're going to have to refactor your code to work with Infinispan rather than JBossCache, if you want to migrate from AS 4.2 to 6.x.
Has anybody heard of the Lucene version 2.3.1.3?
We're using it in a production project.
However the stable version of Lucene version 2.0.0.4.
Should I push to have the project's dependencies moved to version 2.0.0.4?
Are you talking about Lucene or Lucene.NET? These are different but related projects. Lucene.NET is a .NET port of the Lucene Java code.
2.0.0.4 is the stable version of Lucene.NET.
However, there is a version 2.3.1 of Lucene (for Java). The Lucene Website makes it seem like 2.4.1 is the most recent release suitable for production.
I'm running 2.3.1.3 over here in production at about 50 sites.
I wouldn't recommend downgrading the version as a lot of performance and memory leak issues are adressed in 2.3.1.