harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Harmony Wiki] Update of "PolicytoolDev" by AndrasBelicza
Date Mon, 18 Aug 2008 11:41:05 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Harmony Wiki" for change notification.

The following page has been changed by AndrasBelicza:
http://wiki.apache.org/harmony/PolicytoolDev

The comment on the change is:
Added descriptions for new classes and features.

------------------------------------------------------------------------------
  
  = The model package =
  
- The base class of all entries is the PolicyEntry class. Defines 2 abstract methods to get
and set the string representation of a policy entry.
+ The base class of all entries is the PolicyEntry class. Defines an abstract method to get
set the string representation of a policy entry.
- There are basically 2 entry types:
+ There are basically 2 entry types (which are 3):
   *GrantEntry: - this is used to define access and grant to various system resources.
-  *KeystoreEntry and KeystorePasswordURLEntry: these 2 define the location and other parameters
to the keystore
+  *KeystoreEntry and KeystorePasswordURLEntry: these 2 define the location and other parameters
of the keystore
  
  The grant entries might include one or several principals and permissions which are represented
with the respective classes (Principal and Permission).
  
@@ -39, +39 @@

   *PrincipalEntryFormDialog: to view/edit principals
   *PermissionEntryFormDialog: to view/edit permissions
  
- Policytool contains several entities which has to be listed, available for editing and removing,
and provide an interface for adding new entities. Such entities are grant entries, principals,
permissions. The generic ListAndEdit class is responsible to provide such an interface which
is used parameterized when used for the listed entites.
+ Policytool contains several entities which has to be listed, has to be available for editing
and removing, and provide an interface for adding new entities. Such entities are grant entries,
principals, permissions. The generic ListAndEditPanel class is responsible to provide such
an interface which is used parameterized when used for the listed entities.
  
- The LAEFormDialog is a specialized FormDialog which is intended to handle the data view/edit
interface for entities available through a ListAndEdit component. The GrantEntryFormDialog,
PrincipalEntryFormDialog and PermissionEntryFormDialog classes in fact are subclasses of the
LAEFormDialog class.
+ The LAEFormDialog is a specialized FormDialog which is intended to handle the data view/edit
interface for entities available through a ListAndEditPanel component. The GrantEntryFormDialog,
PrincipalEntryFormDialog and PermissionEntryFormDialog classes in fact are subclasses of the
LAEFormDialog class.
  
+ The WarningLogDialog class is a dialog class with a text area to store and display previous
warning and error messages.
+ New feature (compared to Sun's policytool): the warning log dialog is non-modal which is
a lot more useful here because we support direct editing, and switching between the editor
panels can generate errors/warnings frequently (not just when opening a new file or validating
form values). The warning log can be open while we edit the policy text in any editor. If
we use the "View Warnign Log" menu while it's visible, it will be centered again. 
  
  = The control package =
  
- The Controller class drives the GUI and connets it to the model. It is the handler of the
menu items, and it is responsible to passing over the edited policy text in case of editor
panel switching. Handles the unsaved changes before certain operations (exit, open a new file,
load a file).
+ The Controller class drives the GUI and connects it to the model. It is the handler of the
menu items, and it is responsible to passing over the edited policy text in case of editor
panel switching. Handles the unsaved changes before certain operations (exit, open a new file,
load a file).
  
- The PolicyFileHandler class is responsible to gain the policy text out of a policy file
and to save a policy text to a policy file knowing about the mandatory UTF-8 encoding.
+ The PolicyFileHandler class is responsible to gain the policy text out of a policy file
and to save a policy text to a policy file being aware of the mandatory UTF-8 encoding.
  
+ The PolicyTextParser class is responsible to parse a policy text, and return an equivalent
list of policy entries from it. If the policy text is invalid, an InvalidPolicyTextException
will be thrown with a proper error message.
+ Sun's policytool takes out all the comments from an opened policy file. It's a new feature
that this parser parses and remembers comments between the entries in the policy text.
  
  = JIRA issues related to Policytool =
  

Mime
View raw message