365614 – Unnecessary exception thrown when both field and corresponding property are marked with @XmlTransient

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365614 - Unnecessary exception thrown when both field and corresponding property are marked with @XmlTransient

Summary: Unnecessary exception thrown when both field and corresponding property are m...

Status:	RESOLVED FIXED

Alias:	None

Product:	z_Archived
Classification:	Eclipse Foundation
Component:	Eclipselink (show other bugs)
Version:	unspecified
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Nobody - feel free to take it
QA Contact:

URL:
Whiteboard:
Keywords:

Duplicates (1):	363523 (view as bug list)
Depends on:
Blocks:

Reported:	2011-12-05 10:22 EST by Blaise Doughan
Modified:	2022-06-09 10:23 EDT (History)
CC List:	3 users (show)

See Also:

Attachments
Patch - code changes - 2.3 (3.61 KB, patch) 2012-03-20 13:39 EDT, Rick Barkhouse	no flags	Details \| Diff
Patch - code changes - 2.3 (4.56 KB, patch) 2012-03-20 15:56 EDT, Rick Barkhouse	no flags	Details \| Diff
Patch - test changes - 2.3 (11.28 KB, patch) 2012-03-20 15:56 EDT, Rick Barkhouse	no flags	Details \| Diff
Additional patch for class-level XmlTransient (10.47 KB, patch) 2012-03-27 12:49 EDT, Rick Barkhouse	no flags	Details \| Diff
Show Obsolete (1) 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

2011-12-05 10:22:40 EST

Currently with the following object model, MOXy is throwing an exception that the domain object has two mapped properties of the same name, when in reality neither of them are mapped since they are @XmlTransient:

public class Foo {

    @XmlTransient
    private String bar;

    @XmlTransient
    public String getBar() {
        return bar;
    }

    public woid setBar(String bar) {
        this.bar = bar;
    }

}

Workaround:

Annotate just the field or property (not both) as is appropriate for the specified accessor type.

Comment 1 Rick Barkhouse

2012-03-20 13:39:51 EDT

Created attachment 212935 [details]
Patch - code changes - 2.3

Comment 2 Rick Barkhouse

2012-03-20 15:56:04 EDT

Created attachment 212946 [details]
Patch - code changes - 2.3

Comment 3 Rick Barkhouse

2012-03-20 15:56:19 EDT

Created attachment 212947 [details]
Patch - test changes - 2.3

Comment 4 Rick Barkhouse

2012-03-20 15:57:01 EDT

*** Bug 363523 has been marked as a duplicate of this bug. ***

Comment 5 Rick Barkhouse

2012-03-21 10:06:09 EDT

Fixed and checked in to 2.3 and trunk.  Reviewed by bdoughan.

Comment 6 Rick Barkhouse

2012-03-26 15:48:14 EDT

Reopening this bug as it is causing another problem with XmlTransient / propOrder.

The following class will give an "XmlTransient in prop order" error:

@XmlTransient
@XmlRootElement        
@XmlType(name="",propOrder={"s001" , "b001"})
public class TestClass {
    
    private String   s001;
    private boolean b001;

    public TestClass() {}

    public String getS001() {
        return s001;
    }

    public void setS001(String s001) {
        this.s001 = s001;
    }

    public boolean isB001() {
        return b001;
    }

    public void setB001(boolean b001) {
        this.b001 = b001;
    }
    
}

Comment 7 Rick Barkhouse

2012-03-27 12:49:03 EDT

Created attachment 213244 [details]
Additional patch for class-level XmlTransient

Comment 8 Denise Smith

2012-03-28 09:40:34 EDT

Updated to ignore check when Class is Transient as shown in the Additional patch.

Comment 9 Eclipse Webmaster

2022-06-09 10:23:50 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink