ChangeLogTag:Thu Feb 14 11:25:39 2002 Nanbor Wang <nanbor@cs.wustl.edu>

2 files changed, 21 insertions, 8 deletions

diff --git a/ACEXML/docs/bugs.txt b/ACEXML/docs/bugs.txt
index 11baef88416..804a8f7d9fd 100644
--- a/ACEXML/docs/bugs.txt
+++ b/ACEXML/docs/bugs.txt
@@ -2,11 +2,14 @@
 @page acexml_bugs ACEXML Known Bugs
 
 <ul>
-  <li>ACEXML currently do not validate an XML files.
+  <li>ACEXML currently do not validate an XML files.  The validator
+      hooks have not fully integrated into the parser yet.
 
-  <li>Exception handling is not implemented.  Maybe we should not try
-      to use the environment variables/exceptions scheme again.
-      Considering changing to a simpler error reporting method.
+  <li>Exception handling is not implemented.  Currently, we use a
+      reference of ACEXML::Env, similar to CORBA::Environment, to
+      return the status of the execution.  We should consider reusing
+      the ACE CORBA macros to support native exceptions on platforms
+      that support them.
 
   <li>Need to verify predefined entities are working correctly.  Check
       out the SAXPrint example.
@@ -15,7 +18,11 @@
       not working.
 
   <li>Although most namespace supporting features/interfaces are
-  there, the parser currently does not interpret namespace.
+      there, the parser currently does not interpret namespace.
+
+  <li>The encoding attributes in xml decl element is ignore.  We have
+      no plan to support different character encoding other than
+      UNICODE ones.
 
   <li>I'm sure this list will grow. :)
 
diff --git a/ACEXML/docs/guidelines.txt b/ACEXML/docs/guidelines.txt
index eb14f5af560..267a9b89d66 100644
--- a/ACEXML/docs/guidelines.txt
+++ b/ACEXML/docs/guidelines.txt
@@ -4,6 +4,11 @@
 @page acexml_guides ACEXML Programming Guidelines
 
 <ul>
+  <li>A lot of class names under @c $(ACE_ROOT)/ACEXML/common do not
+      follow the naming convention suggested in ACE-guidelines.html.
+      The reason for that is because those classes were derived from
+      the SAX2 API and we would like to keep them as similar as
+      possible.
   <li>Character encoding:  The default character encoding for ACEXML
       can be set at compile time.   ACEXML uses UTF-8 encoding in most
       platforms where <code>ACEXML_Char</code> maps to
@@ -16,16 +21,17 @@
       correctly but it should be trivial to fix.<p>
 
   <li>Currently, there's only an example showing how to use the parser
-      under @c $(ACE_ROOT)/XML/examples/SAXPrint/.
+      under @c $(ACE_ROOT)/ACEXML/examples/SAXPrint/.
 
-  <li>To develop a new validator, one must create a DLL implementing
+  <li><b>(Not supported yet)</b> To develop a new validator, one must
+      create a DLL implementing
       @c ACEXML_Attributes_Def_Builder, @c
       ACEXML_Attribute_Def_Builder, @c ACEXML_Element_Def_Builder,
       @c ACEXML_Validator, and @c ACEXML_DTD_Manager.  The DLL should
       also export a traditional C function called @c
       create_dtd_manager.  The XML parser itself should also be
       modified to support and dynamically link with the new validator.
-      See @c $(ACE_ROOT)/XML/parser/debug_validator/ for an example.
+      See @c $(ACE_ROOT)/ACEXML/parser/debug_validator/ for an example.
 
 </ul>