Summary
Important Observations
- In this exercise you selected a group of objects for check in by name. You can also select objects to check in:
- By Task
- By building a static Editor List or maintaining a dynamic editor list for your changes
- By sorting the Repository tab by Date Modified and selecting changed objects
- By reference to your Last Opened tab
- If you have changed design of a WebRoutine's web page, simply check in the WAM again. No recompile will be necessary
- If you have changed a common layout weblet, check this in and the WAM's which use it will include it at run time.
- If you have changed cascading styles, check in the which defines this style file.
Tips & Techniques
- Remember that the details of a Field Visualization weblet are locked into the XSL when the WebRoutine web page is created and saved. If a field visualization has been changed, for example, from radio button group to dropdown, checking in the WAM will make your application behave correctly without checking in the changed field visualization details. However, you should check the field in, to maintain a consistent application definition in the Master Repository.
- Remember, the web server is waiting for a response from your WAM, so the web server could time out if you spend too long stepping through code in debug.
What You Should Know
- How to check in your WAM and related definitions
- How to run WAMs on the IBM i server from Visual Lansa.