2.2 (Apr 2006)

New Features

Support for Nexaweb Data Framework

• Studio 2.2 supports assembly of data from multiple sources. Studio 2.2 allows the users to pull together in an ease to use interface data driven applications. Users then will be able to see the data that is accessible to their application.
• Studio 2.2 also provides wizards to make creating data driven application easier, including wizards to help connect components to data (i.e. tables to data)
• Users are able manage multiple data sources through the addition of new data perspective, data support in the Outline, data drag and drop support and new wizards.

New Nexaweb Plugin v2.0 Support

• Studio 2.2 now provides the ability to create and manage Nexaweb plugin v2.0 projects which provide all the functionality necessary to build and deliver a redistributable Nexaweb plugin module (jar).
• Studio 2.2 Plugin supports includes a new Nexaweb Plugin perspective, Plugin Explorer View, Plugin Configuration editor.
• Nexaweb Plugins created with Studio 2.2 can be automatically published to any Nexaweb Project within Studio that uses the Plugin.

Support for Desktop Client (a separately licensed component of Platform 4.x)

• Studio 2.2 provides support for creating, running, debugging and packaging Nexaweb 'Desktop Client' applications.
• Debug and Run Nexaweb-based application within Desktop Client from within Studio with a new Studio toolbar.
• New Editors for Desktop Client configuration files.

New Web Tools Platform 1.0.x Support

• Studio 2.2 supports Web Tools Platform 1.0.x functionality including Project facets and new Dynamic web project structure.
• Nexaweb Dynamic Web Application Wizard updated to extend standard WTP 1.0.x Dynamic Web Application Wizard.
• The Web Tools directory structure has changed.
• Check Web Tools 1.0.1 Release Notes for more information on new features and known issues.
• There are important known issues with Web Tools support. 

Data Framework and Desktop Client are available as "Project Facets" within Eclipse.  To add to your project open the project's Properties page and select Project Facets.

Migrating projects from previous versions of Nexaweb Studio

WTP 1.0 has changed its web application project directory structure from its previously released version, WTP 0.7, on which Nexaweb Studio 2.1 is based. Nexaweb-enabled web projects created in Nexaweb Studio 2.1 / WTP 0.7 will need to be migrated. Web Tools 1.0 will attempt to migrate a 0.7 project to 1.0, but unfortunately this migration does not work well.

Instead, we recommend creating a new project using Studio 2.2 and copying files from the old project into the new project.  This works best if you create a new workspace then you can give the projects the same name.

Copy files from an old 2.1 Project to a new 2.2 project

1. Create New Dynamic Nexaweb project.  When creating the project, Web Tools will prompt you to choose the directory names.  The defaults are src, src-client, src-shared and WebContent.  If you are migrating an existing project, you can use the names that exist previously. 
2. Copy files from your old project into the new project as follows; if you have changed the directories copy to the appropriate location:
   • <!--[if !supportLists]-->/JavaSource > /src
   • /MCOSource > /src-client (if this directory is not present simply create it in your file system or drag and drop the contents via Studio)
   • /SharedSource > /src-shared (if this directory is not present simply create it in your file system or drag and drop the contents via Studio)
   • /WebContent > /WebContent
3. Configure any custom project-specific property configurations that the old project had which are necessary on the new project
   • right-click on the project in the Navigator view
   • select “Properties” from the context menu
   • configure any properties which should be configured

Possible Web Tools 1.0.1 Issues

The 1.0.1 release of web tools may have problems with the "Auto Publish" feature.  This can cause a publishing failure messages to appear whenever content files are edited when the application server is running.  See below for details.  To prevent this from ever occurring, Automatic Publishing can be disabled.

To resolve publishing failure message but still have Automatic Publishing enabled:

Web Tools Platform Server publishing failure may occur, resulting in an error message, after a Nexaweb Application project WebContent file is changed when the server is running.  This can happen when new projects are created.  Once you receive the error you will need to take the steps below to resolve.  Once resolved it does not occur again.

The resolution for this is to:

1. Stop the server.
2. Open the Navigator view.
3. Delete the "WEB-INF" and "Nexaweb" directories from the ".nexawebContent" directory under the root of the project.
4. Right click on the project and select "Upgrade Nexaweb support" under Nexaweb.

To prevent the error from happening, you can also disable the "Auto Publish" feature of Web Tools.

Steps to turn off "Automatic Publishing":

1. Stop the server.
2. Double click on the server in the "Servers" view.  This opens the Server Overview properties.
3. Expand "Automatic Publishing".
4. Select "Never Publish Automatically".

Project Facets

Nexaweb project facets (Nexaweb, Data Support and Desktop Client Support) cannot be removed from a project once added.

After adding Nexaweb data support to a project, the data subtree will not appear in the Outline until the Visual Editor is closed and reopened.

Other Issues

Plugin (revision 1, supported by Platform 4.1) applications display an error when using the Run command.  They work properly when run in a web browser through the Studio or externally.

After Export war file from Nexaweb Application the resulting war file may not launch the application properly, because the web.xml not being merged correctly with the required Nexaweb web.xml entries. Workaround is to manually add the .nexawebContent\WEB-INF\web.xml content to the war file web.xml file and jar the war contents again.

In the "Generate Data Bound Form Wizard" if you try to choose bind type or widget type by clicking the combobox button, the whole dialog may disappear. Workaround: click mouse again the dialog will reappear.

When dragging a data xml file or MCO java source file in a Navigator view and dropping on a component in Visual Editor, if the mouse is clicked in the Visual Editor before the wizard starts the wizard will not appear.

In some versions of Linux, the context menu for Nexaweb components in Visual Editor will not appear at right-click. Workaround: right-click on Nexaweb components in the Outline instead.

Saving NXML files may be slow in some older machines. Workaround: turn off Validate file against schema checkbox in Preferences/Nexaweb/Visual Editor.

Changing properties to multi-selected Nexaweb components may propagate changes incorrectly.

After renaming a Nexaweb project, the configuration files .nexawebsettings, .nexawebProjectSettings, and .classpath are not updated automatically.

The nexaweb-client.xml editor in Linux has the text of buttons cut off on some resolution settings.

The nexaweb-server.xml configuration editor always saves clustering settings to the file when switching to the source view.

The Properties View may not refresh until an item in Visual Editor is clicked.

Preview in browser may fail if dirtied files that save require a server restart (preview occurs before initialization is complete).

Right-click Nexaweb-->Run Page in Browser may not build URLs for nested pages properly.

The textArea margin attribute affects scrollbar in Visual Editor.

The properties view hides the onCommand event when a menu and menuItem are selected, but both support this event.

Visual Editor does not scroll when page width/height exceeds VE view size.

Directory name in Japanese does not appear correctly in the Studio/Platform installation wizard on Japanese XP OS.

MCO source files are not included in a war file when exporting a project with export source file option checked.