Expand F5ExceptionHandler's process Exception so that remote Exception deals with other types of remoteExceeption.

[omadawn]

It looks like most errors that we get back are going to be of type RemoteException but they are very different errors.

Known types so far will be A few types of connection errors.

Several different types of iRules errors including: Trying to create an iRule that already exists. Syntax error extra text after the closing bracket Syntax error method not applicable for context Syntax error when a method isn't understood because you haven't used it properly.

Is method not found coming back as a remote Exception? IE when we try and use a method like create_v2 on a version of BIGIP that predates the creation of that method.

Invalid Virtual Server Name Error is an instance of class org.apache.axis.AxisFault Processing Remote Exception Error: 01070088:3: The requested object name (1A-Some FI For ActivityTestsLTM1) is invalid. 01070088:3: The requested object name (1A-Some FI For ActivityTestsLTM1) is invalid.

Error is an instance of class org.apache.axis.AxisFault Processing Remote Exception Error: 01020036:3: The requested virtual server (AAA-USP-SL1-PrimaryVirtualServerLTM2) was not found. 01020036:3: The requested virtual server (AAA-USP-SL1-PrimaryVirtualServerLTM2) was not found.

[omadawn]

Error on creating a virtual Virtual Server someInstitution_virtual illegally shares both address and vlan with Virtual Server Junit_USP_test_virtual.

I know it's not appropos for Njord but I want to centralize my F5ExceptionHandler so all my errors are understood and I can share it with other apps I write for customers.

[omadawn]

Hrmm.... some issues might actually be better handled in the catch block itself. Specifically if it's something I need to retry on. How would I implement that in the exceptionHandler?

[omadawn]

Moving to 0.9