|
From: <ale...@jb...> - 2006-07-05 20:17:38
|
There is a confusing compatibility issue between XB versions up to 1.0.0.CR4 and 1.0.0.CR5 that I would call as binary-but-not-Java-API incompatibility. The issue itself is described here http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossXB100CR5InJBoss404GA The reason for removing the API that's causing the trouble is that the API is old and not actually used by anyone. So, I don't want this API to appear in the future CR's and releases (if ever) of XB. I understand that asking clients who want to use JBossWS version that relies on XB-1.0.0.CR5 or later to recompile 4.0.4.GA with the required XB version is not going to work. To workaround the incompatibility I could release a special binary for 4.0.4.GA every time I release a new version of XB. These binaries could be used with any JBoss version. But all JBoss versions after 4.0.4.GA should be compiled with the XB-1.0.0.CR5 or later. Would this work for everyone? Or do you think I should reinstate the old API now and proceed with the long planned refactoring that includes SchemaBinding API and public API cleanup (probably creating new Java packages for them) on another branch? But the compatibility would still be a question to answer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955661#3955661 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955661 |