[BLOSSOM-251] acme example for Blossom generates invalid blossom-servlet.xml Created: 04/May/18 Updated: 04/May/18 |
|
| Status: | Open |
| Project: | Blossom |
| Component/s: | blossom-spring-loaded |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roger Waldner | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I tried the given example in https://documentation.magnolia-cms.com/display/DOCS56/Getting+started+with+Blossom through the end. When I then load the resulting blossom-servlet.xml into my Eclipse workspace it says for line 63 (<entry key="imgfn">):
|
| Comments |
| Comment by Richard Gange [ 04/May/18 ] |
|
Hi Rodger- I see what you mean. Often Eclipse will complain about different things related to XML validations. However, perhaps there is something that could be improved with the module. Let me kick this ticket over to the Blossom project and have the dev team take a look. I will say it does not seem to stop me from running my project. Cheers! |
| Comment by Roger Waldner [ 04/May/18 ] |
|
Well it is not only Eclipse that complains. During startup of the server I had the same error. But perhaps other people need to configure this part ... |