Difference between revisions of "EclipseLink/Development/359251"

From Eclipsepedia

Jump to: navigation, search
Line 15: Line 15:
  
 
== To Do ==
 
== To Do ==
 
=== XML Headers ===
 
 
* Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=379704
 
  
 
=== Canonicalization ===
 
=== Canonicalization ===
Line 29: Line 25:
  
 
== Completed ==
 
== Completed ==
 +
 +
=== XML Headers (2.4 only) ===
 +
 +
* '''COMPLETE'''
 +
* '''DOCS NEEDED'''
 +
* Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=379704
  
 
=== Test Get/Set For All Properties ===
 
=== Test Get/Set For All Properties ===

Revision as of 15:53, 17 May 2012

Design Documentation: JAXB RI Extensions

ER 359251

In the JAXB RI, developed by Sun, there are a series of "proprietary" extensions that are available to provide advanced JAXB functionality outside of the JAXB spec (these extension classes reside in the com.sun.xml.bind and com.sun.internal.xml.bind packages).

This page will track the various JAXB Extensions that we want to bring into MOXy.

Jan. 2012: Other extension properties: http://jaxb.java.net/2.2/docs/vendorProperties.html

Goal

Our intent is to support these extensions as is, so that MOXy can be a drop in replacement for the JAXB RI.

To Do

Canonicalization

Object Identity Config

Completed

XML Headers (2.4 only)

Test Get/Set For All Properties

  • We need to ensure that we test getting all these properties as well as setting them.
  • COMPLETE : org.eclipse.persistence.testing.jaxb.properties.PropertyTestCases

AccessorFactory (2.4 only)

CycleRecoverable (2.4 only)

XmlLocation (2.4 only)

NamespacePrefixMapper (2.3.3 and 2.4)

IDResolver (2.3.3 and 2.4)

IndentString (2.3.3 and 2.4)

CharacterEscapeHandler (2.3.3 and 2.4)

XML Declaration Control (2.3.3 and 2.4)

Future

The following items are of low priority and there is no current plan to implement these.

OverrideAnnotationOf

  • Allows for more flexible mapping (?)
  • Doesn't work if the field to override is not named "content", customization doesn't work (RI)
  • mgrebac: "The above annotation was actually used only for a very specific case of supporting usecase with XmlMixed, and is actually even not expected to be used outside of xjc."

Locatable

  • Seems to be mainly used internally by the RI
  • Interface only defines get methods... is user resonsible for setting up com.sun.xml.bind.v2.runtime.Location objects? Is this even meant to be a user-feature?
  • mgrebac: "No, this is as well not meant to be user feature, is usable for xjc itself and plugins to point to correct source when there is a failure."

XmlIsSet

  • Doesn't work in RI
  • Deprecated in the RI, no need to implement since we have XmlIsSetNullPolicy?
  • mgrebac: "Correct - deprecated, unused, we shall be able to remove it safely at this point actually."