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.
Related
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.
I've recently released version 4 of SBJson. This is a new major version that is not backwards compatible. Since SBJson is widely bundled by other popular libraries I renamed all the classes & enums to make sure it can be used in conjunction with prior versions.
However, I'm not sure how to best handle this situation with CocoaPods. I contributed a 4.0.0 spec to the existing SBJson specs, but I suspect it will be impossible to install version 3.2 and 4.0.0 in the same project. Do I have to clone the 4.0.0 spec into a SBJson4 (notice extra major version number in name) spec as well?
Morning.
If you want users to have both versions installed simultaneously they will probably have to be separate pods.
AFAIK you can't have one pod installed twice in a project. I don't even know how you'd get round the linker errors etc. for that to be possible!
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.
Is DWR a dead project? It does not appear to be under active development. The latest 3.0 release appears to be stalled. I'm specifically wondering if there are going to be maintenance releases of DWR 1.x or 2.x or is 3.0 is ever going to be released.
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
Well, the 3.0 version is taking a while to get released, but it is nonetheless very stable.
We are using it in our production environment and we do did encounter any issue so far (2+ years in use).
Important issues on 2.0.X are fixed BTW. (seems that currently there are no major issues on 2.0.X).
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
We had issues before (other version) and those were handler very quick.
Update Dec/2015: V3.0.1 released
Seems like it, I have used DWR like a year back and there is no release since then.
Their version 3 is still on RC (release candidate) and from my understanding of versioning, it is not stable or a general acceptance.
I would say move on... pass DWR. Pass Java too if you can ;)
I've been trying to build the 3.2.2 and 3.2.3 tags of WSO2 Carbon from here using Maven 2:
https://wso2.org/repos/wso2/tags/carbon/3.2.2
https://wso2.org/repos/wso2/tags/carbon/3.2.3
However, the Maven pom.xml files throughout the directory trees beneath these tags still refer to version 3.2.0 in both cases - am I missing something obvious please?
When I try and analyse the results of both the builds using our in-house tool I get identical results in the two cases (and indeed results that are identical to those for 3.2.0), which makes me think I may be building 3.2.0 repeatedly by accident.
3.2.2 and 3.2.3 are point releases and typically involves bug fixes/optimizations that do not introduce new features to the 3.2.0 release. If a particular component do not have any fixes/changes, the version still be the older version, no new version is introduced. This is how the versions are handled.
You're not missing anything. It seems they did screw up. Maybe that was their intention, but then it doesn't make any sense at all (at least for me).