Exception handling with try/catch in acrobat

Hi
I have a problem using a try/catch block in my acrobat document-script. Try to enter the following into the debugger-console:
try{nonexistentFunction();}catch(e){console.println('\nacrobat can't catch')}
and run it. The output will be:
nonexistentFunction is not defined
1:Console:Exec
acrobat can't catch
true
The whole point of a rty/catch block is for the application NOT to throw an exception, but instead execute the catch-part of the statement. However, acrobat does both: It throws an exception AND executes the catch-block.
Is there another way to suppress the exception, or to make the try/catch-block work as it's supposed to?

> Also Adobe provides for free the JS or compiled file for Acrobat Reader to support the JS console.
Where is that file located ? How to install it or where to place it ?
What is the method referred by try67 on his site where he sells a product ?
Is that the same as the compiled file you refer to ? or did he sell his solution to adobe ?
It is helpful if people can get an idea of the nature of choices available and make informed decisions, than a cloak and dagger approach.
For some jobs that we have, I have been very frustrated by a consultant who wont even give basic info for transparent billing despite all assurances for privacy, as a result we are forced to do the job ourselves.
Dying Vet

Similar Messages

Surround With Try/Catch : comments issue

hi
Please consider this code:
     public static void main(String[] pArguments)
          FileInputStream vFileInputStream = new FileInputStream("someFile.txt");
          // some comments, e.g. several lines of commented code (that might be uncommented later)
     }It is possible to have JDeveloper "Surround With Try/Catch" this, but that results in this code:
     public static void main(String[] pArguments)
          FileInputStream vFileInputStream;
          // some comments, e.g. several lines of commented code (that might be uncommented later)
          try
               vFileInputStream = new FileInputStream("someFile.txt");
          catch (FileNotFoundException e)
               // TODO
     }Note that the declaration is before the comments and the try block starts after the comments.
Is this intentional behaviour? I would prefer to leave the comments where they are, after the (modified) code.
many thanks
Jan Vervecken

Thanks for your reply John.
I tried the right-click "Surround With..." > "try-catch" approach you suggest, and I get this code:
     public static void main(String[] pArguments)
          try
               FileInputStream vFileInputStream = new FileInputStream("someFile.txt");
          catch (FileNotFoundException e)
          // some comments, e.g. several lines of commented code (that might be uncommented later)
}Indeed, the try-block starts before the comments.
There is another difference with this approach, the declaration is not separated from the assignment.
Next ... I'll try to remember which approach give which result. :)
regards
Jan

Exception handling with eInsight

hi,
Can any body has any specific document regarding to achieve the effective exception handling with respect to JCAPS eInsight. where we have very limited information in the eInsight user guide.
Thanks

We have the same problem, so I could not help you.
Further we migrate from SRE eInsight and use manuell restart on failure which does not have a corresponding handling in JCAPS.

RAISERROR with Try/Catch does not exit after exception in catch block

