I am insterested in creating the metadata that fortress requires without using the javadoc tags.
We have an application using the old ECM roles files and turning its contents into javadoc tags into 750 or so java classes is unappealing. Plus, we are using a tool at development time that maintains our roles file for us and needs it to be there for us to continue to be able to use it, and it does not know about the javadoc tags. So, what I'm thinking is writing something to take the roles file and make the .meta files and the services.list file and whatever else fortress might need, perhaps through an XSL transform.... You seasoned fortress guys and gals: does this sound feasible? Is there documentation (stop laughing!) about the format of the metadata, or do I need to reverse engineer classes like org.apache.avalon.fortress.tools.ComponentMetaInfoCollector and hack it? Or is it so simple as to be trivial? -- Matt Harrah Senior Consultant, PlatinumSolutions, Inc. [EMAIL PROTECTED] http://www.platinumsolutions.com Two Discovery Square, 12012 Sunset Hills Road, Suite 445 Reston, VA 20190 PH: 703.471.9793 FAX: 703.471.7140 This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
