Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366084

Summary:	Unclear sentence.
Product:	z_Archived	Reporter:	Bob NIcholson <bob>
Component:	EDT	Assignee:	Ben Margolis <margolis>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	margolis, svihovec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Bob NIcholson

2011-12-08 13:34:45 EST

EDT:Tutorial: RUI With DataBase Lesson 8

Create functions that use the service-access variable to invoke the service 

Second paragraph following Notes

The second sentence in the following paragraph:

Our example exception handler function just displays the exception messages in the display of error information in the at the bottom of the web page (at run time). However, you would typically an error handler of your own that might log the error information, but display a message to the user saying something like "Your request cannot be completed at this time."

Comment 1 Ben Margolis

2012-01-17 14:54:33 EST

Changed the exception handler:

       sysLib.writeStderr("Failure: " + ex.message);
       if (ex isa ServiceInvocationException)
       	   sysLib.writeStderr("Detail 1:  " + 
       	       (ex as ServiceInvocationException).detail1);
       	   sysLib.writeStderr("Detail 2:  " + 
       	       (ex as ServiceInvocationException).detail2);
       	   sysLib.writeStderr("Detail 3:  " + 
       	       (ex as ServiceInvocationException).detail3);
       end

Changed the statement:

The example exception handler writes text to the Eclipse console or other standard error output. This behavior is appropriate for prototypes and early in development. For production code, you need to consider the exception-handling requirements that are specific to your situation.

Comment 2 Lisa Lasher

2012-01-18 14:39:14 EST

updated to show that this defect was fixed in 0.8.0 I1