Ticket #11 (closed enhancement: fixed)

Opened 6 months ago

Last modified 2 months ago

Use setup/config file as entry point to applications

Reported by: hannes Assigned to: hannes@helma.at
Priority: normal Milestone: Helma NG 0.3
Component: helma-ng Version: Helma NG 0.2
Keywords: Cc:

Description

currently Helma NG requires to pass either the main module or module repository list to the command line tools (run.jar and shell.jar). This is not very flexible. First, it requires configuration to reside in the application itself (ususally the main module). Second, when an application consists of more than one module repositories, the command line gets too long.

In NG 0.3, there should be a config/setup file as entry point. The format should be JS object literals or JSON. Using this file, it should be possible to set up the following:

  • The app's module repositories
  • The app's main module
  • The app's web server setup (TCP port, static resources, config file etc)
  • Required plugins

Change History

10/01/08 13:58:22 changed by hannes

  • status changed from new to closed.
  • resolution set to fixed.

Implemented in trunk. Currently it is only used by helma.webapp and only for server configuration and url dispatching. There is lots more of stuff that should be configures in the setup module, and lots more modules should use it, but I'm closing the bug as the basic implementation is there.