[solved] JPA - persisting parent & child entities in one hit

Hi,
I have an object say, "Bus" and it has a one to many relationship to another object, "Commuter". Suppose i create one Bus instance and one commuter instance and associate them to each other and i want them to save to the database and store the relationship via a foriegn key relationship in the Commuter table, what would the pojo look like? What exact annotations would i require for it to work. Working examples appreciated!

Thanks for the link, and thats exactly why i want to do this (adf).
However, the sample does not demonstrate the code for creating a new Department with a Employee at the same time, and wiring up the relational foriegn key.
Any ideas on how to extend this example to do this? I'd like a form create one entity of each in one action. I followed some advise before to create my own persist() function which persists the Employee object first, then the Department object.
They both successfully persist but the foriegn key does not get mapped in the table. Any sample code available?

Similar Messages

Parent Child relation in one transaction throws error... (

In nutshell, I have a parent->child relation ship in DB and due to the UI requirement, I created view link as Child->parent, it is giving a hack a lot of problems.... (it sounds silly but looks like I am loosing my mind over this)
Let me explain my situation,
- I have a table A with col-a and col-b. I have another table B with col-a (primary key) and col-c. (This way table A is a parent table)
- ON UI side i created relationship like table B is parent and Table A is child using col-a
- I need to create parent-child (one record for each) record programatically.........
I tried following thing:
- from backing bean, as soon as i create Table-B row first, i get error saying too many objects with same key (which is understandable because of table design..... and associaion must be throwing that error)
- from EOImpl file, it doesn't even find the child record being created... so during commit I can't send the foreign key value from Table-a to Table-b
Any suggestion is greatly appreciated?
Thank you,
-Raj

that depends on how you implement the multiple selection of orders.. you have to pass the selectedValues to the backend or store the values in a map or list and pass it..

Incorrect totals from cache with CustomRollupColumn and non-parent-child dimensions

Hello. Before I start let me apologise for my English :)
We have a very complex cube, with 2 (actually more, but only these 2 are important) parent-child dimensions.
One of them has CustomRollupColumn defined.
Not long ago we have decided to make refactoring of our cube. This also included making these dimensions non-parent-child.
All our old reports started to work much faster after that... but we have mentioned that sometimes they show incorrect totals, or no totals at all.
We spend a lot of time trying to figure out what's wrong and finally we had found that if we clear cache before next refresh of the report - the totals are always correct!
If we don't clear cache - we get wrong totals second time, and each next time after that. If we see wrong totals - we could clear cache and get correct totals once again.
If we use "Real Time Olap=True;" connection string parameter - the totals are always correct because cache is not used.
But we don't like this workaround.
Is there any fix for this bug? Google shows that this problem exists from SQL2005, and still we have it :( Also, there is adivice to set CalculationCoverPolicy to 9 - we have tried - but it was fruitless.
And if we revert these 2 dimensions back to parent-child - all working fine again, but as slow as it was before the refactoring :(

Hi Bateks,
Glad to hear that your issue had been solved by yourself, thank you for you sharing which will help other forum members who have the similar issue.
Regards,
Charlie Liao
TechNet Community Support

How to achieve parent - child record insert in forms

Guys,
I am new to forms. I do have a requirement where I need to create one tabular block for 10 rows (parent record) and then I need to create three tabular tabs of 5 rows for detailed records (child). That means each tab can have 5 records for 1 parent row.. Thats how this parent-child structure has ONE to MANY relationships
To achieve this requirement I created one parent block of table type (using table XX_Parent) and then I created three detailed block for each tab (Tab_A,Tab_B,Tab_C) using child table (XX_Child). For each tab while inserting the data I took one context_value column in child table. i.e. when I insert the data using Tab_A , context_value column will be A. In the same way B and C for Tab_B for Tab_C respectively. And I wrote this logic at PRE-INSERT trigger for each tab. But when I insert the data for all the tabs, it allows me to enter successfully for Tab_A only, the moment I navigate from Tab_A to enter the data intoTab_B, it throws me error like "You are passing NULL value to set context_value". I hope I make the requirement clear to you.
I am not sure if I am following the right approach to achieve my requirement. if its not right, please suggest me right one.. and if its right please guide me resolve the error..
Looking forward to your reply.
Thanks
Sunil

Andreas,
I had already created relations between Matster Block -Tab_A block, Master Block -Tab_B block and Master Block - Tab_C block...
The point is all the three tabs are created using one table XX_Child only.. I used context_value A,B and C respectively so that once I query the data for XX_Child from backend, I should be in a position to figure out what data is inserted using Tab A, B and C. why I need so .. because If take my entire form in query mode and search for a master record.. then Tab_A, tab_B and Tab_C display their respective data. I hope, I make you understand.. Can you please guide me.
Thanks
Sunil

Parent Child list form using infopath 2013

Hi All
I have two SharePoint list heaving parent child relation ship ( one parent have multiple child) now i want to create a single form in info path 2013 using code less solution . I am using SharePoint Online don't want to use c# code.
Journey Man

Hi,
Please check this
https://www.sharepointdrive.com/blog/how-to-establish-a-parent-child-relationship-in-sharepoint/
http://sharepoint.stackexchange.com/questions/6493/how-to-automatically-link-parent-in-child-list-new-form
Please remember to click 'Mark as Answer' on the answer if it helps you

Best way to add additional parent child attribute values.

I have a parent Child attribute in my dimension. I am currently displaying the correct ID value as the business wants. So now they can see the rollup of the ID(intOrgNodeID
values.They would also like to see the same rollup of the Name (vcharOrgNodeName) for this ID.However they do
not want it concatenated. They want to be able to see them separate.
You cannot create two parent child attibutes in one dimension so not sure if there is some simple trick to make this work?
It seems like there should be some simple trick for this.
My dimension table looks something like this
intdimOrgNodeID int Key (surreget key)
intOrgNodeID int (Actual ID)
intDimParentOrgNodeID
vcharOrgNodeName
In the Propertys I have set this below.
KeyColumns = tbldimOrgNode.intDimParentOrgNodeID
NameColumn = tbldimOrgNode.intOrgNodeID
Ken Craig

Hi Ken,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Charlie Liao
TechNet Community Support

Parent Child Hiearchy - Expand/Collapse problems

Hello,
We are on 11.1.1.6 and have built a parent child hierarchy on one of our dimensions. Navigation of the hierarchy works just fine if no measures are included. When a measure is added, the hierarchy becomes nearly unnavigable. That is to say clicking on the plus/minus signs doesn't work. Clicking in various locations of the screen can sometimes get it to work but it is ridiculously hard to get anywhere. The fact table from which the measure is pulled is very small, approx. 100,000 rows so we don't see that as the problem.
Has anybody else seen such a problem?
Thanks.

Can you provide more info on this, how have you modeled the hierarchy with the fact table, are you rolling up the measures for the child to the parent level (modeling as measures) or each employee is showing its own revenue only (modeled as attribute)? If it is modeled as measures where you join the employee table to the closure table and then that to fact table then are you applying any filters in your report ? If you are applying filters in your report and somehow only parent is filtered (and not its children) then you won't be able to drill down, though you will see the + sign against it.

Parent-child hierarchy and fragmentation content

Hello,
I've tried to build simple model with OBIEE 11 using Oracle 11r2 as a data source. BMM has fragmentation content for fact table and few dimensions with different hierarchy types. It works fine with all hierarchy types except for parent child.
When I build an answer with parent child hierarchy it terminates with error "Target data source does not support the operation".
Does OBIEE 11 not support parent child with fragmentation content? Or am I missing something?
Greetings
Marcin

I'm seeing the same issue. I've created a parent-child hierarchy along with two normal level-based hierarchies (one "normal", one skipped-level). The two level-based hierarchies work just fine in Answers. I can include them in the criteria, and data is displayed with the correct drilldowns.
If I include the parent-child hierarchy, I get the same results as noted in the original post: "The layout of this view combined with the data, selections, or drills, or prompt values chosen, resulted in no data." I'm trying to look at the table view, with no filters.
Interestingly, I can explicitly include that dimension's Parent column and Member column in the criteria, and data is displayed just fine.
Here is the XML for the set of criteria that includes the separate Parent and Member columns (the one that works):
SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10, s_11 FROM (
SELECT
0 s_0,
"Retro_Biz"."Channels"."MEMBER" s_1,
"Retro_Biz"."Channels"."PARENT" s_2,
"Retro_Biz"."Products"."TOTAL_PRODUCT" s_3,
"Retro_Biz"."Times"."YEAR" s_4,
SPACE(1) s_5,
SPACE(1) s_6,
SPACE(1) s_7,
IDOF("Retro_Biz"."Products"."Product"."Total Product") s_8,
IDOF("Retro_Biz"."Times"."Time"."Year") s_9,
"Retro_Biz"."Facts"."SALES" s_10,
CAST(NULL AS DOUBLE) s_11
FROM "Retro_Biz"
UNION ALL
SELECT
1 s_0,
"Retro_Biz"."Channels"."MEMBER" s_1,
"Retro_Biz"."Channels"."PARENT" s_2,
SPACE(1) s_3,
SPACE(1) s_4,
SPACE(1) s_5,
SPACE(1) s_6,
SPACE(1) s_7,
SPACE(1) s_8,
SPACE(1) s_9,
CAST(NULL AS DOUBLE) s_10,
REPORT_SUM("Retro_Biz"."Facts"."SALES" BY ) s_11
FROM "Retro_Biz"
) djm ORDER BY 1, 5 ASC NULLS FIRST, 4 ASC NULLS FIRST
Here is the XML that includes the Parent-Child hierarchy (the one that fails):
SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10, s_11, s_12 FROM (
SELECT
0 s_0,
"Retro_Biz"."Channels"."MEMBER" s_1,
"Retro_Biz"."Products"."TOTAL_PRODUCT" s_2,
"Retro_Biz"."Times"."YEAR" s_3,
CASE WHEN ISLEAF("Retro_Biz"."Channels"."Channel") THEN 1 ELSE 0 END s_4,
IDOF("Retro_Biz"."Channels"."Channel") s_5,
SPACE(1) s_6,
SPACE(1) s_7,
SPACE(1) s_8,
IDOF("Retro_Biz"."Products"."Product"."Total Product") s_9,
IDOF("Retro_Biz"."Times"."Time"."Year") s_10,
PARENT("Retro_Biz"."Channels"."Channel") s_11,
"Retro_Biz"."Facts"."SALES" s_12
FROM "Retro_Biz"
WHERE
ISROOT("Retro_Biz"."Channels"."Channel")
UNION ALL
SELECT
1 s_0,
SPACE(1) s_1,
SPACE(1) s_2,
SPACE(1) s_3,
CAST(NULL AS INTEGER) s_4,
SPACE(1) s_5,
SPACE(1) s_6,
SPACE(1) s_7,
SPACE(1) s_8,
SPACE(1) s_9,
SPACE(1) s_10,
SPACE(1) s_11,
"Retro_Biz"."Facts"."SALES" s_12
FROM "Retro_Biz"
WHERE
ISROOT("Retro_Biz"."Channels"."Channel")
) djm ORDER BY 1, 4 ASC NULLS FIRST, 3 ASC NULLS FIRST

UCCE Parent-Child question

Dear Networkers,
I have a question concerning the capacity ICM Parent Child deployement :
For one UCCE Parent how many UCCE Child can we deploy ? What is the max capacity for one UCCE Parent to support UCCE Childs ?
Is there a tool that can be used or a document to refer to ?
Thanks a lot in advance.
Best Regards.

Hi,
Page of 41 "Cisco Unified Contact Center Enterprise 8.x SRND" tates,
The Unified CCE Gateway PG can connect to a Unified CCE child that is using the Unified CCE System PG or to Unified CCX. If the Unified CCE child has multiple Unified CCE System PGs and peripherals, a separate Unified CCE Gateway PG peripheral must be installed and configured for each one in the Unified ICM parent system. When deployed on a separate server, a Unified CCE Gateway PG can manage multiple child Unified CCE peripherals or multiple child Unified CCX systems (up to five child systems).
Hope it helps,
Anand

JPA One-To-Many Parent-Child Mapping Problem

I am trying to map an existing legacy Oracle schema that involves a base class table and two subclass tables that are related by a one-to-many relationship which is of a parent-child nature.
The following exception is generated. Can anybody provide a suggestion to fix the problem?
Exception [EclipseLink-45] (Eclipse Persistence Services - 2.0.0.v20091127-r5931): org.eclipse.persistence.exceptions.DescriptorException
Exception Description: Missing mapping for field [BASE_OBJECT.SAMPLE_ID].
Descriptor: RelationalDescriptor(domain.example.entity.Sample --> [DatabaseTable(BASE_OBJECT), DatabaseTable(SAMPLE)])
The schema is as follows:
CREATE TABLE BASE_OBJECT(
"BASE_OBJECT_ID" INTEGER PRIMARY KEY NOT NULL,
"NAME" VARCHAR2(128) NOT NULL,
"DESCRIPTION" CLOB NOT NULL,
"BASE_OBJECT_KIND" NUMBER(5,0) NOT NULL );
CREATE TABLE SAMPLE(
"SAMPLE_ID" INTEGER PRIMARY KEY NOT NULL,
"SAMPLE_TEXT" VARCHAR2(128) NOT NULL )
CREATE TABLE SAMPLE_ITEM(
"SAMPLE_ITEM_ID" INTEGER PRIMARY KEY NOT NULL,
"SAMPLE_ID" INTEGER NOT NULL,
"QUANTITY" INTEGER NOT NULL )
The entities are related as follows:
SAMPLE.SAMPLE_ID -> BASE_OBJECT.BASE_OBJECT_ID - The PKs that are used to join the sample to the base class
SAMPLE_ITEM.SAMPLE_ITEM_ID -> BASE_OBJECT.BASE_OBJECT_ID - The PKs that are used to join the sample item to the base class
SAMPLE_ITEM.SAMPLE_ID -> SAMPLE.SAMPLE_ID - The FK that is used to join the sample item to the sample class as a child of the parent.
SAMPLE is one to many SAMPLE_ITEM
The entity classes are as follows:
@Entity
@Table( name = "BASE_OBJECT" )
@Inheritance( strategy = InheritanceType.JOINED )
@DiscriminatorColumn( name = "BASE_KIND", discriminatorType = DiscriminatorType.INTEGER )
@DiscriminatorValue( "1" )
public class BaseObject
extends SoaEntity
@Id
@GeneratedValue( strategy = GenerationType.SEQUENCE, generator = "BaseObjectIdSeqGen" )
@SequenceGenerator( name = "BaseObjectIdSeqGen", sequenceName = "BASE_OBJECT_PK_SEQ", allocationSize = 1 )
@Column( name = "BASE_ID" )
private long baseObjectId = 0;
@Entity
@Table( name = "SAMPLE" )
@PrimaryKeyJoinColumn( name = "SAMPLE_ID" )
@AttributeOverride(name="baseObjectId", column=@Column(name="SAMPLE_ID"))
@DiscriminatorValue( "2" )
public class Sample
extends BaseObject
@OneToMany( cascade = CascadeType.ALL )
@JoinColumn(name="SAMPLE_ID",referencedColumnName="SAMPLE_ID")
private List<SampleItem> sampleItem = new LinkedList<SampleItem>();
@Entity
@Table( name = "SAMPLE_ITEM" )
@PrimaryKeyJoinColumn( name = "SAMPLE_ITEM_ID" )
@AttributeOverride(name="baseObjectId", column=@Column(name="SAMPLE_ITEM_ID"))
@DiscriminatorValue( "3" )
public class SampleItem
extends BaseObject
@Basic( optional = false )
@Column( name = "SAMPLE_ID" )
private long sampleId = 0;
Edited by: Chris-R on Mar 2, 2010 4:45 PM

Thanks for the thoroughness. There was a mistake in moving the code over for the forum. The field names are correct throughout the original source code.
BASE_OBJECT_ID is used throughout.
I suspect the problem lies in the one-to-many sampleItem(s) relationship that is based upon the subclassed item class. (The relationship is actually "sampleItems" in the real code and somehow got changed in the move over.)
The problem may lie in the mapping of the attribute override in the child class to the referencing of the item class from the parent side of the relationship in the Sample class.
I further suspect this may be specific to Eclipselink based upon other postings I've seen on the web that have similar problems...
Any thoughts?
Edited by: Chris-R on Mar 3, 2010 9:56 AM

Why in case of parent child relation iterator fetching one duplicate record

Hi,
JDev Ver : 11.1.1.2.0
Technology : JPA/TopLik Service Facade Data Control (Without using BC4J)
I have created JPA/TopLink service facade from DB Tables and on facades I have crated DataControl which I have draged and droped on my screen to create input text, table etc.
In my application, I have many tables having one to many relationships. (Primarykey foreign key).
When I add more then one child columns (foreign key columns) for any one parent column (primary key column), in db its getting inserted properly but in iterator after refreshing also it showing one duplicate entry instead of actual entry.
e.g.
For one Account Id 1234 (primary key) , I am adding 3 account holders name (abc, xyz, pqr) in this case in db its inserting proper 3 entries but in iterator its showing
1234 abc
1234 xyz
1234 abc
so instead of pqr its again showing abc.
To select account holders name I have used selectManyShuttle components.
I have also tried tried dciter.refresh(DCIteratorBinding.RANGESIZE_UNLIMITED); to refresh iterator.
This is generic problem on most of the screen in my application where parent child relation comes.
regards,
devang

Hi,
Thanks for your reply. I just emailed the screen shot to your email . Please verify and let me know your comment.
Regards,
Kiran Konjeti

Wrong File(parent, child) behaviour on Windows when child starts with one s

I've sent following problem report:
A DESCRIPTION OF THE PROBLEM :
On Windows when relative path starts from one slash it should be resolved from current disk (not current directory). This behaviour should be preserved for Files constructed with constructor File(parent, child). So results of run "System.out.println(new File(dir, relPath).getAbsolutePath())" and "System.out.println(new File(relPath).getAbsolutePath())" should be identical when running program from directory "dir".
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Compile and run from directory C:\temp\relpath following code:
import java.io.*;
public class Main {
     public static void main(String[] args) throws Exception {
          System.out.println(new File("C:\\temp\\relpath", "\\temp\\relpath\\Main.java").getAbsolutePath());
          System.out.println(new File("\\temp\\relpath\\Main.java").getAbsolutePath());
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
C:\temp\relpath>java Main
C:\temp\relpath\\Main.java
C:\temp\relpath\Main.java
ACTUAL -
C:\temp\relpath>java Main
C:\temp\relpath\temp\relpath\Main.java
C:\temp\relpath\Main.java
The answer was:
I have been analyzing your problem and it is not a bug but the intended behavior of the API.
The File(File,String) constructor includes this in the specification:
"If the |child| pathname string is absolute then it is converted into a relative pathname in a system-dependent way."
In the example provided here, the child path is absolute so it is converted into a relative path. This is the intended behavior.
My comments:
First, child pathname is not absolute. Even so, I don't understand why this guy contend that this behavior is correct.
Please comment this!

Please comment this!
I've sent following problem report:
A DESCRIPTION OF THE PROBLEM :
On Windows when relative path starts from one slash
it should be resolved from current disk (not current
directory). This behaviour should be preserved for
Files constructed with constructor File(parent,
child). So results of run "System.out.println(new
File(dir, relPath).getAbsolutePath())" and
"System.out.println(new
File(relPath).getAbsolutePath())" should be identical
when running program from directory "dir".
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Compile and run from directory C:\temp\relpath
following code:
import java.io.*;
public class Main {
public static void main(String[] args) throws
s Exception {
System.out.println(new File("C:\\temp\\relpath",
", "\\temp\\relpath\\Main.java").getAbsolutePath());
System.out.println(new
ew
File("\\temp\\relpath\\Main.java").getAbsolutePath());
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
C:\temp\relpath>java Main
C:\temp\relpath\\Main.java
C:\temp\relpath\Main.java
ACTUAL -
C:\temp\relpath>java Main
C:\temp\relpath\temp\relpath\Main.java
C:\temp\relpath\Main.java
The answer was:
I have been analyzing your problem and it is not a
bug but the intended behavior of the API.
The File(File,String) constructor includes this in
the specification:
"If the |child| pathname string is absolute then it
is converted into a relative pathname in a
system-dependent way."
In the example provided here, the child path is
absolute so it is converted into a relative path.
This is the intended behavior.
My comments:
First, child pathname is not absolute. Even so, I
don't understand why this guy contend that this
behavior is correct.
*/

Recursive Parent Child relationship in JPA

@Entity
@Table(name = "OBJECTCATEGORY")
public class ObjectCategory implements Serializable {
     @Id
     private String categoryId;
     private String categoryName;
     private String description;
     private static final long serialVersionUID = 1L;
     @ManyToMany(fetch = FetchType.EAGER)
     @JoinTable(name = "MAP_CATEGORY", joinColumns = @JoinColumn(name = "CATEGORYID"), inverseJoinColumns = @JoinColumn(name = "OBJECTID"))
     private List<MapC> mapList = new ArrayList<MapC>();
// Recursion
     @OneToMany(fetch = FetchType.LAZY, mappedBy = "fqQuesCatagory")
     List<ObjectCategory > categoryList = new ArrayList<ObjectCategory>();
     @ManyToOne
     @JoinColumn(name = "PARENTCATEGORY")
     private ObjectCategory fqQuesCatagory
// Recursion
     public FqQuesCatagory() {
          super();
     public String getCategoryname() {
          return this.categoryname;
     public void setCategoryname(String categoryname) {
          this.categoryname = categoryname;
     public String getDescription() {
          return this.description;
     public void setDescription(String description) {
          this.description = description;
     public List<MapC> getMapList() {
          return faqList;
     public void setFaqList(List<MapC> faqList) {
          this.mapList = mapList ;
     public String getCategoryid() {
          return categoryId;
     public void setCategoryid(String categoryid) {
          this.categoryid = categoryId;
     public List<ObjectCategory> getFqCategoryList() {
          return categoryList;
     public void setFqCategoryList(List<ObjectCategory> categoryList) {
          this.categoryList = categoryList;
     public ObjectCategory getFqQuesCatagory() {
          return fqQuesCatagory;
     public void setFqQuesCatagory(ObjectCategory fqQuesCatagory) {
          this.fqQuesCatagory = fqQuesCatagory;
Doesn't SAP JPA support recursive parent-child relationship (highlighted by "// Recursion"). The same model works in TopLink perfectly.

Sorry for the delayed update..
I see an issue in the WSNavigator. I have a method in my EJB exposed as a web service. This method has a single argument, which is a serializable class containing a few string variables and the above-mentioned Entity with suitable getters and setters for all the class variables.
When I try to select this operation under the WSDL in the Webservice Navigator, I get a stack overflow error. I think it is because WD4J run-time is not able to build the nested tree. Not sure though...I've attached the stack trace below:
Cannot send an HTTP error response [500 "Application error occurred during the request procession." (details: java.lang.StackOverflowError
at java.lang.String.lastIndexOf(String.java:1496)
at java.lang.String.lastIndexOf(String.java:1458)
at com.sap.dictionary.runtime.StringUtil.getPackageName(StringUtil.java:143)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:179)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler._getScalarType(DictionaryHandler.java:447)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:159)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:447)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:746)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:759)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder.createParameterNodeInfo(DWSContextBuilder.java:984)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder.access$400(DWSContextBuilder.java:88)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1591)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createComplexTypeObject(DWSContextBuilder.java:1660)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForComplexType(DWSContextBuilder.java:1615)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.buildContextForTypeObject(DWSContextBuilder.java:1574)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createElementObject(DWSContextBuilder.java:1763)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.createFieldObject(DWSContextBuilder.java:1681)
at com.sap.esi.esp.wsnavigator.helper.DWSContextBuilder$DInputParams.intWithStructureFields(DWSContextBuilder.java:1671)
Any thoughts on this will be highly appreciated.
BR.

Toplink ORM parent-child relationship (one-to-many assoc)

Hello,
I'm having some problems changing the parent object of a child object. Can someone point me in the right direction?
the parent class:
public class Parent {
private List<Child> children;
the child class:
public class Child {
private ValueHolderInterface parent;
The children collection is privately owned by Parent.
the code to change the parent:
Child theChild = getTheChild();
Parent oldParent = theChild.getParent();
oldParent.getChildren().remove(theChild);
theChild.setParent(null);
Parent newParent = getTheNewParent();
theChild.setParent(newParent);
newParent.getChildren.add(theChild);
UnitOfWork uow = getSessionFactory().acquireUnitOfWork();
Object workingCopy = uow.readObject(theChild);
if (workingCopy == null) {
throw new RuntimeException("Could not find entity to update");
uow.deepMergeClone(theChild);
uow.commit();
The logs show that Toplink updates the parent_id of the child row (which I expect).
But after that Toplink deletes the child and then deletes the old parent (which I don't expect).
What is the correct way to update the parent of the child?

Hello,
Sounds like you have the bidirectional relationship set as privately owned on the child->parent relationship as well as on the parent->child.
I noticed in your code you are merging theChild into the uow, but not the oldParent. Depending on how you are getting theChild and oldParent objects (I hope you aren't making changes directly on objects in the cache), the changes to oldParent will not be picked up unless you merge them into the uow as well.
What looks like is happening is that when you null out the child->oldParent relation and then set a new parent, this forces TopLink to remove the oldParent (since I believe this relationship is privately owned). Since the oldParent still references theChild and the relationship is privately owned, theChild is also marked for deletion.
You might not want relationships marked as privately owned, since it indicates that the referenced objects cannot exist without the object referencing it. Unsetting the child->parent relation to be private owned should fix the problem, but you will still need to ensure the changes in oldParent are merged. I would suggest that right after you call getTheChild() you acquire a uow, read theChild and then work directly on the working copy instead of theChild object. This will remove the need to merge changes later. If that is not possible, just be sure to merge the oldParent in as well.
Best Regards,
Chris

How to model parent child relationship with DPL? @Transient?

Hello All,
I want to model a parent entity object with a collection of child entities:
@Entity
public class Parent{
@PrimaryKey
String uuid;
List<Child> children;
@Entity
public class Child{
@PrimaryKey
String id;
I know that the DPL won't support automatic persistence where it'll recursively go through my parent bean and persist my children with one call. Is there a way of applying the equivalent to JPA's @Transient annotation on "children" so I can persist the children manually and have the engine ignore the collection?
If not and I want to return to the user a Parent with a List named "children," do I have to create a new object which is identical to Parent, but doesn't have the BDB annotations and manually assemble everything? If possible, I'd like to avoid defining redundant objects.
Thanks in advance,
Steven
Harvard Children's Hospital Informatics Program
Edited by: JavaGeek_Boston on Oct 29, 2008 2:22 PM

Hi Steven,
The definition of persistence is here:
http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/persist/model/Entity.html
And includes this: "All non-transient instance fields of an entity class, as well as its superclasses and subclasses, are persistent. static and transient fields are not persistent."
So you can use the Java transient keyword. If that isn't practical because you're using transient in a different way for Java serialization, see the JE @NotPersistent annotation.
In general a parent-child relationship between entities is implemented almost as you've described, but with a parentId secondary key in the Child to index all children by their parent. This enables a fast lookup of children by their parent ID.
I suggest looking at this javadoc:
http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/persist/SecondaryIndex.html
as it describes all types of entity relationships and the trade-offs involved. The department-employee relationship in these examples is a parent-child relationship.
--mark

[solved] JPA - persisting parent & child entities in one hit

Similar Messages

Maybe you are looking for