I migrated away from Oracle Lite about 3 years, ago, so forgive me if I am rusty or just plain wrong.
You say your app uses the live database when online, then the OLite db offline. Why not use synchronization full-time and convert your app to always use the OLite db. Then synch when changes have been made? This is the most scaleable route. The other benefit is you only have 1 set of table names to refer to, always refer to the local OLite copy. Trust the sync for data flow / replication.
That said, I imagine you have a single webtogo web.xml file that represents your snapshots, so OLite will use the names you give in each "view" definition when it syncs, to create the table in the user schema that is connecting / synchronizing the publication.
1) Are the table names unique (without the schema prefix)? If so, you could use synonyms on the master db, and rewrite your code without schema prefix.
2) Or, I do believe you can synchronize 2 different user's on an Oracle lite database, however I have not done that. I always used single schema / users on my mobile dbs. But if so, I think each user will subscribe / synchronize to a different application name
3) It may be possible for 2 users on the remote schema to synch 2 different subscriptions to the same publication.
