StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6036882
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-17T20:43:17.987
FavoriteCount
0
LastActivityDate
2011-05-17T22:09:45.280
LastEditDate
2011-05-17T22:09:45.280
LastEditorUserId
735145
OwnerUserId
735145
ParentId
6036267
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I'm afraid I can't offer anything on the Scala front, but as far as Java goes you should think of your new service as being in the Service layer of your application, whereas the REST/SOAP/Whatever interface to your service is defined in the Web/Servlet layer. So let us say you have a service like the following in your com.myco.services package: <pre><code>public interface PersonService { public Person createPerson(PersonIdentifier id, PersonType type); public Person retrievePerson(PersonIdentifier id); public void updatePerson(Person existingPerson); public void deletePerson(Person existingPerson); public boolean authenticatePerson(String personName, String password); } </code></pre> We'll take it as read that you have an PersonServiceImpl implementation of this that updates your database or whatever. In your application on the same JVM you can inject the PersonServiceImpl into your code and call the methods directly, without having to marshal or unmarshal the parameters. In the Web layer you can have a separate PersonServiceController that is mapped to URLs in your servlet. When a URL like "http://myco.com/person/update" is hit, the body of the request can be passed to the controller like so: <pre><code>public class PersonServiceController { private final PersonService personService; // Inject PersonServiceImpl in constructor ... public void updatePerson(String requestBody) { Person updatedPerson = unmarshalPerson(requestBody); this.personService.updatePerson(updatedPerson); } ... } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODesigning a multi-module project
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsockets-to-me
UserOwnerUserId
1. USsockets-to-me
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.