You can see current status here: https://nhcontrib.svn.sourceforge.net/svnroot/nhcontrib/branches/nh-search-big-port-from-hs-r15224
org.hibernate.search - 100% org.hibernate.search.annotations - 100% org.hibernate.search.backend - 90%: - Workspace - Not touched at the moment. org.hibernate.search.backend.configuration - 90% - Environment.WORKER_THREADPOOL_SIZE - not ported - Environment.WORKER_WORKQUEUE_SIZE - not ported org.hibernate.search.backend.impl.jms - not ported, we need an MSMQ impl org.hibernate.search.backend.impl.lucene - 100% org.hibernate.search.bridge.builtin - not ported all value type bridges, all are satisfied using ValueTypeBridge org.hibernate.search.bridge - ported org.hibernate.search.cfg - seems like we can't really use that, and there is a working implementation already, deferring inspecting that for now Related to that, I couldn't port ContextHolder properly, needs further review. Solr integration (InitContext.BuildAnalyzer & SolrAnalyzerBuilder) is not there. org.hibernate.search.engine - 100% org.hibernate.search.event - ported, note that this binds us to NH 2.1 SearchFactoryImpl.indexStrategy - not sure how to deal with that. Again, problem with differences between NH config and Hib config. On Mon, Sep 29, 2008 at 9:10 PM, Kailuo Wang <[EMAIL PROTECTED]> wrote: > roger. > > > On Mon, Sep 29, 2008 at 1:46 PM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > >> Okay, that make sense. >> I am now going through the source code and comparing hib to nh. >> In particular, me and Fabio would like to make an alpha 1 release, but I >> would like to have a solid understanding on the difference that we have >> between the two. >> >> If you can watch the commit stream for today and tomorrow, and comment on >> what you think, I would be grateful. >> >> >> On Mon, Sep 29, 2008 at 8:39 PM, Kailuo Wang <[EMAIL PROTECTED]>wrote: >> >>> When I ported that part, there is no WorkType.COLLECTION yet, so >>> basically I let that Layer class do nothing. >>> Once we have WorkType.COLLECTION, we just need to un-comment the line >>> return type != WorkType.COLLECTION ; >>> and return type == WorkType.COLLECTION; >>> >>> >>> On Mon, Sep 29, 2008 at 12:03 PM, Ayende Rahien <[EMAIL PROTECTED]>wrote: >>> >>>> What is the deal with BatchedQueueingProcessor.Layer ? >>>> It looks like it is supposed to process collection on second go, but it >>>> always process everything in the first go, and nothing in the second. >>>> >>>> >>>> LuceneWork and derivatives looks like a classic textbook DON'T DO THIS >>>> example for how not to use inheritance. I am leaning toward making the >>>> behavior use polymorphism rather than explicit checks everywhere. >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com.ar/group/nhcdevs?hl=en -~----------~----~----~----~------~----~------~--~---
