|
|
This section describes known problems and associated workarounds for the Eclipse Plugin.
Limitations:
When two projects uses the same WebNMS installation, the problem will occur. when the first project is closed and trying to create a second project with the same WebNMS installation home as the closed EMS Development project.
Workaround: While creating the new Project with same WebNMS home, keep the first project open. Eclipse will use some linked resources (class folders) from the first project instead of re-creating them. So closing the project will restrict the linked resource from being accessed and will raise the problem <ProjName>_Conf_Link resource is missing and <ProjName>_Link resource is missing.
Limitations:
The below two exceptions occurs when there is a space in the directory path where WebNMS is installed and trying to install a NAR file in WebNMS. This is a JDK bug which occurs in some scenarios where Xalan parsing of XML file is done.
Scenario 1 :
javax.xml.transform.TransformerException: java.io.FileNotFoundException: file:\C:\Program%20Files\AdventNet\WebNMS\NetMonitor\build\uninstall.xml
(The filename, directory name, or volume label syntax is incorrect)
at org.apache.xalan.transformer.TransformerIdentityImpl.createResultContentHandler
(TransformerIdentityImpl.java:260)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform
(TransformerIdentityImpl.java:291)
Scenario 2 :
java.net.MalformedURLException: unknown protocol: c
Workaround : Kindly install the WebNMS in a directory which does not have space characters in its path.
|
|