Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Relationship problem
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Florian Wild  
View profile  
 More options Oct 17 2002, 8:58 am
Newsgroups: comp.lang.java.beans
From: florian.w...@web.de (Florian Wild)
Date: 17 Oct 2002 05:58:44 -0700
Local: Thurs, Oct 17 2002 8:58 am
Subject: Relationship problem
Hello everyone,

I've encountered a tricky problem, where I just don't come further.
I have 3 Entity Beans with the following unidirectional relationships:

Bean1->Bean3 1:n
Bean2->Bean3 1:n

When I try to deploy the beans, I read this:

U:\..\Bean3_PM.java:9: Duplicate variable declaration:
int ___reverse_bean3_ID was int ___reverse_bean3_ID
public static final int ___reverse_bean3_ID = 1;
^
U:\..\Bean3_PMState.java:8: Duplicate variable declaration:
LocalBean2 _reverse_bean3 was LocalBean1 _reverse_bean3
public LocalBean2 _reverse_bean3;
^
2 errors
Compilation failed ...

When I look into the Bean3_PM.java there's the following:
public static final int ___reverse_bean3_ID = 0;
public static final int ___reverse_bean3_ID = 1;

In Bean3_PMState.java:
public LocalBean1 _reverse_bean3;
public LocalBean2 _reverse_bean3;

That means obviously, that the PM-files of Bean3 (which are created
during the deployment) have attributes, where the sources of the
relationships are recorded. But somehow it's done quite stupidly,
without changing the name of the attribute for the second
relationship.

Has anyone encountered a similar problem? Is this a bug or really
wanted? How can I avoid this problem? Any ideas?

Thanx,
-- Flo


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »