[MGNLREST-434] Change rest endpoint in Resource app does not trigger event to re-instance a new endpoint (6.3) Created: 27/Jun/22  Updated: 28/Nov/23

Status: Selected
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 3.0.0
Fix Version/s: 3.0.0

Type: Bug Priority: Major
Reporter: Oanh Thai Hoang Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 5.5h
Original Estimate: Not Specified

Attachments: PNG File definition-app.png     PNG File intellJ.png    
Issue Links:
Relates
relates to MGNLCT-190 adding new CT does NOT create workspace Accepted
relates to MULTISITE-133 New MultiSiteRegistry doesn't limit n... Closed
relation
is related to MGNLRESTCL-179 Test failures after bumping to Java 11 Closed
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:
Story Points: 5

 Description   

This happen only in 6.3 branch.

 

Step to reproduce: 

  • Change rootPath from "/" to "/magnolia-travels" property of any delivery endpoint in Resource app
  • Set breakpoint in any API and get rootPath to watch
  • See rootPath does not change even you see the new rootPath in definition app 

 

 

Problem must be in here, does not receive any event changes from registry



 Comments   
Comment by Michael Duerig [ 05/Jul/22 ]

IIUC, the underlying problem is the same one that cause RestClientDisabledIntegrationTest to fail. See MGNLRESTCL-179

Comment by Oanh Thai Hoang [ 08/Jul/22 ]

Here is my status for this ticket. I haven't finished yet but the problem only happen for rest in dx-core and norsu web app with 6.3 version. For magnolia-cloud, rest has no problem at all.

 

Because the change event register do not introduce in rest but it's in saas-config module in magnolia-cloud only.

So we should introduce same for content type, rest, rest client as well. Example for content type proposal

 

Here is some thought from Mika: https://git.magnolia-cms.com/projects/MODULES/repos/content-types/pull-requests/60/overview?commentId=98175

 

Generated at Mon Feb 12 06:59:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.