"Carlo" wrote : We must have a notion of parent deployment units at metadata
level
I assumed that the metadata api is a representation of the XML and not more than that.
Everything else should be a layer on top. I still think it's a good idea to separate
parsing/unmarshalling issues (and later maybe marshalling) from the "using it"
logic. Having everything in the same place may complicate the api and maintenance.
I suggest we develop some wrapping api that gives the view we need but not add these
changes to the classes that map to XML. The api may live in the metadata project as well,
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147629#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...