Starting upgrading Webtogo to OC4J and here are my likes and dislikes so far:Likes:
- Full J2EE compliance
- Easier to develop and debug application code
- I can specify different JVM from the one that is installed last.
Dislikes:
- Customized workspace is not supported (Although, I think I can get around that)
- WTGJDBCDriver is doing some really, really weird things.
- Session does not contain OraUserProfile object. So, even if wanted to build my own connection string and not use the WTGJDBCDriver, I can’t. I have an SR open for this now.
- All the code is located on the file system and not embedded into webtogo.odb
I think once I get past the WTGJDBCDriver issue and the OraUserProfile issue, I think I will like the OC4J much better. I will keep this post updated with my findings.
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.
Leave a Comment