[jboss-jira] [JBoss JIRA] Closed: (JBPM-701) Do not truncate long messages/exceptions

[Tom Baeyens (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPM-701?page=all ]

Tom Baeyens closed JBPM-701.
----------------------------

    Resolution: Done

 a script is added in the jbpm.db project in the sybase directory.

that build script can generate a modified version of the jbpm library and of the SQL scripts.

users might have to check the properties defined in the script in case it doesn't run out of the box. mainly the location of the jbpm library is specified relative and can vary in different distribution packages.

the script will tell where the modified artifacts are produced.
[ Show » ]
Tom Baeyens [12/Oct/06 10:52 AM] a script is added in the jbpm.db project in the sybase directory. that build script can generate a modified version of the jbpm library and of the SQL scripts. users might have to check the properties defined in the script in case it doesn't run out of the box. mainly the location of the jbpm library is specified relative and can vary in different distribution packages. the script will tell where the modified artifacts are produced.


> Do not truncate long messages/exceptions
> ----------------------------------------
>
>                 Key: JBPM-701
>                 URL: http://jira.jboss.com/jira/browse/JBPM-701
>             Project: JBoss jBPM
>          Issue Type: Sub-task
>         Environment: Sybase/DB2
>            Reporter: Ryan Campbell
>         Assigned To: Tom Baeyens
>         Attachments: sybase.build.xml
>
>
> For sybase, a "text" column should be used instead of the current varchar(4000)
> This will prevent the truncation of stack traces.
> Similarly, a CLOB or equivalent should be used on DB2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira