Kaydet (Commit) 5907bb46 authored tarafından Tor Lillqvist's avatar Tor Lillqvist

Fix compilation error when OSL_DEBUG_LEVEL > 0

Just use SAL_WARN, building up the message using chained << operators instead
of constructing it into a OStringBuffer (or OUStringBuffer) and then passing
that to OSL_FAIL.

Or should we have a real assert() here?

Change-Id: I2c3f64ff2b29a3d81ba444d98c2a38ef49e6d7af
üst 82798d64
......@@ -373,15 +373,12 @@ namespace dbaccess
const OUString sComponentName( stor->second.sName );
if ( !xComponentsStor->hasByName( stor->first ) )
{
#if OSL_DEBUG_LEVEL > 0
OStringBuffer message;
message.append( "DatabaseDocumentRecovery::recoverSubDocuments: inconsistent recovery storage: storage '" );
message.append( OUStringToOString( stor->first, RTL_TEXTENCODING_ASCII_US ) );
message.append( "' not found in '" );
message.append( OUStringToOString( SubComponentRecovery::getComponentsStorageName( eComponentType ), RTL_TEXTENCODING_ASCII_US ) );
message.append( "', but required per map file!" );
OSL_FAIL( message.getStr() );
#endif
SAL_WARN( "dbaccess",
"DatabaseDocumentRecovery::recoverSubDocuments: inconsistent recovery storage: storage '" <<
stor->first <<
"' not found in '" <<
SubComponentRecovery::getComponentsStorageName( eComponentType ) <<
"', but required per map file!" );
continue;
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment