Ok, I thought #droolsdev was ok too. Sorry about
that.
The idea to have a 'name' and a 'description' attribute in
<Resource> elements inside a change-set is to tag them or
to add them some human-friendly information so you can refer to
it not using the URL or the name of the asset (could be
duplicated in different packages), but with a name and a
description.
These changes are 100% end-users oriented, that is why I put
those attributes in API. End users applications (like Guvnor)
could take advantages on these new attributes.
You can add them to the xml, and have that set them on the
InternalResource. We can migrate to public apis over time, I just
want people to take a much more conservative outlook on -api
changes.
So, a change-set now could look like this (the new attributes
are not mandatory):
<change-set>
<add>
</add>
</change-set>
These attributes can also be used in Spring's configuration:
<drools:kbase id="kbase1" node="node1">
<drools:resources>
</drools:resources>
</drools:kbase>
WDYT?
Best Regards,
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev