Bug 280948 - JAXB META-INF/services Entry
Summary: JAXB META-INF/services Entry
Status: RESOLVED FIXED
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:
Keywords: Documentation
Depends on:
Blocks:
 
Reported: 2009-06-19 15:50 EDT by Blaise Doughan CLA
Modified: 2022-06-09 10:21 EDT (History)
0 users

See Also:
blaise.doughan: documentation+

Attachments
MOXy - Fix (374 bytes, patch)
2009-07-20 16:10 EDT, Blaise Doughan CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Blaise Doughan CLA 2009-06-19 15:50:59 EDT 
In EclipseLink trunk the eclipselink.jar contains the following services entry (file):

META-INF/services/javax.xml.bind.JAXBContext

Because of this file when the eclipselink.jar is added to the classpath, the EclipseLink JAXB implementation can become the default JAXB implementation.

Advantages:
- Ease of use, no special configuration to use EclipseLink JAXB, just put it on the classpath.
- EclipseLink JAXB works very well with EclipseLink ORM/JPA and there are advantages to using them together.

Disadvantages:
- Users depending on the default JAXB implementation may be "surprised" when their JAXB/JAX-WS applications behave different when the eclipselink.jar is added (for possibly JPA and not for JAXB).
- Some JAX-WS implementations are dependent on the JAXB-RI (such as in the IBM VM) and putting eclipselink.jar on classpath will cause errors.

To Do:
- Decide if the META-INF/services entry shouls stay
- Document the impact of different deployment options in terms of the impact of using eclipselink.jar vs the bundle jars.
Comment 1 Blaise Doughan CLA 2009-07-20 16:10:54 EDT 
Created attachment 142067 [details]
MOXy - Fix

Removed the services entry in revision 4695.
Comment 2 Blaise Doughan CLA 2009-10-09 14:45:04 EDT 
Closed with resolution described on 2009-07-20.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:21:40 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink