I guess it depends on how it is used.
Essentially the Factory pattern is a reference to a set of objects. Normally combined with something else, possibly like the Strategy pattern (which is more likely to be defined as a type of polymorphism) to provide reference to an object to act on.
The Abstract Factory Pattern by itself is intended to be polymorphic as it is defined as an abstract class type. However the concrete implementation of the factory is the WidgetFactory in your type and is only polymorphic in reference to using a factory and providing an implementation of a factory.
In terms of what you are after, you certainly require a concrete factory, and presumably the actions you perform depend on the exception being caught. To that end you would use your factory implementation in a non-polymorphic way simply by passing it the exception caught, and have the factory pattern return a method to invoke a strategy or even a chain-of-command pattern to deal with how you would like to handle the exception.
Therefore, your factory would not necessarily be polymorphic, and your exception handlers would be polymorphic.
WidgetFactory? – Yannis Rizos♦ Nov 29 '11 at 1:23GUIFactory? – Yannis Rizos♦ Nov 29 '11 at 14:15GUIFactory. – rogcg Nov 30 '11 at 19:36