[MGNLREST-172] Same-implementation problem is gone after decorating Created: 28/Feb/18  Updated: 25/Mar/22  Resolved: 25/Mar/22

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Hieu Nguyen Duc Assignee: Unassigned
Resolution: Inactive Votes: 0
Labels: consolidation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Endpoint v1


Attachments: PNG File problem.png    
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   

Steps to reproduce:

+ Put "duplicated-rest-endpoint" into "modules"

"duplicated-rest-endpoint/restEndpoints/duplicatedRestEndpoint.yaml"

class: info.magnolia.rest.delivery.jcr.v1.JcrDeliveryEndpointDefinition
implementationClass: info.magnolia.rest.delivery.jcr.v1.JcrDeliveryEndpoint
params:
  pages:
    workspace: website
    bypassWorkspaceAcls: true

+ Problems tab shows that the endpoint and tourFinder are using the same implementation that is not supported

+ Decorate it with "duplicated-rest-endpoint-decoration/decorations/duplicated-rest-endpoint/restEndpoints/duplicatedRestEndpoint.yaml"

params:
  pages:
    bypassWorkspaceAcls: false

=> Problem disappears!



 Comments   
Comment by Christopher Zimmermann [ 25/Mar/22 ]

Closing as inactive. Low priority issue.

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