Hi Felix,
             Is there a way to programmatically get the /console/config
information? My bundle is deployed within a server and it's not a good way
to access the same server again(by sending http request) to get information.
This may give rise to security vulnerabilities. Therefore, I need to get
those information programmatically by accessing the web-console API. Is
there a way to do this rather than doing modifications to the web-console
jar? If a modification is needed, how to do it?

Thanks

On Tue, Sep 15, 2009 at 5:19 PM, Felix Meschberger <[email protected]>wrote:

> Hi,
>
> Heshan Suriyaarachchi schrieb:
> > What I want is to programmatically access web console and get the
> rendered
> > information (which is displayed at the UI).
>
> You can place a request to the configuration status page
>
>    http://thehost:9999/system/console/config/afilename.txt
>
> to get the single text file or request
>
>    http://thehost:9999/system/console/config/afilename.zip
>
> to get the ZIP file. The "afilename" part can be any valid URL segment
> (the extension .txt or .zip is important).
>
> Regards
> Felix
>
> >
> > On Tue, Sep 15, 2009 at 4:01 PM, Heshan Suriyaarachchi <
> > [email protected]> wrote:
> >
> >> Hi Felix,
> >>
> >> On Tue, Sep 15, 2009 at 3:54 PM, Felix Meschberger <[email protected]
> >wrote:
> >>
> >>> Hi Hashan,
> >>>
> >>> Heshan Suriyaarachchi schrieb:
> >>>> Hi Felix,
> >>>>
> >>>> On Tue, Sep 15, 2009 at 2:27 PM, Felix Meschberger <
> [email protected]
> >>>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Well, in what respect would it make your life easier ?
> >>>>>
> >>>>> Doing BundleContext.getBundles() is as easy as it could be, no ? Or
> is
> >>>>> it how the web console renders the bundle detail ?
> >>>>>
> >>>> It is the way in which web console renders the bundle details. If I
> >>> could
> >>>> get it as stream (or something like that) I could directly write it to
> a
> >>>> file. WDYT?
> >>> What I have done recently (but not committed yet) is to extend the
> >>> configuration status page as follows:
> >>>
> >>>  * display as tabbed page of status entries
> >>>  * option to download as a single text file
> >>>  * option to download as a ZIP file containing each tab
> >>>     page as a text file
> >>>
> >> These options matches my requirement exactly. Is there a way that I
> could
> >> use these features?
> >>
> >>> Would that suit your needs ?
> >>>
> >>> Regards
> >>> Felix
> >>>
> >>>>> The you could (theoretically) use the web console by sending an HTTP
> >>>>> request  and use the result. But I am not sure, whether this is
> really
> >>>>> worth it....
> >>>>>
> >>>>> Regards
> >>>>> Felix
> >>>>>
> >>>>> Heshan Suriyaarachchi schrieb:
> >>>>>> Hi Marcel,
> >>>>>>                 I did not go through the source code. In my
> scenario,
> >>> I
> >>>>>> could get OSGi information through BundleContext. I only needed to
> >>> know
> >>>>> if I
> >>>>>> could use web console code to capture the bundle info, it would make
> >>> my
> >>>>> life
> >>>>>> easier :) .
> >>>>>>
> >>>>>> On Tue, Sep 15, 2009 at 1:45 PM, Marcel Offermans <
> >>>>>> [email protected]> wrote:
> >>>>>>
> >>>>>>> At the risk of stating the obvious, but did you actually study the
> >>>>> source
> >>>>>>> code of the web management console?
> >>>>>>>
> >>>>>>> On Sep 15, 2009, at 10:12 , Heshan Suriyaarachchi wrote:
> >>>>>>>
> >>>>>>>    I have written an OSGi bundle. In that I am capturing OSGi
> bundle
> >>>>>>>> information and writing it in to a file. I went through the Apache
> >>>>> Felix
> >>>>>>>> Web
> >>>>>>>> Console and found the information shown there interesting. Is
> there
> >>> a
> >>>>> way
> >>>>>>>> that I can progarmmatically access the bundle information shown in
> >>> the
> >>>>>>>> 'Configuration Status' tab of the 'Apache Felix Web Management
> >>> Console
> >>>>>>>> Configuration Status' and write it to a file. If so how?
> >>>>>>>>   Your response is very much appreciated.
> >>>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: [email protected]
> >>>>>>> For additional commands, e-mail: [email protected]
> >>>>>>>
> >>>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: [email protected]
> >>>>> For additional commands, e-mail: [email protected]
> >>>>>
> >>>>>
> >>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [email protected]
> >>> For additional commands, e-mail: [email protected]
> >>>
> >>>
> >>
> >> --
> >> Regards,
> >> Heshan Suriyaarachchi
> >>
> >> http://heshans.blogspot.com/
> >>
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Regards,
Heshan Suriyaarachchi

http://heshans.blogspot.com/

Reply via email to