We seek a solution that all of XPages classes in a nsf can be loaded or included by other NSF Application.

Since 8.5.2 , domino has supply an method using template moudle to aggregate all xpages into one template module.

but our needs is different.  We want to build an Xpages framework which contains of many frameworklevel shared Xpages would used across many NSF. and in one normal nsf application can have its own Xpages . we want normal developer can not see and modify the source code of those framework leveled Xpages.

I hava hacked the ModuleClassLoader of NSFComponentModule to implement that idea. but it is very hard because of the architecture of module classloader very depend the hypothesis of NSF Module ought to be isolated . NotesContext.getCurrent().getModule() occur here and there, and NsfURL is also read contents of current module.

I had successfully conquered all obstacles and let one Xpages successfully include another xpage from other nsf. but some thing like javascripts library, file resources, and ManagedBean's configuration xml cannot load correctly. through seriously consider, I have a good idea to solve this problem.  it is using XPages Extension Library mechanism , and if we can export all Xpages classes and relative resources to an bundle jar and autowrap it as an Xpages library, it will be very cool.