fall flat on the face when doing UNO call with incorrect arguments

I think this is reasonable with debug builds, the import filter
should check the values are in sensible ranges.

1 files changed, 10 insertions, 2 deletions

diff --git a/writerfilter/source/dmapper/NumberingManager.cxx b/writerfilter/source/dmapper/NumberingManager.cxx
index 6582c1fa1396..0b8000a72423 100644
--- a/writerfilter/source/dmapper/NumberingManager.cxx
+++ b/writerfilter/source/dmapper/NumberingManager.cxx
@@ -614,9 +614,17 @@ void ListDef::CreateNumberingRules( DomainMapper& rDMapper,
             OUString sNumRulesName = aPropNameSupplier.GetName( PROP_NUMBERING_RULES );
             xStyle->setPropertyValue( sNumRulesName, uno::makeAny( m_xNumRules ) );
         }
-        catch( const uno::Exception& )
+        catch( const lang::IllegalArgumentException& )
         {
-            OSL_FAIL( "ListTable::CreateNumberingRules");
+            assert( !"Incorrect argument to UNO call" );
+        }
+        catch( const uno::RuntimeException& )
+        {
+            assert( !"Incorrect argument to UNO call" );
+        }
+        catch( const uno::Exception& e )
+        {
+            SAL_WARN( "writerfilter", "Exception: " << e.Message );
         }
     }