[
https://issues.apache.org/jira/browse/OPENJPA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473784
]
Albert Lee commented on OPENJPA-150:
I investigated into this problem and the following changes has corrected
, but functional.
Albert Lee
On 2/16/07, Patrick Linskey [EMAIL PROTECTED] wrote:
Hi,
It looks like the new WebSphere transaction manager lookup code is
missing some functionality available elsewhere.
See OPENJPA-149 (https://issues.apache.org/jira/browse/OPENJPA-149) and
OPENJPA-153 (https
is process, it does not seems to extract the
table name from the annotation. Can someone give me direction if this is the
place to start looking for a solution? And what/where-else should I be
looking?
3) May be someone has a better idea how to correct this problem!
Thanks.
Albert Lee.
appreciated
Thanks
Albert Lee
On 2/7/07, Patrick Linskey (JIRA) [EMAIL PROTECTED] wrote:
EntityManagers cannot be serialized
---
Key: OPENJPA-126
URL: https://issues.apache.org/jira/browse/OPENJPA-126
Project: OpenJPA
three options are available for use by an application, in order of
compliance and portability preferences.
Albert Lee.
On 1/24/07, Patrick Linskey [EMAIL PROTECTED] wrote:
Firstly, thanks for putting this together.
I don't think that portability is a huge problem. I agree with the three
/xsd:complexContent
/xsd:complexType
/xsd:redefine
/xsd:schema
Albert Lee
that accept 3 new openjpa specific stanza as described
in previous example and a validated sample of the instance of
the orm.xml document that uses the new schema. (Note One needs
to update the xsi:schemaLocation to point to an valid location
of openjpa_orm_1_0.xsd)
Albert Lee
On 1/22/07, Craig L
