Product Description
Getting Started
Installation Instructions
What's New

Studio User Area

Studio Users Guide
Known Issues
Helpful Tips
Trouble Shooting
Studio Update Site
License
Copyright
Nexaweb Studio 2.0.x - Known Issues


Check the list below to find know issues with Nexaweb Studio.


Version 2.0.16


CONFIGURATION:
  • Tomcat configuration: Studio requires Tomcat to be installed and configured in Preferences/Nexaweb/Tomcat including home directory location, configuration file location, Tomcat version and Tomcat JRE. Eclipse by default adds the installed JREs in the Preferences/Java/Installed JREs section. However Tomcat requires a full JDK installed in order to compile the jsp pages. The JDK must be added to Preferences/Java/Installed JREs and then it must be selected as the default Tomcat JRE in Preferences/Nexaweb/Tomcat/Tomcat JRE.
GENERAL ISSUES:
  • "Make Start Page" in Studio has no effect on run in browser
  • Creating Nexaweb application in studio after server start may fail to preview until server is restarted
  • ALT+F doesn't work in Nexaweb Perspectives while a .java file is active
  • Customize palette doesn't work in Eclipse 31RC3
  • Drag and drop into Outline or Visual Editor after deleting the root element does not work
  • Changing a panel from <boxLayout> to <gridLayout> does not update Visual Editor
  • Chart color gets confused when series document order changes
  • Clicking on a chart's legend in Visual Editor does not select the legend
  • Dynamic changes to <borderLayout>-managed panel revert visually on drag events
  • In Visual Editor, clicking a <window> title bar does not cause the <window> element in the Outline view to gain focus
  • Layout Wizard does not have scrollbars
  • "onCreate" events assigned an MCO event handler causes MCO not found error to be thrown in Preview mode
  • Dragging a <comboBox> in the Visual Editor leaves the <listBox> apparently open in the original location until the user clicks again in the Visual Editor
  • At times Palette is not available immediately after switching into the Nexaweb Visual Editor Perspective.
  • Preview doesn't pick up gradients defined in the stylesheet (even with the server running).
  • If Firefox is the default browser, Preview in Browser will only work once. For a different page or app to be previewed, Firefox will need to be completely shut down.
  • Properties view doesn't refresh immediately when an undo occurs
  • Replace <cell> in outline mode doesn't cause the Visual Editor rendering to update
  • Restart button in studio designer window doesn't work after server restart. A workaround is to close and reopen the UI file
  • At times interactive resize/reposition of containers(window, dialog) embedded in rootPane in the Visual Editor does not work, i.e. x,y, height or width attributes are not updated correctly. (source edit works)
  • Some icons in the Nexaweb Outline will not show when a NXML file is open when Studio starts up. Closing and reopening the UI file will make the missing icons appear
  • Stylesheet editor buttons may go off screen as the editor gets horizontally constrained
  • Visual Editor removes CDATA tags entered in the source editor
  • New UI Stylesheet Wizard is not updating client configuration file nexaweb-client.xml
  • After Studio install under Linux, the Choose Nexaweb Platform directory dialog will produce an error and fail. Choosing Window/Preferences, Nexaweb, and setting Nexaweb Platform directory will solve the problem.
© Copyright 2005, Nexaweb Technologies, Inc. One Charles Park Cambridge, MA 02142 Phone: (617) 577-8100