I am trying to propogate an error from within my proc out to the caller.
In the attached example I have 2 sets of try catch blocks.
I raiserror in the first
catch the error and then raiserror again. (I expect to exit)
I do not expect :
to get to print 'post test'
to get to second try block.
but this does not exit, instead the code flows as per 2 runs.
I do not understand the reason for the flows, as it seems counterintuitive to be raising an error but then still print following exceptions. I cannot seem to find any references that explains this behaviour.
running tests together results
print '-------------------------------------------------------'
print 'test 15'
exec test_raiseerror 15
print '-------------------------------------------------------'
print 'test 16'
exec test_raiseerror 16
print '-------------------------------------------------------'
print 'test 17'
exec test_raiseerror 17
print '-------------------------------------------------------'
print 'test 18'
exec test_raiseerror 18
print '-------------------------------------------------------'
'RESULTS'
test 15
error number provided: 15
Msg 50000, Level 15, State 1, Procedure test_raiseerror, Line 21
name hello 15
post test
15
Msg 50000, Level 15, State 1, Procedure test_raiseerror, Line 37
name hello 2 15
post test2
test 16
error number provided: 16
Msg 50000, Level 16, State 1, Procedure test_raiseerror, Line 21
name hello 16
post test
16
Msg 50000, Level 16, State 1, Procedure test_raiseerror, Line 37
name hello 2 16
post test2
test 17
error number provided: 17
post test
17
post test2
test 18
error number provided: 18
post test
18
post test2
Msg 50000, Level 17, State 1, Procedure test_raiseerror, Line 21
name hello 17
Msg 50000, Level 17, State 1, Procedure test_raiseerror, Line 37
name hello 2 17
Msg 50000, Level 18, State 1, Procedure test_raiseerror, Line 21
name hello 18
Msg 50000, Level 18, State 1, Procedure test_raiseerror, Line 37
name hello 2 18
run tests seperately
exec test_raiseerror 15
error number provided: 15
RESULTS 15
Msg 50000, Level 15, State 1, Procedure test_raiseerror, Line 21
name hello 15
post test
15
Msg 50000, Level 15, State 1, Procedure test_raiseerror, Line 37
name hello 2 15
post test2
exec test_raiseerror 16
RESULTS 16
error number provided: 16
Msg 50000, Level 16, State 1, Procedure test_raiseerror, Line 21
name hello 16
post test
16
Msg 50000, Level 16, State 1, Procedure test_raiseerror, Line 37
name hello 2 16
post test2
exec test_raiseerror 17
RESULTS 17
error number provided: 17
post test
17
post test2
Msg 50000, Level 17, State 1, Procedure test_raiseerror, Line 21
name hello 17
Msg 50000, Level 17, State 1, Procedure test_raiseerror, Line 37
name hello 2 17
exec test_raiseerror 18
RESULTS 18
error number provided: 18
post test
18
post test2
Msg 50000, Level 18, State 1, Procedure test_raiseerror, Line 21
name hello 18
Msg 50000, Level 18, State 1, Procedure test_raiseerror, Line 37
name hello 2 18
CODEBLOCK:
if object_id('test_raiseerror','P') is not null
drop proc test_raiseerror
go
create proc test_raiseerror(@id as int) as
begin
begin try
declare @name varchar(20)
select @name = 'hello'
raiserror('name %s %d',@id,1,@name,@id)
print 'next'
end try
begin catch
declare @errormessage nvarchar(4000)
declare @errornum int
select @errormessage = error_message()
, @errornum = error_severity()
print 'error number provided: ' + convert(varchar(2),@errornum)
raiserror(@errormessage, @errornum,1)
print 'post test'
end catch
begin try
select @name = 'hello 2'
raiserror('name %s %d', @id,1,@name, @id)
end try
begin catch
select @errormessage = error_message()
, @errornum = error_severity()
print @errornum
raiserror(@errormessage, @errornum,1)
print 'post test2'
end catch
end
go
sqlserver 2008 & 2008 R2

There is a Connect that describes a similiar complaint. But basically a raiserror inside a catch block does not terminate the procedure, it will continue with any additional code in the CATCH and FINALLY unless it hits a return statement.
http://connect.microsoft.com/SQLServer/feedback/details/275308/have-raiserror-work-with-xact-abort

Exception Handling with GUI

