Implementing two 1:M relationships

Hello,
I have a Oppty Fact. As an Extension to it I have resource fact and case fact.
Oppty Fact : Resource fact = 1: M
opty fact : case fact = 1:M.
We need a report with oppty name (from oppty fact), Amount (from oppty fact) , REsource name (from resource fact), Case name (from case fact).
To implement this, I created a Logical table. Added Oppty fact and resource fact to the source. In the Resource fact Joins section, I added Oppty fact and made a Left our join. Similarly I added the case fact and in the joins section added the oppty fact and made a left outer join.
But report is not rendering. I get this error
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Opportunity Resource-Case fact) does not contain mapping for [Opportunity Resource-Case fact.RESOURCE_NAME, Opportunity Resource-Case fact.OPTY_PHASE_NAME, Opportunity Resource-Case fact.CASE_TEAM_NAME]. (HY000)
Can someone please tell how to resolve this
Thanks,
Vinutha

Hi Vinutha,
It seems like you only have fact-tables, am I right?
I guess you need three dimension tables (Oppty, Resource and Case) and one fact (Oppty). The dimensions would have to have a 1:m relation to the fact.
In your phyiscal model you should create aliases for the fact tables and create them as dimension tables. Then you should be good to go.
Good Luck,
Daan Bakboord

Similar Messages

Two 1-N relationships in target message

Hi
I am new to using the functions in message mapping and I was wandering if an expert could please offer me some help. I have a scenario where I need to produce two messages from the source message based on the number of line items for example, if there are 2 line items, the mapping needs to produce 2 messages from the source message. This part I have managed to get working fine.
The problem is that the target message has two 1-N relationships (i.e inside the header and payload) and am I am struggling to produce 2 MessageDestination nodes per message. The mapping that I am currently using only produces 2 MessageDestination nodes inside the first message and not the second message aswell (I am using the splitByValue function). Please see example below:
Source:
Message1
Header
-MessageDestination
--Destination[Destination1]Destination
-MessageDestination
-MessageDestination
--Destination[Destination2]Destination
-MessageDestination
Header
Payload
LineItem
-LineItem
--Line[Line1]Line
-LineItem
-LineItem
--Line[Line2]Line
-LineItem
Payload
Output:
MESSAGE1
Header
-MessageDestination
--Destination[Destination1]Destination
-MessageDestination
-MessageDestination
--Destination[Destination2]Destination
-MessageDestination
Header
Payload
LineItem
-LineItem
--Line[Line1]Line
-LineItem
-LineItem
--Line[Line2]Line
-LineItem
Payload
MESSAGE2
Header
-MessageDestination
--Destination[Destination1]Destination
-MessageDestination
Header
Payload
LineItem
-LineItem
--Line[Line1]Line
-LineItem
-LineItem
--Line[Line2]Line
-LineItem
Payload
The following is the required output that I need to produce (i.e. 2 MessageDestination nodes per target message):
Required Target / Output:
MESSAGE1
Header
-MessageDestination
--Destination[Destination1]Destination
-MessageDestination
-MessageDestination
--Destination[Destination2]Destination
-MessageDestination
Header
Payload
LineItem
-LineItem
--Line[Line1]Line
-LineItem
-LineItem
--Line[Line2]Line
-LineItem
Payload
MESSAGE2
-MessageDestination
--Destination[Destination1]Destination
-MessageDestination
-MessageDestination
--Destination[Destination2]Destination
-MessageDestination
Header
Payload
LineItem
-LineItem
--Line[Line1]Line
-LineItem
-LineItem
--Line[Line2]Line
-LineItem
Payload
Any help will be appreciated very much.
Thank you.
Edited by: Brendon Bouwer on Aug 24, 2009 2:28 PM
Edited by: Brendon Bouwer on Aug 24, 2009 2:31 PM

