Paul. - make it possible to have more than one Synapse configuration flow instantiated when starting a Synapse server
What I mean with this is that as for as I know, one Synapse configuration flow is given as parameter when starting the Synapse serverr. By default Synapse searches for a synapse.xml file in the repository conf directory. If this is true, I think it would be a nice improvement to support multiple configuration flows in stead of only one. I have not looked at the WSO2 console yet, I will do this shortly, thanks. Quartz scheduling would be nice to support functionality to do bulk invocations to a service. So Synapse stores incoming messages and a specified time intervals a service is called with all the messages that have been sent to Synapse. I agree with you that for 1.0 we should not do major additions and should focus on performance improvements etc. Tijs > > van: "Paul Fremantle" <[EMAIL PROTECTED]> > datum: 2007/01/11 Thu AM 10:14:34 MET > aan: [email protected] > onderwerp: Re: 1.0 thoughts > > Tijs > > I'm not sure I understood this: > > > - make it possible to have more than one Synapse configuration flow > > instantiated when starting a Synapse server > > > - some kind of administrative console, this can very simple to begin with > > showing just the deployed flows and a possibility to deploy new flows and > > remove existing flows. > > Have you seen the WSO2 console on top of Synapse? It is ASL licensed > too, and fully open source. See here: > http://wso2.org/projects/esb/java > > > > - support for WS-eventing via the Axis2 Savan module > +1 > > > - integration with quartz to provide support for scheduling > Can you give a use case? > > I think we should start a wiki page to capture our plan. I personally > wanted to do the Savan and some of the more complex aspects post 1.0. > Here's my thinking: > > Axis2 spent a long time at 0.9x. When they did go to 1.0, that is when > they really got some users and feedback. The result is that the 1.1 > release was the really useful highly-tested version. > > So I'd like to see if we can do a 1.0 in the next month or so to aim > to get more downloads and involvement. Then we can start to add new > function, and aim for a really cracking 1.1. > > If we follow this path then the main aim of 1.0 would be just to > stabilize any API or core architecture issues. > > Paul > > > > > > Regards, > > > > Tijs > > > > > > > > van: "Paul Fremantle" <[EMAIL PROTECTED]> > > > datum: 2007/01/09 Tue PM 02:37:11 MET > > > aan: [email protected] > > > onderwerp: 1.0 thoughts > > > > > > Obviously the time is definitely here to have a 1.0 plan. > > > > > > The few things I've thought of are: > > > > > > 1) do some performance and scalability tests > > > 2) get at least the framework in place for non-blocking IO > > > 3) Add WSDL services - i.e. bootstrap the endpoints, MEPs, actions > > > from the WSDL, including fetching the WSDL from a registry. > > > > > > What else? > > > > > > Paul > > > > > > -- > > > Paul Fremantle > > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair > > > > > > http://bloglines.com/blog/paulfremantle > > > [EMAIL PROTECTED] > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Paul Fremantle > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair > > http://bloglines.com/blog/paulfremantle > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
