> Can I use that to load an arbitrary file (e.g. and image) from my "bundle"?
Yes. вт, 24 февр. 2026 г. в 14:18, Pavel Tupitsyn <[email protected]>: > > > Ignite ARE java centric. So having java naming is good thing in my opinion > > Even if we ignore non-Java parts of Ignite, "classpath" is just a > wrong term for this feature, in my opinion. > In some cases it won't have any classes in it, e.g. we might want to > deploy AI models this way. > > - It is just a bundle of files, so we need a more generic name > - "Deployment Unit" is already accepted in Ignite 3.x, so we should do > the same for 2.x to avoid confusing our users > > > `this.getClass().getClassLoader()` not enough for the user? > > Can I use that to load an arbitrary file (e.g. and image) from my "bundle"? > > On Tue, Feb 24, 2026 at 12:39 PM Nikolay Izhikov <[email protected]> wrote: > > > > Hello. Pavel. > > > > > The proposal is quite similar to IEP-103 Code Deployment (Ignite 3.x). > > > > Thanks! Will take a look right away. > > > > > 1. "IgniteClassPath" name is Java-specific. Let's adopt the "Deployment > > > Unit" term, > > > > Don't like this change, currently. > > Ignite ARE java centric. > > So having java naming is good thing in my opinion > > > > "Deployment unit" not clear in my taste. > > Do we have other system world wide that use "deployment unit" naming? > > > > Let's hear what other Igniters think. > > > > > 2. Make sure any files can be added to a "Deployment Unit", including > > nested directories. > > > > Yes. Thanks. > > > > > 3. Provide a way to access current "Deployment Unit" from a compute > > job / service / etc (allows loading arbitrary resources, native > > binaries etc). > > > > Great addition. Will reflect it in IEP. > > Wonder, why is the regular java API: > > `Thread.currentThread().getContextClassLoader()`, > > `this.getClass().getClassLoader()` not enough for the user? > > > > > 4. (Maybe) allow multiple deployment units in `withClassPath` calls. > > > > Interesting idea, but, currently, I want to keep API and > > implementation as simple as possible. > > Nested class paths will make things more complex and hard to understand. > > Tend to restrict feature to a single classpath at a time. > > > > вт, 24 февр. 2026 г. в 12:40, Pavel Tupitsyn <[email protected]>: > > > > > > Hello Nikolay, > > > > > > The proposal is quite similar to IEP-103 Code Deployment (Ignite 3.x). > > > I suggest taking ideas from there, when applicable. > > > > > > 1. "IgniteClassPath" name is Java-specific. Let's adopt the > > > "Deployment Unit" term, which is neutral and can work for > > > compute/services/etc in .NET and other platforms > > > > > > 2. Make sure any files can be added to a "Deployment Unit", including > > > nested directories. > > > > > > 3. Provide a way to access current "Deployment Unit" from a compute > > > job / service / etc (allows loading arbitrary resources, native > > > binaries etc). > > > > > > 4. (Maybe) allow multiple deployment units in `withClassPath` calls. > > > > > > > > > On Tue, Feb 24, 2026 at 11:14 AM Nikolay Izhikov <[email protected]> > > > wrote: > > > > > > > > Hello, Igniters. > > > > > > > > I propose to discuss and then implement improvements to Ignite class > > > > loading approach. > > > > Issues in current way and proposed approach described here - > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-144+IgniteClassPath > > > > > > > > Please, share your thoughts.
