reworked the resolution of AMQ-1191 to split out the locker implementation for ms sqlserver. The current snapshot should now work with Oracle without modification.
2009/7/24 Gary Tully <[email protected]> > yea, exactly like that, where bean id="mydblocker" is an instance of your > OracleDatabaseLocker. > > 2009/7/24 bwtaylor <[email protected]> > >> >> We have been using Oracle without issue with activemq 5.1, so prevoius >> versions worked with Oracle. We can try creating our own >> OracleDatabaseLocker if needed. >> >> I found setDatabaseLocker() on JDBCPersistenceAdapter, so in the custom >> spring dialect, can I say something like >> >> <persistenceAdapter> >> <jdbcPersistenceAdapter dataSource="#mydatasource" >> databaseLocker="#mydblocker" /> >> </persistenceAdapter> >> >> and then define mydblocker via regular spring config? >> >> >> Gary Tully wrote: >> > >> > thanks for the heads up. It looks like it is time to have more than one >> > database locker implementation in the box. >> > A database locker implementation can be injected into the persistence >> > adapter via config if that helps in the short term. Can you validate >> that >> > Oracle works fine without the getMetaData call? >> > >> > I have reopened AMQ-1191, thanks. >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/AMQ-1191-for-5.3-broke-master-slave-locking-for-Oracle-tp24648059p24649622.html >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> > > > -- > http://blog.garytully.com > > Open Source Integration > http://fusesource.com > -- http://blog.garytully.com Open Source Integration http://fusesource.com
