Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 24595 invoked from network); 14 Jul 2003 15:13:16 -0000 Received: from smtp-out.comcast.net (24.153.64.116) by daedalus.apache.org with SMTP; 14 Jul 2003 15:13:16 -0000 Received: from icomcast.net (lb-ldap-155.icomcast.net [172.20.3.155]) by mtaout01.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HI00059VSVGML@mtaout01.icomcast.net> for commons-user@jakarta.apache.org; Mon, 14 Jul 2003 11:11:40 -0400 (EDT) Received: from [172.20.3.56] by msgstore06.icomcast.net (mshttpd); Mon, 14 Jul 2003 11:11:40 -0400 Date: Mon, 14 Jul 2003 11:11:40 -0400 From: Laird NELSON Subject: Re: [jelly] Jelly and BSF? To: Jakarta Commons Users List Reply-to: ljnelson94@alumni.amherst.edu Message-id: <287ab6a2881139.2881139287ab6a@icomcast.net> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.16 (built May 14 2003) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: Anthony Eden > The advantage is to allow applications which use BSF to use Jelly > without needing to code directly to the Jelly engine. Exactly. So from looking at the BSF site, which says this: Usually, a scripting language author extends the BSFEngineImpl class, which implements BSFEngine, and only requires the scripting language author to implement the eval() method. ...it looks like this would be a fairly easy task. Can someone give me a couple of pointers to get started? I'll be happy to do the work. Would I start by looking at a JellyContext? I'm unfamiliar with the guts of Jelly, so a couple of "trail heads" would be very much appreciated. Somewhat disorganized, Laird