Our Monitoring tool for JVx applications is very useful for application maintenance but also for application development. It safes time, problems and costs. The tool itself is a standalone JVx application and it connects to another JVx application which was configured with the monitoring plugin. It's not a hard job to configure a JVx application for monitoring, but it's boring.

We now have a really great VisionX AddOn which does all the boring work for you. It configures your applications for monitoring and makes it possible to monitor your applications during development time. It's very helpful to find bottlenecks or to do tuning before deployment

The plugin comes with an additional awesome Feature, which isn't available without the AddOn. It's the maintenance module. This module allows you to switch your application(s) in maintenance mode. You could use the maintenance mode to do manual database updates, config updates or simple health checks.

We have a short demo video which shows how it works:

The AddOn will be available in our Solution store, but not for free. The monitoring tool needs a separate license.

Our JVx headless UI (aka JVx.web) implementation is available as maven snapshot:

Don't forget the snapshot repository:

Our JVx mobile project is available as maven snapshot:

and only the API

Don't forget the snapshot repository:

Our JavaFX UI for JVx is available as maven snapshot:

or only JavaFX extensions

and don't forget the snapshot repository:

Our JVx online help system is available as maven artifact:

and as snapshot (weekly):

The next JVx release will be version 2.5. It will be available by the end of this week (beginning of July). It's a really cool release because JVx got awesome new features. We had to change the API a little bit but it shouldn't be a problem for your existing applications.

What will be interesting?

• Push-light

  Our push support has nothing to do with Websockets. It's a technology independent solution for JVx. The Push-light mechanism is available on server-side and enables you to send objects from the server to the client. If you use a direct connection betwenn client and server, the objects wil be sent immediate (e.g. vaadin UI). If you use a serialized connection, the objects will be sent with next client call or alive check.

  The API is simple:

  SessionContext.publishCallBackResult("MESSAGE", "Please logout!");

  or, in a Thread

  final ICallBackBroker broker = SessionContext.getCurrentInstance().getCallBackBroker();

  Thread th = new Thread(new Runnable()
  {
      public void run()
      {
          try
          {
              int i = 0;

              while (isMessageLoopEnabled(i))
              {
                  Thread.sleep(200);
                 
                  broker.publish("MESSAGE", getMessage(i++));
              }
          }
          catch (InterruptedException ie)
          {
              //done
          }
      }
  });
  th.start();

  It's also possible to publish to all clients, via ICallBackBroker.

  The client code is short and simple:

  connection.addCallBackResultListener(new ICallBackResultListener()
  {
      public void callBackResult(CallBackResultEvent pEvent)
      {
          if ("MESSAGE".equals(pEvent.getInstruction()))
          {
              showMessage((String)pEvent.getObject());
          }
      }
  });

  More details: Tickets #25, #1635

• H2 DB support

  We support H2 with a custom H2DBAccess. The auto detection works with URLs: jdbc:h2:.

• SQLite DB support

  We support SQLite with a custom SQLiteDBAccess. The auto detection works with URLs: jdbc:sqlite:.

• MySql limit support

  Read more...

• Life-cylcle object method inheritance
• Pie control
• Set individual cells of a table readonly
• Connection retries

  We try to re-send requests, if errors occur during transmission. This feature will be available for serialized connections only.

• Security improvements

  see Tickets: #1605, #1606, #630.

• API changes

  ICellFormat got a Style attribute and the createCellFormat of IFactory got one more parameter

Our Eclipse plugin for JVx and VisionX is available as version 1.2.4.
It's a small bugfix release.

Changes

• Proxy support (tests)

  Some customers had problems with http(s) proxies and our trial activation. We made extended tests with (win/linux) proxies and didn't find any problems. We reduced the communication timeout because it was too long. Please send us your feedback.

• Additional checks for client/server code mixing

  It might be a problem if you use a server class (src.server) in your client classes (src.client). This depends on the deployment mode (Web, Desktop, ...), but it's better to separate client and server code. The new check can be dis/enabled but it checks by default if your client has direct server references.

• Using Metadata independent of AbstractCachedStorage

  It's now possible to use column name autocompletion, even if the storage isn't an instance of "AbstractCachedStorage".

Simply update EPlug via Eclipse or jump to the info page.

We tried to improve the UX of our tool VisionX in the last weeks. The current concept is wizard based and all wizards are kept very simple. This concept works well but requires curiosity. It would be better go guide the user through the application and show the features.

Some software tools use strict guides and explain the application with step-by-step instructions. This is nice but also boring because you can't play around. We tried to add a sort of a guide but without restrictions.

The first preview of this new concept is available as YouTube video. We're not sure if this solution will be available in the next release but our testers love it. It fills the gap between wizards and the question: What should I do next?

Here's the screencast: