On Tue, 4 Dec 2001 22:02, Paul Hammant wrote: > >That is a problem. There was a few things we can do to alleviate this > > issue. We could allow some sort of automagic creation of .xinfo files > > from javadocs of specified blocks. This would help keep cost of > > maaintaining them down a bit. > > Value points = 1 > > >We could also (finally) create ant tasks to run the verifier over .sars > >before they are deployed. This should give a good indication whether the > >format is valid. > > Value points = 2
It should be simple enough to do I think. Have a look at tools.verifier.* - we just need to instantiate that and pass in the proper classloaders etc. > >We could also create DTDs for the different formats as appropriate and > >interpret > > VP = 1 > > >the files with that mind. > > > >I could also write a "Block File Archive Verifier" that verified the > > format of all the Blocks info files, and the relationship beteen services > > inside the jar, the manifest entrtys and so forth. > > VP = 4. > > Something that owuld comprehensively tell you what is wrong with a SAR. > Something that we might not want part of the regular Phoenix machine > (which we are trying to keep lean?) Well anything I intend to use from ant tasks I have placed in phoenix.tools.*. That simply makes it easier to package these tools so that they are separate from container. -- Cheers, Pete ----------------------------------------------- "You can't depend on your eyes when your imagination is out of focus." -Mark Twain ----------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
