Hopbot log for 2009-09-19 - Helma IRC channel: #helma on irc.freenode.net

2009-09-19:

[17:33] <small_jam> hi all
[17:34] <small_jam> is helma alive guys?
[17:40] <small_jam> I can't understand where is helma looking for main.hac file in case of clean project, I have only root dir and main.hac inside
[17:41] <small_jam> looking by logs here is not much discussions .. bad for me
[17:41] <small_jam> bb
[18:39] <zumbrunn> small_jam: that should work
[18:44] <zumbrunn> hannesw: I just noticed that a mountpoint mapping for "/" in apps.properties seems to block out other apps
[18:44] <zumbrunn> is/was that a known bug?
[18:44] <hannesw> really?
[18:44] <zumbrunn> (talking about 1.7rc3 vs 1.6.3)
[18:45] <hannesw> must be a jetty 6 induced problem...
[18:45] <zumbrunn> haven't tried svn trunk yet
[18:45] <hannesw> haven't noticed this, though.
[18:45] <zumbrunn> http://helma.pastebin.com/d3a01852b
[18:46] <zumbrunn> the requests are handled by bar instead
[18:47] <hannesw> strange
[18:47] <hannesw> if i have an app mounted at /; i can get through one other app, but not another.
[18:47] <hannesw> ok, must be a problem with jetty 6.
[18:48] <hannesw> thanks for noticing...
[18:48] <zumbrunn> yeah, I just noticed /manage is reachable
[18:49] <hannesw> i never do much testing on the default apps :)
[18:52] <zumbrunn> apparently, neither do I
[18:52] <zumbrunn> although foo and bar are not default apps :-)
[18:53] <hannesw> well, it's _very_ good that you caught this.
[19:01] <hannesw> just testing a new feature on helma.org
[19:01] <hannesw> redirect pages
[19:01] <hannesw> http://helma.org/redirect/?redirect=no
[19:28] <hannesw> i think it's working fine now
[19:29] <hannesw> http://helma.org/redirect/
[20:36] <hannesw> zumbrunn: i think redirect pages will make it much easier to restructure pages in the future
[20:36] <hannesw> for example, i now set a redirect from wiki/Helma NG to /ng
[20:37] <hannesw> but I think I might now do it the other way round: redirect /ng/... back to wiki/helma ng/...
[20:37] <hannesw> http://helma.org/wiki/Helma+NG/?redirect=no
[20:38] <hannesw> if you leave away the ?redirect=no part you see how that page behaves normally
[21:08] <small_jam> question about NG - is there anywhere some type of internal JS api? I can't find anything at all :(
[21:30] <hannesw> small_jam: can you explain internal JS api?
[21:41] <small_jam> example:
[21:42] <small_jam> I see actions.js as entry point and config.js
[21:42] <small_jam> there is exports object
[21:42] <small_jam> but I can't understand where is the prototype of exports, what it does and when it's called
[21:43] <hannesw> exports is defined by the commonjs module api
[21:43] <small_jam> I've read a bit about helma 1.x but seems in NG chnaged a lot
[21:44] <hannesw> http://wiki.commonjs.org/wiki/Modules/SecurableModules
[21:44] <hannesw> yes, helma 1 and NG are very different
[21:46] <small_jam> ok, clear with SecurableModules
[21:47] <hannesw_> so: the exports object (and most of the module loader, which it is part of) is implemented in the Java core
[21:48] <small_jam> maybe you can tell me in two words -- how can I map urls with regexps?
[21:48] <hannesw_> zumbrunn: I moved the NG wiki back to /wiki/Helma NG
[21:48] <hannesw_> add an entry to the urls array in config.js
[21:49] <hannesw_> each entry is itself an array with two elements. the first is the regexp, the second the module to dispatch to if the regexp matches the requst
[21:50] <small_jam> hm
[21:50] <small_jam> in case of:
[21:50] <small_jam> exports.urls = [
[21:50] <small_jam> [ '/', 'actions' ],
[21:50] <small_jam> [ 'all', 'actions' ]
[21:50] <small_jam> ];
[21:50] <small_jam> I should have "all" pointed to actions.js
[21:50] <small_jam> right?
[21:51] <small_jam> but i got nothing
[21:51] <small_jam> (tried before with regexp)
[21:51] <small_jam> by nothing i mean 404
[21:52] <hannesw_> small_jam: sorry, gotta leave now
[21:52] <hannesw_> maybe I can help you another time

 

 

In the channel now:

Logs by date: