On 1 November 2010 07:45, Samuli Saarinen <samuli.saarinen(a)remion.com> wrote:
On 29.10.2010 19:18, Wolfgang Laun wrote:
> On 29 October 2010 16:08, Samuli Saarinen <samuli.saarinen(a)remion.com
> <mailto:samuli.saarinen@remion.com>> wrote:
> Further more if I declare the event in both of the files with different
> @expires the one being used is the one that is added first. I was hoping
> that the first declaration to be a "default expires" that could be
> overwritten later on with a new declaration but it seems that this is
> currently not possible.
>
>
> If it were possible to enhance the very same class with different
> metadata such
> as @expires, I'd open a JIRA and call it a bug.
Should declaring the same event multiple times throw an exception then
if it's not allowed?
I don't know if it makes sense to override other metadata but I think
with expires it could be possible to use the greater value of two
different declarations as the engine already uses multiple sources for
calculating the actual expires (explicit vs. implicit).
I'm very much against any ad-hoc rules that would silently cover a
situation that might be an error due to oversight. Expiry is currently
a static property of an Event type and I see absolutely no benefit in
having multiple definitions. And why maximum? Why not minimum? Or
average ;-)
-W
Cheers,
Samuli
--
Remion Oy Etävalvontajärjestelmät liiketoiminnan
Samuli Saarinen tehostamiseen
gsm +358 (0)50 3560075
fax +358 (0)3 2125064
www.remion.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users