|
java.io.File directly?
Answer:
Yes, for showing absolute filename path in the tooltip.
Question (resources-layer):
Does your module provide own layer? Does it create any files or
folders in it? What it is trying to communicate by that and with which
components?
Answer:
No.
Question (resources-read):
Does your module read any resources from layers? For what purpose?
Answer:
No.
Question (resources-mask):
Does your module mask/hide/override any resources provided by other modules in
their layers?
Answer:
No.
org.openide.util.Lookup
or any similar technology to find any components to communicate with? Which ones?
Answer:
Yes, it looks for IndentEngine service type class. This class is defined in
this module. The first one indentation engine found for the given MIME is returned.
Others are ignored.
Question (lookup-register):
Do you register anything into lookup for other code to find?
Answer:
No.
Question (lookup-remove):
Do you remove entries of other modules from lookup?
Answer:
No.
System.getProperty) property?
Answer:
No.
Question (exec-component):
Is execution of your code influenced by any (string) property
of any of your components?
Answer:
The module can be influencend by this property:
indentEngine
-
Property hold instance of IndentEngine
and this indentation engine is used instead of system one.
It set these Swing properties:
javax.swing.text.Document.StreamDescriptionProperty
-
Property hold instance of DataObject
from which the document was created. This property can be used by the modules and is part of the Editor API.
javax.swing.text.Document.TitleProperty
-
Property hold instance of String with name of the file being edited.
This property can be used by the modules and is part of the Editor API.
Question (exec-classloader):
Does your code create its own class loader(s)?
Answer:
No.
Question (exec-reflection):
Does your code use Java Reflection to execute other code?
Answer:
Yes, it calls protected method MultiDataObject.getCookieSet().
The class which calls this is deprecated, but it is still in use by clients.
Question (exec-privateaccess):
Are you aware of any other parts of the system calling some of
your methods by reflection?
Answer:
No.
Question (exec-process):
Do you execute an external process from your module? How do you ensure
that the result is the same on different platforms? Do you parse output?
Do you depend on result code?
Answer:
No.
Question (exec-introspection):
Does your module use any kind of runtime type information (instanceof,
work with java.lang.Class, etc.)?
Answer:
The Editor module operate with plain Swing Document in
its APIs and checks whether the document does not implement some of the Netbeans extensions defined in
NbDocument.
It also tries to retype CloneableTopComponent.Ref.getComponents()
to its CloneableEditor. If some document does not implement
StyledDocument,
it is wrapped into FilterDocument which implements limited StyledDocument functionality.
Question (exec-threading):
What threading models, if any, does your module adhere to?
WARNING: Question with id="exec-threading" has not been answered!
Question (security-policy):
Does your functionality require modifications to the standard policy file?
WARNING: Question with id="security-policy" has not been answered!
Question (security-grant):
Does your code grant additional rights to some other code?
WARNING: Question with id="security-grant" has not been answered!java.awt.datatransfer.Transferable?
Answer:
None.
Built on December 9 2004. | Portions Copyright 1997-2003 Sun Microsystems, Inc. All rights reserved.