StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POKeeping a DCOM object alive from Java server on a REST invocation
primarykey
Id
518435
data
AcceptedAnswerId
518508
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-02-05T23:17:09.117
FavoriteCount
0
LastActivityDate
2009-02-15T23:23:38.537
LastEditDate
2009-02-06T02:10:33.697
LastEditorUserId
36694
OwnerUserId
36694
ParentId
0
PostTypeId
1
Score
0
ViewCount
631
LastEditorDisplayName
Inbar Shani
text
Body
I'm implementing a REST API for my Java server. One of the of the resources obtained through the API is actually creating a C++ DCOM object and reflecting its values. The Java to COM bridge I'm using is J-Integra. The problem is that I need to keep that DCOM object alive for subsequent REST calls, but the object is alive just as long as its Java reference is - which is until the REST session expires at most. How can I keep the DCOM object alive until I no longer needs it? The only thing I thought of till now was using an EJB which then will be the one to initiate the DCOM object and hold its reference. I'm not an expert on EJBs, but I think that a) its an overkill solution b) the EJB may be cached (passiviate?) by the server, losing the DCOM reference at that. Any suggestions? Thanks Inbar
Tags
<java><com><rest><ejb><dcom>
Title
Keeping a DCOM object alive from Java server on a REST invocation
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USInbar Shani
UserOwnerUserId
1. USInbar Shani
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. 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.