READERNAME ExceptionHandler.java - Revision history

Stefan: READERNAME ExceptionHanlder.java moved to READERNAME ExceptionHandler.java: typo

2009-05-06T12:44:08Z

2008-02-12T00:33:03Z

2008-02-01T19:31:29Z

2008-02-01T19:29:09Z

‎methodInvocationError

2008-02-01T19:28:48Z

‎invalidCommandError

2008-02-01T19:28:05Z

‎invalidCommandError

2008-02-01T19:27:43Z

‎CommandNotFoundError

2008-02-01T19:27:16Z

‎methodInvocationError

2008-02-01T19:27:05Z

‎invalidCommandError

2008-02-01T19:26:54Z

‎invalidCommandError

← Older revision		Revision as of 00:33, 12 February 2008
Line 1:		Line 1:
		+	[[category:developerDoc]][[category:emulatorDoc]]
	This class should extend GenericExceptionHandler. This page goes through each of the four methods in GenericExceptionHandler and describes in detail what each one does and how it should be implemented. The first three methods must be implemented by the class that extends it, and the last class may (and probably should be) implemented by the subclass.		This class should extend GenericExceptionHandler. This page goes through each of the four methods in GenericExceptionHandler and describes in detail what each one does and how it should be implemented. The first three methods must be implemented by the class that extends it, and the last class may (and probably should be) implemented by the subclass.

@@ Line 1: / Line 1: @@
-This class should extend GenericExceptionHandler.
+This class should extend GenericExceptionHandler.  This page goes through each of the four methods in GenericExceptionHandler and describes in detail what each one does and how it should be implemented.  The first three methods must be implemented by the class that extends it, and the last class may (and probably should be) implemented by the subclass.
-−
-It should override three methods:
 =CommandNotFoundError=

@@ Line 64: / Line 64: @@
 See the above implementation for the commandNotFound.  The handling of this error will likely be the same, but the message might be slightly different.
-==methodInvocationError==
+=MethodInvocationError=
 This exception is thrown in the [[Command Flow|CommandAdapter]] if something goes wrong in the handler method while executing a command.  It often happens if there is a null pointer exception thrown somewhere in the handler method.  While it is not required to implement this method, it is a good idea to do so, so that a proper error message can be sent back to the reader if something like that happens
 <pre>public CommandObject methodInvocationError(ArrayList<Object> arg,CommandObject obj)</pre>
-===Arguments===
+==Arguments==
 #arg - The incoming command
 #obj - The incoming command object
-===Return Value===
+==Return Value==
 An array of objects where the first object in the array is a message to be sent back to the client.
-===Reference Implementation===
+==Reference Implementation==
 This is a reference implementation from the LLRPExceptionHandler.  The ErrorMessage object is an LLRP specific message that the reader is required to send back to the client if an error happens.
 <pre>

@@ Line 49: / Line 49: @@
 See the above implementation for the commandNotFound.  The handling of this error will likely be the same, but the message might be slightly different.
-==invalidCommandError==
+=MalformedMessageError=
-This exception is thrown in the [[Command Flow|CommandAdapter]] if a command is in the reader.xml but is missing a required argument
+Tiis exception is thrown in the [[Command Flow|CommandAdapter]] if a command is in the reader.xml but is missing a required argument
 <pre>public abstract ArrayList<Object> malformedMessageError(ArrayList<Object> arg, CommandObject obj);</pre>
-===Arguments===
+==Arguments==
 #arg - The incoming command
 #obj - The incoming command object
-===Return Value===
+==Return Value==
 An array of objects where the first object in the array is a message to be sent back to the client.
-===Reference Implementation===
+==Reference Implementation==
 See the above implementation for the commandNotFound.  The handling of this error will likely be the same, but the message might be slightly different.

@@ Line 34: / Line 34: @@
 </pre>
-==invalidCommandError==
+=InvalidCommandError=
 This exception is thrown in the [[Command Flow|CommandAdapter]] if a command is in the reader.xml but does has and invalid argument.
 <pre>public abstract ArrayList<Object> invalidCommandError(ArrayList<Object> arg, String value, CommandObject obj);</pre>
-===Arguments===
+==Arguments==
 #arg - The incoming command
 #obj - The incoming command object
-===Return Value===
+==Return Value==
 An array of objects where the first object in the array is a message to be sent back to the client.
-===Reference Implementation===
+==Reference Implementation==
 See the above implementation for the commandNotFound.  The handling of this error will likely be the same, but the message might be slightly different.

← Older revision	Revision as of 12:44, 6 May 2009
(No difference)