Re: [xmlblaster] JdbcQueuePlugin won't load

[Michael Atighetchi <matighet at bbn.com>]

Marcel, Michele,

thanks for your help. I got my setup working with a postgres 7.2
database. I dropped looking into support for mysql, as I will
eventually move to Oracle 9i (haven't figured out how to install the
oracle db yet ... ugh :(

The configuration options I'm using are:

ProtocolPlugin[JDBC][1.0]=org.xmlBlaster.protocol.jdbc.JdbcDriver
CbProtocolPlugin[JDBC][1.0]=org.xmlBlaster.protocol.jdbc.CallbackJdbcDriver
persistence/defaultPlugin=CACHE,1.0
queue/defaultPlugin=CACHE,1.0
useTopicStore=true
queue.persistent.url=jdbc:postgresql://<...>/test
cb.queue.persistent.url=jdbc:postgresql://<...>/test

On to the next issue: I see that new tables get created every time
a message is published. Since all the messages really correspond to a
single queue, they should just be stored as multiple lines within the
same table. Is there a way to specify the queue name upon publishing
new messages ?

Michael



On Wed, Feb 26, 2003 at 10:24:58AM +0100, Marcel Ruff wrote:
> >>I noticed a warning about useTopic=false (although I don't set it that
> >>way in the property file). After looking at the template property
> >>files supplied with xmlblaster, I added the following entries
> >>
> >>persistence/defaultPlugin=JDBC,1.0
> >>queue/defaultPlugin=JDBC,1.0
> >>useTopicStore=true
> 
> Probably you should prefer CACHE over JDBC:
> 
>   persistence/defaultPlugin=CACHE,1.0
>   queue/defaultPlugin=CACHE,1.0
>   useTopicStore=true
> 
> The CACHE implementation uses JDBC internally.
> Using JDBC directly you loose all performance
> benefits of the cache and it is not safer.
> 
> These lines will disappear as soon as we
> deliver a native persistence with xmlBlaster again.
> 
> regards
> 
> Marcel
> 
> 

-- 
matighet at bbn.com   BBN Technologies