● 问题解决了发信人: lywater (雨燕), 信区: J2EE
标 题: 问题解决了
发信站: BBS 水木清华站 (Mon May 17 21:04:53 2004), 站内
偶在csdn上找了一个晚上，终于找到答案了
现向大家共享之，好东东，大家共享啊^_^
－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－
OK then here is the thing:
When you use EJB relationships, you don't have to think only relational
database but also Object Oriented database. I mean you don't have to
store in an entityA field the PK of entityB but rather say to the
system, (in this case the EJB container) my entityA instance is linked
to this instance of entity B and the system (OO DB or the container is
taking care of the persistency of that specific instances' relation).
For example:
EntityA represents BANK's users (PK= String userID + String bankID)
EntityB represents BANKs (PK= String bankID). A Bank may have several
users within the bank.
Suppose you want to create a EJB relationship between users and banks.
So you create a CMR field in EntityA called rBank. This relationship
needs to be persisted so you specify in the deployment descriptor that
the relationship is related to the table Users, column field bankID
(which is, from a relational DB point of vue, a FOREIGN KEY). You need
to "tell" the container how it should persist the relationship. The DD
is there for that.
Of course you have that column represented in the entityA as a CMP field
(bankID) so you may (NOT AN OBLIGATION) have defined (your IDE may have
done that for you automatically) a SET method for that CMP field.
In EntityB you have a CMR field called rUsers for which the getRUsers
method return a Collection of EntityA instances. Again here, that CMR is
linked to the CMP field bankID in the table BANK for persistency
purposes.
Note: CMR fields like CMP fields can have getters and setters.
Now, you want to create a new user.
>From the EntityA home interface you use the create method which will
return you a new EntityA instance.
Within the ejbCreate method of EntityA you may initialise the
relationship with a bank's instance. You can't use the setBankID of
EntityA (THAT's THE RULE in the SPEC) but you need to ge the bank's
instance (findByPK) and apply the method:
instanceB.getRUsers().add(this). Of course I do not recommend to do that
there.. But rather in a SessionBean.
So in the session bean:
EntityA entityA = null;
EntityB entityB = null;
Try
{
entityA = entityAHome.create(new PK);
entityA.setXXX(...) for CMP fields not being part in a relation
(you can do the setter in the ejbCreate method).
entityA.setBankID(bankID); /// THIS WILL CAUSE AN EXCEPTION
～～～～～～～～～～～～～～我自己的实践结果，这一句不应该要的
entityB = entityBHome.findByPK(bankID);
update CMP field bankID in entityA with the right info based on the info
provided in the deployment descriptor). }
Note: I'd recommend you not to provide any setters for CMP-CMR fields to
avoid any tentation!!
Note: in the case of a N-M table relationship, you need to have a
intermediate table (typical database technique) and CMR fields in
entnityA/B needs to be "physically" linked (in the DD) to that
intermediary table.
【 在 itisuptome (马不停蹄) 的大作中提到: 】
: 解决这个问题有简单方法
: 将出问题的这个属性项设为主键（cmp的主键，数据库是不是没关系）
: 这样就没问题了
: ...................
--
family中F是father,A是and,M是mother,I是i,L是love,Y是you.
于是,FAMILY就是:father and mother,i love you!
※ 来源:·BBS 水木清华站 smth.org·[FROM: 166.111.195.*]
索引页面|上一篇|下一篇
[返回] 中文XML论坛 - 专业的XML技术讨论区 →
计算机技术与应用 → 『 Java/Eclipse 』 → 问题解决了
(订阅本版)
2004/9/23 0:40:00
新浪微博
问题解决了
