Oh.. well in that case - If you use JavaLoader, you should note it takes an array of paths as an argument.
So if you have 2 JAR files that reference each other, if you point to both, they will work fine. (or 17 Jars... whatever). You can see this in my first post about JavaLoader: http://www.compoundtheory.com/?action=displayPost&ID=117 And with far less than 300 lines of code, I may add. If you happen to be on the CFHibernate mailing list, you can see that I've got Hibernate running via JavaLoader with relatively ease, and that has no small amount of JAR libraries around. Mark On 7/24/06, James Holmes <[EMAIL PROTECTED]> wrote: > Yes, I understand. > > If you have two separate jars, containing classes that call one > another (e.g. FOP calling XALAN) and you load them separately using, > say, Spikes technique, they can't be found by each other as they only > have access to what's in the machine classpath and their own jar. > > I get around this by just throwing everything into a new, single jar, > which is no big deal. > > On 7/24/06, Mark Mandel <[EMAIL PROTECTED]> wrote: > > Yup, still no idea at all what you are talking about. > > > > Sorry. > > > > Can anyone else point out to me what I am missing? > > > > Mark -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:247459 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
