Eclipse Community Forums: EMF » Texo: problem when attribute is called class

Help

Home

Home » Modeling » EMF » Texo: problem when attribute is called class(Problem with naming colision to Java)

Show: Today's Messages :: Show Polls :: Message Navigator

Texo: problem when attribute is called class [message #865659]

Mon, 30 April 2012 14:09

Olaf Burdziakowski

Messages: 46
Registered: April 2012

Member

In my xml files there are attributes called class. It is standard I can not change it.
When generate with Texo: Generate JPA anotated code + DAO it generates code without exceptions.
The problem is that the code create such function:

public ThresholdClassType getClass() {
return class_;
}

There is a compiler problem: return type is incompatible to Object.getClass()

How to solve that?

Report message to a moderator

Re: Texo: problem when attribute is called class [message #865677 is a reply to message #865659]

Mon, 30 April 2012 14:15

Martin Taal

Messages: 5468
Registered: July 2009

Senior Member

Hmm, you can specify the java property name using an annotations model. But this one should be handled automatically,
can you enter a bugzilla for it?

gr. Martin

On 04/30/2012 04:09 PM, Olaf Burdziakowski wrote:
> In my xml files there are attributes called class. It is standard I can not change it.
> When generate with Texo: Generate JPA anotated code + DAO it generates code without exceptions.
> The problem is that the code create such function:
>
> public ThresholdClassType getClass() {
> return class_;
> }
>
> There is a compiler problem: return type is incompatible to Object.getClass()
>
> How to solve that?
>

--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxx - mtaal@xxxxxxxx
Web: www.springsite.com - www.elver.org

Report message to a moderator