its simple.. you working with xml descriptors during development when you ready for production you compiles your code with special packager (it may be an ant task for example) packager will make class files from xml and place it in jar.. so you again have single jar with your plugin, but whithout xml configuration (its "hardcoded") it will require extended mechanizm for module detection but i don't think it would be difficult task
alebu wrote: > > So such compiled descriptors will be stored in classpath as some > classes? Am I understanding idea correctly? > How Hivemind will discover such descriptors? Can anyone explain more > detailed how it possibly can be implemented ( main concepts )? > How people will use it, and as on... Because IMO Hivemind apps startup > time is probably the only one negative thing about it. > xVik wrote: > -- View this message in context: http://www.nabble.com/why-not-to-production-compile-xml-tf3159231.html#a9027744 Sent from the Hivemind - User mailing list archive at Nabble.com.
