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 では、データドリブンアプリケーションを使用しやすいインターフェイスにまとめることができます。ユーザーは、アプリケーションでアクセス可能なデータを参照できます。
- 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.
- には、コンポーネントとデータ (テーブルとデータ) を接続するためのウィザードなど、データドリブンアプリケーションを簡単に作成できるウィザードも用意されています。
- 新しいデータパースペクティブの追加、Outline でのデータのサポート、データのドラッグ & ドロップのサポート、および新しいウィザードを介して、複数のデータソースを管理できます。
新しい Nexaweb プラグイン v2.0 のサポート
- Studio 2.2 には、再配布可能な Nexaweb プラグインモジュール (jar) のビルドおよび提供に必要なすべての機能を実現する Nexaweb プラグイン v2.0 プロジェクトを作成および管理する機能が用意されています。
- Studio 2.2 プラグインでは、新しい Nexaweb プラグインパースペクティブ、Plugin Explorer View、Plugin Configuration Editor がサポートされています。
- Studio 2.2 で作成した Nexaweb プラグインは、プラグインを使用する Studio 内の Nexaweb プロジェクトに自動的に公開できます。
Desktop Client (Platform 4.x の別ライセンスコンポーネント) のサポート
- Studio 2.2 では、Nexaweb の Desktop Client アプリケーションの作成、実行、デバッグ、およびパッケージ化がサポートされています。
- 新しい Studio ツールバーを使用して、Studio 内から Desktop Client 内の Nexaweb ベースのアプリケーションをデバッグおよび実行します。
- Desktop Client コンフィギュレーションファイルの新しいエディタ。
新しい Web Tools Platform 1.0.x
...
- Studio 2.2 supports では、プロジェクトファセットや新しい動的 Web プロジェクト構造を含む 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. リリースノート」を参照してください。
- Web Tools のサポートに関する重要な既知の問題があります。
...
...
以前のバージョンの Nexaweb Studio プロジェクトの移行
WTP 1.0
...
...
...
...
...
...
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
...
...
- 新しい動的 Nexaweb プロジェクトを作成します。プロジェクトの作成時に、ディレクトリ名の選択を求められます。デフォルトは src、src-client、src-shared、および WebContent です。既存のプロジェクトを移行する場合は、すでに存在する名前を使用できます。
- 古いプロジェクトのファイルを、次のように新しいプロジェクトにコピーします。ディレクトリを変更した場合は、適切な場所にコピーします。
- <!--[if !supportLists]-->/JavaSource
...
- → /src
- /MCOSource
...
- → /src-client (
...
- このディレクトリが存在しない場合は、ファイルシステムに作成するか、Studio でコンテンツをドラッグ & ドロップします)
- /SharedSource
...
- → /src-shared (
...
- このディレクトリが存在しない場合は、ファイルシステムに作成するか、Studio でコンテンツをドラッグ & ドロップします)
- /WebContent
...
Changes
Studio Info Builder Format Error Reporting
The Studio info builder will now report XML formatting issues when files are being loaded or processed. This may manifest in errors on files that did not report errors in previous versions of Studio - this does not mean that these files worked in previous versions of Studio, simply that the errors were not reported when the files were loaded.
For details on errors open the "Problems" view in Eclipse.
.deployables Directory
Web Tools no longer deploys files to the .deployables directory. These are now deployed to a hidden .metadata directory under the workspace path. This is configurable via the server properties through the "Servers" view in Eclipse.
Preview
Preview view has been removed from Studio.
Known Issues
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:
- Stop the server.
- Open the Navigator view.
- Delete the "WEB-INF" and "Nexaweb" directories from the ".nexawebContent" directory under the root of the project.
- 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":
- Stop the server.
- Double click on the server in the "Servers" view. This opens the Server Overview properties.
- Expand "Automatic Publishing".
- 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.
...
- → /WebContent
...
- right-click on the project in the Navigator view
- select “Properties” from the context menu
- configure any properties which should be configured
- 新しいプロジェクトで必要となる、古いプロジェクトで指定されていたすべてのカスタムプロジェクト固有のプロパティ コンフィギュレーションを構成します。
- [Navigator] ビューで、プロジェクトを右クリックします。
- コンテキストメニューから [Properties] を選択します。
- 必要なプロパティを構成します。