On 17.10.2011 16:08, Thomas Wolf wrote: > Dear all, > > while starting our ExtApp project, there seems to be some problems > reading the startup configs files (now called *.provisioning I think). > > I made sure that the files in questions are found indeed, and traced it > to the config keyword "BlueBerry.plugin_cache_dir". > > this is requested upon startup in Line 91 of > std::string AbstractConfiguration::getString(const std::string& key) > in the file AbstractConfiguration.cpp. > (PocoUtild.dll!Poco::Util::AbstractConfiguration::getString() ) > > Requesting the key fails, and the app stops with an exception. > > Can someone tell me which part of the framework is responsible for > creating the correct entries? Is this entry needed and/or is something > wrong at my end?
Apparently the solstice.ini in earlier versins had BlueBerry.plugin_cache_dir=@BLUEBERRY_PLUGIN_CACHE_DIR@ generated entries. Is this info still needed? Ths solctice.ini generated in our project just reads: ---> BlueBerry.home=<somepath>/3rdParty/MITK/BlueBerry BlueBerry.provisioning=<somepath>/3rdParty/MITK/BlueBerry/BlueBerryTesting.provisioning <--- I enabled all CTKPluginFramework configuration variables; But does the cache variable belong to the old blueberry mechanism? Regards, Thomas ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
