|> |Yes, I will be using XML. Same format for both jboss.jcml and
|> |jboss-auto.jcml. Why not?
|>
|> why? if you are not going to read it with humans... why the overhead?
|
|Uhm.. "because!".. ?
|
|No good reason I can think of. To get it to look the same as the other conf
|files I guess. People feel more comfy with text configuration files.
|
|But I guess it would be ok to drop this, yes.
Ok I understand we actually DON'T want people meddling with jboss-auto.jcml
(the source of our problems with jboss.jcml today) so serialization would
buy that for sure, althought Dan and a few other mutants can read bytecode
in the flesh. ("AE 8B 33 08 7F, ahah! you misconfigured your pool!")
Now if you already have the XML read/write done then sure... xml is
interesting at the tools/human interface (tools can parse and play with it,
humans can read and write it) but if it is a pure tools/tools play as in
jboss.jcml then the overhead of parsing and XML'ing is useless.
let's drop it indeed,
marc
|
|/Rickard
|
|
|
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
