The last beta of JVx 0.9 will be available on Friday. We have some really cool improvements in it. I think the most impressive one is the performance improvement up to 60% for meta data handling. The meta data detection takes a lot of time because of the database access, but with the new (dynamic) meta data cache mechanism this delay is gone!

Together with the 0.9 beta-4, we release the first beta of JVx WebUI 0.8. It is significantly faster and supports a lot of new properties defined by the UI.

We have invested much time and energy and look forward to the publication

It took some time, but now our application is available.

We did not change the original source code, so the installation contains our result after ~ 25 hours of work. The application is available as WebUI (html/ajax) application and as RIA (Applet). I think we were the only team with "two" frontends.

But after some good news we have a package with bad news: Most of our REST services do not work because we damaged the whole interface during our last deployment, so we are not happy with that. And last but not least, our start html for the RIA stuff is not correct. Time pressure is a killer

Where were the problems?

It was not an enormous amount of time available, but it was absolutely possible to implement all MUSTs and most SHOULDs of the specification. For the MAYs it was not enough time.

Our biggest problem was the REST integration, because we did not have any support in JVx. We decided to implement a generic REST interface based on RESTlet. We knew that the decision is a high risk because it is easier to implement the REST service without regard to JVx. But we wanted to use the result as part of the framework. We were doing well but some problems with the authentication took more time as calculated and so we had big problems towards the end. We knew that the REST services are very important for the analysis phase by the jury, but it was not possible to fix all problems before the packaging phase. And it was better to deliver our work instead of fixing and not to deliver.
In summary: missing framework support and not enough experience with REST.

The frontend/database parts were straight forward, because JVx has powerful features. We developed with our Swing UI implementation and after we finished a task, we have tested with our Web UI implementation. Of course the Web UI had some limits and smaller problems, but we changed some smaller parts to meet the requirements.
In summary: worked great.

The look and feel of the result was not important, either for us nor for the specification, and we did not check the usability. It was important for us that we have a quick access to all controls. And of course, we normally don't create web portals with JVx. It was designed to develop business (database) applications, but we had surprisingly few problems.

What about unit tests and code quality?

Most tests were manual tests because we did not have a lot of complex workflows and we had not enough time for TDD. Of course, we used JUnit for the REST services and for iCalendar creation, but thats all (best not to start EMMA because our test coverage is holey). On the other side, we produced a perfect source code documentation because our checkstyle config did not tolerate any mistakes.
In summary: With the quality we are satisfied.

Team organization?

Martin handled the whole database stuff, most of the User Interface and all workflows
Roland was in a REST "loop"
René took the rest of the User Interface, Business logic, managed the Team, Deployment, Testing and WebUI fixes

We had no problems to work together, it is always easy if you know each other.

Resume

The result could have been better, but even worse - we have our lessons learned.
We had a lot of fun, a perfect organization team and two days of pure adrenalin paired with motivation.

Jetty for Android devices: http://code.google.com/p/i-jetty/

With this implementation it should not be a problem to run the JVx server via http(s) on Android devices. Of course, it is possible to run JVx as DirectServer, but why not via http?
We have not test JVx with i-jetty, but contact us if you want to try it.

In der aktuellen Ausgabe von Java Aktuell ist der Artikel Single Sourcing mit JVx enthalten. Darin wird anhand eines kurzen Beispiels erklärt, wie der Single Sourcing Mechanismus in JVx umgesetzt wurde. Die Beispiel Anwendung wird als Desktop Anwendung bzw. Web Anwendung gestartet, und das ohne auch nur eine Zeile Source Code zu verändern.

Der Artikel zum Nachlesen: Single Sourcing mit JVx, Java Aktuell Q1-2011

Das Magazin, Java Aktuell, erscheint vierteljährlich und wird vom Interessensverbund der Java User Groups e.V (iJUG) herausgegeben.

JVM technologies for 2011 - Voting

Very interesting postings, and yes - JVx is ready for Desktop Applications

Some days ago, we updated our showcase application and especially the WebUI implementation.
But what is new?

Our WebUI has some great new features, in addition to our Plat_Forms release.

Check out the Help menu - the help is now embedded in the application. Another great feature is the download option for grids - press the small export button beside the grids. Or try uploading an image in the contacts screen - works great

Smaller changes are grid specific, e.g. the sort operation is now a remote operation, same for inserting new lines.

We welcome your feedback!

Our showcase application was updated with the latest versions of JVx and WebUI. It demonstrates the new simple charting, global meta data caching and a lot of new features of WebUI, like Upload or Help integration.

The Plat_Forms contest 2011 is over. We are proud to have participated.

Working together was really fun:

collaboration

The task (Conferences and Participants) was very interesting and we tried to use our JVx WebUI for the implementation (somewhat riskily, but an interesting challenge).

The user interface was not a real problem, of course the WebUI needs some additional features, but it is ok. On the other side, we had problems with the REST service implementation because we tried to solve it very dynamic, to be reusable for JVx.
But there was not enough time to finish the implementation. And last but not least, we damaged the REST authentication during the last possible deployment. That means that our REST service does not work - very frustrating... but we had a lot of fun.

We know that our solution has some problems, but the usage of the framework during the whole contest was really fun. And we used our single sourcing mechanism for development: We developed with our Swing Launcher and deployed the app as Ajax/HTML application - it worked great.

We give a first insight into our result (the design did not matter):

SIB Visions - Plat_Forms 2011

The Web interface is competitive, even if it was not designed for the creation of content management systems:) For classical web development, we need a different application style, but that has nothing to do with the technology behind.

Now we look forward to the results of the Jury.

We talked with James Sugrue from Javalobby (dzone) about JVx. He had some questions about the framework and we talked with him about the next features.

Read the full interview.