This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
From user post on nbusers; http://www.nabble.com/Porting-a-VWP-App-from-MySQL-to-Oracle-tf3978145.html#a11512099 Thanks for all the responses. The checklist was particularly helpful. Random notes: 1) MySQL integers map to BigDecimal under Oracle, so all of those references needed to be updated. 2) JSP/JSF pages needed the DataProvider updated also. The MySQL format of the column names were of the format tablename.column_name. Oracle needed the format of COLUMN_NAME (all caps). 3) Error: SyncResolver.UPDATE_ROW_CONFLICT row 0 Invalid column type This was fixed by making the integer column types cast to BigDecimal as above. When using the Calendar component the format had to be changed to the default Oracle format for the update to work: dd-MMM-yy 4) Error: SyncResolver.UPDATE_ROW_CONFLICT row 0 attempt to update a row that has been updated or deleted by another user This occurred on drill down detail page that used one data provider in the prerender method to populate the form. When I attempted to update the row with additional information from the detail page, via a button action, it kept giving this error no matter how I refreshed this data provider. I worked around this by having another data provider in the button action method and everything worked again. 5) Software Details: NetBeans/VWP 5.5.1 Oracle 10g Java 6 Update 2 JDBC Driver 10.2.0.3 (ojdbc14.jar) I hope they don't want this to use SQL Server next week, and I have to go through all this again! A nice enhancement would be a button to remap a VWP web app to a different database vendor automatically! jwbaker wrote: Here are some checklist items: 1) Drag and drop Oracle tables used to the respective pages 2) Re-bind each component to the Oracle rowsets 3) Remove the MySQL data source references in the _init() method of SessionBean/RequestBean 4) Rename the data provider references in the page beans to the data providers generated for Oracle 5) If there is data provider code that references fields of a table, there may be data type differences that will have to be taken into account (there is mapping involved jdbc-to-data provider) 6) Edit web.xml to reset the resource reference descriptor (located in web/WEB-INF) 7) In the Files tab for the project, if exists, expand the setup folder and edit the server specific files I think that's everything. If these changes are made then reply back and I'll try to follow-up - John