StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16031914
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-04-16T08:13:04.340
FavoriteCount
0
LastActivityDate
2013-05-17T01:07:58.270
LastEditDate
2013-05-17T01:07:58.270
LastEditorUserId
181506
OwnerUserId
181506
ParentId
3094427
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
No, it is not possible. I have been working through the same issue, in the context of deploying an EJB 3.0 application on WebLogic 10.3.x. The application runs on Oracle Application Server 10.1.3 and GlassFish 3.x. <ul> <li>Oracle AS (OC4J) has a proprietary mechanism for looking up the local interface of an EJB using JNDI.</li> <li>GlassFish 3.x implements EJB 3.1 with its portable JNDI name syntax.</li> </ul> Our application uses a lookup mechanism for the current application server, which is determined at runtime. In WebLogic Server 10.3, the local interface of an EJB: <ul> <li>can be injected into managed classes in the servlet container (servlets, filters etc.) and other EJBs using <code>@EJB</code> annotations</li> <li>is only available for lookup from JNDI when it has been declared in a <code>ejb-local-ref</code> element in <code>web.xml</code> or <code>ejb-jar.xml</code></li> </ul> It is not practical for us to declare all EJBs that are looked up. We have 192 stateless EJBs, mostly injected but many looked up from JNDI because we need them available to unmanaged classes. My source for this information, apart from trial and error, is <a href="http://middlewaremagic.com/weblogic/?p=39">WebLogic 10.3 EJB3 Local Lookup Sample</a>. Almost everything else I found, including the Oracle documentation, describes the JNDI lookup syntax with <code>mappedName#fullInterface</code> but does not make it clear that only the remote interface name is in the JNDI tree. Update: We went with declarations in <code>web.xml</code> and <code>ejb-jar.xml</code> (yes, there are EJBs that use utility classes that look up other EJBs in JNDI). Started with a script to generate them from sources then manually edited them until they were correct. Not nice but necessary.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPublishing EJB's local interface in weblogic
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpharsicle
UserOwnerUserId
1. USpharsicle
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPublishing EJB's local interface in weblogic
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. 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.