Xeena

• DTD inside XML files
• Entity references (note that character references are allowed in attribute values and generated automatically by the editor).

Invalid nodes are underlined in red immediately after opening a file and are checked constantly during editing. Selecting the invalid node and activating Validate from the tool bar or menu prints the error messages associated with that node in the message area.

1. Write a Java class that implements the XMLImporter interface. Writing this class consists of three main steps:
1. Implement the getIcon, getName, and getToolTip methods for returning descriptions of your importer, which will be used by the Xeena environment.
2. Implement the init methods to initialize your importer (using information from the XMLEditorContext and/or the data string you may have specified in the configuration file).
3. Implement the importDocument method to do the actual work of letting the user select an import source and import the data into the document. For a detailed sample, please examine the BMLImporter.java sample supplied in the src directory.
2. Hook the class you wrote into the Xeena profile for your DTD as follows: When configuring Xeena for your DTD, insert a new importer element (as a child of the existing importers element), specify its name, and specify the full name of the class you wrote as the value of the class attribute.

1. Write a Java class that implements the XMLExporter interface. Writing this class consists of three main steps:
1. Implement the getIcon, getName, and getToolTip methods to return descriptions of your exporter, which will be used by the Xeena environment.
2. Implement the init methods to initialize your exporter (using information from the XMLEditorContext and/or the data string you may have specified in the configuration file.
3. Implement the exportDocument method to do the actual work of letting the user select an export target and export the data from the document. For a detailed sample, please examine the BMLExporter.java sample supplied in the src directory.
2. Hook the class you wrote into the Xeena profile for your DTD as follows: When configuring Xeena for your DTD, insert a new exporter element (as a child of the existing exporters element), specify its name, and specify the full name of the class you wrote as the value of the class attribute.

1. Write a Java class that implements the ToolHandler interface. Writing this class consists of four main steps:
1. Implement the getIcon, getName, and getToolTip methods to return descriptions of your tool, which will be used by the Xeena environment.
2. Implement the init methods to initialize your tool (using information from the XMLEditorContext and/or the data string you may have specified in the configuration file.
3. Implement the canHandle to give an indication whether the selected documented can be handled by the tool.
4. Implement the handle method to do the actual work of invoking the tool on the selected document. For a detailed sample, please examine the BMLPlayer.java sample supplied in the src directory.
5. Hook the class you wrote into the Xeena profile for your DTD as follows: When configuring Xeena for your DTD, insert a new tool element (as a child of the existing tools element), specify its name, and specify the full name of the class you wrote as the value of the class attribute.

Alternatives that you can use:

com.sun.java.swing.plaf.windows.WindowsLookAndFeel
com.sun.java.swing.plaf.mac.MacLookAndFeel
com.sun.java.swing.plaf.motif.MotifLookAndFeel

If you remove the option altogether, the default Look and Feel will be used.

-DproxySet=true -DproxyHost=proxy.server.name -DproxyPort=port

where proxy.server.name is the name of your proxy server, and where port is the port number.