|
From: Patrick Y. <kc...@ce...> - 2004-06-12 08:29:07
|
Ronald, My apologies. Your previous mails in January have been staying in my TODO mailbox for months. I wanted to review it but never have the time to do so. :-( Hermes is an open source project. Clearly we should leverage on the community effort to develop it. Therefore, we welcome your contribution, the only obstacle out there is resource. Given this, it would be helpful to us to keep the contribution incremental, so that we can review and process the changes in a shorter time. If my proposal is agreeable, we can work out a priority list for us to process in the coming schedule. We are going to package and name the whole thing as 1.0. Before that, we still have a couple of changes planned. Do you think your contribution is mature enough to get into the 1.0 package? Thank you for your effort! Regards, -Patrick Ronald van Kuijk wrote: > Hi all, > > It has been discussed before on this list, but I'd like to discuss it > a little again. There are some things, especially sending messages to > Hermes, that are really integrated with the servlet front-end. A > request object is used alot in places where imho a more abstract > approach could be used. The reason I ask this is we are now working on > realy integrating Hermes in an open source BPM/WFM/B2B/EAI solution. > Sending messages from within the same appserver via a http connection > seems to me not the right way to go. The same is true for configuring > Hermes, it can currently only be done via the standalone client via http. > > A long time ago I changed some things in my local version of hermes, > so sending messages could also take place in a more direct manner, > either by calling a certain class or using a jms queue. I even made it > configurable, so it is not required to have JMS installed for > using/compiling it in just a servlet engine. for configuring the > server I made a small web interface that allows you to configure > currently 40% of the things. > > Are the project owners interested in these changes and willing to > accept a temporary decrease in stability in exchange for flexibility > of the application? We could first discuss the changes, since I'm > willing to adapt it to everybodies liking. > > Kind regards, > > Ronald |