There is no such concept of "packages avaiable to a rexx object". Package visibility refers to code instances, not the objecs to which code happens to be attached in the form of methos. An individual object may have methods that are defined with many different levels of visibility. Again, this is a question that can't be answered because it does not map to any concepts in the language.
Rick On Sat, May 9, 2009 at 9:04 AM, Rony G. Flatscher <rony.flatsc...@wu-wien.ac.at> wrote: > Thanks for clarifiying. > > In my current state of the code for BSF4Rexx for the new APIs it becomes > possible to refer to ooRexx objects from Java. To do that a RexxProxy is > defined at the Java side referring to a ooRexx object, which is > registered (and locked) at the native layer. > > There are two fundamentally different modes of operation in BSF4Rexx: > one is using external functions only, the other one (the preferred one, > because it makes things much easier for the ooRexx coder) requires a > package named "BSF.CLS" (this will also change a fundamental setting at > the Java side of the respective BSF4Rexx engine and expects data from > thereon to be encoded in a special way). > > Now, if the public routines and public classes of "BSF.CLS" were > available at the time the ooRexx proxy was created, I would need to > execute a public routine from that package before sending the Rexx > object the message received from the Java side. > > So the question would be: how can I figure out for an ooRexx object what > package definitions are available for it, if the call does not come from > Rexx, but from JNI ? In this scenario neither GetMessagePackage() nor > GetRoutinePackage() are available [in principle it should be possible > that a RexxProxy on the Java side can be used for another > RexxInterpreter instance spun off via a different engine instance there]. > > ---rony > > > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
