I like the idea of deployable projects. If you took a zone to the next step where it would acually live in a separate config that you could deploy, start and stop independently of other 'zones' it would make SCM, team development and deployment much easier.
I second this. A config that I can check in with a solution that only contains topics/parties/pipelines that are applicable to that solution would be great. If, after deployment, they can be started/stopped independently would be great but allowing Neuron to "merge" in the config would be fine too.
I definitely vote for the ideas from Kris and Ryan about deployable solutions. Somehow to export the relevant parts for the solution from the development/test config into a package that can be imported into the config at next stage (qa/prod whatever).
Also I'd like to see the Service Engine be released. The betas looked interesting but of course it has to be stable for release.
And then stay focused on how Neuron fits into the MS stack with Oslo, Dublin etc.
I am new to Neuron ESB and in our current scenario,We need to process batch transactions comprising of ~1000 records and send them to Neuron ESB for further processing. I would like to understand what is the maximum size of payload that can be transferred using REST interface to Neuron ESB.See More
We have set up an ODBC adapter to poll a stored proc.We found that if the stored proc has a temporary table defined the rows returned are always 0.Any idea why this would be and what we can do to get around it?See More