[ 
https://issues.apache.org/jira/browse/LUCENE-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470409
 ] 

Ken Geis commented on LUCENE-636:
---------------------------------

I was able to work around this problem by using AspectJ to intercept calls to 
System.setProperty(..) and System.getProperty().  This is not a great solution.

A side note...  Tomcat on Ubuntu ships with the security manager turned on by 
default, a strangely uncommon setting for servlet engine distributions.  The 
default security settings prevent a webapp from calling System.setProperty(..).

It would be nice if this got resolved sometime soon because once it is 
resolved, I need to wait for Compass to pick up the change downstream.  It 
looks like it may be a year until I don't need to worry about this issue any 
more.

> [PATCH] Differently configured Lucene 'instances' in same JVM
> -------------------------------------------------------------
>
>                 Key: LUCENE-636
>                 URL: https://issues.apache.org/jira/browse/LUCENE-636
>             Project: Lucene - Java
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Johan Stuyts
>         Attachments: Lucene2DifferentConfigurations.patch
>
>
> Currently Lucene can be configured using system properties. When running 
> multiple 'instances' of Lucene for different purposes in the same JVM, it is 
> not possible to use different settings for each 'instance'.
> I made changes to some Lucene classes so you can pass a configuration to that 
> class. The Lucene 'instance' will use the settings from that configuration. 
> The changes do not effect the API and/or the current behavior so are 
> backwards compatible.
> In addition to the changes above I also made the SegmentReader and 
> SegmentTermDocs extensible outside of their package. I would appreciate the 
> inclusion of these changes but don't mind creating a separate issue for them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to