|
If you were logged in you would be able to see more operations.
|
 Google issue summary
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
5.2 M1,
5.1.2
|
|
|
Time Tracking:
|
|
Original Estimate:
|
1 hour
|
|
|
Remaining Estimate:
|
1 hour
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
| Resolution Date: |
28/09/07 17:35
|
| Require Callback: |
No
|
| Participants: |
Georges Racinet
|
| Tags: |
|
|
The results provider cache bean uses a special class (EmptyResultsProvider) to return an empty set of results, e.g, in cases of invalid queries. Some nuxeo based projects use providers with an extended API and their xhtml fragments choke on this class. They should be able to register their own empty results provider class to avoid the curse of shielding all EL expressions beforehand.
|
|
Description
|
The results provider cache bean uses a special class (EmptyResultsProvider) to return an empty set of results, e.g, in cases of invalid queries. Some nuxeo based projects use providers with an extended API and their xhtml fragments choke on this class. They should be able to register their own empty results provider class to avoid the curse of shielding all EL expressions beforehand. |
Show » |
|
Improvement
Resolved
Minor
Need to make empty provider configurable
Actually the type to generate might depend on the provider, so I let the provider farm do the job. The interface is kept unchanged in 5.1, but this will be added to it for 5.2