[ http://jira.jboss.com/jira/browse/JBRULES-842?page=comments#action_12361588 ] Michael Neale commented on JBRULES-842: --------------------------------------- In order to make search easy as possible, we would like to have automatic meta data collected during the process of importing rules from files or during the save process from UI, to repository back end. The whole idea here is to keep the concept of Category only for business purposes. Besides the category concept , we could have attributes set into the repository attached with its components. With that we mean, that we could automatically (The saver to repository is a suggesiton on doing this), to extract Columns (Could be OTN also?) from rules, and create lists of all column types a given rule uses and even other type of data could be extracted from rule files and definitions With that we could be able to link in searches, business desciptions and categories to real implementation, giving very usefull results (A Better search engine than Google).... This woudl apply to any rule change/save. The meta data would need to be refreshed. We could use a structure like RuleNode / ColumnNode -field list (String[]) -name -- 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

[ https://issues.jboss.org/browse/JBRULES-842?page=com.atlassian.jira.plugi... ] Toni Rikkola updated JBRULES-842: --------------------------------- Parent: (was: GUVNOR-1057) Issue Type: Feature Request (was: Sub-task) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira