Cassalog may define a Classloader to load resources from

[lucasponce]

def include() {
...
def scriptURI = getClass().getResource(script).toURI()
...
}

The current design works well when cassalog is loaded from the same .war, but in a shared environment where cassalog library might be loaded from a different module, it could be nice if a class or classloader can be passed to include() (or globally on a setter) to define from which CL load those resources.

[jsanda]

If there is something we can do in CassalogImpl.groovy to improve loading scripts, I am open to suggestions. I am not so sure about passing a class or class loader to the include function. The include function is used within cassalog scripts. While any groovy/Java code can be embedded in a script, the focus is certainly on schema changes. I fear that having class loader stuff in the scripts adds complexity where it does not really belong.

[lucasponce]

Perhaps implementation could be as easy as add an optional object on the CassalogBuilder

CassalogBuilder builder = new CassalogBuilder();
// new CassalogBuilder(this)
Cassalog cassalog = builder.withKeyspace(keyspace).withSession(session).build();
// .withClass(this)

So, that object if present can reference to the getClass() used in the include.

def include() {
...
def scriptURI = getClass().getResource(script).toURI()
...
}

It's optional, so current behaviour should be the default, but this addition will let to play better with classloading scenarios (cassalog loaded from a different module where it is used).

Just an idea, but hey, if there is another possibility, I'm fine if we can use cassalog from several classloaders.

It's not a blocker at the moment, so just a nice to have for future versions.