While implementing a fix for this I wanted to add a test to ensure long names and values are supported as well. I added a portlet preference with a long name and value to the admin.layout but discovered the value is getting truncated to 1138 characters by something in the Cernunnos import script. The name comes through correctly though. This is in SVN so you can check out the size of the strings in admin.layout do an import and see what ends up in the database.
-Eric Drew Wills wrote:
Jen Bourey wrote:Hi all,I've discovered that as of the RC2 release, the layout imports fail with Oracle (10g, in this case).[...]After looking at the database, it appears that the column for "name" in the UP_PORTLET_PREF table is a CLOB which is not allowed to be null. Is this portlet preference entry not supposed to have a blank name, or is the import tool supposed to try and set the name to an empty string rather than null, or is the table column supposed to allow null entries?These are excellent questions -- my first inclination is that the <entry> element shouldn't be there at all.Eric? Are there preferences that are intended to be a part of the default data set for the 1st 'jasig-test-portlet' on the admin layout?drew wills
smime.p7s
Description: S/MIME Cryptographic Signature
