Hi Shiva, Recently we removed the RXT attributes being added as properties in the registry [1]. With this i believe you would not get the error that you mentioned above about the length being only 1000 characters. This fix was added to the 4.3.0 branch you can try it out and see.
[1] https://wso2.org/jira/browse/REGISTRY-2298 Regards, Pulasthi On Fri, Sep 19, 2014 at 2:12 PM, Shiva Balachandran <[email protected]> wrote: > The Assets are stored in the registry. The fields in db have limited size. > the description column and text areas or any field created is mapped into > the registry table. Using the text-ae in the UI will allow unlimited input > but the column the data is being stored can only handle 1000 characters. > Below is the error message printed. > > > Asset of type: process was not created due to JavaException: > org.wso2.carbon.governance.api.exception.GovernanceException: Failed to add > artifact: artifact id: 35078821-d4eb-4aa2-a46c-eb2a90a7db68, path: > /process/afdsa/sads/svcd. Failed to add properties to the resource > /_system/governance/process/afdsa/sads/svcd. Value too long for column > "REG_VALUE VARCHAR(1000)": "STRINGDECODE('A system that takes a sequence (a > \""batch\"") of commands or jobs, executes them and returns the results, > all witho... (2746)"; SQL statement: > INSERT INTO REG_PROPERTY (REG_NAME, REG_VALUE, REG_TENANT_ID) VALUES (?, > ?, ?) [90005-140] > > Regards > Shiva Balachandran > > > On Fri, Sep 19, 2014 at 1:37 PM, Roshan Wijesena <[email protected]> wrote: > >> Hi Shiva, >> >> I'm just wondering, what prevents you from using a text-area? [1] , it >> can hold unlimited characters. >> >> [1] http://www.w3schools.com/tags/tag_textarea.asp >> >> On Fri, Sep 19, 2014 at 1:11 PM, Shiva Balachandran <[email protected]> >> wrote: >> >>> Hi, >>> >>> Working with the ES, in order to build an extension, I came across a >>> requirement, a necessity, to hold data in a field which consisted more than >>> 1000 characters. Currently the Enterprise Store only caters to Assets >>> Attributes such as description, provider name, version and others but not >>> for Asset contents or editiable contents field. >>> >>> The description field can only hold up to 1000 characters. The >>> requirement was to provide the user with a content field to input large >>> amounts of textual data such as Business Process Definitions which could >>> exceed 1000 characters. >>> >>> Providing a upload document field to hold extensive data could be viable >>> but will reduce the usability of the store. As the users will have to edit >>> the file and re-upload. >>> >>> What would be a possible workaround? >>> -- >>> Shiva Balachandran >>> Software Engineer >>> WSO2 Inc. >>> >>> Mobile - +94 774445788 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Roshan Wijesena. >> Senior Software Engineer-WSO2 Inc. >> Mobile: *+94752126789* >> Email: [email protected] >> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >> lean.enterprise.middleware. >> > > > > -- > Shiva Balachandran > Software Engineer > WSO2 Inc. > > Mobile - +94 774445788 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: [email protected] Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
