You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2010/07/08 00:23:49 UTC

[jira] Commented: (ODE-868) PartnerLink Database operation failure gives little information

    [ https://issues.apache.org/jira/browse/ODE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886117#action_12886117 ] 

Tammo van Lessen commented on ODE-868:
--------------------------------------

Cool, thanks for the patch, Veresh!

Is there any reason for wrapping the exception into a RuntimeException?

I think

        try {
            getSession().save(epr);
        } catch (HibernateException e) {
            logDao.error("Error while saving Partner Link : " + epr.toString());
            throw e;
        }

would be a little bit nicer, just in case something is catching HibernateExceptions later.

WDYT?

> PartnerLink Database operation failure gives little information 
> ----------------------------------------------------------------
>
>                 Key: ODE-868
>                 URL: https://issues.apache.org/jira/browse/ODE-868
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.3.4
>            Reporter: Veresh Jain
>             Fix For: 1.3.5
>
>         Attachments: verbose-error.patch
>
>
> When partnerlink name is long we get exception while inserting w/o knowing the column which caused the exception. For example a user might provide a very long partner role (> 100 characters) and that may cause the failure without giving more information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.