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 ;)
Related
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.
In the project I am working, I have to reuse a project which uses storm 0.9.7.
I do not want to upgrade to higher version as it would need a lot of code changes I I am expected to reuse that code.
Is Storm version 0.9.7 still supported? Or is support for 0.9.7 dropped?
If Storm 0.9.7 is not supported, I may have to rewrite the code
As far as I know development on 0.9.x has stopped. You might still be able to get answers to your questions on the user mailing list, but I'd move to a more recent release.
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.
We are evaluating reactor library for using it in our project. Our project was backed by spring context. So we needed a tool to build event-driven application which has the spring support.
Also our main area of focus was on ability to composing sequence of asynchronous events (Streams & Promises). In certain other use cases we might be in need of publisher/subscriber model or running long running processes asynchronously.
As I was evaluating, I noticed some of the following the latest released reactor-spring version is v1.1.3 with dependency on reactor-v1.1.3 which we could use.
But I also noticed the there’s reactor-v.2.0.0 (under development) which had quite a bit of changes especially in the area of Streams and Promises.
Please suggest me if it is a good idea for going with reactor-v1.1.3 with spring support or should we wait for reactor-v2.0 if we have to use more of Streams and Promises.
If we go ahead with reactor-v1.1.3.RELEASE how much code changes might be needed to get ourselves upgraded to v2.0.0.
I also wanted to check if we have any branch of ‘reactor samples’ for reactor-v1.1.3/v1.1.4. As of now I could see only one master branch available which has been updated to use reactor-v2.0.
Do we have the reactor API for latest release v1.1.4. Currently the API (https://reactor.github.io/docs/api/) points to Reactor 1.1.0 Release.
Where can I find the reactor-core-2.0.0 codebase? I am finding difficult to locate.
As I am new to this library, please feel free to correct me if any of my mentioned points/questions were incorrect. Thanks.
If you're starting new development, definitely go with Reactor 2.0. It's mainly the substantial improvements in the Stream and Promise APIs which resulted in having to bump the major version number. Differences in the rest of the codebase are pretty minimal. Converting between 1.1 code and 2.0 code requires some package renaming and a few tweaks here and there (like eliminating the use of the Deferred object in Stream 1.1).
The other major change that justifies a major point release bump is the implementation of the Reactive Streams specification. It's out of the scope of this question to discuss it further but it is an important part of Reactor moving forward. Being able to natively integrate with Akka Streams, Ratpack, RxJava, and other libraries that already (or will shortly) implement Reactive Streams is a huge benefit to Reactor 2.0.
The reactive-streams branch contains the code for Reactor 2.0. M1 is coming shortly and we'll start the process of updating the samples, though as you've noticed, some components like Spring support have already had to be bumped to Reactor 2.0 since they're relied on in some major almost-production applications.
Does anyone have any information on Spring Web Flow 3 status?
Here are a few relevant links that support my sense that springsource has essentially abandoned the project:
1)Official roadmap indicates they are missing milestones by over a year now with no update to the roadmap.
2)Forum thread filled with these questions ignored by Keith Donald and Spring team.
3)Official Download page says the latest release is 2.2.1 but is actually 2.3 so that is not even being kept up-to-date anymore.
While Web Flow version 2 I'm sure is a great product, the issues above are all obvious red flags when it comes to evaluating an open source product -- as well as evaluating the company behind that project. Am I simply missing some communication channel where all this has been discussed in detail before? I find it hard to believe that springsource, a company that seemingly had their act together, would be this negligent with one of their flagship products.
They just added a graphical web flow editor into STS. See this InfoQ post. Also, I just checked JIRA and Fisheye and it looks like there's bug fixes going into a 2.3.1 coming that corresponds with Spring 3.1. So I don't think it's abandoned, it's just not getting new features.
Just wanted to mention that the latest version (2.3.1) of Spring Web Flow was released on Mar 27, 2012. See the changelog file: http://static.springsource.org/spring-webflow/docs/2.3.x/changelog.txt