ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandr Kuramshin <ein.nsk...@gmail.com>
Subject Re: Inaccurate documentation about transactions
Date Mon, 27 Feb 2017 09:40:59 GMT
I think annotating the methods with @IgniteTransactional is redundant,
because they are already marked by "throws

For example, the same approach was used in JavaBeans 1.01 specs [1] with

The only thing I'd like to do: make all
are derived from the same parent TransactionException. And declare all
transactional methods as "throws TransactionException" with consequent
Javadoc update.


2017-02-18 1:07 GMT+07:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:

> On Fri, Feb 17, 2017 at 3:35 AM, Andrey Gura <agura@apache.org> wrote:
> > From my point of view @IgniteTransactional annotation is redundant
> > entity which will just confuse and lead to questions like "How to use
> > this annotation?" I think documention update is better way.
> >
> Why do you think it will be confusing? This annotation is suggested purely
> for documentation purposes, nothing else. Instead of adding documentation
> to every method, we just add the annotation. User can check the
> @IgniteTransactional javadoc to understand what this annotation means.

Alexandr Kuramshin

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message