You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-users@xml.apache.org by Heinrich Götzger <go...@gmx.net> on 2002/01/14 01:03:44 UTC

integration of Xindice in xmlBlaster

Hi,

I just commited the first alpha release of an integration of Xindice
(dbXML) as an implementation of a persistence layer
(I_PersistenceDriver.java).

To use it, you need a dbXML installed and running (I tested and developed
with 1.0b4). For members of the xmlBlaster list: you can get it at
http://www.dbxml.org.

Add according to your dbXML installation similar to your
$HOME/.[bash|ksh|zsh]rc file:
# dbXML
export DBXML_HOME=/opt/dbXML-Core-1.0b4
export PATH=${PATH}:$DBXML_HOME/bin
export CLASSPATH=${DBXML_HOME}/java/lib/dbXML.jar
export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/xmldb.jar
export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/juggernaut-1.0.jar
export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/openorb-1.2.0.jar
export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/xerces-1.4.3.jar
export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/xalan-2.0.1.jar

Do a new login, update your checked-out release and rebuild all.

In the meanwhile start a new xterm,
do a
$ cd $DBXML_HOME
start the dbXML (if it's not running anyway)
$ ./start

Copy the config/xmlblaster.properties.templates to $HOME or edit
it manually. You need to activate:

Persistence.LazyRecovery=true
Persistence.Path=xmldb:dbxml:///db
# (or wherever your db is running)
Persistence.Collection=xmlBlaster
# (which you need to create manually, but only once, by:
$ dbxmladmin ac -c /db -n xmlBlaster
check with:
$ dbxmladmin lc -c /db
Persistence.Driver=org.xmlBlaster.engine.persistence.xmldb.xindice.XindiceDriver

Start the xmlBlaster.

if you can see something like:

[Jan 14, 2002 12:53:58 AM WARN  XindiceDriver] * * * This Driver is under
development, it may not be used for production environment! * * *
[Jan 14, 2002 12:53:58 AM INFO  XindiceDriver] using collectionPath
'xmldb:dbxml:///db/xmlBlaster'
[Jan 14, 2002 12:53:58 AM INFO  RequestBroker] Loaded persistence driver
'org.xmlBlaster.engine.persistence.xmldb.xindice.XindiceDriver'
[Jan 14, 2002 12:53:58 AM INFO  XindiceDriver] Successfully got 1 stored
message-oids from xmldb:dbxml:///db/xmlBlaster

you're on the right way ;-)
It says which driver the persistence layer is using and that it got 1
message restored from it.

Publish some messages which are tagged 'durable', you can do this by using
the qos-tag:

      String qos = "<qos>" +
                   "   <isDurable />" +
                   "</qos>";

Check, if you want, by using for example
$ dbxml ld -c /db/xmlBlaster

        amIdurable-XmlCon.xml
        amIdurable-XmlKey.xml
        amIdurable-XmlQos.xml

Total documents: 3

and list a single content by using:
$ dbxml rd -c /db/xmlBlaster -n amIdurable-XmlKey.xml
<?xml version="1.0"?>
<key oid="amIdurable" contentMime="text/plain">
   </key>

Now you can to subscribe to your messages and see if they arrive well.

After restarting xmlBlaster all Messages tagged durable should be able to
subscribe to without being published now.


TRAPS/BUGS: What is with BLOBs? (question to Xindice-List):
            How can we store best binarie data?

TODO:       Need to finish Test-case!
            Simple demo!

Comments please.

enjoy


Heinrich
--
http://www.xmlBlaster.org




Re: integration of Xindice in xmlBlaster

Posted by "Mark J. Stang" <ma...@earthlink.net>.
Heinrich,
Thanks!   I will take a look at it as soon as I get a free moment!

regards,

Mark

Heinrich Götzger wrote:

> Mark,
>
> as promised, the answer.
> I just checked, and it is, as I suspected, the order of it. I tried to put
> the dbXML-stuff in the beginning and xmlBlaster would not start properly.
>
> Can someone confirm this please.
>
> This is my CLASSPATH:
> /home/goetzger/java/xmlBlaster/lib/jacorb.jar
> /home/goetzger/java/xmlBlaster/lib/idl.jar
> /home/goetzger/java/xmlBlaster/demo
> /home/goetzger/java/xmlBlaster/classes
> /home/goetzger/java/xmlBlaster/src/java
> /home/goetzger/java/xmlBlaster/lib/testsuite.jar
> /home/goetzger/java/xmlBlaster/lib/demo.jar
> /home/goetzger/java/xmlBlaster/lib/xmlBlaster.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-svggen.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-gvt.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-dom.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-xml.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-svg-dom.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-gui-util.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-css.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-util.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-script.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-extension.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-bridge.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-transcoder.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-parser.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-ext.jar
> /home/goetzger/java/xmlBlaster/lib/batik/batik-awt-util.jar
> /home/goetzger/java/xmlBlaster/lib/jaxp.jar
> /home/goetzger/java/xmlBlaster/lib/parser.jar
> /home/goetzger/java/xmlBlaster/lib/ejb2.0.jar
> /home/goetzger/java/xmlBlaster/lib/jms.jar
> /home/goetzger/java/xmlBlaster/lib/jta-spec1_0_1.jar
> /home/goetzger/java/xmlBlaster/lib/jaas.jar
> /home/goetzger/java/xmlBlaster/lib/connector.jar
> /home/goetzger/java/xmlBlaster/lib/activation.jar
> /home/goetzger/java/xmlBlaster/lib/mail.jar
> /home/goetzger/java/xmlBlaster/lib/xmlrpc.jar
> /home/goetzger/java/xmlBlaster/lib/gnu-regexp-1.0.8.jar
> /home/goetzger/java/xmlBlaster/lib/servlet.jar
> /home/goetzger/java/xmlBlaster/lib/test.jar
> /home/goetzger/java/xmlBlaster/lib/omquery.jar
> /home/goetzger/java/xmlBlaster/lib/xtdash.jar
> /home/goetzger/java/xmlBlaster/lib/jutils.jar
> /home/goetzger/java/xmlBlaster/lib/a2Blaster.jar
> /opt/dbXML-Core-1.0b4/java/lib/dbXML.jar
> /opt/dbXML-Core-1.0b4/java/lib/xmldb.jar
> /opt/dbXML-Core-1.0b4/java/lib/juggernaut-1.0.jar
> /opt/dbXML-Core-1.0b4/java/lib/openorb-1.2.0.jar
> /opt/dbXML-Core-1.0b4/java/lib/xerces-1.4.3.jar
> /opt/dbXML-Core-1.0b4/java/lib/xalan-2.0.1.jar
> /home/goetzger/java/xmlBlaster/lib/jndi-jdk1_3_1.jar
>
> list with:
>         for i in `echo $CLASSPATH| sed -e 's/\:/ /g'`
>         do
>                 echo $i
>         done
>
> On Sun, 13 Jan 2002, Mark J. Stang wrote:
>
> >Heinrich,
> >I tried, not very hard, to see if I could get one Client program to
> >work with dbXML and XML Blaster.   I ran into some conflicts
> >due to the difference ORBs being used.   Did you run into this
> >problem?   Did you solve it?   Tom Bradford offered to help get
> >the two to work together, but I had to move on.
> >
> >thanks,
> >
> >Mark
> >
> regards
>
> Heinrich
> --
> http://www.xmlBlaster.org


Re: integration of Xindice in xmlBlaster

Posted by Heinrich Götzger <go...@gmx.net>.
Mark,

as promised, the answer.
I just checked, and it is, as I suspected, the order of it. I tried to put
the dbXML-stuff in the beginning and xmlBlaster would not start properly.

Can someone confirm this please.

This is my CLASSPATH:
/home/goetzger/java/xmlBlaster/lib/jacorb.jar
/home/goetzger/java/xmlBlaster/lib/idl.jar
/home/goetzger/java/xmlBlaster/demo
/home/goetzger/java/xmlBlaster/classes
/home/goetzger/java/xmlBlaster/src/java
/home/goetzger/java/xmlBlaster/lib/testsuite.jar
/home/goetzger/java/xmlBlaster/lib/demo.jar
/home/goetzger/java/xmlBlaster/lib/xmlBlaster.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-svggen.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-gvt.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-dom.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-xml.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-svg-dom.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-gui-util.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-css.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-util.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-script.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-extension.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-bridge.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-transcoder.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-parser.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-ext.jar
/home/goetzger/java/xmlBlaster/lib/batik/batik-awt-util.jar
/home/goetzger/java/xmlBlaster/lib/jaxp.jar
/home/goetzger/java/xmlBlaster/lib/parser.jar
/home/goetzger/java/xmlBlaster/lib/ejb2.0.jar
/home/goetzger/java/xmlBlaster/lib/jms.jar
/home/goetzger/java/xmlBlaster/lib/jta-spec1_0_1.jar
/home/goetzger/java/xmlBlaster/lib/jaas.jar
/home/goetzger/java/xmlBlaster/lib/connector.jar
/home/goetzger/java/xmlBlaster/lib/activation.jar
/home/goetzger/java/xmlBlaster/lib/mail.jar
/home/goetzger/java/xmlBlaster/lib/xmlrpc.jar
/home/goetzger/java/xmlBlaster/lib/gnu-regexp-1.0.8.jar
/home/goetzger/java/xmlBlaster/lib/servlet.jar
/home/goetzger/java/xmlBlaster/lib/test.jar
/home/goetzger/java/xmlBlaster/lib/omquery.jar
/home/goetzger/java/xmlBlaster/lib/xtdash.jar
/home/goetzger/java/xmlBlaster/lib/jutils.jar
/home/goetzger/java/xmlBlaster/lib/a2Blaster.jar
/opt/dbXML-Core-1.0b4/java/lib/dbXML.jar
/opt/dbXML-Core-1.0b4/java/lib/xmldb.jar
/opt/dbXML-Core-1.0b4/java/lib/juggernaut-1.0.jar
/opt/dbXML-Core-1.0b4/java/lib/openorb-1.2.0.jar
/opt/dbXML-Core-1.0b4/java/lib/xerces-1.4.3.jar
/opt/dbXML-Core-1.0b4/java/lib/xalan-2.0.1.jar
/home/goetzger/java/xmlBlaster/lib/jndi-jdk1_3_1.jar

list with:
        for i in `echo $CLASSPATH| sed -e 's/\:/ /g'`
        do
                echo $i
        done



On Sun, 13 Jan 2002, Mark J. Stang wrote:

>Heinrich,
>I tried, not very hard, to see if I could get one Client program to
>work with dbXML and XML Blaster.   I ran into some conflicts
>due to the difference ORBs being used.   Did you run into this
>problem?   Did you solve it?   Tom Bradford offered to help get
>the two to work together, but I had to move on.
>
>thanks,
>
>Mark
>
regards

Heinrich
--
http://www.xmlBlaster.org


Re: integration of Xindice in xmlBlaster

Posted by "Mark J. Stang" <ma...@earthlink.net>.
Heinrich,
I tried, not very hard, to see if I could get one Client program to
work with dbXML and XML Blaster.   I ran into some conflicts
due to the difference ORBs being used.   Did you run into this
problem?   Did you solve it?   Tom Bradford offered to help get
the two to work together, but I had to move on.

thanks,

Mark

Heinrich Götzger wrote:

> Hi,
>
> I just commited the first alpha release of an integration of Xindice
> (dbXML) as an implementation of a persistence layer
> (I_PersistenceDriver.java).
>
> To use it, you need a dbXML installed and running (I tested and developed
> with 1.0b4). For members of the xmlBlaster list: you can get it at
> http://www.dbxml.org.
>
> Add according to your dbXML installation similar to your
> $HOME/.[bash|ksh|zsh]rc file:
> # dbXML
> export DBXML_HOME=/opt/dbXML-Core-1.0b4
> export PATH=${PATH}:$DBXML_HOME/bin
> export CLASSPATH=${DBXML_HOME}/java/lib/dbXML.jar
> export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/xmldb.jar
> export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/juggernaut-1.0.jar
> export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/openorb-1.2.0.jar
> export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/xerces-1.4.3.jar
> export CLASSPATH=${CLASSPATH}:${DBXML_HOME}/java/lib/xalan-2.0.1.jar
>
> Do a new login, update your checked-out release and rebuild all.
>
> In the meanwhile start a new xterm,
> do a
> $ cd $DBXML_HOME
> start the dbXML (if it's not running anyway)
> $ ./start
>
> Copy the config/xmlblaster.properties.templates to $HOME or edit
> it manually. You need to activate:
>
> Persistence.LazyRecovery=true
> Persistence.Path=xmldb:dbxml:///db
> # (or wherever your db is running)
> Persistence.Collection=xmlBlaster
> # (which you need to create manually, but only once, by:
> $ dbxmladmin ac -c /db -n xmlBlaster
> check with:
> $ dbxmladmin lc -c /db
> Persistence.Driver=org.xmlBlaster.engine.persistence.xmldb.xindice.XindiceDriver
>
> Start the xmlBlaster.
>
> if you can see something like:
>
> [Jan 14, 2002 12:53:58 AM WARN  XindiceDriver] * * * This Driver is under
> development, it may not be used for production environment! * * *
> [Jan 14, 2002 12:53:58 AM INFO  XindiceDriver] using collectionPath
> 'xmldb:dbxml:///db/xmlBlaster'
> [Jan 14, 2002 12:53:58 AM INFO  RequestBroker] Loaded persistence driver
> 'org.xmlBlaster.engine.persistence.xmldb.xindice.XindiceDriver'
> [Jan 14, 2002 12:53:58 AM INFO  XindiceDriver] Successfully got 1 stored
> message-oids from xmldb:dbxml:///db/xmlBlaster
>
> you're on the right way ;-)
> It says which driver the persistence layer is using and that it got 1
> message restored from it.
>
> Publish some messages which are tagged 'durable', you can do this by using
> the qos-tag:
>
>       String qos = "<qos>" +
>                    "   <isDurable />" +
>                    "</qos>";
>
> Check, if you want, by using for example
> $ dbxml ld -c /db/xmlBlaster
>
>         amIdurable-XmlCon.xml
>         amIdurable-XmlKey.xml
>         amIdurable-XmlQos.xml
>
> Total documents: 3
>
> and list a single content by using:
> $ dbxml rd -c /db/xmlBlaster -n amIdurable-XmlKey.xml
> <?xml version="1.0"?>
> <key oid="amIdurable" contentMime="text/plain">
>    </key>
>
> Now you can to subscribe to your messages and see if they arrive well.
>
> After restarting xmlBlaster all Messages tagged durable should be able to
> subscribe to without being published now.
>
> TRAPS/BUGS: What is with BLOBs? (question to Xindice-List):
>             How can we store best binarie data?
>
> TODO:       Need to finish Test-case!
>             Simple demo!
>
> Comments please.
>
> enjoy
>
> Heinrich
> --
> http://www.xmlBlaster.org