[NateBailey]

When scaffolding with MyEclipse for Spring 10 from a PostgreSql Database, selecting Spring JSP MVC, including restful services and json support, there are two bugs.

1. One database table references another database table more than once. This causes the mappedBy declaration in the @OneToMany annotation to reference the same field in the related mapping in every case. Ex: Employee table references Type table twice, employee_tp_id, pay_tp_id.

2. bigint fields are scaffolded as Integer instead of Long.

[support-swapna]

NateBailey,

Sorry that you are seeing issues. We have a bug filed for Bigint fields being scaffolded as Integer.

Please take a look at this thread for a workaround to get the correct java types for your numeric values : https://www.genuitec.com/forums/topic/postgresql-int8-data-type-mapping-during-crud-scaffolding/

For the issue with db table referencing another db table more than once,can you please answer some more questions for us ?

1. Please share the MyEclipse for Spring Installation Details from MyEclipse > Installation Summary > Installation Details.

2. Also share the version of PostgreSql DB along with the driver details.

3. If possible please try with the same database structure on the Derby sandbox database and see if the issue persists.

4. Please post a DDL dump, or other backup of the simplest postgress database that triggers the scaffold issue to help us replicate the issue at our end.

5. Also please attach screenshots of the various selections you made during the scaffolding process.

[NateBailey]

I have attached the DDL script, screenshots of the project creation and scaffolding, and the resulting project.

Attachments:

You must be logged in to view attached files.

[support-swapna]

Nate,

Thank you for the files. We have a bug here with multiple associations to the same table.
The only workaround we have so far is to manually alter the mappedBy parameter. It will not be overwritten if you re-scaffold the application. So, in your case, the modified field becomes:

@OneToMany(mappedBy = "ubmTpByPayTpId", cascade = { CascadeType.REMOVE },  fetch = FetchType.LAZY)
    @XmlElement(name = "", namespace = "")
    java.util.Set<com.testcust.domain.UmbEmp> umbEmpsForPayTpId;

Sorry for the inconvenience caused. We will update this thread when there is a fix for the bug.

Let us know if you see any issues.

[Author]

Posts