geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dondi Imperial (JIRA)" <>
Subject [jira] Commented: (GERONIMO-680) New users "buy-in" hampered by inability to automatically rebuild sub-assemblies at runtime
Date Sat, 18 Jun 2005 05:08:17 GMT
    [ ] 

Dondi Imperial commented on GERONIMO-680:

The Scripting module patch is a bit primitive and there are a few methods from org.python.util.PythonInterpreter,
like eval and execute,  that could be added as GBean operations. This could also help in places
like the DebugConsole where you might want to construct arbitratry objects and from user input
(ie. when trying to cal kernel.invoke() on a GBean method with complex arguments.

> New users "buy-in" hampered by inability to automatically rebuild sub-assemblies at runtime
> -------------------------------------------------------------------------------------------
>          Key: GERONIMO-680
>          URL:
>      Project: Geronimo
>         Type: Improvement
>     Reporter: Sing Li
>  Attachments: ScriptingModule.patch
> Sizable population of current Tomcat, Jetty, 
> OpenEJB, and ActiveMQ users will soon take a look at
> Geronimo.
> Unfortunately, they are very likely to walk away out of 
> pure frustration :-(
> The current usage model for these products are very similar 
> to that of the Apache web server.  A user can:
> 1. change the config file, for example httpd.conf
> 2. restart the server, for example ... via apachectl
> 3. immediately try the new server in action
> This model allows for rapid revision/iteration 
> during experimentation, debugging, and on-the-fly 
> config rewrites.
> Unfortunately, attempting to do the same with 
> their favourite server INSIDE Geronimo will 
> (today) require:
> 1. download of the entire Geronimo source base
> 2. research and understand Maven
> 3. research and understand SVN and CVS
> 4. understand the Geronimo build process
> 5. crossed digits during assorted build failures -
> out-of-sync repository, server lock-ups, etc
> 6. days on end searching mailing list archives (if
> the search feature isn't still broken)
> 7. endless hours lurking on the IRC
> 8. days and days of wondering why he/she is doing it
> All of this is required to make a simple change
> that formerly equates to a text file edit
> and server restart.
> Somewhere between step 1 and 8 above, most sane
> user would have quit, disappointed.  
> Not every server user aspires to become a 
> server-system developer :-(
> Even though this problems will likely go away once 
> GUI admin/deployment/configuration tools 
> and GUI assemblies-construction-kits become available,
> there is an obvious need to address the usability 
> issue in the interim.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message