Bug 291350 - OSGi testing and issues
Summary: OSGi testing and issues
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard: osgi
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-05 09:59 EDT by James Sutherland CLA
Modified: 2022-06-09 10:20 EDT (History)
1 user (show)

See Also:


Attachments
osgi tests and some fixes (84.67 KB, patch)
2009-10-05 09:59 EDT, James Sutherland CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description James Sutherland CLA 2009-10-05 09:59:18 EDT
Several issues were encountered in getting JPA SRG tests running in OSGi.

- weaving does not seem to work when launching Equinox using -jar
- <exclude-unlisted-classes>false</exclude-unlisted-classes> does not work, jar is unable to be found, this requires the classes to be listed, which is very tedidious, a workaround is to list the jar in the persistence unit, which seems to work.
- several imports are missing from the manifest
> core
+ javax.xml.parsers;resolution:=optional,
+ javax.xml.datatype;resolution:=optional,
+ javax.xml.namespace;resolution:=optional,
+ javax.xml.transform;resolution:=optional,
+ javax.xml.transform.dom;resolution:=optional,
+ javax.xml.transform.sax;resolution:=optional,
+ org.xml.sax;resolution:=optional,
+ org.xml.sax.ext;resolution:=optional,
+ javax.xml.xpath;resolution:=optional,
+ javax.naming;resolution:=optional,
> jpa
+ javax.xml.validation;resolution:=optional,
+ javax.xml.transform;resolution:=optional,
+ javax.xml.transform.stream;resolution:=optional,
+ javax.xml.transform.dom;resolution:=optional,

> I assume there are several others as well, depending on what features are used.  Different OSGi environments, or ways of launching seem to require different imports...

- variable 1-1 uses wrong class loader to init classes
- no error was logged if osgi init failed
- multiple persistence units in manifest did not work as spaces were not trimmed
Comment 1 James Sutherland CLA 2009-10-05 09:59:49 EDT
Created attachment 148775 [details]
osgi tests and some fixes
Comment 2 Tom Ware CLA 2009-10-08 11:31:50 EDT
A number of the import issues are resolved by our use of BND
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:20:34 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink