|
> From: Bartell, Aaron L. (TC) > > I don't like the data queue approach because then you can't > intimately use Java class objects but instead have to create a class > layer that receives in a supposedly complete object needing to meet all > of the requirements of that particular method and then make use of the > underlying Java classes which can be instantiated directly at that > point. Hope that made sense. . . It made sense to me, Aaron. I can't decide if that's scary or not <grin>. Seriously, though, your point is right on. Rather than being able to invoke a method from RPG, I have to create a data structure, populate it with data and send it to the JVM, where I then have to decode it (using the toolbox routines most likely), build an object and then invoke the method. If I have more than one method, I also have to have some sort of routing mechanism. It's an awful lot of overhead as opposed to being able to invoke a static method to get an object reference, then invoke a method of that object with the appropriate parameters. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.