Source:
Message1
<Header>
<MessageDestination>
<Destination>1<Destination>
<MessageDestination>
<MessageDestination>
<Destination>2<Destination>
<MessageDestination>
<Header>
<Payload>
<LineItem>
<LineItem>
<Line>1<Line>
<LineItem>
<LineItem>
<Line>2<Line>
<LineItem>
Payload>
Current Output:
MESSAGE1
<Header>
<MessageDestination>
<Destination>1<Destination>
<MessageDestination>
<MessageDestination>
<Destination>2<Destination>
<MessageDestination>
<Header>
<Payload>
<LineItem>
<LineItem>
<Line>1<Line>
<LineItem>
<LineItem>
<Line>2<Line>
<LineItem>
Payload>
MESSAGE2 (Only one MessageDestination Node is being created, not 2)
<Header>
<MessageDestination>
<Destination>1<Destination>
<MessageDestination>
<Header>
<Payload>
<LineItem>
<LineItem>
<Line>1<Line>
<LineItem>
<LineItem>
<Line>2<Line>
<LineItem>
Payload>
The following is the required output that I need to produce (i.e. 2 MessageDestination nodes per target message):
Required Target / Output:
MESSAGE1
<Header>
<MessageDestination>
<Destination>1<Destination>
<MessageDestination>
<MessageDestination>
<Destination>2<Destination>
<MessageDestination>
<Header>
<Payload>
<LineItem>
<LineItem>
<Line>1<Line>
<LineItem>
<LineItem>
<Line>2<Line>
<LineItem>
Payload>
MESSAGE2
<Header>
<MessageDestination>
<Destination>1<Destination>
<MessageDestination>
<MessageDestination>
<Destination>2<Destination>
<MessageDestination>
<Header>
<Payload>
<LineItem>
<LineItem>
<Line>1<Line>
<LineItem>
<LineItem>
<Line>2<Line>
<LineItem>
Payload>

How to join two parallel identifying relationships?

I have four entities A, B, C and D with the following identifying relationships:
A <-- B
A <-- C
B <-- D
C <-- D
A has a single primary key AID. B and C have their own primary keys BID and CID and primary foreign keys to the primary key of A. So the primary keys of B and C are (BID, AID) and (CID, AID). D has his own primary key DID and the primary foreign keys to B and C. So the primary key of D is (DID, (BID, AID), (CID, AID)). As you can see the primary key of A occurs twice in the primary key of D, because of the two parallel identifying relationships.
Now I want the two AIDs in the primary key of D to be identical. The primary key of D should be a four tuple (DID, BID, CID, AID).
How can I express this in the logical model of the Data Modeler?
What I tried so far: I engineered the logical model into a physical model and changed there one of the parallel relationships. I changed the associated child column of the redundant AID reference to the other one. After that Data Modeler asked me to remove the automatically created column, which does not have a reference any more. This seems to be a solution for the physical model.
But: it seems to be neither possible to model this in the logical model directly nor is possible engineer the changes from the physical model back to the logical mode.
So what can I do?
I asked this question with some more concrete variable names at stackoverflow:
http://stackoverflow.com/q/13027950/402322
And this is the physical model after the modification explained above:
https://picasaweb.google.com/lh/photo/TCeW1Si0UOybltn34oIWj9MTjNZETYmyPJy0liipFm0

Hi,
you need to play with overlapping/folding attributes. Open properties dialog of entity D, go to "Overlapping attributes" page - you should see aid-aid1 pair listed. Check "fold" check box. Aid1 attribute will remain in entity but there will be no related column in relational model after forward engineering to it. You can change your decision during forward engineering - Data Modeler detects existence of overlapping keys and position engineering dialog on related tab.
Philip

Implementing two generic interfaces

I have a generic interface,
public interface Callback<R> {
   void result(R r);
}Now I want to implement two Callback interfaces, like this
class X implements Callback<Type1>, Callback<Type2> {
   public void result(Type1 r) {};
   public void result(Type2 r) {};
}But Eclipse tells me "The interface Callback cannot be implemented more than once with different arguments".
I don't see the reason why really. The two overloaded result methods have different signatures so there shouldn't be any problem in resolving the correct one based on parameter type in principle.
Does anybody know the reason for this restriction or is it maybe an issue with Eclipse. I'm using Eclipse 3.2M5a and Java 6.0 beta.

mlk has the correct answer, but here's some more explanation:
Generics are only used at compile time. The actual bytecode specifies the base object type (aka type erasure), in this case Object. When you implement a generified interface, the compiler will generate a bridge method from the erased type to the specific type.
Some examples should make this clearer.
First, your interface. If you run javap on the compiled class, you'll see that it only defines a single method, "void result(Object)".
Code that invokes the interface, like this:
    Callback<String> foo = \\
    foo.result("bar");also gets translated to a call on the base type. As far as the compiled class is concerned, there is no type safety. However, the compiler will complain if you pass something other than a String.
