FW: [ebxmlms-general] Wildcards not Working

[Portelli, J. F <Joe...@te...>]

            The reason why wildcards were not working was as Gait said.
We now have a working Listener. I'm posting this to everyone as its
generally relevant info.

=20

            Thanks Gait.

=20

Joe Portelli
Fab Capodicasa

=20

  _____ =20

From: ebx...@li...
[mailto:ebx...@li...] On Behalf Of Gait
Boxman
Sent: Wednesday, 23 March 2005 6:16 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] Wildcards not Working

=20

Hi Joe,

it might be, if you previously registered a MessageListener that has a
closer match to the parameters than your wildcard.
When you register a Listener, the server keeps track of it until you
unregister it. When your listener is not active, the server will cache
the messages for that Listener, and not deliver it to a listener with
more generic parameters.
To ensure the message are not held for another Listener: try with
different parameters on your message (all four), or
unregister all other Listeners (this can be tricky, but one thing you
could do is start the Monitor with the parameters in question and check
the unregister box.=20
Another way to make sure no other listeners are there is to completely
reset the database for the server, which is simple when running the
server with HSQL (stop tomcat, trash the folder with the DB and the file
cache, and restart the server), but more tricky with other DBs.

--Gait.

Portelli, Joe F wrote:=20

Hi,

According to previous messages, an ApplicationContext can be initialized
with wildcards (*,*,*,*) in order for a MessagerListener to receive all
messages. The problem I have is that with Hermes v1, wildcards to not
seem to work.

For example, if I start up the sample Monitor, and enter the
configuration details as:

            Cpa ID =3D *

            Conversation ID =3D *

            service =3D *

            action =3D *

in order to receive all messages, but then use the Send History tab and
send a message with these parameters:

            cpa ID =3D CPA_2002

            conversation ID =3D Item_No_128

            service =3D http://www.cecid.hku.hk/ebxml/service

            action =3D Order

I do not receive any messages on the Receive History Tab.

Is this normal?

Joseph F. Portelli