|
|
| Re: [Texo] ignore not null syntax [message #877991 is a reply to message #877837] |
Mon, 28 May 2012 08:56  |
 Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Hi Olaf,
Can you enter a bugzilla feature request for this? To always serialize null required elements/attributes.
gr. Martin
On 05/28/2012 12:09 AM, Martin Taal wrote:
> Hi Olaf,
> I asked a question about this on the EMF forum. Based on the answer I get I will maybe change this in Texo...
>
> gr. Martin
>
> On 05/25/2012 03:32 PM, Olaf Burdziakowski wrote:
>> In my model there is defined String attribute than must be always present but may be empty (empty string).
>> Problem occurs when Oracle database is connected. Oracle translate zero length string to null (not standard). Than
>> generate an error during insert do database: null to not nulable column.
>> To make work around I defined column as nulable but ecore model still has this attribute as mandatory.
>> The problem is that Texo when save xml do not write the attribute to xml file (ignore model, use null value from
>> database as more important. I even tried to make default value:
>> @Basic()
>> @Column(name = "xserviceOption", nullable = true)
>> private String serviceOption = "";
>>
>> But still with the same result - attribute is not present in output xml.
>> How to solve this?
>>
>
>
--
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
|
|
|
Powered by
FUDForum. Page generated in 0.02993 seconds
] 
Search
Help
Register
Login
Home
