[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[xmlblaster] confusing XPath subscription behaviour

I have been doing some experimentation with including my own metadata within blaster's key header. The test published message with key header comes through when I submit the following predicate:
 
-xpath /xmlBlaster/key/metadata/BasicTemporal/beginning_date_time_group[hour_time=21]
 
and the message received by the subscriber is:
 
<xmlBlaster>
 <key oid='Pubber'>
  <metadata><baseObject><InfoObjectType><Name>mil.af.rl.jbi.training.basic</Nam
><MajorVersion>1</MajorVersion><MinorVersion>0</MinorVersion></InfoObjectType><
baseObject><BasicTemporal><beginning_date_time_group><day>11</day><hour_time>21
/hour_time><minute_time>23</minute_time><time_zone>Z</time_zone><month_name>Jun
</month_name><year>2001</year></beginning_date_time_group><ending_date_time_gro
p><day>12</day><hour_time>06</hour_time><minute_time>13</minute_time><time_zone
Z</time_zone><month_name>June</month_name><year>2001</year></ending_date_time_g
oup></BasicTemporal></metadata>
 </key>
<content size='2'>
Hi
</content>
 <qos>
  <sender>/node/xmlBlaster_192_122_1_201_3412/client/combsv/-46</sender>
  <subscribe id='__subId:xmlBlaster_192_122_1_201_3412-XPATH1112448315531000000
/>
  <rcvTimestamp nanos='1112448326390000000'/>
  <queue index='0' size='1'/>
  <isUpdate/>
 </qos>
</xmlBlaster>
 
 
When I submit the following subscription predicate however:
 
-xpath /xmlBlaster/key/metadata/BasicTemporal/beginning_date_time_group[hour_time>=21]
 
I get:

[Apr 2, 2005 8:39:35 AM ERROR main Subber] XmlBlasterException errorCode=[user.q
uery.invalid] serverSideException=true location=[XmlKeyDom] message=[#exported S
orry, can't access, query syntax of '/xmlBlaster/key/metadata/BasicTemporal/begi
nning_date_time_group[hour_time' is wrong : com.jclark.xsl.om.XSLException: expe
cted ]] [See URL http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.err
orcodes.listing.html#user.query.invalid]
 
clearly since the attribute is 21 this should work.
 
Any ideas?
 
On a different topic. I ran a test based on the supplied HelloWorldSubscribe.java code. If I start up a publisher and it gets the first message along with a message when I kill the publishing application. If I try to run the publishing application a second time the subscriber gets nothing. Is there a subscribing end client assumption (attribute) being set that I am misinterpreting?
 
Many Thanks
Vaughn  

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com