You are viewing a plain text version of this content. The canonical link for it is here.

Posted to phoenix-dev@avalon.apache.org by bu...@apache.org on 2002/09/14 07:11:21 UTC

DO NOT REPLY [Bug 12639] New: - Decouple MXInfo and migrate to Baxter

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12639>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12639

Decouple MXInfo and migrate to Baxter

           Summary: Decouple MXInfo and migrate to Baxter
           Product: Avalon
           Version: 1.0b1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Phoenix
        AssignedTo: avalon-phoenix-dev@jakarta.apache.org
        ReportedBy: donaldp@apache.org


It would be really nice if we could decouple MXInfo from Avalon/Framework and 
Phoenix and then move it into Phoenix. The best way to do this would be to load 
the descriptor in as a w3c DOM object and process it using this DOM rather than 
Configuration objects.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>