History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: GEOS-281
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: dblasby
Reporter: Holger Lang
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
GeoServer

LockIDs are not considered by the execution of transactions

Created: 08/Feb/05 11:19 AM   Updated: 29/Mar/07 02:06 AM  Due: 14/Mar/05
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3.0-beta

Time Tracking:
Original Estimate: 10 minutes
Original Estimate - 10 minutes
Remaining Estimate: 10 minutes
Remaining Estimate - 10 minutes
Time Spent: Not Specified
Remaining Estimate - 10 minutes

File Attachments: 1. Java Source File TransactionHandler.java (12 kb)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Holger Lang - 08/Feb/05 11:22 AM
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)); }


dblasby - 14/Mar/05 07:19 PM
patch applied - thanks!

Andrea Aime - 29/Mar/07 02:06 AM
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