Jose Comments inline
> I'm using Synapse 1.1 and I need some features that I think there are generic > enough so as to add them to the core. If some of them exists please tell me > how to do. > > 1) Load local entries resources from classpath > When defining a localEntry the src attribute specifies a resource from a URL. > It would be useful to load the resources from classpath using something like > (spring) src="classpath:someFile.xml". +1 I like this syntax. > 2) Possibility to load spring beans before Synapse mediation > At this moment SpringMediator creates the Spring application context at the > first time it mediates a message. This can be expensive (is my case) due to > resources creation (DB connections, etc.). For this I think it would be > necessary to add the possibility to load the spring configuration at the > SpringMediator creation. > > <spring:spring bean="exampleBean1" key="string" > loadContextOnStartup="true"/> Is there any reason to not do it always on startup? When we wrote the Spring mediator we didn't have the managedLifeCycle model -- so we had to do it on first invocation. However, I suggest we just change this to ALWAYS load the context on startup. > 3) Pass the SynapseException through the Synapse context > I've seen that SynapseMessageReciver captures SynapseException and handles it > with a FaultHandler. FaultHandler takes the exception message and stacktrace > and puts it into the synapse context. I think it would be useful to put the > exception into the synapse context so as to retrieve it from a custom > mediator in a fault sequence and do a better handling. +1 > What do you think? Thanks for the feedback! Always appreciated. Paul -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
