thanks for the answer, the hook is interesting but doesn't seem to be
triggered:
trying it it still uses the clazz.newInstance() instead of the provided
instance.
Here the stack to see where it comes from (it is not an exception):
org.apache.openjpa.event.BeanLifecycleCallbacks.newListener(BeanL
[
https://issues.apache.org/jira/browse/OPENJPA-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENJPA-2117 started by Albert Lee.
> XML overriding column names for 1xM attributes causes exception.
> ---
XML overriding column names for 1xM attributes causes exception.
Key: OPENJPA-2117
URL: https://issues.apache.org/jira/browse/OPENJPA-2117
Project: OpenJPA
Issue Type: Bug
Scrap the barrel for performance juice
--
Key: OPENJPA-2116
URL: https://issues.apache.org/jira/browse/OPENJPA-2116
Project: OpenJPA
Issue Type: Improvement
Reporter: Pinaki Poddar
Profiler r
Hi Francesco,
I'm not an expert with Glassfish, so I don't know if there any specific
steps to override the EclipseLink implementation. I was only making an
assumption. Maybe not an accurate assumption...
Is your persistence.xml specifying the openjpa persistence provider? You
are definitely ge
On 26/01/2012 17:18, Kevin Sutter wrote:
> Hi,
> Glassfish ships with EclipseLink (another JPA provider) by default. If you
> are attempting to use an alternate JPA provider (ie. OpenJPA), then have
> you properly disabled or overloaded the EclipseLink impl with the OpenJPA
> impl?
Hi Kevin,
nice
Hi,
Glassfish ships with EclipseLink (another JPA provider) by default. If you
are attempting to use an alternate JPA provider (ie. OpenJPA), then have
you properly disabled or overloaded the EclipseLink impl with the OpenJPA
impl?
Kevin
2012/1/26 Francesco Chicchiriccò
> Hi all,
> I am trying
Hi all,
I am trying to deploy my openjpa-based webapp to Glassfish 3.1.1
A bare deploy of the same WAR working with Tomcat 7 simply fails.
What I've done so far:
1. added WEB-INF/glassfish-web.xml like as follows:
/syncope
jdbc/syncopeDataSource
jdbc/syncopeDataSource
On 26/01/2012 13:22, Prashant Bhat wrote:
> Hi,
>
> Did you try the DB_CLOSE_DELAY connection parameter
> jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 as mentioned in [1].
>
> I've not tested this myself but this seems to be the preferred option in
> such cases.
Hi Prashant,
I was already using ';DB_CLOSE_D
Hi,
Did you try the DB_CLOSE_DELAY connection parameter
jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 as mentioned in [1].
I've not tested this myself but this seems to be the preferred option in
such cases.
[1] http://www.h2database.com/html/features.html#in_memory_databases
Regards,
Prashant
On Thu,
On 25/01/2012 18:48, Kevin Sutter wrote:
> That is interesting data, Francesco. Since the actual query processing
> seems to take less time with H2 (vs MySQL), but the overall time of the
> test takes more time with H2 (vs MySQL), my next guess is with Connection
> management. Maybe the cost of c
11 matches
Mail list logo