Version 2.0.16

1. I made comments in my NXML file and now they are gone.
   If there are comments in the source editor for an NXML file, and the document is then altered in the visual editor, the comments will be deleted.

2. I tried to start the Nexaweb server from the Studio and it didn't work.
   The studio can automatically start and configure a Tomcat Application Server. In order to do so, the server must be properly installed and the studio must be configured correctly. See the Installation Guide for more info on how to configure the server.

3. When I start the client, I receive a "NetServiceException: Connection refused: connect" in the client. What is going on?
   Most likely, the server has not been started. Try starting the server and restarting the client. Otherwise, read the next question.

4. I have the server running. When I start the client, I receive a "NetServiceException: Connection refused: connect" in the client. What is going on?
   Most likely, the client has been configured to run through the TCP Tunnel, and the tunnel has not been started. Look in the menu "Run - Nexaweb Application" and check if the "Run through Tunnel" item is selected. If it is, either deselect the flag, or select "Run - TCP Tunnel Viewer", and restart the client.

5. The server is running, but when the client is run a FileNotFoundException is thrown. What is wrong?
   Most likely the Nexaweb application's context has not been added to the server. Access the Nexaweb Server Config page by right clicking on the project and selecting properties. On the left side of the page select Nexaweb Server Config. Now, make sure that the checkbox for Add web application's context to the server's configuration is checked. The server then needs to be restarted, and the application should run correctly.

6. The server is running and the application context is added to the server configuration, but the client still throws a FileNotFoundException. What is wrong?
   If the client communicates with Servlets, the Servlets need to be properly configured in the web.xml file in the www/web-inf directory. When a Servlet is created by the Studio, it is automatically configured. But, if a Servlet is not made with the Nexaweb wizard, or if the web.xml file has been overwritten by an "Add/Update Nexaweb Support" command, the servlet contexts will be lost. In order to reconfigure the names and contexts of the Servlets, browse to the src/server folder in the Nexaweb application. For every Servlet in the folder, right click on it and select properties. Under the Servlet section of the properties, make sure that a name and URL mapping is given. The servlet name can be the name of the class, and the URL mapping is where the servlet can be found. For example, a servlet called ChatServlet in the project ChatApp can be named Chat and the URL mapping could be /Chat. Then, an http request can be sent to http://localhost:8080/ChatApp/Chat.

7. I set a breakpoint and ran the application in debug mode. I know that the program went past my breakpoint, but it didn't stop. What do I do?
   Keep in mind that there are two different programs running when a Nexaweb application starts up. The server and the client are run on two different JVMs. It is possible to run one in debug mode while the other is in run mode. Make sure if the breakpoint is in the server code that the server is run in debug mode. If the breakpoint is in the client code, the client should be run in debug mode. Both can be run in debug mode at the same time, if needed.

8. I followed the pattern of the sample file and am listening for messages from the server, but no messages ever come. I know that they are being sent. How do I receive them?
   There are three ways to receive messages from the server. A persistent connection is always ready to receive a message. This is computationally expensive. Polling has the client query the server for messages every few seconds. The amount of time between polling is configurable. The third way to receive messages is by user event. An example is a refresh button that a user pushes to receive all messages from the server. The style of messaging is configured in the Nexaweb Client Configuration page. A persistent connection can be turned on by clicking the checkbox. If a persistent connection is not turned on, the developer can specify the polling interval.

9. The server is running but when I start the client up, nothing happens. The console shows no launch has happened. What is the deal?
   Most likely, the Nexaweb Platform Home has not been installed on the machine, or the studio has not been configured correctly. To specify the Nexaweb Platform home, choose Window - Preferences - Nexaweb. Under Nexaweb Platform Directory, specify the location of the platform install. The default install location is Program Files\Nexaweb\Nexaweb Platform 4.0.

10. When I try to run my application using the Nexaweb client inside Studio, I get a blank client window and the following error in the client console:
    com.nexaweb.client.netservice.NetServiceException: Server returned HTTP response code: 500 for URL: http://localhost:8080/NewApplication/Nexel
at com.nexaweb.client.netservice.impl.NetServiceImpl.createSession(NetServiceImpl.java:1492)
at com.nexaweb.client.ClientSessionImpl.requestStartPage(ClientSessionImpl.java:653)
at com.nexaweb.client.applet.ClientPanel.start(ClientPanel.java:250)
at com.nexaweb.client.desktop.DesktopClient.(DesktopClient.java:62)
at com.nexaweb.client.desktop.DesktopClient.main(DesktopClient.java:22)
Caused by...
java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/NewApplication/Nexel
The Nexaweb application was added/upgraded Nexaweb support while the Server was running. As a result the web.xml was corrupted. You will have to stop the server and then choose add/upgrade Nexaweb support (project menu or right-click menu) again.

11. When I try to run my application using the browser, I get a blank browser screen (sometimes JavaScript page errors as well). Where is my application screen?
    The Nexaweb application was added/upgraded Nexaweb support while the Server was running. As a result the web.xml was corrupted. You will have to stop the server and then choose add/upgrade Nexaweb support (project menu or right-click menu) again.

12. The client failed to launch because of the following error. The archive: C:/(directory)/lib/nexaweb-client-api.jar which is referenced by the classpath, does not exist. Why?
    The Nexaweb platform home directory is configured incorrectly in the Studio. See question 9.

13. I am getting an error of the form: the schema file "PATH/directives.xsd" failed to open, (may also happen with other schema files like mco.xsd, etc.) Why?
    The Nexaweb Platform 4.0 installation directory setting is configured incorrectly in Studio. Go to Window/Preferences and then choose Nexaweb and select the correct location for the Nexaweb Platform directory entry.

14. I created an UI file that it is not found by the server (http error 404) when I run my application. What is the problem?
    UI files must be located in the www subdirectory under the Project main folder in order for the server to find them.

15. I have set an image attribute or defined stylesheet styles and attributes that don't seem to be applied in the Visual Editor. Why?
    The server must be running for the images and/or stylesheet styles and attributes to be applied.

16. When I click the Preview tab in the Visual Editor it shows as blank. Why?
    The server must be running for the Preview mode to work.