Hi Jose
> 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".
>
> 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"/>
>
> 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.
>
> What do you think?
>   
I think all of your cases are valid and useful.. could you raise JIRA's
for the specific enhancements so that we could prioritize them for
implementation? for #2 about I think the ManagedLifecycle interface may
be useful.. As always.. If you would like to contribute any of these
enhancements you are most welcome!

asankha

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to