Issue Details (XML | Word | Printable)

Key: JCR-243
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Edgar Poce
Reporter: Edgar Poce
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jackrabbit Content Repository

expose shutdown method in o.a.j.jndi.BindableRepository

Created: 06/Oct/05 04:14 AM   Updated: 13/Oct/06 04:13 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works 05-10-05-bindablerepository.patch 2005-10-06 04:16 AM Edgar Poce 0.6 kB
Issue Links:
Reference
 

Resolution Date: 06/Oct/05 08:31 AM



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Edgar Poce added a comment - 06/Oct/05 04:16 AM
The proposed patch that should fix the problem detailed in a recent conversation about shutting down jackrabbit.

Stefan Guggisberg added a comment - 06/Oct/05 07:05 PM
BindableRepository is a jndi support specific class. rather than allowing every jndi client to
shutdown the repository instance retrieved from the jndi registry i think a cleaner approach
would be to explicitly (through a boolean argument) or implicitly shutdown the repository
instance in RegistryHelper.unregisterRepository. i guess the code that explicitly
instantiated a RepositoyInstance is also responsible for shutting it down.

i suggest to remove to public modifiers of BindableRepository and shutdown and add
a boolean 'shutdown' to RegistryHelper.unregisterRepository.

Edgar Poce added a comment - 07/Oct/05 10:29 AM
I agree, it has sense that if the webapp doesn't start it it shouldn't shut it down. I didn't add an argument, please add it if you prefer the explicit shutdown .
thanks for your suggestion.

fixed in rev. 306970.