|
From: Ronald v. K. <rv...@ab...> - 2004-06-15 16:03:08
|
> -----Oorspronkelijk bericht----- > Van: Julien [mailto:ju...@ni...] > Verzonden: dinsdag 15 juni 2004 15:52 > Aan: ebx...@li... > Onderwerp: [ebxmlms-general] Servlet client for Hermes > > > hi all, > > i'm interested in integrating Hermes features in a web > application which was used to send simple SOAP messages with > servlets controlled by a workflow engine. My questions are: > > - is it possible to build a servlet client for Hermes > keeping all the features that are managed by a regular java > application? In other words is there something a Hermes > client like "Monitor" can't do with servlets? (authentication > using the existing authentication file system, etc...) Not yet, but there is some thinking going on to make these things possible in the future > - is it possible to use just part of it, for example to > build the ebxml soap message? Yes, look at the command object. It uses an ebxml message and some commands parameters. Trace back a little and you will se how a ebxml message is composed > - It is said in the documentation of Hermes that the > architecture chosen (a stub between the client and the > server) is used to resolve firewall issue. What kind of > firewall protection does it go through? In the case of > servlets on the client side sending information to the server > side, is there any firewall security aspect to consider? The client communicating with the server is based on http. A command object is passed to the server. So if the firewall does nothing more than port filtering you should be fine. If it does more and block e.g. none text/html mime times there is a problem since the mime time of this command object is different > should this design be kept? Again, there are some discussions going on on this issues as well. Nothing for the near future, but keep watching this forum, or better.... join the discussion, come with good ideas :-) Ronald |