Menu
▾
▴
Re: [ebxmlms-general] Open source Client to interact with Hermes
|
From: Patrick Y. <kc...@ce...> - 2002-12-10 01:20:42
|
Tony, Other than the "file system" method, you may find a GUI tool useful. We h= ave bundled with Hermes a GUI tool for testing the functionalities of our MSH. The name of the tool is Monitor. And you can execute the tool by followin= g the instruction in our installation guide - Chapter 8: Test Drive. The source code of Monitor is included in the distribution of Hermes, so it a= lso serves as an example of how to write a client of Hermes. Hope this helps. Should you have any further questions, please feel free = to post to the list. Thanks. Regards, -Patrick -- Patrick Yee System Architect Center for E-Commerce Infrastructure Development (CECID) Dept. of Computer Science and Information Systems The University of Hong Kong Tel: (852) 22415674 Fax: (852) 25474611 ----- Original Message ----- From: "Tony Slosar" <Ton...@su...> To: <ebx...@li...> Sent: Saturday, December 07, 2002 11:32 AM Subject: RE: [ebxmlms-general] Open source Client to interact with Hermes > Sorry - this would of course be the "file system" method described in t= he Development Guide. > > Thanks! > > -----Original Message----- > From: Tony Slosar > Sent: Fri 12/6/2002 10:29 PM > To: ebx...@li... > Cc: > Subject: [ebxmlms-general] Open source Client to interact with Hermes > > > > Hello, > > I have installed all of the required software and now have Hermes runni= ng. > > Does anyone know of a open source Client to interact with Hermes ?? > > Thanks! > > Tony > > -----Original Message----- > From: Patrick Yee [mailto:kc...@ce...] > Sent: Mon 12/2/2002 3:45 AM > To: Regis Dubois > Cc: EbXMLms List (E-mail) > Subject: Re: [ebxmlms-general] Hermes v0.9.2.0 released > > > > Hello Regis, > > In Hermes, application context is a four-tuple consist of: > > 1. CPA ID > 2. Conversation ID > 3. Service > 4. Action > > This four-tuple will uniquely identify the clients. So I guess = in your case > you are have clients that use the same application context with different > ToPartyID only. If this is the case, please try to reassign the application > context to make it unique for each client. > > Hope this helps. > > Regards, -Patrick > -- > Patrick Yee > System Architect > Center for E-Commerce Infrastructure Development (CECID) > Dept. of Computer Science and Information Systems > The University of Hong Kong > Tel: (852) 22415674 > Fax: (852) 25474611 > > ----- Original Message ----- > From: "Regis Dubois" <Reg...@va...> > To: "Patrick Yee" <kc...@cs...> > Sent: Thursday, November 28, 2002 5:32 PM > Subject: RE: [ebxmlms-general] Hermes v0.9.2.0 released > > > > Hello Patrick, > > > > Don't Worry I'm now using the 2.0 package for developping my client. > > You are right the /bin is in the all-in-one package (wich I don't need > > anymore because I compiled the source file :-) ) > > > > I'm glad that hermes now support the loopback because I rathe= r like to > > develop on the same machine rather than 2 machines as before, and it will > be > > more convenient to make a demonstration of the prototype to o= ur clients. > > > > I have but a question: > > If I am developping to clients communicating together on the same machine > > using Hermes, I'll send all messages to the same url: > > http://localhost:8080/msh > > my problem is that even though I'm using different frompartyI= D and > > topartyID, the messages will be pulled by the first client > > that will register itself with the application context -> the from and to > > ID's are inoperative. > > The only solution I see to fix this problem is to set up 2 ms= h on the same > > machine. (which is maybe impossible?). > > Am I clear with my problem? Is there a solution you know to f= ix it? > > > > Cheers, > > > > Regis > > > > > -----Message d'origine----- > > > De : Patrick Yee [mailto:kc...@cs...] > > > Envoye : jeudi 28 novembre 2002 02:40 > > > A : Regis Dubois > > > Cc : ebx...@li... > > > Objet : RE: [ebxmlms-general] Hermes v0.9.2.0 released > > > > > > > > > Hello Regis, > > > > > > Are you downloading binary package? As far as I know, we > > > don't have bin > > > directory included in binary package. The bin directory is > > > distributed in > > > a so-called "all-in-one" package. You can find the > > > "all-in-one" package at > > > www.freebxml.org, which is another website for distributing > > > open source > > > ebXML software packages. > > > > > > Another choice is you can get link your client with msh.jar > > > found in lib > > > directory of the binary package. It should contain all the classes you > > > need. Yet another alternative is you can download the sourc= e > > > package and > > > compile the clas > > > > > > Please use 0.9.2.0 whenever possible, it is more functional= ly > > > complete. > > > And please don't use 0.9.1.3 to develop client for 0.9.2.0. > > > They are not > > > compatible. In our convention, 0.9.1.x is not compatible wi= th 0.9.2.x. > > > > > > Regards, -Patrick > > > > > > On Wed, 27 Nov 2002, Regis Dubois wrote: > > > > > > > Hello Patrick I downloaded the 9.2.0 Hermes MSH binary > > > package in order to > > > > upgrade from the 9.1.3. > > > > > > > > but could not find the /bin directory in the package whic= h > > > I use to develop > > > > my ebXML client. > > > > Is that normal? should I use the one provided in the 9.1.= 3 package? > > > > > > > > Cheers > > > > > > > > -----Message d'origine----- > > > > De : Patrick Yee [mailto:kc...@ce...] > > > > Envoye : mardi 26 novembre 2002 05:37 > > > > A : EbXMLms List (E-mail) > > > > Objet : [ebxmlms-general] Hermes v0.9.2.0 released > > > > > > > > > > > > > > > > Dear all, > > > > > > > > We are pleased to announce a new release of Hermes today. > > > You can download > > > > the latest release either from our project homepage on SourceForge ( > > > > http://sourceforge.net/projects/ebxmlms > > > > <http://sourceforge.net/projects/ebxmlms> ), or from freebXML.org ( > > > > http://www.freebxml.org <http://www.freebxml.org> ). > > > > > > > > Thanks a lot for your support. For your information, here > > > is the release > > > > note of this release: > > > > > > > > Version 0.9.2.0 > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > - Supported transaction locking of a message based on its message ID > > > > - Added clean up code to properly free resource such as > > > Resultset, Statement > > > > - Added database fields in vision to support sync reply, > > > message order and > > > > persist duration > > > > - Bug fixed: now deliver message to application works > > > properly no matter > > > > what > > > > mode is used for the MSH client to get message from MSH server > > > > - Added an optional feature: positive acknowledgment to M= SH > > > client if the > > > > message is successfully sent to the destination > > > > - Added a system feature: clean halt, which will stop all > > > sending and > > > > receiving > > > > processes, and the MSH client will receive error messag= es > > > as if the > > > > messages > > > > are not sent successfully > > > > - Added a system feature: backup and restore of MSH state= s > > > and repository > > > > - Bug fixed: no more NullPointerException when fail to > > > authenticate the > > > > command > > > > object due to missing specification of user name/passwo= rd > > > in client side > > > > - Extended the Request API and make it more user-friendly > > > > - Added a system feature: to query the message status > > > > - Bug fixed: now the message can be stored properly to > > > repository even when > > > > the MSH is under stress > > > > - Retry time is now calculated more accurately even if th= e > > > MSH is halted > > > > between retries > > > > - Added a system feature: now we can delete a message in > > > the queue if it has > > > > > > > > not bee nsent successfully > > > > - Added a system feature: archiving the repository of MSH > > > > - Restructured logging > > > > - GUI in MSH Monitor updated to demonstrate the new featu= res > > > > - Modified the namespace to conform to ebMS Specification [2.3.1] > > > > - Bug fixed: NullPointerException when fromUTCString is > > > given an incomplete > > > > date/time string. > > > > - Bug fixed: NullPointerException when an error message i= s > > > received from the > > > > > > > > other MSH (e.g. TimeToLive expired) that needs to be > > > forwarded to the > > > > user. It > > > > was previously caused by the "null" value of > > > mshConnection variable in > > > > onMessage() function when an error message is received. > > > > - Added user interface to add TimeToLive to the message. > > > > - Detailed message status that includes information in > > > SentMessage and > > > > ReceivedMessage table. > > > > - Changed the placement of the text field "Time to Live". > > > > - Appends "charset" to the content-type mime header. > > > > - Added namespace references so that the generated ebXML > > > messages can be > > > > validated. > > > > - Implements "getTrustedRepository()" API. Now it can get > > > trusted repository > > > > locatons from the MSH directly. > > > > - Changed the database column name to avoid any possible > > > SQL keywords > > > > - Fixed the bug that the sending threads are not restarte= d > > > after resuming > > > > MSH from > > > > halt state. > > > > - Fixes the use case that connection pool cannot be reset > > > successfuly if a > > > > connection cannot be closed successfully. > > > > - Fixes the use case that NullPointerException will resul= t if > > > > getMessageStatus() > > > > is used to query more than one message. > > > > - Fixed the bug that the sending threads are not restarte= d > > > after resuming > > > > MSH from > > > > halt state. > > > > - Fixed the bug that diagnosis dump only parses the date part of the > > > > date/time > > > > specified. > > > > - Used CommandConstants objects to contains command > > > constants, so as to > > > > enforce > > > > maximum compatibility of Command objects across version. > > > > - Fixed the bug that diagnosis dump cannot dump database when both > > > > Application > > > > Context and Starting / Ending date/time are specified. > > > > - Retry sending acknowledgment only if the current thread > > > sending the ack > > > > does not > > > > exist. > > > > - Fixed the use case that if the application context cann= ot > > > be archived > > > > because > > > > some of the messages are not ready, archiveByDate() and > > > > archiveByAppContext() > > > > return an invalid error message. > > > > - Fixes the MSH backup function. Now it returns failure > > > message correctly in > > > > case backup operation failed. > > > > - Fixes the use case that archive only creates the > > > directory on the first > > > > time of > > > > invocation if the destination directory does not exist; and runs > > > > successfully > > > > in subsequent runs. > > > > - Allow database password to be zero-length in diagnosis > > > tool configuration > > > > file. > > > > - Modified the MSH properties file to demonstrate correct > > > settings. The > > > > message > > > > repository and the objectstore directories cannot have = a > > > parent-child > > > > relationship. > > > > > > > > > > > > Regards, > > > > -Patrick > > > > -- > > > > Patrick Yee > > > > System Architect > > > > Center for E-Commerce Infrastructure Development (CECID) > > > > Dept. of Computer Science and Information Systems > > > > The University of Hong Kong > > > > Tel: (852) 22415674 > > > > Fax: (852) 25474611 > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > ebxmlms-general mailing list > ebx...@li... > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general > > > N=18uXu)=19Ylg=07=17=C9=B6HzGykzwjYX=E1=A4=82XY=E0=A0=81=E9=AD=A9=CB=B2= q=07ztX=E1=AD=B6~zwX=E1=B4=B6=CB=9Dykzw > > +,=7F =E9=9A=8AX'u=DE=BCN=18ggr=E5=89=9E=1EzH^j =1B= m =18=07( =1F o=19 zwjYXX Y=07z X y+ z m b q =07 =7F+-=EC=8D=B9=ED=B6=B3b ~o=19=DE=A5 = zw > |
