I was wondering if there is a (mostly) objective comparison between the JBoss AS 7 and Glassfish 3.x?
I don't care for any differences in standards or their implementation, I was thinking more about startup time, failover, scalability, performance, memory footprint, known problems, administration, security, clustering etc.
Real world examples & experiences are very welcome!
My opinion is that after the aquisition of Red Hat to JBoss the general quality of documentation has dropped significantly. Even if JBoss is the better product in my next project I will shift to GlassFish because of the better documentation. Who cares about the startup plan if you loose 2/3 of your time dealing with lack of proper documentation?
JBoss 4 and 5 wer an examples of a properly documented products. Things have changes for worse.
Antonio Goncalves recently did a comparison of all the latest application servers including some of the metrics you requested - http://agoncal.wordpress.com/2011/10/20/o-java-ee-6-application-servers-where-art-thou/ .
I found this introduction to JBoss AS7 with short memory/startup comparison to Glassfish 3.1.1: http://hwellmann.blogspot.com/2011/10/jboss-as-7-catching-up-with-java-ee-6.html
Real-world experiences for GlassFish are here: http://blogs.oracle.com/stories
I'm embarking on a project to develop a desktop application but my expertise have been in the web application development realm. I was about to refresh my knowledge on Swing programming when I learned on JavaFX which seems to be a much better alternative. At least version 2.0 seems to fit that bill. My dilemma is that there are no books out on the topic. I was wondering if reading up on 1.3 first would be of help? Or is the syntax too, architecture, etc too different? I understand that there was something called JavaFX Script which is now gone in lieu of a Java API which is a bit why I'm wondering if reading up on 1.3 might be a futile effort?
Does anyone have any recommendations on learning resources other that JavaFX api, sample applications and such?
Obviously the syntax has changed, but if you already know Java, coding with JavaFX 2.0 will look familiar.
The one take away from existing books, is that most of the framework, controls, shapes, and effects, etc., from JavaFX 1.3 was ported over to JavaFX 2.0. So the basic knowledge of the framework can be gleaned from one of the older books. That would help you in at least knowing what component to use and then allow you to research it further to see how it now works in JavaFX 2.0.
There is also a lot of helpful documents at javafx.com. New books will be out within the next six months or so and may be available on-line sooner than that.
I'm thining about using symfony 2.0 for my new project. It's only preview a release at the moment, the final release is due in March which is around the same time I expect my project to go live.
Are there any reasons why I shoulnd't be using 2.0?
Reasons? Yes you shouldn't use it because Sensio who "make" Symfony tell you not to.
Even though it close to thier slated march release they could still make wholesale changes to the api which would leave you stranded and with a lot of rewriting on your hands. 1.4 is very stable and well documented and will be supported until at least 2012 and so unless there is something in the S2 technology that you cannot deliver you project without then stick with 1.4.
I was in two minds myself as i am developing app that will not get release until April or later and so was tempted. My plan is to build the apps in 1.4 but to build stripped down skeletons that match the 1.4 builds to see how they perform and to then build into later in 2011 when 2.0 has notched up a few revision numbers, and stabilised, and got a better body of documentation behind it.
The documentation for Symfony2 is really lacking at the moment, and seeing as it's so very different from symfony 1.4 (well of course, it's a total rewrite) it's rather hard to just pick up and use in its current state.
I'd say use 1.4 for now, and when the documentation picks up, give 2.0 a try. 2.0 does look exciting though, I can understand the temptation!
Can anyone tell me main steps to consider while migrating 1.1 to 3.5 windows based application?
What are the steps need to consider at initially while planing for migration?
as per i know this applicatin i need to migrate like wsf and wpf and soo on.
You'll need to upgrade the projects to .NET 3.5 Framework and then build the solution. Fix any compilation errors (there will likely be a few), and then you will need a large QA effort to make sure you didn't break anything. It's really more of just a time sink than anything you need a specific plan for.
If you can manage it, see if you can write unit tests for your app, and then after the upgrade, make sure all those unit tests pass.
http://www.codeproject.com/KB/books/net2_cs2_newfeatures.aspx
http://www.simple-talk.com/dotnet/.net-framework/.net-3.5-language-enhancements/
I guess you should look through new features and check whether a change in code is necessary for that new feature.
With the amount of effort involved and the changing to newer technologies like WPF, I think you are better off doing a re-write of the application in 3.5. We have had some ugly upgrades done at my place of work that may compile and run as 3.5 but are really just hacked 1.1 applications.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Well, I know it's a preview, and I know it says that it's not yet ready for production, and yet I dare ask the question.
I need to start building a pretty big application, which is planned to go live at around sep-oct 2010.
Lets say I will not release the application to production until the stable version of symfony 2.0 will be released - is it a good idea (well, I'll settle for a viable idea) for me to start building the application using the 2.0 version ?
How big is the chance I will need to rewrite/replace code I've written due to core changes in the framework ?
Thanks.
Edit: the other option right now, is to use symfony 1.4.
I have thought and tried Zend Framework, but I refuse to re-invent each and every module, which will cost me a lot of programming hours (if not days/weeks).
From Fabien's presentation of Symfony 2 at symfony live: use symfony 1.4 for your next project.
From Symfony 2 github page: things WILL change.
Now consider the following:
symfony 1.4 will be supported until late 2012, that's 2 years after your project's release
Symfony 2 does not have code generation, forms, unit tests, etc so everything that you'll do to cover up these fields, you'll have to redo when the official ways are coming (that answers your second question)
so as everyone already said here, go for 1.4
symfony 1.3 or 1.4 is the right choice for now. 1.3 if you've used symfony 1.0 before, 1.4 if not. I am personally not a fan of the from sub-framework in symfony 1.1+ for many reasons, but you may find it entirely agreeable. That's a personal choice, then.
symfony 2.0 is not stable, and many of the features it is introducing are not those which would really interest a developer, I feel, at this stage at least. sf2.0 is however a impressive exercise in making the next generation of web frameworks; but, not in making the sites you make more feature-rich or easier to develop. It may make them faster and more elegant under the hood, but this is not necessarily the primary advantage of a framework to a developer. An example of this is dependency injection. It's a further abstraction of the already excellent symfony core code components, and its inclusion only increases my respect for the symfony core team and their advances - but for an end-user it probably leaves many scratching their heads over the advantage.
The main advantage of symfony once you appreciate the basic framework is the community and its plugins, and this I think is the dealbreaker for sf2.0 right now. Yes, I know it is essentially built from 'plugins', but you will lack several crucial plugins I'm sure, and either have to write them yourself or adapt existing to suit. This is the reason you reject Zend Framework.
Still, just my opinion. I've been a symfony 1.0 and 1.1 developer (mostly 1.0) for over 3 years, and it still hasn't let me down.
That's a million dollar question my friend. It's a gamble, plain and simple. I've used a number of php MVC's (cake,zend, and symfony) and they all operate roughly the same way. What's nice about symfony is it's focus on being modular, not reinventing the wheel and it's ease of use.
I can't cite any examples of larger companies using it, however I personally would use it over cakePHP or Zend at this point. I feel like it has a strong community, it's not in danger of being abandoned (at the moment) and I generally enjoy working with the framework. Which, at the end of the day, is usually all that matters.
Like I said, I don't know how well is scales up or out but it's faster than cakePHP or Zend. It's a gamble regardless of which framework you pick, so, good luck.
Unless there is something specific in Symfony 2.0 that you need for your application, I would suggest that you go with 1.4 and work with a stable version from the get-go. From what I understand, Symfony 2.0 might not be out until the very end of the year. Symfony 1.4 will be officially supported until end of 2012, leaving you plenty of time to upgrade/rewrite for 2.0 later, if you wish to do so.
I have tried Symfony 2 for a week now (I'm a full-time symfony developper) and here are the main reasons why you should continue using symfony 1.x before migrating to 2.0:
Twig is unstable. You can't use form_render, form_error, etc. But it's pretty easy using a PHP view!
Get user's culture (locale) is a pain in the a**.
PHP templates are not fun as Twig to code. Example with this translation function:
PHP: <?php echo $view['translator']->trans('text') ?>
TWIG: {% trans 'text' %}
Bad documentation
It seems not so bad like this, but trust me... it takes me so much time to debug those stuff to realize in the end that it was wrong inside Symfony 2 himself.
By the time you release your project, version 2.0 is most likely will not be stable anyway. And consider that version 1.4 has long terms support for 3 years, which you can count on if you are starting up a new project. Other than that, with symfony 2.0, things are not going to be same :) it is going to be so much different than current versions. You might not like it :) or it might not be suitable for your project.
Or you can just use Lithium...you know, it's better than all of the frameworks on the page mentioned... BUT the question IS about v2.0 readiness not about cake or other frameworks (as mentioned by other posts, though I figured I'd get my jab in too).
I personally wanted to use 2.0 on a major project, but will likely turn out not because of fear (always a bad reason).
My point is this. Nothing is stable. Not even 1.4. EVERYTHING in this world is subject to change and there's always patches and fixes for everything. If we didn't use beta/alpha software, ESPECIALLY in an open source community, we'd never progress.
So. It's a risk. The trick is you gotta be good enough to handle any problems that may crop up. I think that's just the name of the game. You're either the type of developer who goes off and installs Wordpress and Drupal and says look at me mommy grown up pants...Or you're the type that goes out and is on the cutting (or bleeding) edge and sucks it up and gets it done. Rolls with the bad times and smiles (from ear to ear) during the good.
End of the day it's your job. Don't ever let anyone tell you how to do it. You do it how you want.