Helpful Tip
Using Studio 2.4 with Platform 4.5
Studio 2.4 can be used for NXML development using Platform 4.5. To enable, rename "java-integrated.zip" to "nexaweb-platform.zip" under \dist directory of your Platform 4.5 installation
Studio 2.4 provides an integrated installer. The installer optionally includes:
- Eclipse 3.1.2 and WTP 1.0.1
- oXygen XML editor 7.0.0
- Apache Tomcat 5.5.9
- Subversion Eclipse Plugins 1.0.0
New Features
Enhanced Data Visualization
Data views have been refactored to make them easier to use and the ability to drill into remote data sources has been added. Once a data source is created, right click and choose "Connect" to open and explore the remote data. Works for XML and Java Objects.
Enhanced UI Templates
The New From Template Wizard (File - New - Other - Nexaweb - New from Template) has been reorganized, and many new templates have been added. Note: The CardLayout template's logic will only work in 4.2.x projects because it relies on a parameterized macro. The same effect can be achieved using an MCO in 4.1, but an MCO is outside of the scope of a UI template.
Event Wizard Refactoring
The Event Wizard has been refactored for improved usability.
Macro Wizards
Macro wizards have been added to aid with creating macros within Nexaweb UI markup.
Usability Refactoring
Wizards have been streamlined, user interface simplified and consistency improved.
Defects Resolved
| Id | Description |
| 6005 | a memory leak proportional to file size occurs when opening and closing nxml files in Visual Editor |
| 5941 | Event wizard doesn't auto populate with the event when started from properties view |
| 5934 | Backwards compatibility properties are missing from client configuration editor in the Studio |
| 5920 | Nexaweb platform directory requires an end slash in the new project wizard |
| 5886 | Studio 2.3 windows XP installation provides no "uninstall" option under Program Files |
| 5883 | exception thrown when removing a project from a server |
| 5880 | Unable to add dataFramework to project created with 4.1.4, then upgraded to 4.2.2 |
| 5866 | Welcome Perspective does not show the correct SVN URL for Nexaweb samples and demos |
| 5766 | Two backwards compatibility properties: <ensure-pre-4-...> and <use-root-...> are missing from nexaweb-client.xml |
| 5733 | MCO wizard needs to update the instruction due to the structure change in 4.2 |
| 5732 | New MCO Wizard: Method name is filled with component name when selecting a component. |
| 5731 | New MCO Wizard: Finish Button doesn't work when Method name is manually typed. |
| 5729 | Unable to save an nxml file after changing component order in outline view |
| 5719 | Finish Button in Event Wizard should be enabled only when event handlers are specified. |
| 5693 | .plugin-lib directory does not get created during a Clean Build if it’s missing after a project import |
| 5669 | Data bind component attribute wizard: Can't replace old attribute value with a value suggested by Content Assist |
| 5667 | Studio's Plugin Explorer View doesn't show projects |
| 5656 | Unable to remove the data support facet from a project |
| 5655 | After adding data support, data doesn't appear in the Outline view until index.nxml is closed and reopened |
| 4937 | 712-1753559 - Studio 2.1 multi-select property change "over changes" - applies changes to additional components |
| 4888 | Text gets cut off at the bottom in the About Nexaweb dialog from Help --> About Eclipse SDK --> Nexaweb |
| 4791 | right-click nxml files in Navigator View; Run Page in Browser does not build correct URLs for nested files |
| 2657 | replace a table cell with another cell or component in outline mode doesn't cause Visual Editor to refresh |
Special Notes
5934
Backwards compatibility flags are missing from client configuration editor in the Studio
The following backwards compatibility flags have been added to the client configuration editor. For more information, see Nexaweb Platform 4.2.x backward compatibility documentation at Backwards Compatibility
<ensure-pre-4-dot-2-mco-string-argument-compatibility>
<ensure-pre-4-dot-2-macro-compatibility>
<ensure-pre-4-dot-2-resolution-syntax-compatibility>
<use-root-element-as-context-instead-of-document>
5766
Two backwards compatibility properties are missing from nexaweb-client.xml in newly created Dynamic Nexaweb Projects.
The two properties are: <ensure-pre-4-dot-2-resolution-syntax-compatability> and <use-root-element-as-context-instead-of-document>. The nexaweb-client.xml file that appears in a new Dynamic Web Project under WebContent/WEB-INF now contains these two backward compatibility properties.
Known Issues
| Id | Description |
| 6197 | Creating a project with IME characters for a name generates two warnings |
| 6196 | Entering IME text in the properties view doesn't immediately update VE |
| 6195 | Right click on a label to modify text, then enter IME text doesn't update the source nxml |
| 6194 | With IME characters values entered in the properties view will be copied to other fields in the view when clicked away from the field being entered in |
| 6193 | Use of Japanese IME text doesn't scroll correctly in properties view |
| 6084 | DataView: When I refresh a dataSource thats really just empty I get a NPE |
| 5775 | All-in-one Studio installer not testing for valid eclipse install when some variant of 'studio only' install is selected |
| 5708 | upgrade nexaweb support should close all open editors in the project before upgrading |
| 5700 | can't unpublish WEB-INF/client/classes - directory stays in the temp space after the app has been removed from the server |
| 5675 | src-client folder does not exist in eclipse workspace when it's empty |
| 5610 | Studio initial dynamic web app is created with an error right out of the gate because the Java Facet version does not match the Java Compiler version |
| 5431 | information builder throws XML Parse Error when it parses nested macros and/or CDATA |
| 5312 | Export war file from studio - can't launch app because the web.xml in the resulting WAR file does not contain any of the Nexaweb Servlets, Listeners, or Filters |
| 4745 | properties View does not refresh until an item in Visual Editor is clicked |
| 4564 | Visual Editor does not scroll when page width/height exceeds VE view size |
| 3744 | holding down CTRL+Z, CTRL+Y, CTRL+V cycles through undos/redos/pastes too fast |
| 2235 | Visual Editor removes CDATA tags and comments when saving or switching back and forth between VE and Source tabs |
Special Notes
5312
Export war file from studio - can't launch app because the web.xml in the resulting WAR file does not contain any of the Nexaweb Servlets, Listeners, or Filters
Some WTP Server drivers rely on the export as war functionality (e.g. JBoss 4). In this scenario, you won't be able to use that Server runtime within Studio for development. A properly built WAR file can still be deployed though.
Workaround: Running Eclipse using BEA's JRocket JRE appears to correct this problem
Workaround: Use command line tools (Ant) to build your project and manually deploy it.