That's why it is listed in API changes :-)
Of course we can replace the second constructor with a call to the first one to be 2.0 API compatible:
Yes, I think deprecation and calling the first constructor would be better.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
