NetBeans internally uses the concept of a virtual filesystem. This module provide APIs for accessing such virtual files as well as some support classes to make writing of custom vitual filesystems easier.Question (arch-usecases): Describe the main use cases of the new API. Who will use it under what circumstances? What kind of code would typically need to be written to use the module? Answer:
For general overview of the filesystem concepts, related topics, together with code samples, see chapter 3, of NetBeans Platform for Beginners by Jason Wexbridge and Walter Nyland. Many of the usecases are described at the overall documentation, in a way how to register a mime type. Some of the additional usecases are covered here.
See documentation about dynamically changing the system filesystem.Question (arch-time): What are the time estimates of the work? Answer:
XXX no answer for arch-timeQuestion (arch-quality): How will the quality of your code be tested and how are future regressions going to be prevented? Answer:
XXX no answer for arch-qualityQuestion (arch-where): Where one can find sources for your module? Answer:
The sources for the module are in the NetBeans Mercurial repositories.
The default answer to this question is:
These modules are required in project.xml:
XXX no answer for deploy-dependencies
XXX no answer for compat-deprecation
java.io.Filedirectly? Answer: Yes, naturally. 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. Question (resources-preferences): Does your module uses preferences via Preferences API? Does your module use NbPreferences or or regular JDK Preferences ? Does it read, write or both ? Does it share preferences with other modules ? If so, then why ? Answer:
FileChooserBuilder uses NbPreferences as the backing storage for per-key recently used directories.
org.openide.util.Lookupor any similar technology to find any components to communicate with? Which ones? Answer: The following services are looked up:
URLStreamHandlerFactoryimplementations for nbfs: and memory: protocols are registered as named services. Question (lookup-remove): Do you remove entries of other modules from lookup? Answer: No.
System.getProperty) property? On a similar note, is there something interesting that you pass to
java.util.logging.Logger? Or do you observe what others log? Answer:
true, better diagnostic information will be available as to when file input or
output streams were opened that prevent a file from being deleted because they were not closed.
This information comes at a performance cost, however.
See documentation of
The MultiFileSystem defines some pseudo attributes on files and folders, which provide rollback features. Please see MultiFileSystem class javadoc for more information.Question (exec-ant-tasks): Do you define or register any ant tasks that other can use? Answer:
XXX no answer for exec-ant-tasksQuestion (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: methodvalue-newvalue - When special form of
setAttributeis supported by the filesystem, the
getAttributecan behave like XMLFileSystem's
newvalueattributes: raw-value - It is possible to prefix call to FileObject.
raw:prefix to evaluate the attribute without instantiating it (e.g. get Method or Class values from
newvalueattributes. This API is not intended for public use at present and can change in future. Question (exec-privateaccess): Are you aware of any other parts of the system calling some of your methods by reflection? Answer: FileObjectMoveLookup -
masterfsmodule is using a reflection to re-associate the lookup after a move operation. 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 external process. Question (exec-introspection): Does your module use any kind of runtime type information (
instanceof, work with
java.lang.Class, etc.)? Answer: No answer Question (exec-threading): What threading models, if any, does your module adhere to? How the project behaves with respect to threading? Answer:
XXX no answer for exec-threadingQuestion (security-policy): Does your functionality require modifications to the standard policy file? Answer:
XXX no answer for security-policyQuestion (security-grant): Does your code grant additional rights to some other code? Answer:
XXX no answer for security-grant
java.awt.datatransfer.Transferable? Answer: None.
XXX no answer for perf-spi
Built on August 9 2022. | Copyright © 2017-2022 Apache Software Foundation. All Rights Reserved.