To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=109658





------- Additional comments from [email protected] Sun Oct 10 05:43:49 
+0000 2010 -------
arielch->brinzing: try the sample component (a NB Project in
ProtocolHandlerExample.tar.gz).

You can simply avoid the crash by catching the exception thrown in the bridge.

    public Object executeScript(final String script, final Object[] aArgs) {

        try {
            //...

        } catch (final IllegalArgumentException e) {
            System.err.println(e.getMessage());
        } catch (final ScriptFrameworkErrorException e) {
            System.err.println(e.getMessage());
        } catch (final InvocationTargetException e) {
            System.err.println(e.getMessage());
        } catch (final NullPointerException e) {
            System.err.println(e.getMessage());
        } catch (final com.sun.star.uno.Exception e) {
            System.err.println(e.getMessage());
        } catch (final java.lang.Exception e) {
            System.err.println(e.getMessage());
        }
        return null;
    }


I still do not see why it works the first time and crashes the second... may be
because you use getCurrentComponent() which is always a bad idea. Your
ProtocolHandler gets an XFrame, pass it to your working class.
On the other side, the StartModule has no model, and its controller does not
implement XScriptInvocationContext.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to