Re: [eclipselink-users] RCP-Eclipselink Classloader Problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipselink-users] RCP-Eclipselink Classloader Problem

From: Bryan Hunt <bhunt@xxxxxxx>
Date: Wed, 06 Aug 2008 11:21:11 -0500
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>


The golden rule with the OSGI stuff is Managed Entities CANNOT cross
classloader boundries. However, you can keep mappedsuperclasses in a
different classloader, that's fine.

One thing I can add ... I'm working on an extension to EclipseLinkthat will get around this limitation. I hope to have somethingavailable soon, but every time I start working on it, something higherpriority comes up. Stay tuned.


Bryan

References:
- [eclipselink-users] RCP-Eclipselink Classloader Problem
  - From: Markus Franz
- Re: [eclipselink-users] RCP-Eclipselink Classloader Problem
  - From: Tim Hollosy

Breadcrumbs