I am building out an object model and services for an
existing relational model and the table structure is a
little strange and I am having trouble with the object
mapping.
Here are the details
We have 2 tables
company with primary key
id
12M_company_venue with columns
As title.
Regards,
Yu Wang
I am new to OpenJPA and run into a little confusion over
auto detaching.
My setup.
Hessian servlet [1] which does some JPA and returns an
object. This acts as the server for a remote Swing client.
In my persistence.xml [2] I have
property name=openjpa.AutoDetach value=close, commit/
Which
Peter -
What kind of problems are you having? An exception or stack trace would be
very helpful.
-Rick
Peter Henderson wrote:
...
If I don't manually call em.detach() I get lots of problems
when hessian tries to serialize the object for wire transfer.
...
--
View this message in
This query works great and we use it in a few places in our PHP as well when
we need everything. I guess I am not seeing through to your solution. How
would I use a OneTooManyCopmanyVenue entity to get these results? In an
ideal world I would have
@Enity
@Table(name=company)
public class Company
Thanks for replying.
The stack trace is within Hessian (server side)
StandardWrapperValve[AccountsService]: PWC1406:
Servlet.service() for servlet AccountsService threw exception
java.lang.StackOverflowError
at
com.caucho.hessian.util.IdentityIntMap.get(IdentityIntMap.java:114)
Heather,
Good question... :-) This topic has come up recently due to some potential
locking issues (serialized access) when reading the metadata repository in a
multi-threaded environment. At this point, there is not a clear cut answer
for forcing the initialization of the metadata repository.
Hi Kevin,
Thanks for your comments.
1) I am using transactions simply because this test was
pared down for more complex code.
2) Because I'm not the smartest tool in the box. Probably
legacy from using another JPA implementation which would
only give meaningful errors at flush.
3)
