Swing Client to Oracle DB architecture change

Hello.

In our company we have a big Java Swing application directly interfacing to Oracle through JDBC drivers.

In order to re-architecture the application looking for minimize bugs, maintenance, development delays, etc, etc, i'd like to use something different.

Obviously different modification will throw different development times...

I was thinking to:

1) Using a persistence facility like for example Hibernate

2) Using an MVC architecture to make all more in order; for example SWIXAT

I also thought about some RAD like for example WindowBuilder (this will not be very good in conjunction with SWIXAT)

Generally i'd like to change our 2 tier architecture in a 3 tier architecture to avois puttin business logic in presentation layer; like it is now.

Any suggestions, please.

Thanks in advance.

[868 byte] By [raffaeledianaa] at [2007-10-2 7:57:28]