Bugzilla – Full Text Bug Listing
| Summary: | NonJTA Datasource testing failed on WebSphere | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Kevin Yuan <kevin.yuan> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | tom.ware |
| Version: | unspecified | Keywords: | test |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 296961 | ||
| Bug Blocks: | |||
|
Description
Kevin Yuan
The server framework is written to run with Transactional EntityManagers so any tests written for resource local EMs or Extended EMs will not run in our server tests. The server test framework made change manually in order to to run nonJTA datasource on server, and also successfully run nonJTA datasource on WLS, some snippet code just like the following:
public boolean isTransactionActive(EntityManager entityManager) {
if (isOnServer() && isJTA()) {
return getServerPlatform().isTransactionActive();
} else {
return entityManager.getTransaction().isActive();
}
}
The issue is with how the EM is obtaionss:
@PersistenceContext
private EntityManager entityManager;
By default, that's a transactional EM. That is likely why WAS is throwing an exception for the NON JTA datasoruce issue.
Reopening as a test case bug - as per above. Note: We have seen issues with running non-jta datasources on WLS, so the fix is not as simple as changing the way the injection works. More configuration may be required to get the non-jta datasource working properly. Already fixed on both 2.0.2 and trunk. Refer to the bug: 296961. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |