StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4546837
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2010-12-28T14:41:48.200
FavoriteCount
0
LastActivityDate
2010-12-28T14:47:17.360
LastEditDate
2010-12-28T14:47:17.360
LastEditorUserId
472792
OwnerUserId
472792
ParentId
4545593
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Your description of the problem is a little sloppy: <blockquote> persistent.xml is presnt only in project A.Do i need to place persistent.xml in project A too? </blockquote> I take it you mean: persistence.xml is present only in project B. Do I need to place persistence.xml in project A too? What exactly is the setup? Are both projects deployed to the same server? Are they on different servers? Is project A accessing a remote session bean of project B? What projects are we talking about? Web projects, EJB projects? EAR projects with both Web and EJB projects in them? I don't think it's supported that you ship an entity manager from one application to the other. The idea is that a client calls a remote bean, then this remote bean obtains a local entity manager, does some work with it and returns the results. If A is your client, then A certainly does not need to have a local persistence.xml. Your problem might well be that the entity manager you're after is simply not available under the name you think it is. <code>java:comp/env/persistence</code> obviously doesn't exist. Normally an entity manager doesn't appear automatically in JNDI. If B was a servlet, you would need something like this: <pre><code><persistence-context-ref> <persistence-context-ref-name>persistence</persistence-context-ref-name> <persistence-unit-name>yourpu</persistence-unit-name> </persistence-context-ref> </code></pre> If B was an EJB session bean, you need something like this: <pre><code>@Stateless @PersistenceUnit(name="persistence", unitName="yourpu") public class BBean implements BRemoteInterface { // some code here... } </code></pre> After this, the entity manager would be available under <code>java:comp/env/persistence</code>, but only when the JNDI lookup is being initiated from that servlet or bean. java:comp/env is a relative context, that is different for each location that a lookup is done on it. The least you could do is simply printing your <code>java:comp/env</code> context from B and see what's in there exactly. See this simple example how to do such printing: <a href="http://tripoverit.blogspot.com/2007/03/print-jndi-tree.html" rel="nofollow">http://tripoverit.blogspot.com/2007/03/print-jndi-tree.html</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POproblem with JNDI
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USArjan Tijms
UserOwnerUserId
1. USArjan Tijms
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POproblem with JNDI
 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

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.