RE: Re[4]: James Configuration Tool

[Robert Cadena <ro...@machine501.com>]

Right, that's why you can register views with the editor, otherwise it's
just an xml editor.  

If you open the jamesconfig.props you'll see these properties:

service_node.James.editor=com.machine501.james.config.nodes.james.JamesNode

If you remove this, then the James Editor on the left will not appear and
instead will be replaced by the default node editor, which just edits XML.
So the immediate goal is to create views (or editors) for the top nodes in
the app. If you notice, for example, the POP3 Server node doesn't show the
subnodes - the editor implemented for that
(com.machine501.james.config.nodes.pop3server.POP3ServerNode) hides the
subnodes, like you suggested.  

In this way mailet authors, for example, can provide editor implementation
for their own mailets, and the editor can be appropriately updated without
some central body having to do this.

Good luck and thanks for trying it out.

/r



-----Original Message-----
From: Miroslav Nachev [mailto:miro@space-comm.com] 
Sent: Thursday, April 17, 2003 12:28 AM
To: James Users List; robert@machine501.com
Subject: Re[4]: James Configuration Tool


   Also, some XML nodes must be restricted to be shown because there is no
sense of them like nodes in the tree. In this case this configuration file
will look like true config file, because the XML Tree will not be shown like
XML Tree - instead will be shown like config file.



---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org