JBossXB as a project

[adrian.brock]

Hi Alex,

How close are we to being able to do this?
http://jira.jboss.com/jira/browse/JBBUILD-61

I think such a project should serve as an integration point for everybody's xml needs
where issues cannot be resolved through the JAXP api?

[aloubyansky]

IMO, feature-wise the project is ready.
What I would like to do before that step is:

- http://jira.jboss.com/jira/browse/JBXB-37 (has been linked)

- perhaps, http://jira.jboss.com/jira/browse/JBXB-36 also (has not been linked yet)

- address packaging (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70841) and package name (sunday) issues

If you would like to add something, link existing issues or create new ones.

Also, let's discuss the priority of this task. I have WS XB-related issues to work on that are my top priority currently.

[adrian.brock]

It is not urgent, but I would like to split up jboss-commons
(which is becoming garguntuan :-)
so I can see what is still used and how it fits together after we split off
jbossxb, logging, protocol handlers, javabean editors, and threadpool/timeout/lru/etc.

Reasons:
* Allows other projects to take things ala carte
* JBoss-commons is too big (discourages adoption of shared code and not invented here)
* JBoss-commons has become a dumping ground
* There is some leakage across jboss-commons utilities that shouldn't really be there (or if it should, it should be better thought out)
* It doesn't make sense maintaining a different version of common utilities on every JBossAS branch

JBossXB is the biggest part of it
Logging is the most used - but many projects use commons-logging or roll your own because they don't want the large jboss-commons