StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUsing Spring by Creating Multiple ApplicationContexts to manage bean life time - is this okay?
primarykey
Id
1136607
data
AcceptedAnswerId
1136674
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-16T10:04:32.907
FavoriteCount
0
LastActivityDate
2009-07-16T10:20:25.577
LastEditDate
LastEditorUserId
0
OwnerUserId
139346
ParentId
0
PostTypeId
1
Score
0
ViewCount
430
LastEditorDisplayName
text
Body
I have used Spring before but I am no expert and only used it for standard web-development previously. Currently, I am working on a project where Spring is being used very differently. It's a stand-alone Swing app which has many displays and the user can switch between a display via a toolbar. When the display changes, all the components need to be destroyed (garbage-collected). Currently, this is done by having separate ApplicationContexts associated with each display. So when the display is changed, the idea is that the AppCtx associated with the display is destroyed then a new app context is created (from a different XML file) to load the components in the new display. Is this an appropriate way of using Spring? I don't know much about the internals of the Spring Container and the way the container manages the beans so I can't figure out whether it's a good thing or not.
Tags
<spring>
Title
Using Spring by Creating Multiple ApplicationContexts to manage bean life time - is this okay?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPaul Drummond
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.