|Where is it documented?
advanced JBoss, jboss.dtd, configuration and trails etc etc...
listen there is little discussing here and I will be brief. The previous
metadata was a _catastrophy_ from many standpoints. The new metadata
DELIVERS on "ease of use" and actually **works**, which was a first.
If you now want to merge the structures for some reason, you still have our
trust, but do so without impacting the ground that was gained in the
container. If you can make transparent for users good, if you can make it
transparent for container developers better. But I am not going back to the
madness of having GUI classes in jboss.container and unreadable code all for
the sake of EJX the GUI and "fancy" code from Rickard Oberg.
So again TAG your work so we can go back if it doesn't work.
marc
|Yes it is necessary and yes it is a priority. As I said before, I began
|doing upgrades but realized that the current metadata structures are too
|static and cumbersome to work with to easily add features.
|
|> |server and the
|> |GUI editor (as I have said before) is a bad idea.
|> |
|> |I have done about 1/3 of the code now, and it rocks. The editor is so
|much
|> |cooler now that it can handle all three at the same time.
|>
|> Again please TAG THE CURRENT VERSION, this is risky rickard.
|
|I won't check it in until it is completely done. But yeah, I will try to
|check it in in a safe way. If anyone knows how to make branches, let me
|know.
|
|/Rickard
|
|
|
|
|
