Which version of Infinispan runs on Jboss AS 5.1.0 GA? - caching

As per this post Infinispan 4.x can be run on Jboss AS 5.1.0 GA.
1. So, is that it? Can't we run higher versions of Infinispan on Jboss AS 5.1.0 GA?
2. Some bug fixes would have been done on Infinispan 4.x and upgraded to higher versions. So, if I use Infinispan 4.x what all bugs I could face?

You can run any version you like, but you'll have to isolate the classes to avoid conflicting with the ones included in the AS. Of course you can't replace the clustering technology in AS5 with it: you can use it exclusively with your own applications. If you intend to use it with Hibernate make sure you pick an Hibernate version compatible with the Infinispan version you choose: consequentially you might need to bundle a custom Hibernate version as well, and isolate from the older version provided in AS5. Generally, the Infinispan team does not consider AS5 support a goal and we're not actively testing for this.
Hard to tell which issues could affect you not knowing what you plan to use it for. All issues are tracked in the open as well so feel free to check: Infinispan changelog or ask for more advice on the Infinispan forums.

Related

Is there a recent version of Apache Derby that is supported in OSGi?

I am using Derby 10.8.2 which requires Gemini DBAcess. These versions are very old (circa 2011) and do not work with JRE > 1.8.
As the title asks, does anyone know of a more recent version that will work in an OSGi evnironment?
Thanks
The Derby community have an open Enhancement Request to support OSGi on the most recent versions of Derby: DERBY-7056
There are a set of proposed changes to provide this support.
My understanding is that the primary blocker on this is access to somebody who is relatively familiar with OSGi and could test the support, as none of the Derby committers are users of OSGi.
So perhaps you could volunteer to work with the Derby community and help get the OSGi support tested and committed?

Is it safe to use spring cloud GREENWICH.SR3 version? Is it a stable version? Or should we have to stick with GREENWICH.RELEASE flavor?

GREENWICH.RELEASE was released by the beginning of this year while SR3 is recently released. Can anyone explain what service release (SR) means? Is it same as SNAPSHOT and will be changed frequently? Or are they fairly stable versions that can be used in a production environment?
An SR means Service Release (subsequent maintenance releases that come after major RELEASE), it's completely stable and can be used on production.

Which version of Spring I should start learning?

From which version I should start learning Spring framework?
I am confused from which version I should start, there are multiple major versions strating from 2 till 5.
Start with latest version is a general rule of thumb. Unless you are working in an environment (say collaborative project) where you have no choice but to use a specific version.
Docs will have sections explaining concepts for a newbie.
In a framework like Spring major versions have different concepts about how things should be handled and things wouldn't be compatible between versions. Why learn something which is known to be outdated and not supported by newer version.
Newer version also introduce newer technologies and paradigms e.g. Spring 4 introduced websockets and Sprint 5 has support for reactive style and HTTP2.
Also newer version would be fixing what is broken in a previous version.

Spring IO Platform 2.0 - Themes/Changes?

Noticed that there is a 2.0 version of the Spring IO Platform available as a snapshot. I am looking to understand what might be driving the major version number change. Can someone with better insight into the changes share the themes here (or point to somewhere where this is better documented)?
Look at the "Upgrading" section of the documentation: http://docs.spring.io/platform/docs/2.0.0.BUILD-SNAPSHOT/reference/htmlsingle/#upgrading-removal
Some dependencies were removed, which leads to a major version, since it's a breaking change.

Impacts of using Jetty 9.2 with Spark-Java

I want to use Spark-Java 2.0 with Jetty 9.2. The trick here is that the Maven repository for Spark has dependency on jetty 9.0. The reason is that we already have working code using 9.2. When we bind/load the Spark jar at runtime there are class load errors.
The question is what issues may arise for Spark if I do a build to use jetty 9.2?
They other question could be, can I use excludes some how to load Jetty 9.2 over the 'requested' 9.0 classes? Is that possible, or will it cause me more bother?
Let me know if you think of other considerations. Also let me know where to find release notes for Jetty if you can? I looked for Jetty release notes here: Jetty Documentation hub; it is a little disappointing because they simply link to updated manuals. I look for Release Notes to show me what's different and changed between versions -- A new manual won't help unless I have a way to do 'diff' on the two manuals.
My thinking is that a jump between 9.0 to 9.2 should be a valid increment. My thanks in advance for your insights.

Resources