The Oracle Lite Blog

Ported a J2EE application this week to webtogo. I had an issue with my deployment due to the fact that I had an ‘_’ in my relative path. OJSP compiler translated that to ‘__’ and webtogo couldn’t find the package when I would reference the jsp. Also, noticed that the Webtogo Packaging Wizard doesn’t compile WEB-INF very well. So I created my own compile script to compile my jsps.

Here is a sample of an OJSP compile script for version 9.0.2 of the translator/comiler:

java -classpath %CLASSPATH% oracle.jsp.tools.Jspc -encoding UTF-8 -verbose -appRoot c:\webtogo\myapp\ -d c:\webtogo\myapp\_pages -packageName _myapp._web_2d_inf._jsp -verbose c:\webtogo\myapp\WEB-INF\jsp\*.jsp

Once your JSPs are compiled, you need to move them to your repository. You can do this either by WAR(ing) your web directory and using the Mobile Manager to deploy the WAR. You could also just unwar the war file to $ORACLE_HOME/j2ee/mobileserver/applications/mobileserver/myapp/.

Once your application has been deployed, if this is the first deployment all you need to do is sync. If you have modified your model or JSPs from a previous deployment, you can simply replace the files in the repository and then you have to update the MOBILEADMIN.APPLICATIONS table.

UPDATE MOBILEADMIN.APPLICATION SET PUBLISH_TIME = SYSDATE WHERE ID = ?

Your client should be able to sync the new webtogo application.