[JIRA-OS] Created: (WF-215) BeanShellFunctionProvider exception logging misses key info!

[email protected]
Newsgroups gmane.comp.java.open-symphony.cvs
Message-ID <[email protected]>
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WF-215


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WF-215
    Summary: BeanShellFunctionProvider exception logging misses key info!
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: OSWorkflow
 Components: 
             FunctionProviders
   Versions:
             2.6

   Assignee: Hani Suleiman
   Reporter: Eric Pugh

    Created: Sat, 13 Sep 2003 9:05 AM
    Updated: Sat, 13 Sep 2003 9:05 AM

Description:
Hi all,
In the example.xml unit test, I am having a problem in the BeanShell section:
 String caller = context.getCaller();
                                propertySet.setString("caller", caller);
                                boolean test = true;
                                String yuck = null;
                                String blah = "987654321";
                                System.out.println("$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$");

In the JDBCFunctionalWorkflowTestCase it fails due to a JDBC error I had.  Unfortunantly, that error is eaten, and instead I just get an error saying:

Target exception: java.lang.NullPointerException

	at com.opensymphony.workflow.util.beanshell.BeanShellFunctionProvider.execute(BeanShellFunctionProvider.java:64)

But, what I really want is something telling me that it was a JDBC error:
java.lang.NullPointerException
	at com.opensymphony.module.propertyset.database.JDBCPropertySet.setImpl(JDBCPropertySet.java:267)
	at com.opensymphony.module.propertyset.AbstractPropertySet.set(AbstractPropertySet.java:565)

So, I can't seem to get that error to log, the best I could do was add this line: 

evalError.fillInStackTrace().printStackTrace(); 

to at least output the error somehow...  I don't really understand the whole fillInStackTrace() stuff..   I couldn't get it to log though.  If you agree, I can attach a patch that adds the key line, and provide a unit test as well.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.