Hi, > Agents should handle any throwable, I usually don't propagate > exceptions to the engine, except via agent_result or another field.
Ok ! > It all boils down to calling one of the apply methods of the > DecisionService instance. > > I guess that by imitating DecisionParticipant it would be fairly easy > for you to implement an EmbeddedDecisionParticipant, perhaps less > sophisticated, just as you need it. > > Maybe that would make a nice addition to the decision module. Sure. I'm working on this right now. Am I right in reader the DecisionParticipant that, if there was a tableName parameter in the config, it will call DecisionService.apply() twice with that same table name ? > > I was also wondering if the decision tables could be loaded from the > > classpath (Ive seen other things being loadable with a resource: > > prefix in openwfe but didnt see this for the decision tables, at first > > glance) > > I'll gladly add that if you want. I've also had a look at the code and > didn't see the use of the "resource:" prefix, it would be a nice > addition, that's true. > Just tell me. Well, I would assume any parameter that can be a url should go through to same path of utility methods to potentially reach a resource. Would be great if you added it anyhow, but I'll stick with 1.7.2 final for now anyway ;) Cheers g --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFE users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en -~----------~----~----~----~------~----~------~--~---
