[MAGNOLIA-5086] AreaElement should ignore autogeneration problems on versioned nodes - provide details on others Created: 06/Jun/13  Updated: 06/Jun/13  Resolved: 06/Jun/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.5.9
Fix Version/s: 4.5.10

Type: Bug Priority: Major
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

As integration tests show, we sometimes run into a problem trying to auto generate AreaElements:

Parsing log /Users/daniellipp/Documents/git/mgnl_5.0/ce-bundle/magnolia-integration-tests/tests/target/java-io-tmpdir/Jetty_0_0_0_0_8088_magnolia.test.public.webapp.5.0.SNAPSHOT.war__magnoliaTestPublic__upicm4/webapp/logs/magnolia-error.log
========================================
ERROR  info.magnolia.templating.elements.AreaElement 06.06.2013 07:38:05 -- ignoring problem w/ creating area in workspace website for node a1154bb9-2f0f-4e17-ad31-2c1f5959c175
1 errors!

In fact we should distinguish: if we get RepositoryException trying to generate AreaElement on versioned node we can gracefully ignore it - if it's happening for "normal" nodes it might point to a severe problem and we need to have the full details (e.g. stack trace) in the logs.


Generated at Mon Feb 12 04:01:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.