Closed thekid closed 13 years ago
The JSON API should probably stay part of the core distribution. I'd suggest to create a new top-level "webservices" package and stuff it there; but this should be a new RFC.
friebe, Sun, 22 Oct 2006 16:59:23 +0200
The creation of a top-level webservices package will be included in this RFC after all.
friebe, Thu, 16 Nov 2006 10:36:44 +0100
As soon as an upgrade advisor and a migration script are available, I'll set this to discussion.
friebe, Thu, 16 Nov 2006 11:07:35 +0100
contrib/rfc0084/migrate contains reporting and migration scripts. See http://xp-framework.info/xml/xp.en_US/news/view?131 on how to use them.
friebe, Fri, 17 Nov 2006 11:05:37 +0100
Scope of Change
The domain-specific packages in the XP framework will be moved from the skeleton/ directory to ports/classes/. The domain-specific org.json- package and all other webservice-related packages will be joined into one new package, webservices; unittests will become top-level, deprecated packages will be removed and other (should-be domain-specific) packages will be renamed and moved to ports/classes/.
Rationale
Clean up the core distribution; make it consistent.
Functionality
Quite a bit of reorganizing will be done, not limited to moving the domain- specific packages but rethinking what will be core and what will be moved.
1) The following packages will have incompatible changes:
Legend: S: stays in skeleton but gets a new name there M: moved to ports/classes under a new name R: removed completely
In all cases, XAR files retaining the old classes will be created.
2) The following packages will be moved as-is to ports/classes
ch ~~
com
net
org
us ~~
After the changes are applied, the packages will be distributed as follows:
skeleton
ports/classes
Security considerations
n/a
Speed impact
n/a
Dependencies
Users of the packages moved to ports/classes will need to add the /path/to/xp/trunk/ports/classes/ directory to their include path.
Users of packages moved within skeleton can either change their source- code (a migration script will be provided) or use of the BC xars which retain the old class names, adding them to their include path.
Related documents