[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inherited methods from interface that are update transactions. (? ?)
On Wed, 31 Jan 2001, Mario Vackier wrote:
> I have a question regarding the marking of methods that are update
> transactions.
>
> I have a serie of database objects that all implement a common
> interface.
> Because some methods are update transactions, I put in that interface an
> /*update*/ after them.
> After compiling everything and generating the proxies for the database
> objects it seems that those methods from the interface are marked as
> read transactions.
> What's wrong ??
>
> For example :
>
> public interface SomeInterface {
> public void aMethod() throws Exception; /*update*/
> }
>
>
> public interface DbObject_Int extends SomeInterface {
> public void otherMethods() throws Exception; /*update*/
> }
>
> The implementation of DbObject implements these two methods.
> The result is that only method otherMethods() is an update transactions
> instead of both as I intended to.
This was a bug. It's fixed in CVS.
>
> Thanks in advance for the help.
>
> By the way, not taking into account some problems I struggle with now,
> Ozone seems to be something great !!!
:)
> I'm buzy to implement a production tracking system with ozone as a
> persistent object environment in the backend. More on that later.
looking forward!
Falko
--
______________________________________________________________________
Falko Braeutigam mailto:falko@smb-tec.com
SMB GmbH http://www.smb-tec.com