Recently I have had to ask a very long question. The configuration involved is fairly extensive and will require any user to spend a decent amount of time investigating. Given that I would not expect someone to answer such a question for only 15 reputation, I have put a bounty on it, but I still have not gotten too many responses. Is there a way I could have written this question better in order to receive more answers?
Sometimes people won't read all the way to the bottom of your question to find out all the details. They may have the answer, but give up reading because the question is so long. One strategy that I have used is to put an "executive summary" at the top of the question. This should boil the problem down to just a couple of sentences. Mark it as such and set it off from the rest of the question so it doesn't look like one long ramble.
Using a summary gets your question out there, right in front. People who have some insight, then know that they may be able to help and could be encouraged to continue reading. You might also want to mention the bounty in your summary -- having that message at the bottom of your question seems to somewhat defeat the purpose in your case.
- Executive summary at the top
- Bolded specific questions at the bottom
- Don't list long files, configurations, code segments, etc inline - provide links so the question is simple and to the point, and anyone that wants detailed information can then dig into the links. (wish we had code folding on the site)
- Try to pare your question down to the absolute minimum.
- Break it up into several smaller problems/issues/questions if possible and ask them individually in separate questions.
- Explain what you've tried, why it didn't work, or why you can't use it if it did work.
- Provide only enough information to get people interested in asking you follow up questions - once they're hooked on the problem they may be more likely to spend time researching it.
At a certain point your question becomes too obscure/specialized and you won't be able to get quality answers to your question.
I think your bounty might work. Keep checking it, but also keep hammering away at the problem on your own and try to further update the question with any extra information you gather.
Whilst I'm no expert on Spring I do know that for some technologies it's hard to boil everything down into a single concise paragraph or two, and a couple of code snippets.
The important thing is that you've supplied as much of the configuration data that may be of value as you can, and because of the larger font size used by Prettify on Stack Overflow, this can make some questions look more long winded that they need to be.
I think what you've done is fine. It's a niche problem and perhaps there aren't so many eyes on Stack Overflow looking at this with the level of experience you're looking for.