Page History

...

• Create a solr/bootstrap module with a solr.jar  to replace start.jar  as the entrypoint (java -jar solr.jar ...)
• Write our own bootstrap code which will load Solr's webapp using WebappContext loading the existing web.xml. This will replace Jetty's Main class scanning for servlet contexts.
• Hide jetty even more, i.e. rename jetty.port  → port , and perhaps clean up other Sysprops as well
• Get rid of web.xml and instead build our contexts and paths from Java code, driven by Solr config
• Be able to lock Solr's memory to prevent swapping (SOLR-14335)

This will then in turn enable many many other improvements which may or may not be part of the SIP as such:are currently not in scope for this SIP but may be followup JIRAs, such as:

• Get rid of web.xml entirely by defining a SolrServletContextFactory interface pluggable in solr.xml, which will default to setting up the servlet in Java code. People with need to customize web.xml can then provide their own custom implementation of the factory, which will do what they need.
• Be able to shutdown JVM in various error situations (SOLR-6935 etc)
• Easier to control things like CORS in our own config (SOLR-12292)
• Get rid of jetty-ssl.xml and instead control SSL config in Java code, driven by Solr config
• Slim down bin/solr & bin\solr.cmd and move more startup logic into our bootstrap Java code
• Unified handling of key timeout values (SOLR-13457)

...