Hi,
> >Thats ok, but be very careful with sequence managers - i
> know most of them
> >are NOT happy with other apps doing inserts! see:
> >http://db.apache.org/ojb/docu/guides/sequencemanager.html
> >
> >
> yes I have not Other solution I can not convert Webapp 2 to
> use same Ojb
> cache or OJB.
I also work with an enviroment where different apps uses the same database.
With native oracle sequences it isn't a problem because this are sequences,
which does'nt give the same value twice also on different sessions or
applications.
I use the following sequence manager:
<sequence-manager
className="org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl"
/>
and I use native oracle sequences in the mapping like thies:
<field-descriptor
name="texpId"
column="TEXP_ID"
jdbc-type="BIGINT"
conversion="ch.braunvieh.ojb.db.Long2LongFieldConversion"
sequence-name="GESTHO.S_T_TIEREXPORT"
autoincrement="true"
primarykey="true"
/>
> >>My Problem
> >>when Webapp 2 (Update or Insert) in the Data Base the
> result is no 't
> >>visible for the Webapp 1
> >>what is best using for performance
A possible way would be to write a cache manager which becomes informed of
updates/inserts of other application by triggers on each table. In Oracle
you could use the PL/SQL-package DBMS_ALERT for the information exchange of
db and ojb, because there are functions/procedures which only send messages
on commit.
If you use only OJB to access the db you could write a cachemanager which
does the same on OJB level instead of DB level, one app informs the other on
updates/inserts.
At the moment I use:
ObjectCacheClass=org.apache.ojb.broker.cache.ObjectCacheEmptyImpl
which means NO CACHE ... but in future I will need to use the trigger
system to manage the cache.
regards
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
