There is a setting in the server which determines whether it automatically recompiles an application
when any of the source files it depends on change.


in WEB-INF/lps/config/lps.properties

#===============================================================================
# Compilation manager dependency options:
#
# never - compile once
# check  - check all includes
# always - compile for each access
#
# 'never' results in highest performance, requires an ?lzrecompile=true request
# to recompile the application.
compMgrDependencyOption=check

It defaults to check each time, so if it is set that way and isn't automatically recompiling the app, something is wrong.

Can you make a simple test case of an app which is not getting recompiled when you change the source?
Can you make a test case of an app that uses an <include>, which doesn't get recompiled when you modify
the included file?




On 9/21/06, James Howe <[EMAIL PROTECTED]> wrote:
I have an OpenLaszlo application that my company is using internally.
As I develop new features, or make fixes, I want to roll these out to my
users.  However, I'm not sure what the best way is to do this.  I've
tried just updating the particular .LZX files, but my changes don't seem
to take affect.  I've resorted to shutting down the Tomcat server,
clearing out the various cache entries in the work directory and
restarting the server, but this seems to be more than I should have to
do.  What is the recommended way to deploy changes to OpenLaszlo
applications?

Thanks!
--
  James Howe
  [EMAIL PROTECTED]


_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user



--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user

Reply via email to