StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1157629
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-21T06:53:28.900
FavoriteCount
0
LastActivityDate
2009-07-21T06:53:28.900
LastEditDate
LastEditorUserId
0
OwnerUserId
3105
ParentId
1157558
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Assuming that responding to a command is not that different from responding to a http request, I think you're going the right path. A commonly used pattern in http applications is to wrap logic of the application into short lived objects that have both parameters from request and some backends injected. Then you instantiate such object and call a simple, parameterless method that does all magic. Maybe scopes could inspire you somehow? Look <a href="http://code.google.com/p/google-guice/wiki/Scopes" rel="nofollow noreferrer">into documentation</a> and <a href="http://code.google.com/p/google-guice/wiki/CustomScopes" rel="nofollow noreferrer">some code examples</a> for read the technical details. In code it looks more less like that. Here's how this might work for your case: <pre><code>class MyRobot { Scope myScope; Injector i; public void doCommand(Command c) { myScope.seed(Key.get(Command.class), i.getInstance(Handler.class).doSomething(); } } class Handler { private final Command c; @Inject public Handler(Command c, Hardware h) { this.c = c; } public boolean doSomething() { h.doCommand(c); // or c.modifyState(h) if you want c to access internals of h } } </code></pre> Some people frown upon this solution, but I've seen this in code relying heavily on Guice in the past in at least two different projects. Granted you'll inject a bit of value objects in the constructors, but if you don't think of them as value objects but rather parameters of the class that change it's behaviour it all makes sense. It is a bit awkward and some people frown upon injecting value objects that way, but I have seen this in the past in projects that relied heavily on Guice for a while and it worked great.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGetting to Guice created objects from dumb data objects
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMarcin
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.