FeatureLock merged with DefaultFeatureLock
------------------------------------------
Key: GEOT-3476
URL: http://jira.codehaus.org/browse/GEOT-3476
Project: GeoTools
Issue Type: Improvement
Components: data
Reporter: Jody Garnett
Assignee: Jody Garnett
Fix For: 2.8-M1
We recently completed GEOT-3055 to merge Query with DefaultQuery.
Problem was Query was not all of the data structure involved in making a
request. The rest of it was FeatureLock.
And this one is even more messed up, with a Factory, a default implementation
and so forth. The same story applies, the interface is not earning its keep,
and the complexity is not warranted. This time it is a bit easier as
FeatureLock does not define any setter methods.
Same solution applies:
{code}
class FeatureLock {
protected String authorization;
protected long duration;
public FeatureLock(String authorization, long duration ){
this.authorization = authorization;
this.duration = duration;
}
public long getDuration(){
return duration;
}
...
}
class DefaultFeatureLock extends FeatureLock {
DefaultFeatureLock( String id, long duration ){
super( id, duration );
}
...
}
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
