Actually a List might make sense if the order you define faceting is the order you want to expose it. But that's a tiny bit far fetched. I would love for our API to be easily consumed by UIs but it's a tiny bit impractical at the moment. I've identified the name list issue, serializability is a concern (JSON) and Facet.getValue() for range facets is crap to expose. Emmanuel On Wed 2013-05-29 14:11, Hardy Ferentschik wrote: > One could also return the FacetRequest instances. Something like: > > interface FacetingManager { > Set<FacetingRequest> getAppliedFacetRequests(); > } > > Either way it should probably be a set. > > --Hardy > > On 29 Jan 2013, at 1:10 PM, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; wrote: > > > Trying to write a slightly generic code listing the facets and exposing > > them in a UI. I cannot find a way to list the faceting requests applied. > > > > Am I missing something? What do you think of adding > > > > interface FacetingManager { > > List<String> getFacetingNames(); > > ... > > } > > > > I'd love a less stringy API but I am out of idea. > > > > Emmanuel > > _______________________________________________ > > hibernate-dev mailing list > > hibernate-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev