Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Retail Modules] StoreServermajorhave not tried2019-03-19 12:422019-03-19 12:42
ReportermtaalView Statuspublic 
Assigned Tomtaal 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0040416: ResourceLocationRouter overrides standard router, provide override/extension mechanism

DescriptionThe location needs to be routed taking into account standard retail tables as well as sometimes custom tables.
An example is the resource location foreign key. The location should also be routed to the orgs of the resource.

However, currently we can only define one router per table. For the location table this router should normally defined in the standard retail sync module. This does not allow us to take into account custom modules like resource characteristics.
Steps To ReproduceSymmetric ds with retail sync and resource sync module
Proposed SolutionProvide an extension or override mechanism.

For example allow defining multiple synchronized table records for the same table but only use the one with highest priority.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2019-03-19 12:42 mtaal New Issue
2019-03-19 12:42 mtaal Assigned To => mtaal
2019-03-19 12:42 mtaal Triggers an Emergency Pack => No

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker