[Yanel-dev] Resource has workflow, but not live yet and hence show most recent revision or show a 404

Guillaume Déflache guillaume.deflache at wyona.com
Fri Sep 25 15:59:52 CEST 2009


Michael Wechner schrieb:
> Bruno von Rotz schrieb:
>> shouldn't we wait and collect similar requests to make it then 
>> worthwile to create a new API version?
> 
> agreed
>> Maybe there are more.
> 
> please see http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=5096
> 
> I have opened a bugzilla entry to collect possible API changes
> 
> http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=7264

I am adding mine here and not in Bugzilla because I think it's better to 
discuss these 1st:

OTOH:

- parametrizable 'getRepoNavigation' method, for e.g. to get the 
sitetree revision at some given point in time
   (also not sure why we abstracted the name further as the API always 
returns a Sitetree anyway)

- the 'getMenuClass' method should probably be replaced by a 'getMenu' 
method which would return a Menu instance: no need for the client code 
to do instantiation itself, we could still have an Object... parameter 
for constructor parameters

- replace the 'getConfigFile' method by a 'getConfigInputStream' one if 
possible or remove it entirely: I guess we only use that to build 
file-system paths but using File makes testing hard: maybe a 
'getRealmFilesURL' is more what is needed?

- moving the many i18n/translation/language methods to a dedicated 
component (with a better name that *Manager ;) if possible) could also 
shrink the API quite a bit IMHO

- ditto for proxying stuff: this blocks 
http://bugzilla.wyona.com/cgi-bin/bugzilla/show_bug.cgi?id=4964 (Neutron 
Auth also needs a proxy config to work and available JDK abstractions 
did not cut last time I check)


WDYT?


More information about the Yanel-development mailing list