Bugzilla – Full Text Bug Listing
| Summary: | Allow Isolated classes to work with client session broker | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Tom Ware <tom.ware> | ||||||
| Component: | Eclipselink | Assignee: | Tom Ware <tom.ware> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | eclipselink.foundation-inbox | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 184388 [details]
proposed change 2.1.2
Created attachment 184395 [details]
Changes for trunk - slightly less restrictive
Chanes for trunk allow descriptors that are not isolated AND are not isolated in the UOW
Above fixes checked in. Tested with JPA and Foundation LRG Reviewed by Gordon Yorke The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
Currently sessionBroker.createClientSessionBroker throws an exception if any of the classes owned by the sessionbroker use an isolated cache. If the classes are all isolated in the UnitOfWork, a client session broker should be allowed to be created. The code change changes this: if (serverSession.getProject().hasIsolatedClasses()) { throw ValidationException.isolatedDataNotSupportedInSessionBroker(sessionName); } To This: if (serverSession.getProject().hasIsolatedClasses() && serverSession.getProject().hasNonIsolatedUOWClasses()) { throw ValidationException.isolatedDataNotSupportedInSessionBroker(sessionName); }