| 9000 Byte Classpath Causes - JdbcSQLException: Value too long for column ATTR_VALUE VARCHAR(4000) [message #717226] |
Fri, 19 August 2011 16:11  |
 Brian Brooks
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
I'm trying to use Jubula to test a large Swing application. The classpath is 8000 bytes, which is too long to fit in the 4000 byte AUT_CONF_ATTR.ATTR_VALUE column defined by Jubula's
org.eclipse.jubula.client.core::org.eclipse.jubula.client.core.model.AUTConfigPO @CollectionTable annotation.
Oracle limits VARCHAR columns to 4000 bytes. Some possibly ways to support a long classpath value would be:
1. Use a different SQL data type
2. Use a different storage strategy that understands how to break a large value across multiple rows.
3. Use a different storage strategy that understands how to break a large value across multiple columns (wouldn't be unlimited like rows but could support storing >4000).
Has someone already opened an enhancement request for this kind of change to Jubula?
Brian
[Updated on: Fri, 19 August 2011 20:41] Report message to a moderator |
|
|
| Re: 9000 Byte Classpath Causes - JdbcSQLException: Value too long for column ATTR_VALUE VARCHAR(4000 [message #717247 is a reply to message #717226] |
Fri, 19 August 2011 17:36  |
|
You can file a bug against Jubula with this request. We'll have to check if this is supported by JPA and EclipseLink.
There is a solution if you are using a JVM which supports the "-javaagent" option and the "_JAVAOPTIONS" environment variable. All Sun/Oracle JVMs since 1.5 will work, others might. Just start your AUT with a script or an executable wrapper and put this script/exec in the "Executable File Name" field in the "AUT configuration" dialog. This way your application is set up like on a normal start and the instrumentation is done by the agent.
HTH
Achim
|
|
|
Powered by
FUDForum. Page generated in 0.02418 seconds
] 
Search
Help
Register
Login
Home
