<answer id="arch-what">
The HTTP Monitor is a tool for debugging J2EE web-tier
applications.
</answer>
<answer id="dep-nb">
The HTTP Monitor client (the IDE module) requires the OpenIDE
and schema2beans.
</answer> <!-- <questionid="dep-non-nb"> WhatotherprojectsoutsideNetBeansdoesthisonedependon? <hint> Somenon-NetBeansprojectsarepackagedasNetBeansmodules (see<ahref="http://libs.netbeans.org">libraries</a>)and itispreferedtousethisapproachwhenmoremodulesmay dependonsuchthird-partylibrary. </hint> </question>
-->
<answer id="dep-non-nb">
The HTTP Monitor client (the IDE module) requires the HTTP
Servlet APIs version2.0 or higher. The HTTP Monitor
server side component requires a J2EE servlet container
implementing Servlet 2.3 or higher.
</answer>
<!-- <questionid="dep-platform"> Onwhichplatformsdoesyourmodulerun?Doesitruninthesame wayoneach? <hint> IfyourmoduleisusingJNIordealswithspecialdifferencesof OSeslikefilesystems,etc.pleasedescribeherewhattheyare. </hint> </question>
-->
<answer id="dep-platform">
The HTTP Monitor server side component contains some extra
functionality for Tomcat 4.0 or higher. It is possible for
other Server vendors to provide the same level of functionality
on their servers.
</answer>
<!-- <questionid="deploy-jar"> DoyoudeployjustmoduleJARfile(s)orotherfilesaswell? <hint> IfyourmoduleconsistsofjustonemoduleJARfile,justconfirmthat. IfitusesmorethanoneJAR,describewheretheyarelocated,how theyrefertoeachother. IfitconsistofmoduleJAR(s)andotherfiles,pleasedescribe whatistheirpurpose,whyotherfilesarenecessary.Please makesurethatinstallation/deinstallationleavesthesystem instateasitwasbeforeinstallation. </hint> </question>
-->
<answer id="deploy-jar">
The HTTP Monitor client (the IDE module) consists of
httpmonitor.jar only. The server side component, which
is deployed on a Servlet container, consists of
monitor.jar which resides in modules/ext. It needs to
be made available as a shared library on the Servlet
engine, together with schema2beans.jar. There is also
an optional jar file, monitor-valve.jar, which
provides some extra functionality for the Tomcat
Servlet container.
</answer> <!-- <questionid="deploy-nbm"> CanyoudeployanNBMviatheUpdateCenter? <hint> Ifnotwhy? </hint> </question>
-->
<answer id="deploy-nbm">
Yes.
</answer>
<!-- <questionid="deploy-shared"> Doyouneedtobeinstalledinthesharedlocationonly,orintheuserdirectoryonly, orcanyourmodulebeinstalledanywhere? <hint> Installationlocationshallnotmatter,ifitdoesexplainwhy. Consideralsowhether<code>InstalledFileLocator</code>canhelp. </hint> </question>
-->
<answer id="deploy-shared">
This module can be installed anywhere.
</answer> <!-- <questionid="deploy-packages"> Arepackagesofyourmodulemadeinaccessiblebynotdeclaringthem public? <hint> NetBeansmodulesystemallowsrestrictionofaccessrightsto publicclassesofyourmodulefromothermodules.Thisprevents unwanteddependenciesofothersonyourcodeandshouldbeused wheneverpossible(<ahref="http://www.netbeans.org/download/apis/org/openide/doc-files/upgrade.html#3.4-public-packages"> publicpackages </a>). </hint> </question>
-->
<answer id="deploy-packages">
No but they should be...
</answer>
<answer id="compat-version">
Yes, as long as the client-side component and the server-side
component are from the same version. Data files are portable.
</answer>
<!-- <questionid="resources-file"> Doesyourmoduleuse<code>java.io.File</code>directly? <hint> NetBeansprovidealogicalwrapperoverplainfilescalled <code>org.openide.filesystems.FileObject</code>that providesuniformaccesstosuchresourcesandistheprefered waythatshouldbeused.Butofcoursetherecanbesituationswhen thisisnotsuitable. </hint> </question>
-->
<answer id="resources-file">
No
</answer> <!-- <questionid="resources-layer"> Doesyourmoduleprovideownlayer?Doesitcreateanyfilesor foldersinit?Whatitistryingtocommunicatebythatandwithwhich components? <hint> NetBeansallowsautomaticanddeclarativeinstallationofresources bymodulelayers.Moduleregisterfilesintoappropriateplaces andothercomponentsusethatinformationtoperformtheirtask (buildmenu,toolbar,windowlayout,listoftemplates,setof options,etc.). </hint> </question>
-->
<answer id="resources-layer">
Yes. It installs one action in two menus (View and Debug) and
on the Debugging toolbar.
</answer> <!-- <questionid="resources-read"> Doesyourmodulereadanyresourcesfromlayers?Forwhatpurpose? <hint> Asthisissomekindofintermoduledependency,itisakindofAPI. Pleasedescribeitandclasifyaccordingto <ahref="http://openide.netbeans.org/tutorial/api-design.html#categories"> commonstabilitycategories</a>. </hint> </question>
-->
<answer id="resources-read">
No
</answer>
<answer id="exec-reflection">
The extra functionality avaiable for the Tomcat in the
server side component currently uses reflection.
The server side component was originally designed to
run on Tomcat only, and used Tomcat specific
interfaces to achieve its task. With the advent of
Filters in version2.3 of the Servlet specification,
it was possible to provide most, but not all, of the
functionality using the Servlet APIs. In order not to
lose functionality, a couple of pieces were
reimplemented using Tomcat specific interfaces. These
are not required for the tool to operate. In Servlet 2.4, practically all the Monitor functionality can be
provided through the Servlet APIs, and we will
probably remove the one remaining piece that requires
cooperation by the server.
</answer>
<answer id="format-types">
The HTTP Monitor client and server side components use HTTP to
communicate with one another. They require an IDE internal HTTP
server for this (the server side relies on the Servlet
container it is running on).
Data is sent as XML, as defined by monitor.dtd in the source
space.
</answer>
<!-- <questionid="perf-startup"> Doesyourmodulerunanycodeonstartup? </question>
-->
<answer id="perf-startup">
No
</answer>
<!-- <questionid="perf-exit"> Doesyourmodulerunanycodeonexit? </question>
-->
<answer id="perf-exit">
It deletes data files created during its operation that were
not explicitly saved by the user.
</answer>
<!-- <questionid="perf-limit"> Arethereanyhardcodedorpracticallimitsinthenumberorsizeof elementsyourcodecanhandle? </question>
-->
<answer id="perf-limit">
No
</answer>
<!-- multithreading -->
<!-- <questionid="perf-mem"> Howmuchmemorydoesyourcomponentconsume?Estimate witharelationtothenumberofwindows,etc. </question>
-->
<answer id="perf-mem">
TBD.
</answer> <!-- <questionid="perf-wakeup"> Doesanypieceofyourcodewakeupperiodicallyanddosomething evenwhenthesystemisotherwiseidle(nouserinteraction)? </question>
-->
<answer id="perf-wakeup">
No
</answer> <!-- <questionid="perf-progress"> Doesyourmoduleexecuteanylong-runningtasks? <hint>Typicallytheyaretaskslikeconnectingover network,computinghugeamountofdata,compilation. Suchcommunicationshouldbedoneasynchronously(forexample using<code>RequestProcessor</code>),definitivelyitshould notblockAWTthread. </hint> </question>
-->
<answer id="perf-progress">
Yes, when data is sent between the client and the
server. These tasks are carried out in separate threads.
</answer>
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.