The implementation class is where things get interesting:
public class TestCallback implements Callback<String> {
public void result(String x) {
}If you run javap on this class, you'll see that it contains two implementations of result(): one that takes a String, and one that takes an Object. If you look at the bytecode, the latter performs a cast on the Object and invokes the String variant.

Error in video training - Implementing two-way binding

During the Video training for Implementing two-way binding you have a slight error.
If you follow along with the video training the instructor misses the step of assigning the Value Object(DTO) as Bindable.
The instructor goes from adding the "@" symbol to the bound selectedEmployee.salary to running the application and it runs fine. To do this in the code you need to add [Bindable] to the Value Object(DTO) Employee.
<s:TextInput id="salaryInput"
                         text="@{selectedEmp.salary}"/>
package valueObjects
    [Bindable] 
    public class Employee

Can you please file a bug at http://bugs.adobe.com/flex/ and post the bug number here.
Thanks,
Peter

How to implements two interface?

i have a applet to implement two interface,the actionlistener and the appletcontext.how to do it??
Thank You!

with a comma

How to implement one to many relationship between two Document Line Table

Hi,
I want to implement the following relationship into user defined tables:
Example Situation:
There are tables A, B and C.
For one record of Table A, there could be multiple records in table B.
For one record of Table B, there could be multiple records in table C.
i.e. A(1) -> B(n) [One to many relationship]
B(1) -> C(n) [One to many relationship]
finally: A(1) -> B(n) -> C(n)
How can I achieve this? If I make Table A as Document and table B & C as Document Line and then make them UDO, will it work? Kindly suggest me a solution.
Regards,
Sudeshna.

Hi,
I think that the database representation is exactly what you ask for. 3 tables, A, B, C. A should have a UDF that is linked to B table, and B should have a UDF that is linked to C table.
You should manage the database transactions, and the UI to support all this stuff.
Regards,
IBai Peñ

How to implement two dependent dropdown lists in an input table row?

Hi all,
I am new in Jdev 11g. I try to develop an input table with two dependent dropdown list. I can create independent dropdown list in such table. When I try to implement dependent one following some examples do it in a form using bind variable in the view object I get an empty listbox. How can I do this? Is it possible. I cannot find any documents about this.
Thanks in advance

Hi,
it hasn't changed between 10.1.3 and 11. The basic outline of how you do it is
- use a managed bean to query the data
- populate the list with f:selectItems that point to the managed bean ArrayList<SelectItem> for the master and the detail
- obtain the master ID in the managed bean by parsing the #{row} variable when the table renders
- then bulild the detail list
- have the detail list referencing the ArrayList<SelectItem> you expose for the details
Note that without proper caching, the action is quite expensive
Frank

How to implement a 1-n relationship

I'm using oracle 8.1 and currently learning JDO.
Havin the following schema :
DROP TABLE permission_group_map CASCADE CONSTRAINTS;
CREATE TABLE permission_group_map (
permission_group_map_oid NUMBER(10) NOT NULL,
version_oid NUMBER(3) NOT NULL,
group_oid NUMBER(10) NOT NULL,
permission_oid NUMBER(10) NOT NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL
ALTER TABLE permission_group_map
ADD ( CONSTRAINT PKpermission_group_map PRIMARY KEY (
permission_group_map_oid) ) ;
DROP TABLE permission CASCADE CONSTRAINTS;
CREATE TABLE permission (
permission_oid NUMBER(10) NOT NULL,
version_oid NUMBER(3) NOT NULL,
name VARCHAR2(60) NULL,
visibility NUMBER(1) NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL
ALTER TABLE permission
ADD ( CONSTRAINT PKpermission PRIMARY KEY (permission_oid,
version_oid) ) ;
DROP TABLE user_group CASCADE CONSTRAINTS;
CREATE TABLE user_group (
group_oid NUMBER(10) NOT NULL,
name VARCHAR2(60) NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL
ALTER TABLE user_group
ADD ( CONSTRAINT PKuser_group PRIMARY KEY (group_oid) ) ;
ALTER TABLE permission_group_map
ADD ( CONSTRAINT fk2_permission_group_map
FOREIGN KEY (group_oid)
REFERENCES user_group ) ;
ALTER TABLE permission_group_map
ADD ( CONSTRAINT fk1_permission_group_map
FOREIGN KEY (permission_oid, version_oid)
REFERENCES permission ) ;
How can represent a 1-n relation in a .jdo file without adding more fileds.
Here is my .jdo implementation
<class identity-type="application" name="UserGroup"
objectid-class="UserGroupKey" requires-extent="false">
<extension key="table" value="USER_GROUP" vendor-name="kodo"/>
<field name="name" null-value="exception" primary-key="false">
<extension key="data-column" value="NAME"
vendor-name="kodo"/>
<extension key="column-length" value="60"
vendor-name="kodo"/>
</field>
<field name="userId" null-value="exception"
primary-key="false">
<extension key="data-column" value="USER_ID"
vendor-name="kodo"/>
</field>
<field name="groupOid" null-value="exception"
primary-key="true">
<extension key="data-column" value="GROUP_OID"
vendor-name="kodo"/>
</field>
<field name="timestamp" null-value="exception"
primary-key="false">
<extension key="data-column" value="TIMESTAMP"
vendor-name="kodo"/>
</field>
<field name = "permissionGroupMap">
<collection element-type="PermissionGroupMap"/>
<extension vendor-name="kodo" key="inverse"
value="userGroup"/>
</field>
<extension key="lock-column" value="jdolock"
vendor-name="kodo"/>
<extension key="class-column" value="none" vendor-name="kodo"/>
</class>
<class identity-type="application" name="PermissionGroupMap"
objectid-class="PermissionGroupMapKey" requires-extent="false">
<extension key="table" value="PERMISSION_GROUP_MAP"
vendor-name="kodo"/>
<extension key="lock-column" value="jdolock"
vendor-name="kodo"/>
<extension key="class-column" value="none" vendor-name="kodo"/>
<field name="permissionGroupMapOid" null-value="exception"
primary-key="true">
<extension key="data-column"
value="PERMISSION_GROUP_MAP_OID" vendor-name="kodo"/>
</field>
<field name="userId" null-value="exception"
primary-key="false">
<extension key="data-column" value="USER_ID"
vendor-name="kodo"/>
</field>
<field name="permissionOid" null-value="exception"
primary-key="false">
<extension key="data-column" value="PERMISSION_OID"
vendor-name="kodo"/>
</field>
<field name="groupOid" null-value="exception"
primary-key="false">
<extension key="data-column" value="GROUP_OID"
vendor-name="kodo"/>
</field>
<field name="versionOid" null-value="exception"
primary-key="false">
<extension key="data-column" value="VERSION_OID"
vendor-name="kodo"/>
</field>
<field name="timestamp" null-value="exception"
primary-key="false">
<extension key="data-column" value="TIMESTAMP"
vendor-name="kodo"/>
</field>
</class>
and here is the class code
public class PermissionGroupMap {
java.math.BigDecimal permissionGroupMapOid;
java.lang.String userId;
java.math.BigDecimal permissionOid;
java.math.BigDecimal groupOid;
java.math.BigDecimal versionOid;
java.util.Date timestamp;
/** relationship fields **/
UserGroup userGroup;
public class UserGroup {
java.lang.String name;
java.lang.String userId;
java.math.BigDecimal groupOid;
java.util.Date timestamp;
/** relationship fields **/
ArrayList permissionGroupMap = new ArrayList();
Here is the exception that I'm getting :
javax.jdo.JDODataStoreException: [SQL=SELECT t0.PERMISSION_GROUP_MAP_OID,
t0.jdolock, t0.GROUP_OID, t0.PERMISSION_OID, t0.TIMESTAMP,
t0.GROUPOID_USERGROUPX, t0.USER_ID, t0.VERSION_OID FROM
PERMISSION_GROUP_MAP t0 WHERE t0.GROUPOID_USERGROUPX = 1] ORA-00904:
invalid column name

Thanks for you quick response, But I changed the schema a little bit, just
to play arround, now I'm doing a m-n, but it does not work, can you tell
me what I'm doing wrong, here is the schema :
CREATE TABLE user_group (
group_oid NUMBER(10) NOT NULL,
name VARCHAR2(60) NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL,
CONSTRAINT PKuser_group
PRIMARY KEY (group_oid)
CREATE TABLE permission (
permission_oid NUMBER(10) NOT NULL,
version_oid NUMBER(3) NOT NULL,
name VARCHAR2(60) NULL,
visibility NUMBER(1) NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL,
CONSTRAINT PKpermission
PRIMARY KEY (permission_oid, version_oid)
CREATE TABLE permission_group_map (
group_oid NUMBER(10) NOT NULL,
permission_oid NUMBER(10) NOT NULL,
version_oid NUMBER(3) NOT NULL,
CONSTRAINT PKpermission_group_map
PRIMARY KEY (group_oid, permission_oid, version_oid),
CONSTRAINT R_4
FOREIGN KEY (permission_oid, version_oid)
REFERENCES permission,
CONSTRAINT R_3
FOREIGN KEY (group_oid)
REFERENCES user_group
the .jod file :
<class identity-type="application" name="Permission"
objectid-class="PermissionKey" requires-extent="false">
<extension key="table" value="PERMISSION" vendor-name="kodo"/>
<field name="permissionOid" null-value="exception"
persistence-modifier="persistent" primary-key="true">
<extension key="data-column" value="PERMISSION_OID"
vendor-name="kodo"/>
<extension key="column-length" value="10"
vendor-name="kodo"/>
<extension key="column-index" value="pkPermission"
vendor-name="kodo"/>
</field>
<field name="versionOid" null-value="exception"
persistence-modifier="persistent" primary-key="true">
<extension key="data-column" value="VERSION_OID"
vendor-name="kodo"/>
<extension key="column-index" value="pkPermission"
vendor-name="kodo"/>
<extension key="column-length" value="3"
vendor-name="kodo"/>
</field>
<field name="userGroups">
<collection element-type="UserGroup"/>
<extension vendor-name="kodo" value="permissions"/>
<extension vendor-name="kodo" key="table"
value="PERMISSION_GROUP_MAP"/>
<extension vendor-name="kodo" key="groupOid-data-column"
value="GROUP_OID"/>
<extension vendor-name="kodo"
key="permissionOid-ref-column" value="PERMISSION_OID"/>
<extension vendor-name="kodo" key="versionOid-ref-column"
value="VERSION_OID"/>
</field>
<extension key="class-column" value="none" vendor-name="kodo"/>
<extension key="lock-column" value="jdolock"
vendor-name="kodo"/>
</class>
<class identity-type="application" name="UserGroup"
objectid-class="UserGroupKey" requires-extent="false">
<extension key="table" value="USER_GROUP" vendor-name="kodo"/>
<field name="name" null-value="exception" primary-key="false">
<extension key="data-column" value="NAME"
vendor-name="kodo"/>
<extension key="column-length" value="60"
vendor-name="kodo"/>
</field>
<field name="permissions">
<extension vendor-name="kodo" value="userGroups"/>
<extension vendor-name="kodo" key="table"
value="PERMISSION_GROUP_MAP"/>
<extension vendor-name="kodo" key="groupOid-ref-column"
value="GROUP_OID"/>
<extension vendor-name="kodo"
key="permissionOid-data-column" value="PERMISSION_OID"/>
<extension vendor-name="kodo" key="versionOid-data-column"
value="VERSION_OID"/>
</field>
<extension key="lock-column" value="jdolock"
vendor-name="kodo"/>
<extension key="class-column" value="none" vendor-name="kodo"/>
</class>
CODE :
public class Permission {
     java.math.BigDecimal visibility;
     java.lang.String name;
     java.lang.String userId;
     java.math.BigDecimal permissionOid;
     java.math.BigDecimal versionOid;
     java.util.Date timestamp;
private Collection userGroups = new ArrayList();
public class UserGroup {
     java.lang.String name;
     java.lang.String userId;
     java.math.BigDecimal groupOid;
     java.util.Date timestamp;
Collection permissions = new ArrayList();
Patrick Linskey wrote:
Manuel,
When mapping relations to pre-defined schemas using application identity,
you must use the '<fieldname>-data-column' extension syntax discussed in
http://www.solarmetric.com/Software/Documentation/2.2.6/manual.html#metadata
_extensions.
Additionally, in general, you should not have foreign key fields declared in
your java code as well as relations to other objects. For example, in
PermissionGroupMap, you should just have a relation to UserGroup, and no
groupOid field -- the foreign key information will be handled by JDO, and
should not be user-accessible except through the UserGroup relation.
So, something like this is probably more like what you want (I've removed
some fields for brevity):
<class identity-type="application" name="UserGroup"
objectid-class="UserGroupKey" requires-extent="false">
<field name="groupOid" null-value="exception" primary-key="true">
<extension key="data-column" value="GROUP_OID"
vendor-name="kodo"/>
</field>
<field name = "permissionGroupMap">
<collection element-type="PermissionGroupMap"/>
<extension vendor-name="kodo" key="inverse" value="userGroup"/>
</field>
</class>
<class identity-type="application" name="PermissionGroupMap"
objectid-class="PermissionGroupMapKey" requires-extent="false">
<field name="permissionGroupMapOid" null-value="exception"
primary-key="true">
<extension key="data-column" value="PERMISSION_GROUP_MAP_OID"
vendor-name="kodo"/>
</field>
<field name="userGroup" null-value="exception" primary-key="false">
<extension key="groupOid-data-column" value="GROUP_OID"
vendor-name="kodo"/>
</field>
</class>
public class PermissionGroupMap {
java.math.BigDecimal permissionGroupMapOid;
// this is not needed: java.math.BigDecimal groupOid;
/** relationship fields **/
UserGroup userGroup;
public class UserGroup {
java.math.BigDecimal groupOid;
/** relationship fields **/
ArrayList permissionGroupMap = new ArrayList();
On 6/8/02 11:56 AM, "Manuel Ledesma" <[email protected]> wrote:
I'm using oracle 8.1 and currently learning JDO.
Havin the following schema :
DROP TABLE permission_group_map CASCADE CONSTRAINTS;
CREATE TABLE permission_group_map (
permission_group_map_oid NUMBER(10) NOT NULL,
version_oid NUMBER(3) NOT NULL,
group_oid NUMBER(10) NOT NULL,
permission_oid NUMBER(10) NOT NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL
ALTER TABLE permission_group_map
ADD ( CONSTRAINT PKpermission_group_map PRIMARY KEY (
permission_group_map_oid) ) ;
DROP TABLE permission CASCADE CONSTRAINTS;
CREATE TABLE permission (
permission_oid NUMBER(10) NOT NULL,
version_oid NUMBER(3) NOT NULL,
name VARCHAR2(60) NULL,
visibility NUMBER(1) NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL
ALTER TABLE permission
ADD ( CONSTRAINT PKpermission PRIMARY KEY (permission_oid,
version_oid) ) ;
DROP TABLE user_group CASCADE CONSTRAINTS;
CREATE TABLE user_group (
group_oid NUMBER(10) NOT NULL,
name VARCHAR2(60) NULL,
jdolock NUMBER NULL,
user_id VARCHAR2(20) NULL,
timestamp DATE NULL
ALTER TABLE user_group
ADD ( CONSTRAINT PKuser_group PRIMARY KEY (group_oid) ) ;
ALTER TABLE permission_group_map
ADD ( CONSTRAINT fk2_permission_group_map
FOREIGN KEY (group_oid)
REFERENCES user_group ) ;
ALTER TABLE permission_group_map
ADD ( CONSTRAINT fk1_permission_group_map
FOREIGN KEY (permission_oid, version_oid)
REFERENCES permission ) ;
How can represent a 1-n relation in a .jdo file without adding more fileds.
Here is my .jdo implementation
<class identity-type="application" name="UserGroup"
objectid-class="UserGroupKey" requires-extent="false">
<extension key="table" value="USER_GROUP" vendor-name="kodo"/>
<field name="name" null-value="exception" primary-key="false">
<extension key="data-column" value="NAME"
vendor-name="kodo"/>
<extension key="column-length" value="60"
vendor-name="kodo"/>
</field>
<field name="userId" null-value="exception"
primary-key="false">
<extension key="data-column" value="USER_ID"
vendor-name="kodo"/>
</field>
<field name="groupOid" null-value="exception"
primary-key="true">
<extension key="data-column" value="GROUP_OID"
vendor-name="kodo"/>
</field>
<field name="timestamp" null-value="exception"
primary-key="false">
<extension key="data-column" value="TIMESTAMP"
vendor-name="kodo"/>
</field>
<field name = "permissionGroupMap">
<collection element-type="PermissionGroupMap"/>
<extension vendor-name="kodo" key="inverse"
value="userGroup"/>
</field>
<extension key="lock-column" value="jdolock"
vendor-name="kodo"/>
<extension key="class-column" value="none" vendor-name="kodo"/>
</class>
<class identity-type="application" name="PermissionGroupMap"
objectid-class="PermissionGroupMapKey" requires-extent="false">
<extension key="table" value="PERMISSION_GROUP_MAP"
vendor-name="kodo"/>
<extension key="lock-column" value="jdolock"
vendor-name="kodo"/>
<extension key="class-column" value="none" vendor-name="kodo"/>
<field name="permissionGroupMapOid" null-value="exception"
primary-key="true">
<extension key="data-column"
value="PERMISSION_GROUP_MAP_OID" vendor-name="kodo"/>
</field>
<field name="userId" null-value="exception"
primary-key="false">
<extension key="data-column" value="USER_ID"
vendor-name="kodo"/>
</field>
<field name="permissionOid" null-value="exception"
primary-key="false">
<extension key="data-column" value="PERMISSION_OID"
vendor-name="kodo"/>
</field>
<field name="groupOid" null-value="exception"
primary-key="false">
<extension key="data-column" value="GROUP_OID"
vendor-name="kodo"/>
</field>
<field name="versionOid" null-value="exception"
primary-key="false">
<extension key="data-column" value="VERSION_OID"
vendor-name="kodo"/>
</field>
<field name="timestamp" null-value="exception"
primary-key="false">
<extension key="data-column" value="TIMESTAMP"
vendor-name="kodo"/>
</field>
</class>
and here is the class code
public class PermissionGroupMap {
java.math.BigDecimal permissionGroupMapOid;
java.lang.String userId;
java.math.BigDecimal permissionOid;
java.math.BigDecimal groupOid;
java.math.BigDecimal versionOid;
java.util.Date timestamp;
/** relationship fields **/
UserGroup userGroup;
public class UserGroup {
java.lang.String name;
java.lang.String userId;
java.math.BigDecimal groupOid;
java.util.Date timestamp;
/** relationship fields **/
ArrayList permissionGroupMap = new ArrayList();
Here is the exception that I'm getting :
javax.jdo.JDODataStoreException: [SQL=SELECT t0.PERMISSION_GROUP_MAP_OID,
t0.jdolock, t0.GROUP_OID, t0.PERMISSION_OID, t0.TIMESTAMP,
t0.GROUPOID_USERGROUPX, t0.USER_ID, t0.VERSION_OID FROM
PERMISSION_GROUP_MAP t0 WHERE t0.GROUPOID_USERGROUPX = 1] ORA-00904:
invalid column name
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com

Stub compile failure when entity has two 1:1 relationships

I think I've found a bug in the Sun J2EE SDK (surprised? no, but looking for workaround...)
The stub code that is generated during deployment of my .ear file creates two "__reverse_item_uid" fields for my ItemBean entity.
This started when I added a second 1:1 relationship to my ItemBean. I have a PurchaseItem-Item relationship and have now added a SalesOrderItem-Item relationship. They are both 1:1 and unidirectional. See relevent section from ejb-jar.xml
<ejb-relation>
<ejb-relationship-role>
<ejb-relationship-role-name>PurchaseItem-Item</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>PurchaseItem</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>item</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>Item-PurchaseItem</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>Item</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
<ejb-relation>
<ejb-relationship-role>
<ejb-relationship-role-name>SalesOrderItem-Item</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>SalesOrderItem</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>item</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>Item-SalesOrderItem</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>Item</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
When I add my .jar to my application using the GUI of the deploytool, set everything up (jndi, generate sql, ...) run verifier is OK, and then deploy, the deploy will fail due to stub compilation failure.
If I then open up the sun-j2ee-ri.xml that is generated and found in my c:\j2sdkee1.3.1\repository\myname\applications\myapp1234.jar notice the use of two "__reverse_item_uid" fields in the following sample:
<ejb>
<ejb-name>Item</ejb-name>
<jndi-name>Item</jndi-name>
<gen-classes />
<ejb20-cmp>
<sql-statement>
<operation>storeRow</operation>
<sql>UPDATE "ItemBeanTable" SET "__reverse_item_uid" = ? , "__reverse_item_uid" = ? , "itemType" = ? , "location" = ? , "name" = ? , "peachID" = ? , "price1" = ? , "price2" = ? , "price3" = ? , "unitmeasure" = ? , "version" = ? WHERE "uid" = ? </sql>
</sql-statement>
GRRRRR!!!!! What do I do to avoid this? Can't the Sun Ref Impl generate this and the stub code smarter so that it does something like use the <ejb-relationship-role-name> as the fieldname?
Any help would be greatly appreciated :)
-Gretel

I figured it out... here's the answer in case anyone is wondering...
Use different field names for 'item' in both PurchaseItem and SalesOrderItem. In other words, here is the correct segment of ejb-jar.xml
<ejb-relation>
<ejb-relationship-role>
<ejb-relationship-role-name>SalesOrderItem-Item</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>SalesOrderItem</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>itemHack</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>Item-SalesOrderItem</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>Item</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
Simply by changing the <cmr-field-name>itemHack</cmr-field-name> from 'item' to 'itemHack' :)
Sometimes in the land of EJB development, it's the "easy" things that can waste a lot of time.

Implement two way replication on few tables

Is there a way where I can implement 2 way replication.
For instance I've two database A and B
In a table in database A get updated or changed ..the effect should be shown on B
and vice versa....
Need ideas...

* Oracle edition (enterprise, standard),
Enterprise edition
* network connectivity (is there a stable network link between the two),
Yes we have a stable network
* latency requirements (how quickly does a change on one have to appear on the other), and
probably every 3 hrs
* business requirements (why are you replicating the data in the first place)
Well ours is call center, we work according to the availability of the interpereters and also we keep change pricing of call on daily basis.
So there are few tables which needed to be updated regularly.

Implementing Two Guest Anchor WLCs

Hello -
I am wondering if anyone has ever setup a guest network solution using two anchor controllers where the internal WLCs each have two anchors configured and use a primary Anchor and when unavailable can dynamically fail over to a secondary Anchor.
I am looking to bring my current guest service onto the DMZ. Right now we are using separate ISPs where we tunnel the guest traffic to an anchor controller and out the separate ISP. We do not use our corporate internet service for guest. In any event. The DMZ design I am working on would include two WLCS sitting on our DMZ. I'd like to have each internal WLC configured to associate to the DMZ WLC that is connected to our active DMZ/Border. Upon failure, I would then like to have the internal WLCs failover to the second DMZ WLC on our standby DMZ/Border. So I would need to configure both anchors on the guest WLAN of each WLC. I'm just wondering if this is possible and if the failover will actually work.
Any input is appreciated. I'd like to implement a redundant guest solution where internal WLCS can dynamically failover to a backup Anchor....
Thanks
Chuck

Hi, I just got done moving our anchors to the DMZ so you are in luck as everything is fresh in my mind. I, like you, have dual anchors in the DMZ I also have over 30 inside (foreign controllers) connected to these anchors.
When you anchor a WLAN to (2) anchor controllers, the controllers automagically load balance guest associations. Example: 2 guest attached to SSID: GUEST. Guest#1 goes to anchor#1 and guest #2 goes to anchor#2. You dont configure anything, this happens automagically, like I mentioned.
As for failover. Yes, if you pull the plug to anchor#1. The EoIP tunnel breaks between the anchor and the foreign controller. Guest that were on anchor#1 will require reauthentication and then join to anchor#2.So if you had say a "accept page", these guest will get that same page again from anchor 2.
Does that answer your question?

Class implementing two interfaces with same methods

interface Foo {
public void execute();
interface Bar {
public void execute();
class Dam implements Foo, Bar {
public void execute() {
//Which interface's execute method is being called here?
How do I make the Damn class have different implemenations for the execute method of the Foo and the Bar interfaces?

hi,
//Which interface's execute method is being calledinterfaces' method are neither called to be executed by the JVM because they're not concrete implementation but only signature declaration.
How do I make the Damn class have different
implemenations for the execute method of the Foo and
the Bar interfaces?this can't be done if the signatures are the same, but if they're not, for instance
public void execute( int i )
public void execute( String s )
then you can have two implementation...anyway, what's the point if the signature are the same ? if you really want them to do different things why wouldn't you name them differently ?
raphaele

2013 Design implementation-two sites

Hi!
I have a design implementation question. We are a small firm with 80 AD users, 100 mailboxes, DB store is 200 gigs and all on Exchange 2007 (Virtualized connecting to a SAN), but growing rapidly. Also, we currently have two sites in Chicago and New York(Exchange
2007 server in NY). We would like to upgrade from 2007(all roles installed on a VM server ESX 5.5 server) to 2013. Should we virtualized the Exchange 2013 or should they be physical servers? Also, since the servers will be in separate sites will I need a Load
Balancer in both location? Also, should I split up the roles since we have two locations running the both roles on both servers. For example below:
1 Chicago server-CAS/Mailbox Role
1 New York server-CAS/Mailbox Role
Should I have the Chicago users connect to the Chicago Server? And the New York users pointed to the New York Server? Currently everyone connects to the mail sever in NY. Any advice or comments would be appreciated.
Thanks!

Hi,
Yes, if you need proxy or redirection settings on OWA and other Exchange web services, one CAS in each site is must.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

How can I implement two TCP/IP servers (on two separate machines) and one TCP/IP client (on third machine)

I have an application where I need to send data via TCP/IP from two separate machines to a third machine. The machines are on a local area network connected through a network switch. The data are generated independently through data acquisition by the two independent machines before are sent to the client on third machine. Each machine has one network card. Thanks.
Solved!
Go to Solution.

If you have three separate machines, you don't need to use separate ports. They will have three IP addresses.
Remember this rule: TCP connections are EXACTLY like telephone connections.
Have your client open two connections: same port on two different IP addresses.
Each client listens for connections.
After connections are established, you get to decide the protocol: maybe the client should explicitly ask for data, maybe the servers just dump it without being asked. It's up to you.
Read this:
TCP tips and tricks
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Implementing two 1:M relationships

Similar Messages

Maybe you are looking for