We have been trying to implement a hibernate search with our project and in this case we had to implement Hibernate 3.5 previously we were using Hibernate Core 3.2.
Initially we tried to upgrade our version directly to the latest hibernate search and hibernate core. But, in Hibernate 4 they have removed the TransactionManagerLookupClass.
So, now what we can do in order to upgrade our Hibernate to Hibernate 3.5. As we can't upgrade our Application Server because we have other applications running on the same server.
Currently we are using:
hibernate-commons-annotations-4.0.1.Final.jar
hibernate-core-4.1.9.Final.jar
hibernate-jpa-2.0-api-1.0.1.Final.jar
hibernate-search-4.1.0.Final.jar
hibernate-search-analyzers-4.1.0.Final.jar
hibernate-search-engine-4.1.0.Final.jar
hibernate-search-orm-4.1.0.Final.jar
These are the files that we are using but, we know Hibernate 4 is not at all compatible with JBOSS 4.2.3. What we want to know that is there anyway to upgrade our hibernate core to a version where it's compatible with Hibernate search.
Secondly, the way be which we can keep the same application server.
You could use a very old version of Hibernate Search which is compatible with such a very old version of Hibernate ORM.
A better alternative would be to download a more recent version of the application server like WildFly 8 and start using that for the new applications: you can use the old JBoss 4.2 for the old applications and use a new container in parallel.
Remember that you can run multiple different application servers on the same server, you only have to make sure they use different ports.
Related
we are planning to migrate our Tomcat from 8.5 to 10/11 version.
at the moment we are using Java 8, we are planning to use Java 17 .
I wanted to know if any one has previously migrated and what were the concerns regarding that.
I am aware that javax needs to be changed to jakarta series.
in our 8.5 tomcat we are using following maven dependencies
spring - 4.3.25.RELEASE
jackson
googleapi
graph
aws amazon jdk
javax servlet
mysql connector 5.1.44
log4j
slf4j
jsoup
unirest
httpcomponents
should we also need to update these dependencies to latest version? to be compatible with latest Tomcat 10
any other issues I need to be aware of ? I will post more on the same thread as I face issues while miggrating, appreciate the feedback and support from you guys. Thanks
Solution/ best way to migrating and also any tools that does it automatically? issues faced be individuals and how they resolved while migrating.
Can i upgrade spring data mongo version to 2.2 without upgrading the spring framework version. Currently i am using spring framework version 3.2. I need to upgrade spring data mongo db version to support mongo db 4.2 TLS support.
No, you can't. The 2.x generation of Spring Data requires Spring 5 at least. Spring Framework 3.2 is severely out of date and not maintained anymore. Spring 4 was released over 6 years ago. I can only strongly recommend to upgrade to a currently maintained version to make sure you benefit from security fixes that the 3.x generation has already not seen anymore for years.
I've upgraded an application from grails 2 to grails 3. This also meant an upgrade from hibernate 4 to hibernate 5. As the application is deployed on premise in quite few installations, we've used external-config to avoid migrating configurations (from groovy to yaml).
In our current config, we have:
dataSource.dialect = org.hibernate.dialect.SQLServerDialect
However, this doesn't work. Changing this to SQLServer2012Dialect solves the problem, but requires manually changing this on every installation.
Are there any settings (e.g. in hibernate) that solves this issue?
We're using jtds as driver
I need to use WiredTiger Engine in my application which is available in the latest mongodb version 3.2.2 and my Maven repository which is using the version Spring Data MongoDB version 1.8.4, Java driver version 2.13.3 and I've installed MongoDB version 2.6.11.
Which version of spring-data-mongodb should i use, in order to be compatible with Spring 3.2.2.RELEASE?
This is the duplicate of the following unanswered question :
Which version of Spring Data MongoDB is compatible with Spring 3.2.2.RELEASE?
But I don't have enough privilege to re-ask or comment on the Question.
The last Spring Data release train compatible with Spring 3.2 is Dijkstra and has seen its last service release January 27th, 2015. The Spring Data MongoDB version contained in it is 1.5.5.RELEASE.
Note that this version is not compatible with any MongoDB 3.x version. MongoDB 3.x support was introduced in the Fowler release train and is refined in even more current releases only. So I am strongly suggesting to upgrade to one of those versions if you want to work with a MongoDB of that generation.
This may be annoying and discussed before but I could not find a good reference which would help to set a direction. I have to plan a migration of TopLink 10g (Spring 2.5 ORM Native Support) to JPA. I need some guidelines (steps) to follow and plan a successful migration.
Let me brief what I have in my technology stack. Primarily, as I mentioned above, application build around Spring 2.5 and Spring 2.5 Native ORM Support of TopLink. Spring 2.5 bundled to support only up to TopLink 10g and if you simply upgrade the TopLink JAR with the latest version it would not work as latest version of TopLink has completely changed the packaging but this still can be tackled by easily find and replace the package names. The main issue is the native api of TopLink ORM in Spring 2.5 which is built around TopLink 10g.
The reason of this migration activity is we cannot upgrade Spring until we migrate data-layer to JPA.
Please share steps if you already achieved something similar in your past or if the above briefing gives you an understanding on the problem you can also drop your opinion on how should I plan this migration.
I am facing a similar migration, toplink10g and Spring 2.5. For the integration we were using as support spring-toplink.jar, but not such support for toplink 12 that actually is the current version. At the moment seems it is not a straight fordward solution but I started first using the renaming tool provided by oracle.
The renaming tool it is necesary since jpa toplink 11 g is provided by eclipselink. You will see all the packages oracle.toplink.* will be renamed by org.eclipse.persistence.*
Did you have any advice othe advices for this migration?