Drive mappings fail in 1.2.17

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create Drive mappings
2. Start the Service Container
3. Check the debug logging / try to use the drive letter

What is the expected output? What do you see instead?
Expected debug logging:
Current Network mapings : DriveLetter: 'P:'
Location: \\servername\sharename
Username: null
Password: null

Actual debug logging:
No drive mappings defined.

What version of the product are you using? On what operating system?
FileConnector 1.2.17, BOP-4 CU14

Please provide any additional information below.
ApplicationConfiguration.getNetworkDrives() says:
        int[] aiMapping = Find.match(iMappings, "fChild<" + PROP_DRIVE_MAPPING + ">");
This is old style NOM-searching which does not match the value of 
PROP_DRIVE_MAPPING: "/configuration/Configuration/drivemapping"
Changing the value to "drivemapping" fixes the problem, although of course it 
would be better to change to the new search style, and use the correct XPath 
(/configuration/Configuration/drivemappings/drivemapping)

Original issue reported on code.google.com by mdrai...@capgemini.com on 7 Feb 2011 at 1:09

[GoogleCodeExporter]

I assume this is the same issue as the Script Connector had: it cannot read the 
configuration properly, because an additional XML tag is in between.

Original comment by pgus...@gmail.com on 7 Feb 2011 at 1:15

[GoogleCodeExporter]

Fixed in the next releasr

Original comment by pgus...@gmail.com on 18 Feb 2011 at 12:11

• Changed state: Fixed

[GoogleCodeExporter]

cool!

Original comment by ma...@vandeveen.com on 19 Feb 2011 at 10:53