The map file has been updated for the following Bug changes:
+ Bug 243383. The default configuration must be calculated after determine
if there is a user supplied configuration (FIXED)
+ Bug 244625. Implement new service registry hooks (RFC 126) (FIXED)
+ Bug 250705. bug list link is broken on si
I have had the most luck with Groovy, JRuby and Beanshell as far as
utilizing them in an OSGi container with BSF. Rhino in my experience has
been a nightmare and I can almost get Jython to work.
James
On Mon, Oct 20, 2008 at 11:41 AM, Craig Phillips
<[EMAIL PROTECTED]>wrote:
> Hi,
>
> I also man
Hi,
I did run into one issue - a memory leak... and, I don't think it's in my code,
although I'll desk check it with a fine tooth comb...I've been watching a
la jconsole (as well, I had yoyo'd enough time that I actually ran out of
heap)...
It seems that when I have a script return and I
Craig,
This is starting to sounds a bit like what I had to do to get JSPs to
compile and run in an OSGi environment. You might want to take a look at
some of the code in the org.eclipse.equinox.jsp.jasper project as it might
provide an even better fit in terms of the class loaders you want.
-Simo
Hi,
I also managed to successfully get ruby scripting up and running with BSF and
OSGi ... that was another riddle WRT class loaders... I'm using ruby 1.3.0,
BTW... Turns out, it's a similar trick to log4j... Ruby's JavaSupport.class is
essentially hard set to use the context class loader...