Check the object model attached. Parent has reference to firstSeqChild and then onward the seqChild object keeps the reference to next seqChild, hence creating a linked list.
Problem: Hibernate saveOrUpdate fails with StackOverflow exception if the parent has approx 300 transient seqChildren (due to cascade save effect).
Is there anyway to bypass this problem? I am expecting this seqChildren list to be in thousands in actual implementation.
Another obvious thought I had was to convert the parent seqChild relationship to a "one to many" and use sorted set based on a new index column. but that does not server the purpose becuase an object can be inserted in between the chain (linked list). "it is mandatory for every seqChild to know its preceeding and follwoing seqChild". Design changes, that does not contradict this rule are also welcome.
Relevant code ..
Please ask for any additional information required .. Thanks for your help ..
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com