I think better understanding is a bit too vague. Is there a specific problem you have? Your Jetty example would make sense if, for example, your goal was to automatically generate solrconfig.xml from some other configuration. But even then, you would probably use fillable templates and don't need fully corresponding JAVA api.
For example, you are unlikely to edit the very line you are asking about, it's a little too esoteric: <updateHandler class=solr.DirectUpdateHandler2> Perhaps, what you want to do is to look at the smallest possible solrconfig.xml and then expand from there by looking at additional options. Regarding specific options available, most are documented on the Wiki and in the comments of the sample file. Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Fri, Oct 25, 2013 at 5:19 PM, Amit Aggarwal <amit.aggarwa...@gmail.com>wrote: > Hello All, > > Can some one explain me following snippet of SolrConfig.xml in terms of > Solr API (Java Psuedo Code) for better understanding. > > like > *<updateHandler class=solr.DirectUpdateHandler2>* > * * > * <UpdateLog>* > * <str dir="BLAH" />* > * </UpdateLog>* > ** > ** > *....* > *</UpdateHandler>* > > > Here I want to know . > > 1. What is "updateHandler" ? Is it some Package or class of interface ? > 2. Whats is solr.DirectUpdateHandler2 ? Is it class > 3. What is "updateLog" ? is it package ? > 4. How do we know that UpdateLog have sub-element "dir" ? > 5. how do we know that "updateLog" would be sub-element of "updateHandler" > ?? Is "updateLog" some kind of subClass of something else ? > > > I KNOW that all these things are given in SolConfig.xml but I donot want to > cram those things . > > One example of jetty.xml whatever we write there , it can be translated to > JAVA psuedo code >
