Well, the JessDE plugins already have the registration, so if you are repackaging jess.jar in an eclipse plugin, then yes, you need to do this. The last line of the MANIFEST.MF for the jess plugin should be something like
Eclipse-BuddyPolicy: registered and then in your own code, Eclipse-RegisterBuddy: jess.core (the name of your jess containing plugin). Each plugin in Eclipse has its own classpath, so when Jess tries to import arbitrary classes from your project, it only knows about its own classpath, not the one from your new code (plugin). By registering Jess with the Eclipse buddy system, you are making it able to see the classpath of any code that decides to expose its classpath to Eclipse. It is "willing to be another plugin's buddy". This is done in your own code by telling your code that its buddy is Jess. This means that your own code will share its classpath with its buddy. This is a clever device, because the Jess plugin only has to say that it is willing to be a buddy to other code, but does not need to know about the other code in advance. It's analogous (I risk displaying Java naivete) to the listener pattern. - Mike J. Michael Dean, M.D., M.B.A. H.A. and Edna Benning Presidential Professor of Pediatrics Professor of Family and Preventive Medicine Professor of Biomedical Informatics Chief, Division of Pediatric Critical Care Vice Chairman, Department of Pediatrics University of Utah School of Medicine -------------------------------------------------------------------- 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] --------------------------------------------------------------------
