Before we decide on implementation details, lets have a look at the current sittuation with respect to tools/metadata. Please step back a little and look at it from a consultants perspective whose only aim it is to make it better in the future - what happend in the past is not of interrest. | * jbossws-2.0.x is a functional superset of jbossws-1.2.x and jbossws-1.0.x. There is however a conflicting implementation with respect to how JSR181 endpoints are handled. | | * currently we have two (in the near future three) code bases | that are divergent to a degree where it becomes virtualy impossible to merge changes from branch to trunk and vice versa. Effectivly, team members spend days merging trivial functionality or don't do it at all (which is worse) | | * the tools code base in branch has virtually not been maintained for the largest part of the year it is also in a state where it is still difficult to maintain | | * the tools code base in trunk builds on the tools code base from branch, such that maintainability concerns apply likewise | | * there is no tools api that can be used from core and thirdparty | | | Therefore, I'll put some effort in | | | | * unify the metadata model accross branches | | * reuse a single tools code base accross branches | | * draft a tools api | | | | I see this as necessary prerequisity before I continue with CTS work and the foundation for 1.0.5, 1.2.0 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991630#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...