GeoServer

LockIDs are not considered by the execution of transactions

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.3.0-beta
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Activity

Hide
Holger Lang added a comment -

This will be fixed by modifying org.vfny.geoserver.requests.wfs.TransactionHandler.startElement(String, String, String, Attributes)

(line 200, after dealing the releaseAction)

insert

else if (atts.getLocalName.equals("LockId")) { LOGGER.finest("found LockId: " + atts.getValue(i)); request.setLockId(atts.getValue(i)); }

Show
Holger Lang added a comment - This will be fixed by modifying org.vfny.geoserver.requests.wfs.TransactionHandler.startElement(String, String, String, Attributes) (line 200, after dealing the releaseAction) insert else if (atts.getLocalName.equals("LockId")) { LOGGER.finest("found LockId: " + atts.getValue(i)); request.setLockId(atts.getValue(i)); }
Hide
dblasby added a comment -

patch applied - thanks!

Show
dblasby added a comment - patch applied - thanks!
Hide
Andrea Aime added a comment -

These issue has been in resolved state for at least one month (quite a bit, a lot more than one month). Batch transitioning them to closed state

Show
Andrea Aime added a comment - These issue has been in resolved state for at least one month (quite a bit, a lot more than one month). Batch transitioning them to closed state

People

Vote (0)
Watch (0)

Dates

  • Due:
    Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
10m
Original Estimate - 10 minutes
Remaining:
10m
Remaining Estimate - 10 minutes
Logged:
Not Specified
Time Spent - Not Specified