StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6544049
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-01T05:45:29.927
FavoriteCount
0
LastActivityDate
2011-07-01T05:45:29.927
LastEditDate
LastEditorUserId
0
OwnerUserId
735533
ParentId
3877110
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Been a while since this was posted so probably moot point but may help others. Another option on having a single shared library used by separate higher level applications is a versioning system within the utility library. In essence, you publish a defined API "service level" from the utility library under some version ID - such as an incremented integer (regardless of the underlying codebase of the utility library): <ul> <li>API Level: 1</li> <li>API ID: UTIL_API_20110630_1.0.1</li> </ul> Then, within the utility library, you handle passthru support for "legacy" APIs ... by simply wrapping the "old" library interfaces within the new library ... either in the same jar or a "child" jar library (the Utility.jar remaps calls to the child.jar). In this manner, the application establishes the API Level it desires. Thus, the applications only ever see the main "Utility.jar" and access it via the desired API level even though the back end implementation may change and evolve. <pre><code>App X, Y, Z Util.jar --> Util_1.0.1.jar (API Level: 1) --> Util_1.0.3.jar (API Level: 1) --> Util_1.2.7.jar (API Level: 1) --> ... --> Util_2.0.1.jar (API Level: 2) </code></pre> Another benefit is if "App X" is no longer under active development it still has the same API, functionality, and behaviour it has always known. Meanwhile, the utility library and Applications Y and Z can continue unabated. It's a bit more work to create the pass thru wrappers for the first of the subsequent releases. (And depends heavily on the nature of the utility library.) But then it becomes a quick copy/paste, change the API level, rename, and you're on your way.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEclipse Java utility project and multiple web apps
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDevByStarlight
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.