|
From:
<tor...@tu...> - 2005-11-25 17:39:35
|
Hi, Reportedly an aquaintance got it working. For my part, I even dug in the code of Hermes and don't understand = where the wildcard functionality is implemented, the SQL prepared statement = string in MessageServer.getUndeliveredMessages contains a 'WHERE DbTableManager.ATTRIBUTE_CONVERSATION_ID + "=3D?"' and = "query.setString(2, appContext.getConversationId());" and I didn't see that any other = method than getUndeliveredMessages was called to determine which messages to deliver. Is it some database-specific functionality we are relying on here? = Because as far as I remember, "WHERE field =3D '*'" is not standard SQL. Or is it that the sending of the message registers a listener for the conversation-id, even if the MessageListener parameter is null, and I = am trying to receive with a wildcard on the same Hermes instance that I am sending from? I am going to try this theory on Monday. /tobe -----Ursprungligt meddelande----- Fr=E5n: ebx...@li... [mailto:ebx...@li...] F=F6r Julien = Choulet Skickat: den 25 november 2005 17:52 Till: ebx...@li... =C4mne: [ebxmlms-develop] Problem with WildCards Hi, I have read all the posts on the wildcard use in application context = but I can't make it work. I made sure no other MessageListener is registered in Hermes but still = the listener won't pick the messages (only one entry in mshconfig). If I = put the exact context parameters for the received message, then messages are correctly picked up. Do you have any clue ? -- Julien Choulet ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick _______________________________________________ ebxmlms-develop mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop |