<snip>
> I'm not sure I fully understand the issue. You mean if a ft _unrelated_ 
> to the request under execution can't be computed? if so, it shouldn't, 
> ok. If the ft is related to the request (say a request involving more 
> than one ft) the request should obviously fail.
> 
> By the patches at GEOS-3049 it seems you're in need for an enabled() 
> method in FeatureTypeInfo and StoreInfo?
> only concern is if it's gonna scale. Right now the enabled() derived 
> property does not check for actual resource availability, just cascades 
> the isEnabled() property. But if we get to force the acquisition of the 
> DataStore/FeatureType I'm not sure how well it'll behave UI lists wise 
> (though yeah, when it comes to scaling to thousand of layers we'll have 
> to implement some sort of deferred list loading that plays well with 
> paging).
> 
> So what about this: keep enabled() being just a configuration concern, 
> no I/O nor exceptions involved, and add a reachable() property that 
> checks the involved resource (featuretype, datastore, coverage reader) 
> is actually accessible? This one should be used in more constrained 
> situations (non bulk) and may avoid a lot of try{get to the resroucepool 
> and grab the resource}catch(resource pool complains){}

I think I agree with Gabriel in that adding a derived property which 
just used other properties is one thing, but adding a method that does a 
full blown resource lookup is another, and something I would like to 
avoid on model objects themselves.

As for the case described in GEOS-3049, I think just a better check on 
startup will fix that, since it involves physically removing jars from 
geoserver and restarting. I have not been able to reproduce a similar 
issue by simply brining a database down in between two requests. The 
behavior in that case seems reasonable, unless i am failing to reproduce 
the real issue.
> 
> does that make sense?
>> Cheers
>> Andrea
>>
> 
> 


-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to