Hello Jake and Chris,
Thank you for your reponse. Yes Jake I am directly connecting to the SQL server underlying OneWorld. But when I am moving my services to the production server I have to use the JDBC adapter built on that IS for the SQL Server, which unfortunately has a different namespace. And hence I guess I have to rebuild all of my adapter services.
Also, In any development process you connect to a testing database initially and then migrate to production. Now in your adapter services you specify the table name as <current>.<current>.table, which may change when you move to production. So you have to make change in all you adapter services before moving into production. Is there an easier way of doing this ??