Re: [ebxmlms-general] Servlet client for Hermes

[Ronald v. K. <rv...@ab...>]

Patrick Yee wrote:

>
>>> - 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
>>
>>  
>>
> If Julien means can we write "Monitor" as a servlet, then I guess it 
> is possible. Of course, our assumption is, the information which is 
> currently captured interactively using Java Swing, like keystore 
> location, password, etc, shall be managed by the servlet in other 
> ways. One possible way is by pre-configuration.

Yes, I agree. Some other person on this list (won't mention any names 
Sacha ;-) ) likes to have a xml-rpc implementation. Since I made the 
monitor part rather flexible (see the 'WebAdmin and other contrib' 
thread this would not be to difficult now. Just find the time somewhere. 
One thing I like to do there is move the Command object internal into 
Hermes and not expose it to the outside world. Each monitor is then 
responsible for mapping a request into a Command object. e.g.
- an xml structure can have all command elements in tags
- a jms monitor gets the command elements from jms headers
- a servlet monitor gets it from request parameters

This is exactely what I was proposing on the other thread by splitting 
the use of the one servlet into separate things. Each implementation of 
a monitor is then also responsible for their own authentication (which I 
hope will one day be based on the principal from the servlet/j2ee engine

Ronald