Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316483 - JAXB Externalized Metadata: Issues with XmlAccessorType NONE and xml metadata
Summary: JAXB Externalized Metadata: Issues with XmlAccessorType NONE and xml metadata
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-10 11:20 EDT by David McCann CLA
Modified: 2022-06-09 10:34 EDT (History)
1 user (show)

See Also:

Attachments
Fix and test case (7.16 KB, patch)
2010-06-17 11:17 EDT, Matt MacIvor 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 David McCann CLA 2010-06-10 11:20:32 EDT 
If access type is set to 'NONE' (indicating only annotated properties are processed) and a property is configured in XML that is not annotated, the property is not processed, and we get the following warning:

[EL Warning]: 2010-06-10 11:01:11.778--Ignoring attribute [myAttribute] on class [org.example. Employee] as no Property was generated for it.

We need to generate a property in this case if annotations processor did not.
Comment 1 Matt MacIvor CLA 2010-06-17 11:17:39 EDT 
Created attachment 172133 [details]
Fix and test case
Comment 2 Matt MacIvor CLA 2010-06-24 14:45:14 EDT 
Fix backported to 2.1 stream
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:34:35 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink