Hi,
the tarball with all fixes (and Martins jabber-drop.sql) is inside the file storage
The nsjabber tarball is inside the jabber/c dir, I did put the utils-extra.tcl inside the top-level dir, but I think Martins suggestion might be better (tcl_to_oracle_list should only be called once from inside jabber/www/index.tcl).
The package should now work with the newest oacs templating system (conference won't break).
The new Greenthumb Applet is included as well, but it doesn't work jet, it is split up into 2 .jar files (core and skin) and it seems that the core jar (E4-neu.jar) can not load the skin.jar (probably because it doesn't send a cookie with it's request). You can try to put the .jar files inside your server0/www dir and download them from that dir, but server0/www is usually disabled.
Does anyone know if (and how) public access (no cookies required) can be granted to a subdir of a packages www directory ?
Their is a jabber-portlet and dotlrn-jabber package (for .LRN) for Oracle but not for postgres (jet).
Hi Martin,
I'm sorry for letting you wait for a response again.
Did you start with the use of namespaces inside the jabber-procs.tcl ?
If you make a list like
jb_old_proc jabber::util:new_proc
we can let a script replacing all old_proc_names with the new ones, (I have written a script which almost fit that need for the KNOPPIX cd, changing it will be easy).
This way it doesn't matter if the package changes meanwhile.