From my point of view as a developer who writes code
against the api,
I have to handle to case of a Resource not being there, or
being invalid/corupt... theese are casses that I need to recover from in my
code...
and I have no way of knowing what do I need to catch
and where, without first writing the code, run tests against it, and
examine stack traces. I find this quite inefficient...
If you google for ResourceNotFoundException, you will find
out that there is quite a few APIs out there that implement it. There is other
apis that have InvalidResourceException... or
javx.resource.ResourceException
My preference would be toward catched Exceptions in this
case.
--zoly
Zoltan Farkas wrote:
Based on current
implementation, the following methods I think should throw a exception,
something like:
ResourceNotFoundException
do
you want this as runtime or catched exception? At the moment we are trying to
avoid catched exceptions.
Mark
org.drools.compiler.PackageBuilder.addKnowledgeResource()
org.drools.builder.impl.KnowledgeBuilderImpl.add()
another option might be to verify the validity of a Resource
object at creation time and make ResourceFactory factory methods throw ResourceNotFoundException.
I believe the case of a "not
found resource" the user of the api should be "ecouraged" to
handle.
Another case that might be needed to be
handled could be InvalidResource?
Let me know what you guys
think
Regards
--zoly
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev