<questionid="compat-standards"> Doesthemoduleimplementsordefinesanystandards?Isthe implementationexactoritdeviatessomehow? </question>
-->
<answer id="compat-standards">
It loosely (non-normatively) follows the standard syntax for JSP, Java and HTML.
It relies on the Servlet/JSP specification to interpret the syntax of JSP pages.
The module itself does not implement or define any standard.
</answer>
<!-- Question: compat-version
<questionid="compat-version"> Doesyourmoduleproperlycoexistswithearlierandfuture versions?Canyoucorrectlyreadsettings?Willfuture versionsbeabletoreadsettings? <hint> Veryhelpfulforreadingsettingsistostoreversionnumber there,sofutureversionscandecidewhetherhowtoread/convert thesettingsandolderversionscanignorethenewones. </hint> </question>
-->
<answer id="compat-version">
The module persists information about editor colors for JSP syntax elements.
It can read this information stored by previous versions of the IDE, and it is
anticipated that future versions of the module will be able to read the current
format.
</answer>
<!-- Question: dep-jre
<questionid="dep-jre"> WhichversionofJREyouneed(1.2,1.3,1.4,etc.)? <hint> Itisexpectedthatifyourmodulerunson1.xthatitwillrun on1.x+1ifno,statethatplease.Alsodescribeherecaseswhere yourundifferentcodeondifferentversionsofJREandwhy. </hint> </question>
-->
<answer id="dep-jre">
It uses JRE 1.3 or higher.
</answer>
<!-- Question: dep-jrejdk
<questionid="dep-jrejdk"> DoyourequireJDKorisJREenough? </question>
-->
<answer id="dep-jrejdk">
In theory the JRE should be enough, although this was not tested.
</answer>
<!-- Question: dep-nb
<questionid="dep-nb"> WhatotherNetBeansprojectsthisonedependson? <hint> Ifyouwant,describesuchprojectsasimportedAPIusing the<code><apiname="identification"type="importorexport"category="stable"url="whereisthedescription"/></code> </hint> </question>
-->
<answer id="dep-nb">
It uses various kinds of API's:
<ul>
<li>
<api
name="OpenAPIs" type="import"
category="stable"
group="java" url="http://www.netbeans.org/download/dev/javadoc/OpenAPIs/"
/>
NetBeans OpenAPIs
</li>
<li>
<api
name="ExecutionAPIs" type="import"
category="stable"
group="java" url="http://www.netbeans.org/download/dev/javadoc/ExecutionAPI/index.html"
/>
NetBeans Execution APIs - at least I believe this is stable
</li>
<li>
<api
name="web-core" type="import"
category="friend"
group="java" url=""
/>
The <code>web-core</code> module. Notably, the <code>JSPParserAPI</code> class defined
in the <code>web-core</code> friend API is implemented by this module.
</li>
<li>
<api
name="servletapi23" type="import"
category="standard"
group="java" url="http://java.sun.com/products/servlets/"
/>
The Servlet 2.3/JSP 1.2 APIs, packaged as a NetBeans module.
</li>
<li>
<api
name="editor" type="import"
category="friend"
group="java" url="http://editor.netbeans.org/"
/>
The NetBeans editor.
</li>
<li>
<api
name="xml-editor" type="import"
category="friend"
group="java" url="http://xml.netbeans.org/"
/>
The NetBeans XML module, in particular the XML text editor.
</li>
</ul>
The module also relies on the presence of the JSP Parser module,
however it does not direcly use any of its APIs.
</answer>
<questionid="dep-platform"> Onwhichplatformsyourmodulerun?Any?Doesitruninthesame way? <hint> IfyourmoduleisusingJNIordealswithspecialdifferencesof OSeslikefilesystems,etc.pleasedescribeherewhattheyare. </hint> </question>
-->
<answer id="dep-platform"> 100% pure Java. It should run anywhere.
</answer>
<!-- Question: deploy-jar
<questionid="deploy-jar"> DoyoudeployjustmoduleJARfile(s)orsomeotherfiles? <hint> IfyourmoduleconsistjustfromonemoduleJARfile,justconfirmthat. IfitusesmorethanoneJAR,describewheretherearelocated,how theyrefertoeachother. IfitconsistofmoduleJAR(s)andotherfiles,pleasedescribe whatistheirpurpose,whyotherfilesarenecessary.Please makesurethatinstallation/deinstallationleavesthesystem instateasitwasbeforeinstallation. </hint> </question>
-->
<answer id="deploy-jar">
There is the module jar: <code>jsp-syntax.jar</code>, and the parser database,
used by the NetBeans editor: <code>servlet23jsp12.jcb</code> and <code>servlet23jsp12.jcs</code>.
</answer>
<questionid="deploy-shared"> Doyouneedtobeinstalledinsharedlocationoronlyinuserdirectory? <hint> Installationlocationshallnotmatter,ifitdoesexplainwhy. </hint> </question>
-->
<answer id="deploy-shared">
Either way is possible.
</answer>
<questionid="format-clipboard"> Whichprotocolsyourcodereads/insertswhencommunicatingwith clipboard? </question>
-->
<answer id="format-clipboard">
It does not directly communicate with the clipboard - instead it relies
on the underlying Editor module to communicate with clipboard.
</answer>
<!-- Question: format-dnd
<questionid="format-dnd"> Whichprotocolsyourcodeunderstandsduringdrag-n-drop? </question>
-->
<answer id="format-dnd">
Drag and drop is not implemented or used by this module.
</answer>
<!-- Question: format-types
<questionid="format-types"> Whichfileformatsyourcodereadsorwritesondisk? </question>
-->
<answer id="format-types">
Indirectly (through the Editor module) it stores settings of the JSP editor.
It also reads the parser database files (through the same module).
</answer>
<questionid="perf-limit"> Arethereanylimitsinnumber/sizeofelementsyourcode canhandle? </question>
-->
<answer id="perf-limit">
With large JSP files open in the editor performance can detoriate.
</answer>
<!-- Question: perf-mem
<questionid="perf-mem"> Whatistheamountofmemoryyourcomponentoccupies?Estimate witharelactiontothenumberofwindows,etc. </question>
-->
<answer id="perf-mem">
Most of the data structures created by this module are kept by the editor module,
so indirectly the module does occupy some space. This space is proportional to the
size of open JSP files.
</answer>
<questionid="perf-scale"> Whichexternalcriteriainfluencetheperformanceofyour program(sizeoffileineditor,numberoffilesinmenu, insourcedirectory,etc.)andhowwellyourcodescales? Pleaseincludesomeestimates. </question>
-->
<answer id="perf-scale">
Size of file in editor, number of components (e.g. tag libraries) in the web module,
the length of the deployment descriptor.
Performance improvements are possible.
</answer>
<!-- Question: perf-startup
<questionid="perf-startup"> Doesyourmoduleexecutesanythingonstartup? </question>
-->
<answer id="perf-startup">
In case there is a JSP file open in the editor,
it performs lexical analysis of (a part of) this file.
</answer>
<questionid="resources-layer"> Doesyourmoduleprovideownlayer?Doesitcreatesomefilesor foldersonit?Whatitistryingtocommunicatebythatandwithwhich component? <hint> NetBeansallowsautomaticanddeclarativeinstallationofresources bymodulelayers.Moduleregisterfilesintoappropriateplaces andothercomponentsusethatinformationtoperformtheirtask (buildmenu,toolbar,windowlayout,listoftemplates,setof options,etc.). </hint> </question>
-->
<answer id="resources-layer">
Yes. It registers its components with the Editor module using this layer.
</answer>
<!-- <questionid="security-grant"when="final"> Doesyourcodegrantadditionalrightstosomeothercode? <hint>Avoidusingaclassloaderthataddsextra permissionstoloadedcodeunlessreallynecessary. AlsonotethatyourAPIimplementation canalsoexposeunneededpermissionstoenemycodeby callingAccessController.doPrivileged().</hint> </question>
-->
<answer id="security-grant">
<p>
XXX no answer for security-grant
</p>
</answer>
<!-- <questionid="security-policy"when="final"> Doesyourfunctionalityrequiremodificationstothestandardpolicyfile? <hint>Yourcodemightpasscontroltothird-partycodenot comingfromtrusteddomains.Thiscouldbecodedownloadedoverthe networkorcodecomingfromlibrariesthatarenotbundled withNetBeans.Whichpermissionsneedtobegrantedtowhichdomains?</hint> </question>
-->
<answer id="security-policy">
<p>
XXX no answer for security-policy
</p>
</answer>
</api-answers>
Messung V0.5 in Prozent
¤ Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.0.40Bemerkung:
(vorverarbeitet am 2026-09-28)
¤
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.