Affects Version/s: None
Fix Version/s: None
Number of attachments :
Here is my ordering for the web services in my SimpleUrlHandlerMapping class:
TroubleshootingManager Service has an Array of Maps configured thru Aegis mappings. If I change the order of the entries in the xml config file and put, for instance, PeformanceMonitorService last, then the mappings get screwed up and they stop working (i.e. keyType not configured for property 'blah' in bean 'blah' ).
But if I reorder them the way it is shown here then everything is fine. This is a VERY strange error and I think something might be wrong the way services "share" mapping configurations. I was not able to track this back to any part of XFire, actually.
I put this issue 'critical' because I am afraid a "circular-reference" (deadlock) may occur if I add a "specific" 'bad' service to my mapping, which would lead to my application stop working.
I tried this with 1.1.2 version only because 1.2.1 has a problem with Arrays of Maps (there is an isse already open).
PS: I added Array of Maps mapping capability by modifying code, it COULD also be a bug included by me, but I touched just a few lines... who knows. Maybe we should look into this once the "official" Array of Maps mapping is fixed in 1.2.2