Enterprise Java productivity is still not ideal?

Spring community say that enterprise Java productivity is still not ideal. Why not? To start up the project you use code from previous projects or some assets. They are not ideal for new project. But why new Spring framework Roo provide ideal assets? There are exist many applications with designers just click and you have final applications. Such as WebSphere and AquaLogic. But still many developers and companies prefer use spring, ejb. This tools are more flexible. And actually I like idea of Spring Community. But Roo is still a toy. And I am afraid of automatically generated aspects. Last year innovations in enterprise application developing to create productive application with best practices is agile and cloud computing. I think it's quit interesting to have tool for manual coding and customization. We are going to the past no UI designers only command line. It's still flexible and fast solution.

Java future

Java future is abstract. But I think with time Java world would be stronger. I like the idea of Spring community. Java has more 3rd party libraries, but there are no one platform. The Spring present new framework ROO. At the first look it's pretty nice. Interesting how it's work for complex projects. Because for simple CRUD application it's wonderful. I think Java community need new technology for fast application creation. The maven help us to add dependency. But yet not exist flexible solution for assets.

Cloud computing

Working on cloud computing application and still doesn't understand why is popular. Actually it has only business value. For big projects, which has some computation loading. But for small it has no value. Platform clouds such as Google Apps its still simple hosting. You have platform but no multi threads. But simple DB access. The Amazon is infrastructure cloud and have more features. They have many success stories. But still it's big projects. 72$ for month +traffic +storage it's quite expensive for small startups. But for enterprise solutions its cheap.

Wicket vs GWT

Wicket and GWT both use component approach. But it's too different. The Wicket uses a special HTML attribute to denote components, enabling easy editing with ordinary HTML editors. With Wicket you get the benefits of a first-class component model and a non-intrusive approach to HTML. In Wicket, all server side state is automatically managed. For many applications, it will be worth trading off the increased server load of extra server-side state for decreased development costs, lower maintenance costs, quicker time-to-market and generally higher quality software. But the GWT has a different approach to AJAX. The GWT use pour HTML and Java DOM model, to translates your Java application to browser-compliant JavaScript and HTML. Making a heavy use of client browser and minimizing number and size of HTTP requests. With Java to JavaScript translation you should always control your code. In client code you can use only base types. To call service you should create special classes. With service implementation you get 3 files. Two interface where first is for synchrony use, second is for asynchrony use and one implementation. So you have messy code. One of disadvantages is complex structure of modules. Personally I chose Wicket. It impresses me with its simplicity and ability to create reusable panels without any XMLs.

Social SOA

Maybe it's just the way I am wired, but all this social networking stuff, all the time, is starting to get on my nerves. So perhaps I was predisposed to react poorly when I saw IBM's announcement last week that they would be introducing a "global social network" to advance Service Oriented Architectures. It really isn't such a horrible idea, I suppose; get high-concept thinkers from around the world to interact with one another virtually and brainstorm the future of SOA in a supportive environment. So go on: get in on the SOA Jam while you can. It runs through Thursday. Someone else please go log in and tell me if it's as ridiculous as I imagine it might be (Microsoft's failed Aggreg8 was the first thing that came to mind as a model).

Test performance with Apache JMeter

JMetter is application designed to load test functional behavior and measure performance. Can be used for testing Web Applications. I'd like to test our company web application. To start use JMetter I download and unzip archive. After that I just run jmeter.bat yep GUI is opened. But how to run test??? I configure elements, but button "Run" is disabled.

The future of Social Networks

I think one of the most innovated ideas in social networks is DataPortability group. The DataPortability try to make personal data shared between social networks.

Just imagine you have registered on some social networks and want to sign up in new one. You shouldn't to fill in any profile information, search some friends and upload photos. Only you should do is agree this policy and the system take all necessary information from you previous social profiles.

DataPortability is not inventing any new standards, but use existence, such as RSS, APML, OAuth, openID, XMPP, XRI. They simply a complete reference design and put the pieces together.