2362N/A * Copyright (c) 2001, Oracle and/or its affiliates. All rights reserved. 0N/A * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. 0N/A * This code is free software; you can redistribute it and/or modify it 0N/A * under the terms of the GNU General Public License version 2 only, as 0N/A * published by the Free Software Foundation. 0N/A * This code is distributed in the hope that it will be useful, but WITHOUT 0N/A * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 0N/A * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 0N/A * version 2 for more details (a copy is included in the LICENSE file that 0N/A * accompanied this code). 0N/A * You should have received a copy of the GNU General Public License version 0N/A * 2 along with this work; if not, write to the Free Software Foundation, 0N/A * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 2362N/A * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 2362N/A * or visit www.oracle.com if you need additional information or have any 0N/A * @summary When the system property "sun.rmi.server.suppressStackTraces" is 0N/A * set to boolean true, then the RMI runtime should take positive action to 0N/A * counteract the new feature in 1.4 of an exception's stack trace being part 0N/A * of its serialized form so that the server-side stack trace of an exception 0N/A * that occurs during the execution of a remote method invocation gets 0N/A * marshalled to the client. In most cases, this feature-- along with the 0N/A * final fix to 4010355 to make the server-side stack trace data available 0N/A * at the RMI client application level-- is highly desirable, but this system 0N/A * property provides an opportunity to suppress the server-side stack trace 0N/A * data of exceptions thrown by remote methods from being marshalled, perhaps 0N/A * for reasons of performance or confidentiality requirements. 0N/A * @author Peter Jones 5551N/A * @build SuppressStackTraces Impl2_Stub Impl1_Stub Impl1_Skel 0N/A * Verify right at unmarshalling time that this exception instance 0N/A * contains no stack trace data from the server (regardless of whether 0N/A * or not it would be apparent at the RMI client application level). 0N/A "TEST FAILED: exception contained non-empty stack trace: " +
0N/A // stub class generated with "rmic -v1.2 ..." 0N/A // stub and skeleton classes generated with "rmic -v1.1 ..." 0N/A * Verify behavior for both -v1.1 and -v1.2 stub protocols. 0N/A "TEST PASSED (server-side stack trace data suppressed)");
0N/A "trace of exception thrown by remote call:");
0N/A "TEST FAILED: trace contains more than one __FOO__");
0N/A "TEST FAILED: trace contains __BAR__");
0N/A "TEST FAILED: trace lacks client-side method __FOO__");