Paul Hammant wrote:
> Stephen,
>
>>> Stephen,
>>>
>>> No dude, we're supposed to do it in the same package! This one
>>> generates meta information, yours uses it!?
>>
>>
>>
>>
>> Umm .. your going to have to explain this some more.
>> The code that is there is Phoenix specific - I'm talking about
>> equivalent code targetted at the excalibur/meta package.
>
>
> If does not import any Phoenix classes.
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.
Steve.
>
> - Paul
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
