[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: 'public' API stability when embedded in JBossAS

[mark.little@jboss.com]

Anything that is within the internal package should not be covered by deprecation. It's in the docs and the support guys are aware of it. Anything public can change through normal deprecation rules.

This works for other projects, so I'm not sure why we need to make special rules. XTS is different in that there is no standard API for it to conform to, but I assume it's still using the internal/mwlabs approach so the above still applies.

The trouble with listing interfaces/classes is that it's fairly arbitrary. Do we take only what we use in the AS? What about when running stand-alone? What about JTS or any of the extensions we have to the various standards?

So I'd prefer that we stick with the .internal. and use the deprecation rules (which don't prevent changes that are incompatible with previous releases, but in a controlled manner.)

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209060#4209060

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209060