+1. I see no reason why we don't do that.
Francisco Borges wrote:
Any opinions about changing that? (despite our CR1 status)
I like the idea but I'm not sure it is the right time to do it and delay 2.3.0.Final release much further.
This would not impact much AS7 integration since we use the HornetQ configuration API directly. However, I think that doing a concerted effort around configuration API would be better addressed in the next major release as that would leave us with the opportunity to break API/schema as it fits us.
btw, I talked to Francisco about using a builder-style API for HornetQ configuration. That'd fit nicely with any configuration schema changes...
I agree with Jeff, it means re writing the AS7 integration layer and transformers to handle the new config. lets wait for now