There is almost no new features in jLibrary client side:

• The core infrastructure has been migrated to Eclipse 3.2
• The main change is that now to connect to a remote server you have to use the prefix http:// just as a regular URL instead the old prefix jlibrary://.

  

• The deployment process is now much easier and is taking advantage of the Maven PDE Plugin making really easy to deploy new jLibrary versions for many platforms and architectures.

• The bad news is that several UI components have been removed as I don't have enough time to maintain them. The help pages and cheatsheets have been removed. All the help will be now only accessible from the jLibrary main web page. Another component that has disappeared is the intro page. And finally, the start dialog has been removed as currently the local repositories will always be confined to the local installation folder.

• Several bug fixes have been removed specially in the categories, bookmarks and web browsing areas.
• The linux version has been improved.
• Now finally, after many requests, there is a Mac OS X jLibrary version!

The server core is the part that has experienced more changes:

• Now there is the possibility to register custom properties on the repositories. After that, you can add this custom properties to any document, search within the properties content, etc.

  public void testCreateCustomProperty() {
  
    try {		
      if (!repositoryService.isPropertyRegistered(
      				testTicket,customProperty.getName())) {
        repositoryService.registerCustomProperty(
        				testTicket, customProperty);
        assertTrue(repositoryService.isPropertyRegistered(
        				testTicket,customProperty.getName()));
      } else {
        fail("The custom property already exists!");
      }
    } catch (Exception e) {
      e.printStackTrace();
      fail(e.getMessage());
    }
  }
  		  

• The main change in jLibrary is that the default communications way has been replaced from using Web Services to use tunelling over HTTP. A new streaming layer has been added solving all the problems associated with the serialization and transport of big objects over the wire, making jLibrary more performing, scalable and with a less memory compsumption.
• All the system is now configurable through factory based dependency injection.There is still the old Axis web services interface but it is only optional. However, changing the old interface for the web services one is only a matter of changing a factories definition configuration file.
• The jLibrary server now is only distributed in WAR format.
• All the jLibrary servlets are initilizated now at server startup.
• The deployment system has been simplified and migrated from the old Ant scripts to a more suitable Maven 2.x based process.
• Plenty of unit tests have been added to make easier the platform adoption to new developers.