Sounds like "Oh Ja" in German

Our developer console arrived today! What a great day.

First impressions:

OUYA unboxing

OUYA Console

Stay tuned.

Some of you asked me why no new beta releases are available.

The answer is that we don't build beta versions since we have our nightly builds. It is better to "release" daily instead of monthly. You get access to the latest features with the delay of one day.

You can download the nightly builds from here.

We have posted that JVx quality reports are available.

Today, we also offer nightly JVx builds. The builds contain (nightly) in the Implementation-Title and Implementation-Version.

Don't use nightly build versions in production environments.

To use our nightly builds, go to

https://dev.sibvisions.com/jvx.nightly/

and click the Download link in the top menu.

Congratulations to Stefan Wurm for graduation!

He sent us his Master Thesis about JVx EE. It is a great documentation about the features and power of JVx EE. The document is in German.

Feel free to send us your comments.

The project is hosted on sourceforce and is available under Apache License 2.0.

The good old Oracle Forms UI does not look really cool. Of course, you can use nice icons and choose the right colors, but the controls are not fancy compared to swing controls.

If you try to to migrate from Oracle Forms to Java, wouldn't it be great to migrate one screen after the other. Or better, create new screens with Java and integrate them in your existing Oracle Forms application. Use both technologies as long as is necessary.

Don't think that you have to migrate the whole Oracle Forms application, migrate step by step. It is absolutely possible to use your new screens in your Oracle Forms aplication or as separate application without Forms. Save time, money and don't replace your existing Oracle Forms developers.

You would like to see how this can look like?


The first screenshot shows a standard Java swing application, with a simple master/detail and some editors:

JVx Swing UI

The next screenshot shows the same screen (without source code changes) used in an Oracle Forms application:

Forms with Java screen

You are right, it is great to embedd the same Java screen, but the Look and Feel is not very cool. Do you know that Java has some nice LaF's? Here is the same screen with Nimbus Look and Feel:

Oracle Forms Nimbus LaF

The scource code is online. Thanks to Stefan for his great work!

Check out the project page.

In the coming weeks we will finalize the documentation and build the binaries.

You find the JPA integration and a complete example application in the repository.
Have fun.

Our new project is created and we are preparing the source upload.

What is JVx EE?

It's the integration of JPA 2.0 in JVx. Create professional backend software with JVx and use your domain model which is already available in your Java EE based web application. With JVx EE you can use the configured EntityManager and JPA implementation of your web application. Reuse your existing DAOs or EAOs without changes in your application.

With JVx EE it is possible to create a standard JVx application that is connected to your domain model, e.g.:

or with a custom EAO

Do you need a professional backend application for your existing web frontend? Use JVx and your problems are solved. You get all advantages of JavaEE in your JVx application.

JVx EE is licensed under Apache License 2.0.

Do you have any questions? Let me know.

We were never asked what JVx means, neither on conferences nor via social media - until yesterday!
So we simply reveal the secret.

JVx stands for: Java Application extension

Why not JAx?
JAX is a well-known conference about Java, so we were a little creative and turned the A to a V.

We used Hudson for nightly builds since the first day of JVx. The hudson server was an internal server, so the reports were "private". We have never liked it!

Since 1 May are the reports now publicly available. Check it out:

https://dev.sibvisions.com/jvx.nightly/

You see the JUnit test reports, Checkstyle reports, Code Coverage reports and FindBugs reports.
And we now use Jenkins instead of Hudson

The current Javilion release 1.2.0 allows configuration via Preferences or Project properties. Now it is very easy to change the http port or to configure automatic reloads by file extension. With the old version, you had to change the .project file manually.

If you use the port parameter with Javeleon, no automatic reload is executed. The old Javilion plug-in sent a reload event after a java file was changed, but that was a bug. With the current version, you can configure, for which file extension you want to send a reload event.

The configuration is saved per project.

Project properties		Open the project properties (right click on the project / Properties) and be sure that Javilion nature has been added to your project! Otherwise it is not possible to change the configuration.
Preferences		Open the preferences (Window / Preferences) and set the default values! The default values are used when you Reset the settings in your project setup.

Have fun