Stephen, > No, but it reads Phoenix specific tags and generates Phoenix specific > meta. > >> We can have one XML generater that generates all for all yes? > > Maybe - but not in the way its implemented - the code base is > implicitly Phoenix based in that the code knows how to translate a > "phoenix:xxx" to corresponding Phoenix meta statement in a file. > That's actually what I found attractive - the implementation is clean > because is is NOT doing a generic generation process. > >> We could have switches in the Ant taskdef to control the generated XML? > > Sure - but how would seperate the different meta models without a > corresponding parrallel tag translation engine for excalibur/meta? > Just for reference - what you have written appears to me to be a good > example of a tag translation engine for Phoenix.
Because it picks op on the word "phoenix"? The xinfo file it generates does not have the word "phoenix" in it We're _not_ using one codebase then? Regards, - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
