StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1080553
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-03T19:25:25.077
FavoriteCount
0
LastActivityDate
2009-07-03T19:25:25.077
LastEditDate
LastEditorUserId
0
OwnerUserId
123054
ParentId
1076221
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I've implemented something which works but involves some slightly ugly setup... still interested in any improvements on this & there may be a bit too much code to post really so just put some snippets in that hopefully illuminates it's a a variation on the SimpleScope example which involves; <ul> <li>bringing up the spring ctx </li> <li>grabbing a specific bean out of it (that is a registry of pipeline keys) </li> <li>passing that to the Guice module along with the beanfactory</li> <li>giving that registry to the Scope impl so the scope is entered when the pipe is activated (which happens later when certain spring beans are init'ed)</li> </ul> It seems I have to grab the specific bean rather than access it through a Named after doing a bindAll on the beanfactory as the Scope instance is new'ed yourself in the Module, i.e. <pre><code> PipeScope<SecurityId> pipeScope = new PipeScope<SecurityId>(); pipeScope.setPipeIdRegistry(pipeIdRegistry); bindScope(Pipe.class, pipeScope); bind(PipeScope.class) .annotatedWith(Names.named("pipeScope")) .toInstance(pipeScope); SpringIntegration.bindAll(binder(), beanFactory); </code></pre> The fact I have to new it means I need to explicitly provide the registry to the module, can't see a way around this as it's a chicken & egg situation. The PipeScope basically stores values against the pipe key (actually a List of keys) as opposed to a ThreadLocal so my enter is like <pre><code>public void enter(List<K> scopedKeys) { checkState(values.get(scopedKeys) == null, "A scoping block is already in progress"); values.put(scopedKeys, Maps.<Key<?>, Object>newHashMap()); } </code></pre> all in all seems to function perfectly well... at least in my quickly knocked up test harness anyway 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGuice Custom Scopes and Spring managed beans
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMatt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGuice Custom Scopes and Spring managed beans
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.