Hi,
I'm new to Java so I'm a little rusty with exception handling. Please help me with this portion of my code. I'm supposed to screen out the bad input by the user. The user has to enter a double value and not an illegal value, for example: 45ab would be unacceptable. I've tried this way but after entering a number, the program just exits. Thanks first for helping me out.
import javax.swing.*;
import java.io.*;
import java.text.*;
public class Circle {
public static double readDouble() {
boolean done = false;
String s;
double d=0;
while (!done) {
JOptionPane.showInputDialog("Enter a double : ");
System.out.flush();
try {
BufferedReader in = new BufferedReader (
new InputStreamReader(System.in));
s = in.readLine();
d = Double.parseDouble(s);
d = new Double(s).doubleValue();
done = true;
}catch (IOException e){
done = true;
}catch (NumberFormatException e1){
JOptionPane.showMessageDialog(null,"Error -- input a double -- Try again");
return d;
public static void area(){
double radius1;
double area;
radius1 = readDouble();
area = (radius1 * radius1) * Math.PI;
// Rounding the area value to 2 decimal places
NumberFormat nf = NumberFormat.getNumberInstance();
nf.setMaximumFractionDigits(2);
JOptionPane.showMessageDialog(null, "The area is " + nf.format(area));
// There are more code after this.

Hello, I quickly wrote a possible solution to your problem, hope it will help you. (ICQ #28985387)
import javax.swing.*;
public class InputExample {
public static double getDouble() {
String input;
do {
input = JOptionPane.showInputDialog(null, "Enter a double", "Input", JOptionPane.QUESTION_MESSAGE);
} while(!validateDouble(input));
return Double.parseDouble(input);
private static boolean validateDouble(String input) {
double num = 0;
try {
if(input.length() == 0) {
JOptionPane.showMessageDialog(null, "Please enter a value", "Warning", JOptionPane.WARNING_MESSAGE);
return false;
num = Double.parseDouble(input);
} catch(NullPointerException exception) {
System.exit(0);
} catch(NumberFormatException exception) {
JOptionPane.showMessageDialog(null, "Not a double", "Warning", JOptionPane.WARNING_MESSAGE);
return false;
if (num < -Double.MAX_VALUE || Double.MAX_VALUE < num) {
JOptionPane.showMessageDialog(null, "Must be between\n" + (-Double.MAX_VALUE) + "\nand " + Double.MAX_VALUE, "Warning", JOptionPane.WARNING_MESSAGE);
return false;
return true;
}

Please help with try/catch

Hello, I'm writing a program and I got surprised with the following. I've got the following try/catch block:
try {
String param = config.getConfigValue("db2.driver");
if (param == null)
// parameter not defined.
throw new Exception("Parameter 'db2.driver' missing!");
else
Class.forName(param);
catch (SQLException sqlEx) {
// do something
catch (Exception e) {
System.out.println("*** ERROR loading driver..."); (1)
finally {
releaseDB2Resources();
I know the program flow goes through the finally block, but it doesn't print the message (1). Why is that? I don't understand it. What am I doing wrong?
Thanks in advance.

A finally block always gets executed, so that's why the println always works there. The only reason why the println in the catch wouldn't work is if that exception wasn't thrown. If a config value is not there, it might be the null string "" instead of null. Try this:
if (param.equals(""))
throw new Exception("blah");
You could also try:
if (true)
throw new Exception("blah");
to make sure that the exception is caught where you think it should be.

OutOfMemory Exceptions on Servlets, Try-Catch unable to help

Hi, I'm playing with Java servlets right now and I seem to be getting some OutOfMemory errors. The weird thing is that even though I had identify the souce of error and tried to enclose it with a try-catch, the exception still occurs. Why is that so?

OutOfMemoryError is actually a java.lang.Error, not a RuntimeException. So if you use a try/catch like this
try {
// stuff
} catch (Exception e) {..}Errors will fall through, since Error is not a subtype of Exception. (Check the API.)
You can catch it by catching Error or Throwable, like this:
try {
// stuff
} catch (Error e) { // this is rarely a good idea
}But you normally wouldn't want to do this. When there's no memory left, there's not a whole lot you can do about it, and most of the code you might want to put inside the catch block will merely throw another OutOfMemoryError.
As voronetskyy said, you're either creating too many (or too large) objects (typically in an endless loop), or you have specified too little memory for your application.

Exception handling with fault message type not working

Hi,
I have a sync proxy to proxy scenario and I have created a fault MT and specified in the outbound and Inbound service interface...
*In Inbound proxy I have the following code--*......
RAISE EXCEPTION TYPE z_cx_test_fault
EXPORTING
standard = l_standard_data.
In the sender side abap code which calls the outbound proxy I have the follwing code -
CATCH cx_ai_system_fault INTO lo_cx_ai_system_fault.
txt = lo_cx_ai_system_fault->get_text( ).
WRITE txt.
CATCH z_cx_test_fault INTO lo_cx_test_fault.
txt = lo_cx_standard_message_fault->get_text( ).
WRITE txt.
CATCH cx_ai_application_fault INTO lo_cx_ai_application_fault.
txt = lo_cx_ai_application_fault->get_text( ).
WRITE txt.
when i test the inbound proxy separately I get the custom fault message properly...
however when i run the proxy to proxy sync scenario and the custom exceptionz_cx_test_fault is raised inside the receiver proxy .......control goes to CATCH cx_ai_application_fault and not CATCH z_cx_test_fault .
I understand that cx_ai_application_fault is the super class of all the exception class but why does control go to its exception handling when a custom exception is raised...
Edited by: hema T on Feb 26, 2012 1:16 PM
Edited by: hema T on Feb 26, 2012 1:17 PM

Hi
I tried changing the sequence also but it did not work...
I can see an appropriate response coming from the receiver in SXMB_MONI of PI...this response has the "fault response "
"fault detail" data that I want.....however when the control goes to the sender why does it go to CATCH CX_AI_APPLICATION_FAULT and not not my CATCH z_cx_test_fault .
My observation - If I change the scenario to SOAP to Proxy sync..then the sender SOAP client gets the appropriate custom fault message back.
Edited by: hema T on Feb 27, 2012 1:17 PM
Edited by: hema T on Feb 27, 2012 1:17 PM

How to accept 2 strings in a class with try catch method..help!!

the program below will accept two strings and compare str1 and str2 if equal. this program uses functions. can any one help me with this?
import java.io.*;
public class StrCompare {
     private BufferedReader takyoin = null;
     //private BufferedReader intakyo = null;
     * @param args
     public StrCompare(){
          takyoin = new BufferedReader(new InputStreamReader(System.in));
          //intakyo = new BufferedReader(new InputStreamReader(System.in));
     public String UserInput(){
     public static void main(String[] args) {
          // TODO Auto-generated method stub
}

What are you talking about? There is no such thing as "try-catch-methods", and there are no functions but methods.
Strings by the way have their own means of comparision. Apart from that: do your own homework.

Weird thing with try-catch

Hey everyone, I have a problem compiling this .java
import java.io.*;
public class lector
    public static void main (String args[])
    public void lector()
        listapersonas listap = new listapersonas();
        listaconocidos listac = new listaconocidos();
        String linea, per, con;
        persona nuevapersona,actual,nuevoconocido;
        BufferedReader texto = new BufferedReader(new FileReader("conocidos.txt"));
        linea="";
        try {
        while ((linea=texto.readLine())!=null)
            per = linea.substring(0,linea.indexOf(','));
            con = linea.substring(linea.indexOf(','));
            nuevapersona = new persona(per);
            nuevoconocido = new persona(con);
            if (listap.existe(per)==false)
                nuevapersona.conocidos.agregar(nuevoconocido);
                listap.agregar(nuevapersona);
                linea=texto.readLine();
                continue;
            if (listap.existe(per)==true)
                if (listac.existe(con)==false)
                    listac.agregar(nuevoconocido);
                else
                    linea=texto.readLine();
                    continue;
            else
                linea=texto.readLine();
                continue;
        } //while
        } //try
        catch (java.io.* e)
            System.out.print("Imposible leer el archivo");
        } //catch
    } //lector
} // classWell what it is supposed to do is read a string from a file and then transform and add them to a linked list.
The problem is that when I compile there is an error message called "<identifier> expected" and points to the catch block. Please help me

Nothing weird about it at all.
That's not the syntax of a catch block. What you've written there will only work in an import statement.
What you probably mean to catch is java.io.IOException.

Exception Handling with Custom Tags/Exceptions

Hello all --
          I'm looking for some guidance in handling Custom errors in my app. I can't
          seem to find the message string of my custom exception when trying to call
          my JSP Error page. I'm consistently getting:
          javax.servlet.jsp.JspTagException: runtime failure in custom tag
          'CalendarHandler' .
          I am using custom JSP tag libraries to process logic on my EJBs. When I
          reach an error in business logic I raise a custom exception and propogate
          this back up to doStartTag:
          public int doStartTag() throws JspException {
          CalendarProcessor cp = new CalendarProcessor();
          try {
          String eventAction = getEventID();
          // pageContext contains information for the JSP;
          // Initialize the page with the current context and session
          cp.init(pageContext.getServletContext(), pageContext.getSession());
          HttpServletRequest req = (HttpServletRequest)pageContext.getRequest();
          cp.processRequest(req, eventAction );
          } catch (CalendarException ce) {
          throw new JspException(ce.getMessage());
          return SKIP_BODY;
          Then, in my JSP, I am enclosing the TagHandler in a try...catch block; I
          can't catch CalendarException because it is Throwable and conflicts with
          JspException.
          <% try { %>
          <gtc:CalendarHandler eventID="updatecal"/>
          <% } catch (Exception e) {
          throw e instanceof JspException ? (JspException) e : new
          JspTagException(e.getMessage());
          %>
          many thanks in advance!
          s.


I could not tell what the problem was that you were describing. Could you
          clarify?
          Cameron Purdy
          [email protected]
          http://www.tangosol.com
          WebLogic Consulting Available
          "Shari" <[email protected]> wrote in message
          news:[email protected]...
          > Hello all --
          >
          > I'm looking for some guidance in handling Custom errors in my app. I can't
          > seem to find the message string of my custom exception when trying to call
          > my JSP Error page. I'm consistently getting:
          > javax.servlet.jsp.JspTagException: runtime failure in custom tag
          > 'CalendarHandler' .
          >
          > I am using custom JSP tag libraries to process logic on my EJBs. When I
          > reach an error in business logic I raise a custom exception and propogate
          > this back up to doStartTag:
          >
          > public int doStartTag() throws JspException {
          >
          > CalendarProcessor cp = new CalendarProcessor();
          >
          > try {
          >
          > String eventAction = getEventID();
          >
          > // pageContext contains information for the JSP;
          >
          > // Initialize the page with the current context and session
          >
          > cp.init(pageContext.getServletContext(), pageContext.getSession());
          >
          > HttpServletRequest req = (HttpServletRequest)pageContext.getRequest();
          >
          > cp.processRequest(req, eventAction );
          >
          > } catch (CalendarException ce) {
          >
          > throw new JspException(ce.getMessage());
          >
          > }
          >
          > return SKIP_BODY;
          >
          > }
          >
          > Then, in my JSP, I am enclosing the TagHandler in a try...catch block; I
          > can't catch CalendarException because it is Throwable and conflicts with
          > JspException.
          >
          > <% try { %>
          >
          > <gtc:CalendarHandler eventID="updatecal"/>
          >
          > <% } catch (Exception e) {
          >
          > throw e instanceof JspException ? (JspException) e : new
          > JspTagException(e.getMessage());
          >
          > }
          >
          > %>
          >
          > many thanks in advance!
          >
          > s.
          >
          >
          >
          >
          >
          >
          >

Resume process instance after exception handling with an event subprocess

We have a process with several automatic activities so we implement an event-based subprocess to catch any exception that occurs in the process.
Since the error event is an interrupting event, how could we control the exception and resume the process where it was?
BPM version 11.1.1.7
Any suggestion?
Thank you

Know this isn't the answer you are looking for, but the answer to this gets much better in 12c where you can go back into the process after catching an exception in an event subprocess.
In 11g however, once you catch an exception in an event subprocess you cannot go back where you left off in the main process.
These are not great options I know, but here are a couple things I've seen to work around this:
Exception error events in event subprocesses are always interrupting so one solution would be to instead use boundary events on the individual activities where the exceptions will occur. Know you know this, but the down side of this is that it makes your process incredibly cluttered with boundary events.
Catch the error in the event subprocess -> handle the cause of the exception -> exit the process -> invoke the process again. The problem with this is that you would not be starting where you left off and where the error occurred. You could work around this by having an exclusive gateway that directed it to the right activity in the process.
Dan

Exception handling with AWT

I'm having a weird problem when trying to catch an exception with the Frame component.
// ********* code snipet *******************************************
try
Frame f = new Frame();
bFailed = false;
catch ( InternelError ie )
System.out.println( ie );
bFailed = true;
The first time that this code is executed, it works properly. But, on the next pass, I get NoClassDefFoundError.
Any ideas as to why it doesn't do the same thing everytime?

I'm running JVM 1.3.1.02 according to the java.version property. The problem I'm having is under Unix.
Here's all of my code:
//*** test.java ***********************************************
package mypackage;
import java.lang.*;
public class test
public static void main( String args[] )
ConsoleDisplay oFirst = new ConsoleDisplay();
if ( oFirst.isGuiAvailable() == true )
System.out.println( "gui" );
else
System.out.println( "no gui" );
ConsoleDisplay oSecond = new ConsoleDisplay();
if ( oSecond.isGuiAvailable() == true )
System.out.println( "gui" );
else
System.out.println( "no gui" );
//*** ConsoleDisplay.java *****************************
package mypackage;
import java.lang.*;
import java.awt.Frame;
import java.beans.Beans;
public class ConsoleDisplay
private boolean bGuiAvailable = false;
public ConsoleDisplay()
checkForGui();
private void checkForGui()
String szOsName = System.getProperty( "os.name" );
if ( szOsName.startsWith( "Windows" ) == true )
bGuiAvailable = true;
else
if ( Beans.isGuiAvailable() == true )
try
System.out.println( "about to create frame" );
Frame oFrame = new Frame();
System.out.println( "created frame" );
bGuiAvailable = true;
catch ( InternalError ie )
System.out.println( "catch" );
bGuiAvailable = false;
public boolean isGuiAvailable()
return bGuiAvailable;

Exception Handling with OC4J Web Services

Hi,
I want to throw some custom exceptions from my web services, based upon my business logic. From the documents I came to know that I can use "javax.xml.rpc.soap.SOAPFaultException" for the same. Following is the sample web service code which I'm trying in my environment.
import javax.ejb.Stateless;
import javax.jws.WebMethod;
import javax.jws.WebService;
import javax.xml.namespace.QName;
import javax.xml.rpc.soap.SOAPFaultException;
@WebService
@Stateless
public class TestService {
     @WebMethod
     public void greeting()
          throw new SOAPFaultException(new QName("uri", "local"),
     "My Fault String", "My Fault Actor", null);
Deployment of the web service goes fine and on the invocation of the "greeting" operation the exception is being thrown. But the problem is that, the soap response, which my web service client receives is as of follows,
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://service.csm.nb.md.inglife.jp.co/">
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Internal Server Error (Caught exception while handling request: oracle.oc4j.rmi.OracleRemoteException: javax.xml.rpc.soap.SOAPFaultException: My Fault String; nested exception is: javax.xml.rpc.soap.SOAPFaultException: My Fault String)</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
This means that OC4J again wraps the SOAPFaultException thrown by me. Is there any way by which I can avoid the further wrapping of my exceptions? If there is anything wrong in my approach please do let me know.
Regards,
Dipu

This is one of the "classic" design problems in this kind of architecture. And, unfortunately, the answer is "it depends on how you think you need to handle it." And I'm sure there are plenty of "gurus" that will tell you one way or another is the only way to do it.
I'll be more honest: I'll give you a couple of personal suggestions, based on experience in this architecture. These are suggestions - you may do with them what you will. I will not say this is the best, most correct, or even remotely relevant to what you're doing.
If it's simple data validation for "typing" (e.g. String, number, Date, etc.), that is taken care of when you attempt to stuff in the information into the appropriate DTO. If it's more "sophisticated" than that (must be in a certain range, etc.), that particular checking should probably be delegated from your Controller to a helper class. That not only saves the "expense" of transmitting the information back and forth across the wire, it's "faster" to the end user so say "Ooopsie" by redirecting back to the form right then. Basically the same thing if the types are wrong.
That only leaves the "big" problems in the business layer (EJBs), where you have to deal with concurrency, database failures, etc. Generally these kinds of exceptions are thrown back to to the Controller in one of two forms:
1) a sublass of RuntimeException, which signals that some Very Bad Things have happened in your container. EJBException is one like that and you can see where it's being thrown from.
2) a subclass of Exception, also called "application exceptions." They are usually something like a "duplicate record" or a validation-like error (which you mentioned) like a missing field. They're used as a signal to a failure in the logic, not the container. That way you have to decide at what layer of your architecture they should be handled and/or passed on to the next.

Exception Handling after the Catch Statement

Hi every one,
How to handle the exceptions after Catch Statement.
What does a catch statement can do?
Regards,
Johny

Hi,
Check this link:
http://help.sap.com/saphelp_nw70/helpdata/en/a9/b8eef8fe9411d4b2ee0050dadfb92b/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/cf/f2bbce142c11d3b93a0000e8353423/content.htm
Regards
Adil

Exception handling with try/catch in acrobat

Similar Messages

Maybe you are looking for