> Yeah well, one of the advantages of the metadata that is now is that it is
> virtually "Bug-free". The old version was riddled with bugs and never
> enabled people to get past the "I am confused and I can't configure the
> stuff".
Of course. This is mostly a "behind the scenes" upgrade which won't affect
users, other than the fact that EJX will be much much easier to use (1 EJX
plugin instead of 3, taking care of both EJB JBoss and JAWS XML).
> Features as the differential metadata and the stability and ease of use,
> need to stay.
Agree.
> Frankly Rickard I am not convinced reworking the metadata back to its old
> state is a good idea. Please flag the current version in memory because
the
> last version was very buggy
Never said that it would be going back to its old state. It is going to be a
blend between the old and the new. The current org.jboss.metadata is perhaps
stable, but it is too static and simplistic to be easy to work with (from a
developer point of view). Also, having two structures for the 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.
/Rickard
