I think Alan Moore wrote: > This might be a good application for aspects (e.g. aspectj) or any of the > various byte code weaving tools. > > I've often thought about jess' requirement on definstanced (dynamic) objects > to implement property change events. This *could* be implemented at runtime > by byte code weaving for existing objects that doesn't fire property change > events. Obviously, this complicates the class loading issues in some > environments, but for simple applications it just might do the trick. >
Hmmm. Well, this is a good question to ask my buddy Ramnivas Laddad, who's currently promoting his "AspectJ in Action" book over on JavaRanch. > There are lots of other possibilities that wouldn't be all that hard to > implement and would be a good fit between aspects and jess. One could > automatically, for example, definstance all objects of a particular type or > that matched a given pattern, etc. by using aspects. > "AspectJ in Action" has a chapter in it in which Laddad shows how you can check things at various points throughout an application with a rule engine (using Jess as the example implementation.) It's really cool. > For details on aspectj see: > > http://www.aspectj.org > > alan > > -----Original Message----- > From: Mark Egloff [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 17, 2003 1:33 PM > To: [EMAIL PROTECTED] > Subject: AW: AW: JESS: Working with collections > > > > > -----Urspr|ngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im > Auftrag von [EMAIL PROTECTED] > Gesendet: Dienstag, 16. September 2003 23:21 > An: [EMAIL PROTECTED] > Betreff: Re: AW: JESS: Working with collections > > > >The idea of creating standard wrappers for various Collections is a > >reasonable one. It won't help people who will want to be able to use > >unwrapped Collection objects, too, but it's a reasonable approach. > > I don't see any other possibilities; otherwise you have to extend the > underlying JVM ;). > > However, I also think you don't need too many wrappers. Most collection > types are working properly with the Collection Interface, so I suggest > to do the following wrappers: > > - Collection > - Iterator (may be not needed) > - Map > - Bean Wrapper (works internally with Java Reflection) > > This should be enough for the first release. But may be there are more > So if somewhere is out there, add your comments. > > Regards > Mark > > -------------------------------------------------------------------- > To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' > in the BODY of a message to [EMAIL PROTECTED], NOT to the list > (use your own address!) List problems? Notify [EMAIL PROTECTED] > -------------------------------------------------------------------- > > -------------------------------------------------------------------- > To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' > in the BODY of a message to [EMAIL PROTECTED], NOT to the list > (use your own address!) List problems? Notify [EMAIL PROTECTED] > -------------------------------------------------------------------- > --------------------------------------------------------- Ernest Friedman-Hill Distributed Systems Research Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
