On 01/02/2007, at 9:28 PM, Andrus Adamchik wrote:
We are talking about BLOBS of text. Consider people using this for javadocs, with each attribute having a 100 char comment field. For the model of 50 entities with 20 attributes each, we have (50 + 50*20) * 100 = 102K. Not crucial, but still keeping this stuff around in runtime seems wrong. Those things add up over time, resulting in framework becoming heavier with every new release.
Not to mention it might contain private notes we may not want in a public release of a product. I don't want our entity documentation released to the world.
How about a velocity(?) script which could strip some parts of the XML file for deployment? As long as they were easily identifiable, we could even put a little regex into our main ant build script for deploying the application.
On the other hand, a separate config file for comments would make this easier...
Ari --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
PGP.sig
Description: This is a digitally signed message part
