You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hivemind.apache.org by hi...@jakarta.apache.org on 2004/09/24 05:15:13 UTC

[Jakarta HiveMind Wiki] Updated: FrequentlyAskedQuestions

   Date: 2004-09-23T20:15:13
   Editor: TomDavies <to...@exemail.com.au>
   Wiki: Jakarta HiveMind Wiki
   Page: FrequentlyAskedQuestions
   URL: http://wiki.apache.org/jakarta-hivemind/FrequentlyAskedQuestions

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -16,3 +16,8 @@
 
 HowardLewisShip: Yes, passing {{{Object.class}}} will continue work but it is not recommended in ''normal'' cirmcumstaces.  The idea of passing in the expected (assignable) type is to allow HiveMind to do a check that the service object or proxy returned is assignable. Better a good message from inside HiveMind than a bad ClassCastException. Using java.lang.Object is acceptible if you don't care about that test. 
 
+'''Question 3):''' '''["PuttingHivemindConfigurationFilesOutsideAnEAROrWAR"]''' (TomDavies 24/09/2004)  
+
+I have configuration data which may change reasonably often, and which I'd like an administrator to be able to change without rebuilding an ear/war file. What's the best way to make this available to HiveMind?
+
+

---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org