Skip to content
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.

@XmlValue too restrictive #37

Open
glassfishrobot opened this issue Aug 27, 2004 · 3 comments
Open

@XmlValue too restrictive #37

glassfishrobot opened this issue Aug 27, 2004 · 3 comments
Assignees
@glassfishrobot
Labels
Component: javatoxsd ERR: Assignee Priority: Major Type: Bug
Milestone
milestone 1

Comments

@glassfishrobot
Copy link

The clause "@XmlValue must be the only mapping annotation on the JavaBean
property" in javadoc is too strong. You should be able to use other annotations,
such as XmlID, XmlIDREF, or XmlJavaTypeAdapter.

This phrase should be modified to "@XmlValue, @XmlAttribute, and @xmlelement are
mutually exclusive and may not be on one property at the same time"

Environment

Operating System: All
Platform: All

Affected Versions

[2.0 draft]
@glassfishrobot
Copy link
Author

Reported by kohsuke

@glassfishrobot
Copy link
Author

Was assigned to sekhar

@glassfishrobot
Copy link
Author

This issue was imported from java.net JIRA JSR222-37

@glassfishrobot glassfishrobot added this to the milestone 1 milestone May 11, 2017
@glassfishrobot glassfishrobot self-assigned this May 11, 2017
@Tomas-Kraus Tomas-Kraus mentioned this issue Sep 13, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@glassfishrobot glassfishrobot

Labels
Component: javatoxsd ERR: Assignee Priority: Major Type: Bug
Projects
None yet
Milestone
milestone 1
Development

No branches or pull requests
1 participant
@glassfishrobot