[
https://issues.apache.org/jira/browse/FELIX-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Valchev updated FELIX-1441:
------------------------------------
Attachment: bundles-filter-template-i18n_status.patch
The attached bundles-filter-template-i18n_status.patch includes the following
changes:
- it searches the last received bundle data matching the filter (which is
regexp) against bundles id, name, symbolic name and version. (Client-Side only)
- the install/update is shown in a dialog now
- JS: uses a template for bundle entry given in the HTML instead of building
the elements on the fly.
- JS: the state of the bundle now can be translated, previously it was
hard-coded in the Java/JSON.
- JSON: removed 'actions' per bundle - now the JS decide which actions to be
shown and which not, the server-side now provides more data, than logic.
Felix, I was thinking about that server-side filtering. Maybe the cost of
adding such an option is quite big. A lot of I/O operations, temporary memory
for searching all manifest headers. A general search is too expensive.
As for the import/export packages, I though about a new Packages Manager
plugin. This might be a better solution. To see the list of exported packages,
their versions, exporters and importers. Then you can also filter by package
name.
> Search manifest entries of bundles
> ----------------------------------
>
> Key: FELIX-1441
> URL: https://issues.apache.org/jira/browse/FELIX-1441
> Project: Felix
> Issue Type: New Feature
> Components: Web Console
> Reporter: Sahoo
> Attachments: 2010-03-08 15 00 24.png,
> bundles-filter-template-i18n_status.patch, bundles.zip
>
>
> It will be good have an ability to have a search facility which searches
> bundle manifest entries of all installed bundles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
