On Fri, Mar 5, 2010 at 16:56, Felix Meschberger <[email protected]> wrote: > Hi, > > On 05.03.2010 16:47, Guillaume Nodet wrote: >> On Fri, Mar 5, 2010 at 16:42, Felix Meschberger <[email protected]> wrote: >>> Hi, >>> >>> Thanks for taking a stab at this. Looks great from my POV. >>> >>> Some issues I discovered on the Resource details page: >>> >>> * The item labelled "Imported Bundles" actually lists >>> imported services >>> * The button labeled "Start" probably means "Deploy and Start" >>> while the button labeled "Deploy" probably just deploys. >>> Could this be marked somehow ? >>> * The "optional" checkbox probably means "include or exclude >>> optional requirements", right ? Can this be claraified in the gui ? >> >> Yeah, sounds like good suggestions. >> >>> NB: I have tested with a default build of Apache Sling whose OBR setup >>> points to mainly Apache artifacts thus showing the drawback of using the >>> alphabet to segment the list (I do not have a better solution so, lets >>> not change ;-) ). >> >> If you want to see all the bundles, just use the following url: >> http://localhost:8181/system/console/obr?query=* >> Which you can obtain from entering '*' in the search box and hit return ... >> You'll see the full list. >> >> I think the default should be segmented because if your repository is >> big enough, the first request should not take minutes to display ;-) > > I think segmentation is great; I just wanted to say in my limited > english, that my setup has almost all bundles under "A" for "Apache XYZ" ;-)
LOL, you're right, I actually have the same problem :-) > > Regards > Felix > >> >>> Regards >>> Felix >>> >>> On 05.03.2010 09:31, Guillaume Nodet wrote: >>>> This week, i've done a major rewrite of the webconsole OBR's plugin. >>>> The two main problems were scalability and lack of information. >>>> Scalability was a problem because if your bundle containts lots of >>>> bundles, the time taken to serialize all the resources into json is >>>> prohibitive. >>>> Lack of information is because beyond the name of the bundle, you >>>> can't see anything. >>>> >>>> The approach i've taken is to display a list of bundles by starting >>>> letter, so the first time you open the tab, you'll see all bundles >>>> starting with 'A' >>>> you can send select another letter. The search box can also be used >>>> to select bundles which name contains a given sentence or even use >>>> more complex filters. >>>> For example you can use: >>>> package:(package=javax.transaction) >>>> in the search box, and all the bundles exporting this package will be >>>> displayed. >>>> >>>> In the bundles list, you can then click on the name and a list of >>>> versions will be displayed. >>>> Clicking on the version will display details about the bundle >>>> (imported / exported packages / services, required bundles, and the >>>> resolution of the mandatory dependencies). >>>> >>>> Feedback welcomed ! >>>> >>> >> >> >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
