Re: [ebxmlms-develop] Setup of ApplicationContexts

[Patrick Y. <kc...@ce...>]

RE: [ebxmlms-develop] Setup of ApplicationContextsMy comment inline.
Regards, -Patrick
  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Friday, March 28, 2003 6:10 AM
  Subject: RE: [ebxmlms-develop] Setup of ApplicationContexts


  In my listener I create a new Request with ApplicationContext("*", =
"*", "*", "*"), which presumably listens to everything. Since this =
registration is permanent, it only needs to be done once, but I presume =
it doesn't hurt to do it multiple times.

  Yes the registration is permanent, even when the client or Hermes =
quits. If the registered client goes offline, Hermes will store the =
messages for it. If Hermes goes offline, the registration information =
will be reloaded after it goes online again. It doesn't hurt to do =
registration multiple times.

  I haven't yet tested what happens if my listener registers with =
Hermes, but the listener is not up (or returns a failure response) when =
a message arrives.

  As said above, Hermes will store those messages and deliver them to =
the listener when it goes online again.

  There's a small problem here. My listener servlet registers itself =
with Hermes in its init() method. If my listener starts for the first =
time while Hermes isn't up, the registration won't work, and Hermes will =
never know about the listener. Therefore, I've added a doGet() to my =
listener servlet which also does the registration, so I can manually =
register whenever I like, just in case.

  Is there anyway to control the load sequence in app server?

  I also presume that it doesn't hurt to create an ApplicationContext =
with a null MessageListener. When I'm sending messages, I want to use =
the same MessageListener all the time, not a different one for every =
message. (I can't believe I haven't tested this yet. :-)

  The AppContext registered (through Request object) specifies which =
kind of messages you want to receive. You can use that Request object to =
send out any messages. The AppContexts of those sent messages are not =
necessariliy the same as the one you registered.

  PJDM=20
  --=20
  Peter Mayne=20
  Technology Consultant=20
  Spherion Technology Solutions=20
  Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602=20
  T: 61 2 62689727  F: 61 2 62689777=20

The information contained in this email and any attachments to it:

(a) may be confidential and if you are not the intended recipient, any =
interference with,=20
use, disclosure or copying of this material is unauthorised and =
prohibited; and

(b) may contain personal information of the recipient and/or the sender =
as defined=20
under the Privacy Act 1988 (Cth). Consent is hereby given by the =
recipient(s) to=20
collect, hold and use such information and any personal information =
contained in a=20
response to this email, for any reasonable purpose in the ordinary =
course of=20
Spherion's=20
business, including forwarding this email internally or disclosing it to =
a third party. All=20
personal information collected by Spherion will be handled in accordance =
with=20
Spherion's Privacy Policy. If you have received this email in error, =
please notify the=20
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s) =
supplied in=20
this email and any attachments without first entering into a contractual =
agreement with=20
Spherion. You further agree not to divulge any information contained in =
this document=20
to any person(s) or entities without the express permission of Spherion.