You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Delos <da...@gmail.com> on 2009/12/15 10:19:50 UTC
[Need review] The mock UI for displaying bundle information
Hi all,
OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
many Mbeans used to get bundle information in OSGI environment. So it's
necessary for admin console to show the information of OSGI bundles.
Therefore, Rodger and I mocked up a couple of portlets. Here are some
screenshots for the mock UI. As you can see, we have two portlets here, to
show the bundle list and bundle information. It's a initial draft based on
Dojo widgets without full javascript implementation.
Screenshot 1:
https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
Screenshot 2:
https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
In the attachment, 1 is the bundle list portlet, while 2 is the bundle
information portlet. Bundle list portlet gives a list of installed
bundles;besides, the portlet also allow user to stop/start/uninstall
bundles. Bundle information portlet is much simpler, it only display the
bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
obtain the information.
For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
A - With these widgets, user can install any bundle from file system. If
"start" is checked, the bundle will be started automatically after it's
installed.Meanwhile, user can also specify the start level of this bundle.
I'm not sure if the "Deploy New" portlet will be applicable for OSGI
bundles, so I just mock the installation UI according to Web console of
Felix.
B - All the possible actions can be taken to bundles. Every bundle can be
selected through the checkbox in front of it. Each time an action is taken
to all the selected bundles. If the action is not applicable for some
bundles, these bundles will be ignored.
C - Each column in the table can be sorted by clicking the column header.
The up arrow stands for sort asending while the down arrow stands for sort
desending.
D - The textbox here is used to filter bundles by symbolic name. Only the
bundles with symbolic name containing specified text will be shown. If no
text provided, all the bundles will show
E - The drop down list here gives the possible status of an installed bundle
- "resolved","starting","active","stopping". It's used to filter bundles by
status. If one status is selected, only bundle with status the same as
selected value will be shown. If no value is selected, all the bundles will
be shown.
That's all for the snapshot. Any comments?
Thanks a lot!
--
Best Regards,
Delos
Re: [Need review] The mock UI for displaying bundle information
Posted by Delos <da...@gmail.com>.
Thanks Alan for your comments!
See my reply in blue.
Sorry for the delay!
2009/12/17 Alan D. Cabrera <li...@toolazydogs.com>
> Very nice!
>
> On Dec 15, 2009, at 1:19 AM, Delos wrote:
>
> Hi all,
>
> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
> many Mbeans used to get bundle information in OSGI environment. So it's
> necessary for admin console to show the information of OSGI bundles.
>
> Therefore, Rodger and I mocked up a couple of portlets. Here are some
> screenshots for the mock UI. As you can see, we have two portlets here, to
> show the bundle list and bundle information. It's a initial draft based on
> Dojo widgets without full javascript implementation.
>
> Screenshot 1:
> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
> Screenshot 2:
> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>
> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
> information portlet. Bundle list portlet gives a list of installed
> bundles;besides, the portlet also allow user to stop/start/uninstall
> bundles. Bundle information portlet is much simpler, it only display the
> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
> obtain the information.
>
>
> I assume that you'll format the exported and imported packages in the same
> manner as BND in #1?
>
In fact, exported and imported packages are included in screenshot 2.
The format of exported and imported packages will be the same as that in Ma
nifest.MF.
>
> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>
> A - With these widgets, user can install any bundle from file system. If
> "start" is checked, the bundle will be started automatically after it's
> installed.Meanwhile, user can also specify the start level of this bundle.
> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
> bundles, so I just mock the installation UI according to Web console of
> Felix.
>
> B - All the possible actions can be taken to bundles. Every bundle can be
> selected through the checkbox in front of it. Each time an action is taken
> to all the selected bundles. If the action is not applicable for some
> bundles, these bundles will be ignored.
>
> C - Each column in the table can be sorted by clicking the column header.
> The up arrow stands for sort asending while the down arrow stands for sort
> desending.
>
> D - The textbox here is used to filter bundles by symbolic name. Only the
> bundles with symbolic name containing specified text will be shown. If no
> text provided, all the bundles will show
>
>
> I would have a drop down box to the left so that you could enter in:
>
> - imported packages
> - exported packages
>
> in addition to the Symbolic Name.
>
> It would also be great if one could trace the wirings to help discover
> where conflicts lie. Maybe this would be a different screen but I think
> that tooltips that showed the wirings would be pretty helpful.
>
It's a good idea to take "imported packages" and "exported packages" as
filters when we display bundle list.
>
> E - The drop down list here gives the possible status of an installed
> bundle - "resolved","starting","active","stopping". It's used to filter
> bundles by status. If one status is selected, only bundle with status the
> same as selected value will be shown. If no value is selected, all the
> bundles will be shown.
>
>
> I imagine the status would update automatically via some kind of comet
> call.
>
Sounds reasonable.
>
> Again, very nice!
>
> Regards,
> Alan
>
>
--
Best Regards,
Delos
Re: [Need review] The mock UI for displaying bundle information
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Very nice!
On Dec 15, 2009, at 1:19 AM, Delos wrote:
> Hi all,
>
> OSGI Bundle is a new item for Geronimo admin console and RFC 139
> defines many Mbeans used to get bundle information in OSGI
> environment. So it's necessary for admin console to show the
> information of OSGI bundles.
>
> Therefore, Rodger and I mocked up a couple of portlets. Here are
> some screenshots for the mock UI. As you can see, we have two
> portlets here, to show the bundle list and bundle information. It's
> a initial draft based on Dojo widgets without full javascript
> implementation.
>
> Screenshot 1: https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
> Screenshot 2: https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>
> In the attachment, 1 is the bundle list portlet, while 2 is the
> bundle information portlet. Bundle list portlet gives a list of
> installed bundles;besides, the portlet also allow user to stop/start/
> uninstall bundles. Bundle information portlet is much simpler, it
> only display the bundle information in OSGI framework. Mbeans
> defined in RFC 139 is a way to obtain the information.
I assume that you'll format the exported and imported packages in the
same manner as BND in #1?
> For better illustration, I added some markers (A,B,C,D,E) in
> snapshot 1.
>
> A - With these widgets, user can install any bundle from file
> system. If "start" is checked, the bundle will be started
> automatically after it's installed.Meanwhile, user can also specify
> the start level of this bundle. I'm not sure if the "Deploy New"
> portlet will be applicable for OSGI bundles, so I just mock the
> installation UI according to Web console of Felix.
>
> B - All the possible actions can be taken to bundles. Every bundle
> can be selected through the checkbox in front of it. Each time an
> action is taken to all the selected bundles. If the action is not
> applicable for some bundles, these bundles will be ignored.
>
> C - Each column in the table can be sorted by clicking the column
> header. The up arrow stands for sort asending while the down arrow
> stands for sort desending.
>
> D - The textbox here is used to filter bundles by symbolic name.
> Only the bundles with symbolic name containing specified text will
> be shown. If no text provided, all the bundles will show
I would have a drop down box to the left so that you could enter in:
- imported packages
- exported packages
in addition to the Symbolic Name.
It would also be great if one could trace the wirings to help discover
where conflicts lie. Maybe this would be a different screen but I
think that tooltips that showed the wirings would be pretty helpful.
> E - The drop down list here gives the possible status of an
> installed bundle - "resolved","starting","active","stopping". It's
> used to filter bundles by status. If one status is selected, only
> bundle with status the same as selected value will be shown. If no
> value is selected, all the bundles will be shown.
I imagine the status would update automatically via some kind of comet
call.
Again, very nice!
Regards,
Alan
Re: [Need review] The mock UI for displaying bundle information
Posted by Jack Cai <gr...@gmail.com>.
If I am a developer/admin, it would be interesting for me to just KNOW this
information, for example, for debug purpose or monitor purpose. This does
not have to be a checking step before removing some bundles. Hope this makes
sense to others too.
-Jack
Re: [Need review] The mock UI for displaying bundle information
Posted by Rex Wang <rw...@gmail.com>.
That is possible by using
bundleContext.getAllServiceReferences(class=service class,null)
and then traverse the ServiceReferences to find whose
getBundle().getSymbolicName/getVersion matches your bundle.
But, as I wrote above, is there any need to know such information?
-Rex
2009/12/16 Jack Cai <gr...@gmail.com>
> By "using" I mean service wiring, i.e., bundles that have a live instance
> of a service exported by this bundle. Is this possible?
>
> -Jack
>
>
> On Wed, Dec 16, 2009 at 10:39 AM, Delos <da...@gmail.com> wrote:
>
>> *Thanks Rex.
>>
>> There is a method "getRequiringBundles()" in BundleStateMbean defined in
>> RFC 139. I hope to get the bundle list for Jack's request. Do you think it
>> has taken #1 into account?*
>>
>> 2009/12/16 Rex Wang <rw...@gmail.com>
>>
>>
>>>
>>> 2009/12/15 Jack Cai <gr...@gmail.com>
>>>
>>> Nice work. A few comments -
>>>>
>>>> 1. Better add a "filter" or alike text before textbox D
>>>> 2. Area B is a little far away from the selection checkboxes, suggest to
>>>> move them closer. By design, users always need to select some bundles by
>>>> checking the check boxes and then move the mouse to the action buttons in B.
>>>> So the nearer, the better
>>>> 3. It looks like the buddle information page is pretty lightweight. Have
>>>> we considered to embed it into the list page? As a pop up or expandable
>>>> area...
>>>> 4. Might want to add paging function
>>>> 5. Might want to use icon to show the status
>>>>
>>>> Also, will it be interesting to show what other bundles are currently
>>>> using a certain bundle?
>>>
>>> There are three kinds of "using":
>>> 1. import-package/required-bundle wiring
>>> 2. service wiring
>>> 3. geronimo bundle dependency
>>> for #1, that means a view to show which one imports the packages the
>>> bundle exports.
>>> for #2, I think we don't need to care about that, because even if a
>>> service provider bundle is uninstalled, the bundle using the service object
>>> can still run without problems. OSGi framework will maintain the service
>>> object for this bundle until it un-gets the service.
>>> for #3, that is the current dependency viewer in the debug-view Portlet.
>>>
>>> So, do you mean the #1? That will be great to display such information.
>>>
>>> -Rex
>>>
>>>>
>>>> -Jack
>>>>
>>>>
>>>> On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> OSGI Bundle is a new item for Geronimo admin console and RFC 139
>>>>> defines many Mbeans used to get bundle information in OSGI environment. So
>>>>> it's necessary for admin console to show the information of OSGI bundles.
>>>>>
>>>>> Therefore, Rodger and I mocked up a couple of portlets. Here are some
>>>>> screenshots for the mock UI. As you can see, we have two portlets here, to
>>>>> show the bundle list and bundle information. It's a initial draft based on
>>>>> Dojo widgets without full javascript implementation.
>>>>>
>>>>> Screenshot 1:
>>>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
>>>>> Screenshot 2:
>>>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>>>>>
>>>>> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
>>>>> information portlet. Bundle list portlet gives a list of installed
>>>>> bundles;besides, the portlet also allow user to stop/start/uninstall
>>>>> bundles. Bundle information portlet is much simpler, it only display the
>>>>> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
>>>>> obtain the information.
>>>>>
>>>>> For better illustration, I added some markers (A,B,C,D,E) in snapshot
>>>>> 1.
>>>>>
>>>>> A - With these widgets, user can install any bundle from file system.
>>>>> If "start" is checked, the bundle will be started automatically after it's
>>>>> installed.Meanwhile, user can also specify the start level of this bundle.
>>>>> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
>>>>> bundles, so I just mock the installation UI according to Web console of
>>>>> Felix.
>>>>>
>>>>> B - All the possible actions can be taken to bundles. Every bundle can
>>>>> be selected through the checkbox in front of it. Each time an action is
>>>>> taken to all the selected bundles. If the action is not applicable for some
>>>>> bundles, these bundles will be ignored.
>>>>>
>>>>> C - Each column in the table can be sorted by clicking the column
>>>>> header. The up arrow stands for sort asending while the down arrow stands
>>>>> for sort desending.
>>>>>
>>>>> D - The textbox here is used to filter bundles by symbolic name. Only
>>>>> the bundles with symbolic name containing specified text will be shown. If
>>>>> no text provided, all the bundles will show
>>>>>
>>>>> E - The drop down list here gives the possible status of an installed
>>>>> bundle - "resolved","starting","active","stopping". It's used to filter
>>>>> bundles by status. If one status is selected, only bundle with status the
>>>>> same as selected value will be shown. If no value is selected, all the
>>>>> bundles will be shown.
>>>>>
>>>>> That's all for the snapshot. Any comments?
>>>>>
>>>>> Thanks a lot!
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>>
>>>>> Delos
>>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>
>
Re: [Need review] The mock UI for displaying bundle information
Posted by Jack Cai <gr...@gmail.com>.
By "using" I mean service wiring, i.e., bundles that have a live instance of
a service exported by this bundle. Is this possible?
-Jack
On Wed, Dec 16, 2009 at 10:39 AM, Delos <da...@gmail.com> wrote:
> *Thanks Rex.
>
> There is a method "getRequiringBundles()" in BundleStateMbean defined in
> RFC 139. I hope to get the bundle list for Jack's request. Do you think it
> has taken #1 into account?*
>
> 2009/12/16 Rex Wang <rw...@gmail.com>
>
>
>>
>> 2009/12/15 Jack Cai <gr...@gmail.com>
>>
>> Nice work. A few comments -
>>>
>>> 1. Better add a "filter" or alike text before textbox D
>>> 2. Area B is a little far away from the selection checkboxes, suggest to
>>> move them closer. By design, users always need to select some bundles by
>>> checking the check boxes and then move the mouse to the action buttons in B.
>>> So the nearer, the better
>>> 3. It looks like the buddle information page is pretty lightweight. Have
>>> we considered to embed it into the list page? As a pop up or expandable
>>> area...
>>> 4. Might want to add paging function
>>> 5. Might want to use icon to show the status
>>>
>>> Also, will it be interesting to show what other bundles are currently
>>> using a certain bundle?
>>
>> There are three kinds of "using":
>> 1. import-package/required-bundle wiring
>> 2. service wiring
>> 3. geronimo bundle dependency
>> for #1, that means a view to show which one imports the packages the
>> bundle exports.
>> for #2, I think we don't need to care about that, because even if a
>> service provider bundle is uninstalled, the bundle using the service object
>> can still run without problems. OSGi framework will maintain the service
>> object for this bundle until it un-gets the service.
>> for #3, that is the current dependency viewer in the debug-view Portlet.
>>
>> So, do you mean the #1? That will be great to display such information.
>>
>> -Rex
>>
>>>
>>> -Jack
>>>
>>>
>>> On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
>>>> many Mbeans used to get bundle information in OSGI environment. So it's
>>>> necessary for admin console to show the information of OSGI bundles.
>>>>
>>>> Therefore, Rodger and I mocked up a couple of portlets. Here are some
>>>> screenshots for the mock UI. As you can see, we have two portlets here, to
>>>> show the bundle list and bundle information. It's a initial draft based on
>>>> Dojo widgets without full javascript implementation.
>>>>
>>>> Screenshot 1:
>>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
>>>> Screenshot 2:
>>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>>>>
>>>> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
>>>> information portlet. Bundle list portlet gives a list of installed
>>>> bundles;besides, the portlet also allow user to stop/start/uninstall
>>>> bundles. Bundle information portlet is much simpler, it only display the
>>>> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
>>>> obtain the information.
>>>>
>>>> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>>>>
>>>> A - With these widgets, user can install any bundle from file system. If
>>>> "start" is checked, the bundle will be started automatically after it's
>>>> installed.Meanwhile, user can also specify the start level of this bundle.
>>>> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
>>>> bundles, so I just mock the installation UI according to Web console of
>>>> Felix.
>>>>
>>>> B - All the possible actions can be taken to bundles. Every bundle can
>>>> be selected through the checkbox in front of it. Each time an action is
>>>> taken to all the selected bundles. If the action is not applicable for some
>>>> bundles, these bundles will be ignored.
>>>>
>>>> C - Each column in the table can be sorted by clicking the column
>>>> header. The up arrow stands for sort asending while the down arrow stands
>>>> for sort desending.
>>>>
>>>> D - The textbox here is used to filter bundles by symbolic name. Only
>>>> the bundles with symbolic name containing specified text will be shown. If
>>>> no text provided, all the bundles will show
>>>>
>>>> E - The drop down list here gives the possible status of an installed
>>>> bundle - "resolved","starting","active","stopping". It's used to filter
>>>> bundles by status. If one status is selected, only bundle with status the
>>>> same as selected value will be shown. If no value is selected, all the
>>>> bundles will be shown.
>>>>
>>>> That's all for the snapshot. Any comments?
>>>>
>>>> Thanks a lot!
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>>
>>>> Delos
>>>>
>>>
>>>
>>
>
>
> --
> Best Regards,
>
> Delos
>
Re: [Need review] The mock UI for displaying bundle information
Posted by Delos <da...@gmail.com>.
*Thanks Rex.
There is a method "getRequiringBundles()" in BundleStateMbean defined in RFC
139. I hope to get the bundle list for Jack's request. Do you think it has
taken #1 into account?*
2009/12/16 Rex Wang <rw...@gmail.com>
>
>
> 2009/12/15 Jack Cai <gr...@gmail.com>
>
> Nice work. A few comments -
>>
>> 1. Better add a "filter" or alike text before textbox D
>> 2. Area B is a little far away from the selection checkboxes, suggest to
>> move them closer. By design, users always need to select some bundles by
>> checking the check boxes and then move the mouse to the action buttons in B.
>> So the nearer, the better
>> 3. It looks like the buddle information page is pretty lightweight. Have
>> we considered to embed it into the list page? As a pop up or expandable
>> area...
>> 4. Might want to add paging function
>> 5. Might want to use icon to show the status
>>
>> Also, will it be interesting to show what other bundles are currently
>> using a certain bundle?
>
> There are three kinds of "using":
> 1. import-package/required-bundle wiring
> 2. service wiring
> 3. geronimo bundle dependency
> for #1, that means a view to show which one imports the packages the bundle
> exports.
> for #2, I think we don't need to care about that, because even if a service
> provider bundle is uninstalled, the bundle using the service object can
> still run without problems. OSGi framework will maintain the service object
> for this bundle until it un-gets the service.
> for #3, that is the current dependency viewer in the debug-view Portlet.
>
> So, do you mean the #1? That will be great to display such information.
>
> -Rex
>
>>
>> -Jack
>>
>>
>> On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
>>> many Mbeans used to get bundle information in OSGI environment. So it's
>>> necessary for admin console to show the information of OSGI bundles.
>>>
>>> Therefore, Rodger and I mocked up a couple of portlets. Here are some
>>> screenshots for the mock UI. As you can see, we have two portlets here, to
>>> show the bundle list and bundle information. It's a initial draft based on
>>> Dojo widgets without full javascript implementation.
>>>
>>> Screenshot 1:
>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
>>> Screenshot 2:
>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>>>
>>> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
>>> information portlet. Bundle list portlet gives a list of installed
>>> bundles;besides, the portlet also allow user to stop/start/uninstall
>>> bundles. Bundle information portlet is much simpler, it only display the
>>> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
>>> obtain the information.
>>>
>>> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>>>
>>> A - With these widgets, user can install any bundle from file system. If
>>> "start" is checked, the bundle will be started automatically after it's
>>> installed.Meanwhile, user can also specify the start level of this bundle.
>>> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
>>> bundles, so I just mock the installation UI according to Web console of
>>> Felix.
>>>
>>> B - All the possible actions can be taken to bundles. Every bundle can be
>>> selected through the checkbox in front of it. Each time an action is taken
>>> to all the selected bundles. If the action is not applicable for some
>>> bundles, these bundles will be ignored.
>>>
>>> C - Each column in the table can be sorted by clicking the column header.
>>> The up arrow stands for sort asending while the down arrow stands for sort
>>> desending.
>>>
>>> D - The textbox here is used to filter bundles by symbolic name. Only the
>>> bundles with symbolic name containing specified text will be shown. If no
>>> text provided, all the bundles will show
>>>
>>> E - The drop down list here gives the possible status of an installed
>>> bundle - "resolved","starting","active","stopping". It's used to filter
>>> bundles by status. If one status is selected, only bundle with status the
>>> same as selected value will be shown. If no value is selected, all the
>>> bundles will be shown.
>>>
>>> That's all for the snapshot. Any comments?
>>>
>>> Thanks a lot!
>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> Delos
>>>
>>
>>
>
--
Best Regards,
Delos
Re: [Need review] The mock UI for displaying bundle information
Posted by Rex Wang <rw...@gmail.com>.
2009/12/15 Jack Cai <gr...@gmail.com>
> Nice work. A few comments -
>
> 1. Better add a "filter" or alike text before textbox D
> 2. Area B is a little far away from the selection checkboxes, suggest to
> move them closer. By design, users always need to select some bundles by
> checking the check boxes and then move the mouse to the action buttons in B.
> So the nearer, the better
> 3. It looks like the buddle information page is pretty lightweight. Have we
> considered to embed it into the list page? As a pop up or expandable area...
> 4. Might want to add paging function
> 5. Might want to use icon to show the status
>
> Also, will it be interesting to show what other bundles are currently using
> a certain bundle?
There are three kinds of "using":
1. import-package/required-bundle wiring
2. service wiring
3. geronimo bundle dependency
for #1, that means a view to show which one imports the packages the bundle
exports.
for #2, I think we don't need to care about that, because even if a service
provider bundle is uninstalled, the bundle using the service object can
still run without problems. OSGi framework will maintain the service object
for this bundle until it un-gets the service.
for #3, that is the current dependency viewer in the debug-view Portlet.
So, do you mean the #1? That will be great to display such information.
-Rex
>
> -Jack
>
>
> On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
>
>> Hi all,
>>
>> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
>> many Mbeans used to get bundle information in OSGI environment. So it's
>> necessary for admin console to show the information of OSGI bundles.
>>
>> Therefore, Rodger and I mocked up a couple of portlets. Here are some
>> screenshots for the mock UI. As you can see, we have two portlets here, to
>> show the bundle list and bundle information. It's a initial draft based on
>> Dojo widgets without full javascript implementation.
>>
>> Screenshot 1:
>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
>> Screenshot 2:
>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>>
>> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
>> information portlet. Bundle list portlet gives a list of installed
>> bundles;besides, the portlet also allow user to stop/start/uninstall
>> bundles. Bundle information portlet is much simpler, it only display the
>> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
>> obtain the information.
>>
>> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>>
>> A - With these widgets, user can install any bundle from file system. If
>> "start" is checked, the bundle will be started automatically after it's
>> installed.Meanwhile, user can also specify the start level of this bundle.
>> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
>> bundles, so I just mock the installation UI according to Web console of
>> Felix.
>>
>> B - All the possible actions can be taken to bundles. Every bundle can be
>> selected through the checkbox in front of it. Each time an action is taken
>> to all the selected bundles. If the action is not applicable for some
>> bundles, these bundles will be ignored.
>>
>> C - Each column in the table can be sorted by clicking the column header.
>> The up arrow stands for sort asending while the down arrow stands for sort
>> desending.
>>
>> D - The textbox here is used to filter bundles by symbolic name. Only the
>> bundles with symbolic name containing specified text will be shown. If no
>> text provided, all the bundles will show
>>
>> E - The drop down list here gives the possible status of an installed
>> bundle - "resolved","starting","active","stopping". It's used to filter
>> bundles by status. If one status is selected, only bundle with status the
>> same as selected value will be shown. If no value is selected, all the
>> bundles will be shown.
>>
>> That's all for the snapshot. Any comments?
>>
>> Thanks a lot!
>>
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>
>
Re: [Need review] The mock UI for displaying bundle information
Posted by Delos <da...@gmail.com>.
I agree your comments.See my reply in red. Thanks for your good suggestion!
Base on your discussion with Rex, we will also provide information about
requiring bundles that using a certain bundle.
As Rex said, possible solution is making use of
bundleContext.getAllServiceReferences(class=service
class,null)
and then traverse the ServiceReferences to find whose
getBundle().getSymbolicName/getVersion.
Thank both of you!
2009/12/16 Jack Cai <gr...@gmail.com>
> In line below.
>
> On Wed, Dec 16, 2009 at 10:35 AM, Delos <da...@gmail.com> wrote:
>
>> Thanks for your comments, Jack. See my reply below.
>>
>> 1. Better add a "filter" or alike text before textbox D
>> I agree it's better to add a label for a textbox. But since there has been
>> "symbolic name" in front of the textbox, I'm afraid the "filter" text
>> here may cause confusion.We will add tool tips such as "filter" for the
>> textbox. That can also indicate what it is used for.
>>
>>
> We might borrow the design from Eclipse then, i.e., show the default text
> "type filter text" in the filter box.
>
Right,we should add the default text
>
>
>>
>> 2. Area B is a little far away from the selection checkboxes, suggest to
>> move them closer. By design, users always need to select some bundles by
>> checking the check boxes and then move the mouse to the action buttons in B.
>> So the nearer, the better
>> Agree. Besides, we're trying to replace "select all" and "deselect all"
>> button with two icons. Hopefully, they can be put into the header of the
>> checkboxes column. Then, area B will be placed in the left side, it will
>> be nearer to the checkboxes
>>
>>
>> 3. It looks like the buddle information page is pretty lightweight. Have
>> we considered to embed it into the list page? As a pop up or expandable
>> area...
>> In Web console of Felix, the bundle information page is embedded in the
>> table. When user expand the bundle item in the table, the bundle information
>> will show. But not all the bundle information is so short as shown in our
>> screenshot. The information is often too long to shown in a table. So we
>> hope to show it in a separate portlet.
>> Since several portlets can be shown in one page, we can show the two
>> portlets together to avoid page jump. I will upload another screenshot for
>> it later.
>>
>>
>> 4. Might want to add paging function
>> I think you mean the paging for bundle list.
>> We hope to use the scroll bar in the table instead of separate bundle list
>> into several pages. With the scroll bar for the table, user can locate to
>> any bundle in the list. In this way, the paging is transparent to user.
>>
>>
> Do you mean something like the Google Reader does? ie., auto-load more
> items as the user scrool down? That's cool!
> Yes. It works similar to Google Reader
>
>>
>> 5. Might want to use icon to show the status
>> Do you mean we replace the text such as "Active","Resolved" with icons. If
>> so, we have to make user realize what status the icon stands for. Do you
>> think tool tip is enough? BTW, I'm also considering to replace the buttons
>> in Area B with icons.
>>
>>
> We can keep the text in addition to the icon. Icons give user faster
> "visual" sense compared to text.
>
>
>> Also, will it be interesting to show what other bundles are currently
>> using a certain bundle?
>>
>> Yes.There is a method to get the bundle list using a certain bundle in RFC
>> 139. Then, we can just place the list as a section in bundle information
>> portlet. All the bundle item can be clickable. If a bundle is clicked, the
>> bundle information portlet will show its information.
>>
>
>
>> 2009/12/15 Jack Cai <gr...@gmail.com>
>>
>>> Nice work. A few comments -
>>>
>>>
>>> 1. Better add a "filter" or alike text before textbox D
>>> 2. Area B is a little far away from the selection checkboxes, suggest to
>>> move them closer. By design, users always need to select some bundles by
>>> checking the check boxes and then move the mouse to the action buttons in B.
>>> So the nearer, the better
>>> 3. It looks like the buddle information page is pretty lightweight. Have
>>> we considered to embed it into the list page? As a pop up or expandable
>>> area...
>>> 4. Might want to add paging function
>>> 5. Might want to use icon to show the status
>>>
>>> Also, will it be interesting to show what other bundles are currently
>>> using a certain bundle?
>>>
>>> -Jack
>>>
>>>
>>> On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
>>>> many Mbeans used to get bundle information in OSGI environment. So it's
>>>> necessary for admin console to show the information of OSGI bundles.
>>>>
>>>> Therefore, Rodger and I mocked up a couple of portlets. Here are some
>>>> screenshots for the mock UI. As you can see, we have two portlets here, to
>>>> show the bundle list and bundle information. It's a initial draft based on
>>>> Dojo widgets without full javascript implementation.
>>>>
>>>> Screenshot 1:
>>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
>>>> Screenshot 2:
>>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>>>>
>>>> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
>>>> information portlet. Bundle list portlet gives a list of installed
>>>> bundles;besides, the portlet also allow user to stop/start/uninstall
>>>> bundles. Bundle information portlet is much simpler, it only display the
>>>> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
>>>> obtain the information.
>>>>
>>>> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>>>>
>>>> A - With these widgets, user can install any bundle from file system. If
>>>> "start" is checked, the bundle will be started automatically after it's
>>>> installed.Meanwhile, user can also specify the start level of this bundle.
>>>> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
>>>> bundles, so I just mock the installation UI according to Web console of
>>>> Felix.
>>>>
>>>> B - All the possible actions can be taken to bundles. Every bundle can
>>>> be selected through the checkbox in front of it. Each time an action is
>>>> taken to all the selected bundles. If the action is not applicable for some
>>>> bundles, these bundles will be ignored.
>>>>
>>>> C - Each column in the table can be sorted by clicking the column
>>>> header. The up arrow stands for sort asending while the down arrow stands
>>>> for sort desending.
>>>>
>>>> D - The textbox here is used to filter bundles by symbolic name. Only
>>>> the bundles with symbolic name containing specified text will be shown. If
>>>> no text provided, all the bundles will show
>>>>
>>>> E - The drop down list here gives the possible status of an installed
>>>> bundle - "resolved","starting","active","stopping". It's used to filter
>>>> bundles by status. If one status is selected, only bundle with status the
>>>> same as selected value will be shown. If no value is selected, all the
>>>> bundles will be shown.
>>>>
>>>> That's all for the snapshot. Any comments?
>>>>
>>>> Thanks a lot!
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>>
>>>> Delos
>>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>
>
--
Best Regards,
Delos
Re: [Need review] The mock UI for displaying bundle information
Posted by Jack Cai <gr...@gmail.com>.
In line below.
On Wed, Dec 16, 2009 at 10:35 AM, Delos <da...@gmail.com> wrote:
> Thanks for your comments, Jack. See my reply below.
>
> 1. Better add a "filter" or alike text before textbox D
> I agree it's better to add a label for a textbox. But since there has been
> "symbolic name" in front of the textbox, I'm afraid the "filter" text
> here may cause confusion.We will add tool tips such as "filter" for the
> textbox. That can also indicate what it is used for.
>
>
We might borrow the design from Eclipse then, i.e., show the default text
"type filter text" in the filter box.
>
> 2. Area B is a little far away from the selection checkboxes, suggest to
> move them closer. By design, users always need to select some bundles by
> checking the check boxes and then move the mouse to the action buttons in B.
> So the nearer, the better
> Agree. Besides, we're trying to replace "select all" and "deselect all"
> button with two icons. Hopefully, they can be put into the header of the
> checkboxes column. Then, area B will be placed in the left side, it will
> be nearer to the checkboxes
>
>
> 3. It looks like the buddle information page is pretty lightweight. Have we
> considered to embed it into the list page? As a pop up or expandable area...
> In Web console of Felix, the bundle information page is embedded in the
> table. When user expand the bundle item in the table, the bundle information
> will show. But not all the bundle information is so short as shown in our
> screenshot. The information is often too long to shown in a table. So we
> hope to show it in a separate portlet.
> Since several portlets can be shown in one page, we can show the two
> portlets together to avoid page jump. I will upload another screenshot for
> it later.
>
>
> 4. Might want to add paging function
> I think you mean the paging for bundle list.
> We hope to use the scroll bar in the table instead of separate bundle list
> into several pages. With the scroll bar for the table, user can locate to
> any bundle in the list. In this way, the paging is transparent to user.
>
>
Do you mean something like the Google Reader does? ie., auto-load more items
as the user scrool down? That's cool!
>
> 5. Might want to use icon to show the status
> Do you mean we replace the text such as "Active","Resolved" with icons. If
> so, we have to make user realize what status the icon stands for. Do you
> think tool tip is enough? BTW, I'm also considering to replace the buttons
> in Area B with icons.
>
>
We can keep the text in addition to the icon. Icons give user faster
"visual" sense compared to text.
> Also, will it be interesting to show what other bundles are currently using
> a certain bundle?
>
> Yes.There is a method to get the bundle list using a certain bundle in RFC
> 139. Then, we can just place the list as a section in bundle information
> portlet. All the bundle item can be clickable. If a bundle is clicked, the
> bundle information portlet will show its information.
>
> 2009/12/15 Jack Cai <gr...@gmail.com>
>
>> Nice work. A few comments -
>>
>>
>> 1. Better add a "filter" or alike text before textbox D
>> 2. Area B is a little far away from the selection checkboxes, suggest to
>> move them closer. By design, users always need to select some bundles by
>> checking the check boxes and then move the mouse to the action buttons in B.
>> So the nearer, the better
>> 3. It looks like the buddle information page is pretty lightweight. Have
>> we considered to embed it into the list page? As a pop up or expandable
>> area...
>> 4. Might want to add paging function
>> 5. Might want to use icon to show the status
>>
>> Also, will it be interesting to show what other bundles are currently
>> using a certain bundle?
>>
>> -Jack
>>
>>
>> On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
>>> many Mbeans used to get bundle information in OSGI environment. So it's
>>> necessary for admin console to show the information of OSGI bundles.
>>>
>>> Therefore, Rodger and I mocked up a couple of portlets. Here are some
>>> screenshots for the mock UI. As you can see, we have two portlets here, to
>>> show the bundle list and bundle information. It's a initial draft based on
>>> Dojo widgets without full javascript implementation.
>>>
>>> Screenshot 1:
>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
>>> Screenshot 2:
>>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>>>
>>> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
>>> information portlet. Bundle list portlet gives a list of installed
>>> bundles;besides, the portlet also allow user to stop/start/uninstall
>>> bundles. Bundle information portlet is much simpler, it only display the
>>> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
>>> obtain the information.
>>>
>>> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>>>
>>> A - With these widgets, user can install any bundle from file system. If
>>> "start" is checked, the bundle will be started automatically after it's
>>> installed.Meanwhile, user can also specify the start level of this bundle.
>>> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
>>> bundles, so I just mock the installation UI according to Web console of
>>> Felix.
>>>
>>> B - All the possible actions can be taken to bundles. Every bundle can be
>>> selected through the checkbox in front of it. Each time an action is taken
>>> to all the selected bundles. If the action is not applicable for some
>>> bundles, these bundles will be ignored.
>>>
>>> C - Each column in the table can be sorted by clicking the column header.
>>> The up arrow stands for sort asending while the down arrow stands for sort
>>> desending.
>>>
>>> D - The textbox here is used to filter bundles by symbolic name. Only the
>>> bundles with symbolic name containing specified text will be shown. If no
>>> text provided, all the bundles will show
>>>
>>> E - The drop down list here gives the possible status of an installed
>>> bundle - "resolved","starting","active","stopping". It's used to filter
>>> bundles by status. If one status is selected, only bundle with status the
>>> same as selected value will be shown. If no value is selected, all the
>>> bundles will be shown.
>>>
>>> That's all for the snapshot. Any comments?
>>>
>>> Thanks a lot!
>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> Delos
>>>
>>
>>
>
>
> --
> Best Regards,
>
> Delos
>
Re: [Need review] The mock UI for displaying bundle information
Posted by Delos <da...@gmail.com>.
Thanks for your comments, Jack. See my reply below.
1. Better add a "filter" or alike text before textbox D
I agree it's better to add a label for a textbox. But since there has been
"symbolic name" in front of the textbox, I'm afraid the "filter" text here
may cause confusion.We will add tool tips such as "filter" for the textbox.
That can also indicate what it is used for.
2. Area B is a little far away from the selection checkboxes, suggest to
move them closer. By design, users always need to select some bundles by
checking the check boxes and then move the mouse to the action buttons in B.
So the nearer, the better
Agree. Besides, we're trying to replace "select all" and "deselect all"
button with two icons. Hopefully, they can be put into the header of the
checkboxes column. Then, area B will be placed in the left side, it will be
nearer to the checkboxes
3. It looks like the buddle information page is pretty lightweight. Have we
considered to embed it into the list page? As a pop up or expandable area...
In Web console of Felix, the bundle information page is embedded in the
table. When user expand the bundle item in the table, the bundle information
will show. But not all the bundle information is so short as shown in our
screenshot. The information is often too long to shown in a table. So we
hope to show it in a separate portlet.
Since several portlets can be shown in one page, we can show the two
portlets together to avoid page jump. I will upload another screenshot for
it later.
4. Might want to add paging function
I think you mean the paging for bundle list.
We hope to use the scroll bar in the table instead of separate bundle list
into several pages. With the scroll bar for the table, user can locate to
any bundle in the list. In this way, the paging is transparent to user.
5. Might want to use icon to show the status
Do you mean we replace the text such as "Active","Resolved" with icons. If
so, we have to make user realize what status the icon stands for. Do you
think tool tip is enough? BTW, I'm also considering to replace the buttons
in Area B with icons.
Also, will it be interesting to show what other bundles are currently using
a certain bundle?
Yes.There is a method to get the bundle list using a certain bundle in RFC
139. Then, we can just place the list as a section in bundle information
portlet. All the bundle item can be clickable. If a bundle is clicked, the
bundle information portlet will show its information.
2009/12/15 Jack Cai <gr...@gmail.com>
> Nice work. A few comments -
>
> 1. Better add a "filter" or alike text before textbox D
> 2. Area B is a little far away from the selection checkboxes, suggest to
> move them closer. By design, users always need to select some bundles by
> checking the check boxes and then move the mouse to the action buttons in B.
> So the nearer, the better
> 3. It looks like the buddle information page is pretty lightweight. Have we
> considered to embed it into the list page? As a pop up or expandable area...
> 4. Might want to add paging function
> 5. Might want to use icon to show the status
>
> Also, will it be interesting to show what other bundles are currently using
> a certain bundle?
>
> -Jack
>
>
> On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
>
>> Hi all,
>>
>> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
>> many Mbeans used to get bundle information in OSGI environment. So it's
>> necessary for admin console to show the information of OSGI bundles.
>>
>> Therefore, Rodger and I mocked up a couple of portlets. Here are some
>> screenshots for the mock UI. As you can see, we have two portlets here, to
>> show the bundle list and bundle information. It's a initial draft based on
>> Dojo widgets without full javascript implementation.
>>
>> Screenshot 1:
>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
>> Screenshot 2:
>> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>>
>> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
>> information portlet. Bundle list portlet gives a list of installed
>> bundles;besides, the portlet also allow user to stop/start/uninstall
>> bundles. Bundle information portlet is much simpler, it only display the
>> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
>> obtain the information.
>>
>> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>>
>> A - With these widgets, user can install any bundle from file system. If
>> "start" is checked, the bundle will be started automatically after it's
>> installed.Meanwhile, user can also specify the start level of this bundle.
>> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
>> bundles, so I just mock the installation UI according to Web console of
>> Felix.
>>
>> B - All the possible actions can be taken to bundles. Every bundle can be
>> selected through the checkbox in front of it. Each time an action is taken
>> to all the selected bundles. If the action is not applicable for some
>> bundles, these bundles will be ignored.
>>
>> C - Each column in the table can be sorted by clicking the column header.
>> The up arrow stands for sort asending while the down arrow stands for sort
>> desending.
>>
>> D - The textbox here is used to filter bundles by symbolic name. Only the
>> bundles with symbolic name containing specified text will be shown. If no
>> text provided, all the bundles will show
>>
>> E - The drop down list here gives the possible status of an installed
>> bundle - "resolved","starting","active","stopping". It's used to filter
>> bundles by status. If one status is selected, only bundle with status the
>> same as selected value will be shown. If no value is selected, all the
>> bundles will be shown.
>>
>> That's all for the snapshot. Any comments?
>>
>> Thanks a lot!
>>
>>
>> --
>> Best Regards,
>>
>> Delos
>>
>
>
--
Best Regards,
Delos
Re: [Need review] The mock UI for displaying bundle information
Posted by Jack Cai <gr...@gmail.com>.
Nice work. A few comments -
1. Better add a "filter" or alike text before textbox D
2. Area B is a little far away from the selection checkboxes, suggest to
move them closer. By design, users always need to select some bundles by
checking the check boxes and then move the mouse to the action buttons in B.
So the nearer, the better
3. It looks like the buddle information page is pretty lightweight. Have we
considered to embed it into the list page? As a pop up or expandable area...
4. Might want to add paging function
5. Might want to use icon to show the status
Also, will it be interesting to show what other bundles are currently using
a certain bundle?
-Jack
On Tue, Dec 15, 2009 at 5:19 PM, Delos <da...@gmail.com> wrote:
> Hi all,
>
> OSGI Bundle is a new item for Geronimo admin console and RFC 139 defines
> many Mbeans used to get bundle information in OSGI environment. So it's
> necessary for admin console to show the information of OSGI bundles.
>
> Therefore, Rodger and I mocked up a couple of portlets. Here are some
> screenshots for the mock UI. As you can see, we have two portlets here, to
> show the bundle list and bundle information. It's a initial draft based on
> Dojo widgets without full javascript implementation.
>
> Screenshot 1:
> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/dojoBundleList_anntation.JPG
> Screenshot 2:
> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/singlebundle.JPG
>
> In the attachment, 1 is the bundle list portlet, while 2 is the bundle
> information portlet. Bundle list portlet gives a list of installed
> bundles;besides, the portlet also allow user to stop/start/uninstall
> bundles. Bundle information portlet is much simpler, it only display the
> bundle information in OSGI framework. Mbeans defined in RFC 139 is a way to
> obtain the information.
>
> For better illustration, I added some markers (A,B,C,D,E) in snapshot 1.
>
> A - With these widgets, user can install any bundle from file system. If
> "start" is checked, the bundle will be started automatically after it's
> installed.Meanwhile, user can also specify the start level of this bundle.
> I'm not sure if the "Deploy New" portlet will be applicable for OSGI
> bundles, so I just mock the installation UI according to Web console of
> Felix.
>
> B - All the possible actions can be taken to bundles. Every bundle can be
> selected through the checkbox in front of it. Each time an action is taken
> to all the selected bundles. If the action is not applicable for some
> bundles, these bundles will be ignored.
>
> C - Each column in the table can be sorted by clicking the column header.
> The up arrow stands for sort asending while the down arrow stands for sort
> desending.
>
> D - The textbox here is used to filter bundles by symbolic name. Only the
> bundles with symbolic name containing specified text will be shown. If no
> text provided, all the bundles will show
>
> E - The drop down list here gives the possible status of an installed
> bundle - "resolved","starting","active","stopping". It's used to filter
> bundles by status. If one status is selected, only bundle with status the
> same as selected value will be shown. If no value is selected, all the
> bundles will be shown.
>
> That's all for the snapshot. Any comments?
>
> Thanks a lot!
>
>
> --
> Best Regards,
>
> Delos
>