StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1263739
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-12T00:55:03.853
FavoriteCount
0
LastActivityDate
2009-08-12T00:55:03.853
LastEditDate
LastEditorUserId
0
OwnerUserId
67015
ParentId
1050889
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Just to make this complete. Instead of using Hibernate, EclipseLink could be used as JPA-provider in a Eclipse RCP application. EclipseLink is the former TopLink from Oracle and has been choosen to be the reference implementation for JPA 2. The point for an RCP is, that EclipseLink is available as OSGI-Bundles (org.eclipse.persistence.jpa), and due to that it can load classes from another plugin without an additional buddy-policy. Currently I was playing around, using the following project structure (Model-View-Presenter Pattern). The names in the brackets specify the dependecy plugins (not all are included, only the ones related to this question) <ul> <li>rcp.mvp.view (rcp.mvp.presenter / rcp.mvp.model)</li> <li>rcp.mvp.presenter (rcp.mvp.data - data reexports the model, so this is not needed here) *</li> <li>rcp.mvp.data (rcp.mvp.data.mysql / rcp.mvp.model / javax.persistence / org.eclipse.persistence.jpa)</li> <li>rcp.mvp.data.mysql - provides only the mysql-jdbc-driver. has to be inside the classpath</li> <li>rcp.mvp.model</li> </ul> In this scenario, the JPA provider in the data-plugin is able to load the classes from the model-plugin without a buddy-policy. *Note, the presenter is not dependent on any JPA packages since this is encapsulated by DAOs (the main reason why to use them still) Links <ul> <li><a href="http://wiki.eclipse.org/EclipseLink/UserGuide" rel="nofollow noreferrer">User Guide</a></li> <li><a href="http://wiki.eclipse.org/EclipseLink/Examples/JPA/RCP" rel="nofollow noreferrer">RCP example</a> (unfortunately not using DAOs)</li> <li><a href="http://live.eclipse.org/node/490" rel="nofollow noreferrer">EclipseLink conceptual Webinar</a> from live.eclipse.org</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing Hibernate with Dynamic Eclipse Plug-ins
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USlostiniceland
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.