Outline below. Comments welcome! Are there tools for writing the xdocs?
--- Avalon/Phoenix Management Documentation ======================================= Objectives ---------- - Create a simple mechanism by which component authors can define management operations and attributes without regard for how the container implements management - Define a structure for how management information is organized that is rich enough to be useful without restricting or presupposing the interface - Work across broad range of components (eg. not restricted to Phoenix blocks) - Be able to retrofit existing components without modifying the source code Outline ------- 1) Organizing Structure for Management Data (Contexts, Targets & Topics) (audience: everone) 2) Implementation Overview (audience: everyone) 3) MXINFO files (audience: component authors) 4) phoenix-mx xdoclet tags (audience: component authors) 5) Container responsibilities to support management (audience: container authors) 6) link to javadocs (audience: reference) 7) future direction (eg. generation of interfaces from MXINFO files) (audience: internal) - Huw -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
