You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cxf.apache.org by Tomasz Oponowicz <to...@gmail.com> on 2010/06/17 23:15:24 UTC

[GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Hi,

On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
>> Just for the record, Tomasz's project is also going well....
>Well, for the record, I haven't seen anything on the dev list about it yet.
>Thus, from CXF/Apache's point of view, it's not going well.   Definitely
>encourage him to get involved here and not send you anything off list.

I have created project site and blog, few weeks ago.
Sorry that I didn't announce about it at mailing list.

I will store documentation and source code on Google Code Project [1].
Additionally I will announce important events and changes through blog
[2], which I created for this occasion.

Currently repository [1] contain draft of all features (on my roadmap
it's milestone 1).
There is also "Software Requirements Specification" document
and  "Software Design Description" document. At the moment I'm working to
fix and refactor source code.

When I finish I will move all source code to CXF sandbox.

Once again sorry for my misunderstanding.

[1] http://code.google.com/p/cxf-log-browser/
[2] http://cxf-log-browser.blogspot.com/

Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@oponowicz.org>.

Hi,

On Fri, Jun 18, 2010 at 12:15 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi Tomasz
>
> I think you're doing really well; I agree with Dan that we'd like to see
> more discussions on the dev list but it's my fault I did not CC to the dev
> list during our last exchange :-) but I think i did not do it because the
> links to the slides were pointing to your own album.

I published screenshots at more suitable place [1].

[1] http://cxf-log-browser.blogspot.com/2010/06/milestone-1.html

-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

I think you're doing really well; I agree with Dan that we'd like to see
more discussions on the dev list but it's my fault I did not CC to the dev
list during our last exchange :-) but I think i did not do it because the
links to the slides were pointing to your own album.
Please don't hesitate to ping me privately if needed - but we'll have to
make sure now the community is aware of what is happening :-). This is one
of the advantages of working in the CXF sandbox by the way, all the commits
are being copied to the dev list

cheers, Sergey

On Thu, Jun 17, 2010 at 10:15 PM, Tomasz Oponowicz <
tomasz.oponowicz@gmail.com> wrote:

> Hi,
>
> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
> >> Just for the record, Tomasz's project is also going well....
> >Well, for the record, I haven't seen anything on the dev list about it
> yet.
> >Thus, from CXF/Apache's point of view, it's not going well.   Definitely
> >encourage him to get involved here and not send you anything off list.
>
> I have created project site and blog, few weeks ago.
> Sorry that I didn't announce about it at mailing list.
>
> I will store documentation and source code on Google Code Project [1].
> Additionally I will announce important events and changes through blog
> [2], which I created for this occasion.
>
> Currently repository [1] contain draft of all features (on my roadmap
> it's milestone 1).
> There is also "Software Requirements Specification" document
> and  "Software Design Description" document. At the moment I'm working to
> fix and refactor source code.
>
> When I finish I will move all source code to CXF sandbox.
>
> Once again sorry for my misunderstanding.
>
> [1] http://code.google.com/p/cxf-log-browser/
> [2] http://cxf-log-browser.blogspot.com/
>
> Best regards,
> Tomasz Oponowicz
>

RE: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Ram Maddela <Ra...@datacard.com>.

HI Friends,

Could you please send me an example for SOAP message body encryption with CXF?

Actually I am using the third party web service which was developed using Apache CXF.

I found some example online, but it's kind of complicated to understand.

Thanks
Ram.K.Maddela
Office: 952-988-1490
Cell     : 916 833 1480
Email: ram_maddela@datacard.com

-----Original Message-----
From: Sergey Beryozkin [mailto:sberyozkin@gmail.com] 
Sent: Wednesday, July 07, 2010 3:40 PM
To: dev@cxf.apache.org
Subject: Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Hi Tomasz

thanks - I'll be evaluating the demo these weekends, sorry, won't be able to
get to it earlier, but I'll do it in time so that we can prepare a mid term
evaluation report

I'd like to clarify the role of StaticContentServlet.java. I'm a bit
concerned about users having to add this servlet entry in addition to two
other ones (one for handling AtomPullServer and the other one for
BootstrapStorage).

What exactly does this servlet do that can not be done by enhancing say
BootstrapStorage or (CXF) AbstractHttpServlet ?

cheers, Sergey

On Tue, Jul 6, 2010 at 3:00 PM, Tomasz Oponowicz <tomasz.oponowicz@gmail.com
> wrote:

> Hi,t
> I've just committed basic version of logbrowser [1] (described by my
> proposal).
>
> I also created sample application [2] for easy testing all parts of
> the project.
> However it's more or less what user have to do to integrate logbrowser
> into his application.
> Detailed description, how to run sample application, is here [3].
>
> I'm staring work on [4] and [5] (i.e. refactoring, clean up and
> writing documentation)
> and I'm going to finished those tasks before mid-term evaluations
> deadline (i.e. 16.07.2010).
>
> Next I will add optional features [6].
>
> [1] http://svn.apache.org/viewvc?rev=960895&view=rev
> [2] ./distribution/src/main/release/samples/logbrowser
> [3] ./distribution/src/main/release/samples/logbrowser/README.txt
> [4] https://issues.apache.org/jira/browse/CXF-2881
> [5] https://issues.apache.org/jira/browse/CXF-2882
> [6] https://issues.apache.org/jira/browse/CXF-2883
>
> On Mon, Jun 21, 2010 at 6:55 PM, Tomasz Oponowicz
> <to...@gmail.com> wrote:
> > Hi,
> >
> > I've just commit changes at repository [1]. Changes from last version:
> >
> > - Created Maven project structure;
> > - Configured 'maven-gwt-plugin' for automatic execute GWT compiler (to
> > convert Java to JavaScript);
> > - Added draft implementation of 'BootstrapStorage';
> > - Create sample configuration of 'AtomPullServer';
> > - Added support for HTTP basic authentication (temporary solution, at
> > the end I will replace it with UsernameToken);
> > - Added support for JSON web service (client-side - in GWT);
> > - Added support for XML web service (client-side - in GWT);
> > - Removed GWT-RPC mock web services;
> >
> > Additionally you can easily run application by downloading source code
> and type:
> >
> > $ mvn gwt:run
> >
> > Authentication details:
> >
> > username: "admin"
> > password:"admin";
> >
> > It'll start in debug mode - it's much more slower than production mode.
> >
> > At the moment I'm working to move all source code to Apache CXF sandbox.
> >
> > [1] svn checkout http://cxf-log-browser.googlecode.com/svn/trunk/
> > cxf-log-browser-read-only
> >
> > On Fri, Jun 18, 2010 at 3:29 PM, Daniel Kulp <dk...@apache.org> wrote:
> >> On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
> >>> Hi,
> >>>
> >>> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
> >>> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
> >>> >> Just for the record, Tomasz's project is also going well....
> >>> >
> >>> >Well, for the record, I haven't seen anything on the dev list about it
> >>> >yet. Thus, from CXF/Apache's point of view, it's not going well.
> >>> >Definitely encourage him to get involved here and not send you
> anything
> >>> >off list.
> >>>
> >>> I have created project site and blog, few weeks ago.
> >>> Sorry that I didn't announce about it at mailing list.
> >>>
> >>> I will store documentation and source code on Google Code Project [1].
> >>> Additionally I will announce important events and changes through blog
> >>> [2], which I created for this occasion.
> >>
> >> One of the aspects of GSoC, and in particular Apache's involvement in
> it, that
> >> is often missed is teaching the students how the community works.   It's
> not
> >> supposed to be "just do this coding project".    For Apache, it's also
> getting
> >> the student involved in the community and keeping the entire community
> up to
> >> date with what is happening.
> >>
> >> I would strongly suggest that any "import events" and any questions and
> stuff
> >> get posted here on the dev list.   You can add it to the blog as well,
> but
> >> make sure they appear on the dev list.
> >>
> >> There is a saying in Apache:  "if it didn't happen on the dev list, it
> didn't
> >> happen".
> >>
> >> Dan
> >>
> >>
> >>
> >>
> >>> Currently repository [1] contain draft of all features (on my roadmap
> >>> it's milestone 1).
> >>> There is also "Software Requirements Specification" document
> >>> and  "Software Design Description" document. At the moment I'm working
> to
> >>> fix and refactor source code.
> >>>
> >>> When I finish I will move all source code to CXF sandbox.
> >>>
> >>> Once again sorry for my misunderstanding.
> >>>
> >>> [1] http://code.google.com/p/cxf-log-browser/
> >>> [2] http://cxf-log-browser.blogspot.com/
> >>>
> >>> Best regards,
> >>> Tomasz Oponowicz
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org
> >> http://dankulp.com/blog
> >>
> >
> >
> >
> > --
> > Pozdrawiam,
> > Tomasz Oponowicz
> >
>
>
>
> --
> Best regards,
> Tomasz Oponowicz
>
NOTICE � This message and any attachment(s) are for authorized use by the intended recipient(s) only and may contain privileged or confidential information.  Unless you are an intended recipient, you may not use, copy, retain, or disclose to anyone any information contained in this message and any attachment(s).  If you are not an intended recipient of this message, please immediately contact the sender and delete this message and any attachment(s).

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

On Sun, Jul 25, 2010 at 5:51 PM, Tomasz Oponowicz <
tomasz.oponowicz@gmail.com> wrote:

> Hi,
>
> I've got some problem and I can't figure it out:
>
> LogBrowser contains BootstrapStorage service. It's used to retrieve
> user's settings from server - It's crucial service and user must
> include it in his application in order to use LogBrowser. At the
> moment BootstrapStorage service contains "filters" of two kinds. One
> depends on user, e.g. AbstractAuthenticationFilter. Others are always
> required, e.g. configured JSONProvider and
> BootstrapStorage.StaticFileProvider.
>
> Is there any way I can include this "filters" automatically without
> user knowledge (e.g. by annoation or programmatically). I found only
> something like this:
>
> @org.apache.cxf.interceptor.InInterceptors (interceptors =
> {"com.example.Test1Interceptor" })
>
> Currently, registering providers with (CXF) JAXRS endpoints requires the
explicit configuration, either
from Spring or from CXFNonSpringJaxrsServlet. No scanning is supported. I'm
hoping that in time what
StaticFileProvider does will be supported by AbstractHttpServlet. Perhaps
@Providers annotation can also be added in time

thanks, Sergey




> On Thu, Jul 15, 2010 at 11:19 PM, Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > Hi Tomasz
> >
> >>
> >>
> >> > - how do you consider letting users browse through the entries given
> that
> >> a
> >> > number of entries to be displayed on a page is limited - there should
> be
> >> > first/previous/next/last links.
> >>
> >> This is already implemented. first/previous/next/last links are
> >> visible or hidden depend on response from AtomPullServer.
> >>
> >> For example:
> >>
> >> <feed xmlns="http://www.w3.org/2005/Atom">
> >>    [...]
> >>    <link href="http://localhost:8888/log/logs" rel="self"/>
> >>    <link href="http://localhost:8888/log/logs/alternate/1"
> >> rel="alternate"/>
> >>    <link href="http://localhost:8888/log/logs/2" rel="next"/>
> >>    <link href="http://localhost:8888/log/logs/4" rel="last"/>
> >>    [...]
> >> </feed>
> >>
> >> There are visible only refresh, next and last links. first and
> >> previous links are hidden.
> >>
> >>
> > sorry, I guess I should've generated more log entries - will try later...
> >
> > by the way - given that it is an HTML-aware browser, you may want to use
> the
> > 'alternate' links to retrieve the content to be displayed, both for the
> feed
> > and for individual entries
> >
> > thanks, Sergey
> >
>
>
>
> --
> Best regards,
> Tomasz Oponowicz
>

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi,

I've got some problem and I can't figure it out:

LogBrowser contains BootstrapStorage service. It's used to retrieve
user's settings from server - It's crucial service and user must
include it in his application in order to use LogBrowser. At the
moment BootstrapStorage service contains "filters" of two kinds. One
depends on user, e.g. AbstractAuthenticationFilter. Others are always
required, e.g. configured JSONProvider and
BootstrapStorage.StaticFileProvider.

Is there any way I can include this "filters" automatically without
user knowledge (e.g. by annoation or programmatically). I found only
something like this:

@org.apache.cxf.interceptor.InInterceptors (interceptors =
{"com.example.Test1Interceptor" })

On Thu, Jul 15, 2010 at 11:19 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi Tomasz
>
>>
>>
>> > - how do you consider letting users browse through the entries given that
>> a
>> > number of entries to be displayed on a page is limited - there should be
>> > first/previous/next/last links.
>>
>> This is already implemented. first/previous/next/last links are
>> visible or hidden depend on response from AtomPullServer.
>>
>> For example:
>>
>> <feed xmlns="http://www.w3.org/2005/Atom">
>>    [...]
>>    <link href="http://localhost:8888/log/logs" rel="self"/>
>>    <link href="http://localhost:8888/log/logs/alternate/1"
>> rel="alternate"/>
>>    <link href="http://localhost:8888/log/logs/2" rel="next"/>
>>    <link href="http://localhost:8888/log/logs/4" rel="last"/>
>>    [...]
>> </feed>
>>
>> There are visible only refresh, next and last links. first and
>> previous links are hidden.
>>
>>
> sorry, I guess I should've generated more log entries - will try later...
>
> by the way - given that it is an HTML-aware browser, you may want to use the
> 'alternate' links to retrieve the content to be displayed, both for the feed
> and for individual entries
>
> thanks, Sergey
>

-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi Sergey,

I forgot to mention that currently I'm going to add some documentation
and JavaDoc before 16th August.

On Sun, Aug 8, 2010 at 12:06 PM, Tomasz Oponowicz
<to...@gmail.com> wrote:
> Hi Sergey,
>
> I've just finished refactoring (in revision 983258, 983286). I think
> source code now looks much better.
>
> In revision 983373 I fixed bugs and add features described by your comments.
>
> On Thu, Aug 5, 2010 at 5:18 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
>> Hi Tomasz
>>
>>
>> I've rebuilt the latest demo yesterday evening and run it but did not finish
>> this email, sending now - as I've seen a reminder on the mentors list the
>> code freeze is at 16 Aug. There are still few bits and pieces to improve but
>> the progress is obvious.
>>
>> Here're the comments :
>>
>> 1. it's not possible to add more than 1 endpoint; adding a new endpoint
>> overwrites the new one.
>
> Fixed. Before testing please remove "logbrowser-settings.xml" file in
> main directory of sample project.
>
>> 2. please remove milliseconds in dates - they make a single date and hence
>> the entry in the top right corner to occupy 2 lines; also as long as
>> AtomPullServer ensures the records follow each other in the order they were
>> submitted by the log subsystem the milliseconds are not really critical; we
>> will deal later on with letting users to customize the views so milliseconds
>> can be dealt with later on
>>
>
> Done.
>
>> these are less critical :
>>
>>
>> 3. The demo lets users add/get/delete a customer which is fine; there was
>> still 'Generate log entries' option there, I did not have time to check if
>> it was handled by GenerateServlet or not. I think it would just make sense
>> to remove 'Generate log entries' altogether and have logs generated during
>> customer-related invocations
>
> Done.
>
>> 4. please update the custom endpoint code to generate logs with different
>> levels (ex INFO, FINE/DEBUG)
>
> Done.
>
>> 5. try to configure the demo to have the log entries produced by the CXF
>> runtime blocked for now and have only the logs generated by the application
>> endpoint's code displayed; if you were using Spring then you could've
>> configured a 'loggers' property on the AtomPullServer bean:
>>
>> <property name="loggers"
>> value="org.apache.cxf.systest.jaxrs.JAXRSLoggingAtomPullSpringTest$Resource"/>
>>
>> You can configure this property in AtomPullServer in your custom Application
>> explicitly
>>
>
> Done.
>
>> 6.please check how you register JAXRS providers with Application - I can see
>> warnings that they're both singletons & per-request ones
>
> Fixed.
>
>> 7. When we have more than 25 records, say 30 then I can see both 'next' &
>> 'last' links. I thought AtomPullServer would offer both links only when the
>> next page is not the last one, but in this case the next one is the last
>> one. Please just confirm that the browser does not add the 'last' link
>> itself
>
> I think this issue is related with AtomPullServer - LogBrowser shows
> only links, which are defined in response (I checked it by compare
> plain XML responses AtomPullServer).
>
>> Only if you have any time left (can be addressed after the end of the GSOC
>> project)
>>
>> 8. Please show the newest records on top (we can configure the preferences
>> later on). I think AtomPullServer returns them last but for the display
>> purposes I'd prefer the opposite, ex, I had more than 1 page, and was on the
>> first one, then tried to get a customer but had to go to the next page in
>> order to see the related log entries
>
> Fixed partially. I mean I invert order of entries list - at the top of
> the list are entries which are continuation of previous page (other
> words older entries). If you think about changing order of pages
> (first page contains the newest entries), it's not trivial (I need
> more time). Please give me feedback if you thinking about changing
> order of pages.
>
>> 9. can you try to enable a login dialog only if the server challenges ?
>> See we have two cases : unsecure plain HTTP connection and thus there's no
>> point in asking for the name & password info. Or we may have HTTPS and if we
>> do then the browser should get back a challenge and then a log-in dialog
>> will be shown - this assumes the browser is capable of working with the
>> HTTPS endpoints - you can definitely look at it once the project completes,
>> as part of enhancing and merging it all to the trunk
>>
>>
>> Please address some of the issues above (say 1, 2 and something from 3-7)
>> and I think we can consider this project be a success and then hopefully
>> you'll start working on enhancing it a bit more and preparing for the merge
>> to the trunk
>>
>> thanks, Sergey
>>
>>
>> On Sat, Jul 31, 2010 at 6:02 PM, Tomasz Oponowicz <
>> tomasz.oponowicz@gmail.com> wrote:
>>
>>> Hi Sergey,
>>>
>>> Referring to commit r981073, I introduce as fallows changes (include
>>> your comments):
>>>
>>> - Added word wrap to entry content;
>>> - Added fancy exception handler;
>>> - Hided security fields in "add/edit endpoint" dialog box;
>>> - Added Customer service and client (for easy interact) to sample -
>>> service produces log entries which simulate using LogBrowser in
>>> production environment;
>>> - Updated default AtomPullServer's pageSize from 40 to 25;
>>> - Added restoring entry selection when change page;
>>> - Added validation for "Copies" fiels in sample;
>>> - Added support for arrows in entries list;
>>> - Replace cutting message with "title" property;
>>> - Added milliseconds to datetime format;
>>> - Fixed clearing entries list - added removing all cells rather than
>>> clearing content;
>>> - Added validation for "name" and "url" in "add/edit endpoint" dialog box;
>>>
>>> I think all issues and missing features has been resolved. If you mind
>>> I'll come back to refactoring, adding documentation etc.
>>>
>>> Below I gather all your previous comments, which has been resolved in
>>> last commit:
>>>
>>> On Thu, Jul 29, 2010 at 1:38 PM, Sergey Beryozkin <sb...@gmail.com>
>>> wrote:
>>> >> However I also found issues (I will fix them ASAP):
>>> >>
>>> >> - Hide security fields (username, password etc) in "Add/Edit endpoint"
>>> >> dialog box (because I won't implemented authentication for endpoints
>>> >> in the near future,)
>>> >> - Add more advanced exception handler for easy investigating exception;
>>> >> - Add word wrap to entry content;
>>>
>>> Done.
>>>
>>> >> > - the log entry content does not show now date/level but it has some
>>> >> > prefixes which I'm not sure about, ex, if the log entry in the list in
>>> >> the
>>> >> > top right corner reads DEBUG SomeTime "1" then what is displayed below
>>> id
>>> >> > "[12]1", so no level & time but some bogus "[12]" prefix
>>>
>>> Done.
>>>
>>> >> > - GenerateServlet still causes issues for me, had to enter 40 entries
>>> 1 by 1
>>>
>>> Fixed - it should work without any problem, but to make sure I add
>>> numbers only ability to input and fail fast when can't parse number in
>>> GenerateServlet.
>>>
>>> >> >  but rather introduce a JAXRS app
>>> >> > endpoint which generates some custom log entries and have the browser
>>> >> > involking on that endpoint as discussed earlier on.
>>>
>>> Done.
>>>
>>> >> > - Update AtomPullServer to have say a 20-25 limit per page by default
>>> - I
>>> >> > put 40 originally but it is too much..
>>>
>>> Done.
>>>
>>> >> > - Key Focus is lost periodically. Example, I have to select an
>>> individual
>>> >> > log entry in the top right corner. But it has to be selected once I
>>> >> select
>>> >> > TestEndpoint in the left pane (if the entries already exist) or after
>>> >> > Refresh and the focus should stay there on that initial entry. If I
>>> now
>>> >> > press 'next' I should see the first entry in the next list selected
>>> again
>>> >> > and the same should happen when I press previous. May be this is not
>>> easy
>>>
>>> Done.
>>>
>>> >> If possible :-) It would also be nice to be able to browse using just
>>> > keyboard (using up and down arrows) - but it would be an additional
>>> > enhancement
>>>
>>> Done.
>>>
>>> --
>>> Best regards,
>>> Tomasz Oponowicz
>>>
>>
>
> --
> Best regards,
> Tomasz Oponowicz
>



-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi Sergey,

I've just finished refactoring (in revision 983258, 983286). I think
source code now looks much better.

In revision 983373 I fixed bugs and add features described by your comments.

On Thu, Aug 5, 2010 at 5:18 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi Tomasz
>
>
> I've rebuilt the latest demo yesterday evening and run it but did not finish
> this email, sending now - as I've seen a reminder on the mentors list the
> code freeze is at 16 Aug. There are still few bits and pieces to improve but
> the progress is obvious.
>
> Here're the comments :
>
> 1. it's not possible to add more than 1 endpoint; adding a new endpoint
> overwrites the new one.

Fixed. Before testing please remove "logbrowser-settings.xml" file in
main directory of sample project.

> 2. please remove milliseconds in dates - they make a single date and hence
> the entry in the top right corner to occupy 2 lines; also as long as
> AtomPullServer ensures the records follow each other in the order they were
> submitted by the log subsystem the milliseconds are not really critical; we
> will deal later on with letting users to customize the views so milliseconds
> can be dealt with later on
>

Done.

> these are less critical :
>
>
> 3. The demo lets users add/get/delete a customer which is fine; there was
> still 'Generate log entries' option there, I did not have time to check if
> it was handled by GenerateServlet or not. I think it would just make sense
> to remove 'Generate log entries' altogether and have logs generated during
> customer-related invocations

Done.

> 4. please update the custom endpoint code to generate logs with different
> levels (ex INFO, FINE/DEBUG)

Done.

> 5. try to configure the demo to have the log entries produced by the CXF
> runtime blocked for now and have only the logs generated by the application
> endpoint's code displayed; if you were using Spring then you could've
> configured a 'loggers' property on the AtomPullServer bean:
>
> <property name="loggers"
> value="org.apache.cxf.systest.jaxrs.JAXRSLoggingAtomPullSpringTest$Resource"/>
>
> You can configure this property in AtomPullServer in your custom Application
> explicitly
>

Done.

> 6.please check how you register JAXRS providers with Application - I can see
> warnings that they're both singletons & per-request ones

Fixed.

> 7. When we have more than 25 records, say 30 then I can see both 'next' &
> 'last' links. I thought AtomPullServer would offer both links only when the
> next page is not the last one, but in this case the next one is the last
> one. Please just confirm that the browser does not add the 'last' link
> itself

I think this issue is related with AtomPullServer - LogBrowser shows
only links, which are defined in response (I checked it by compare
plain XML responses AtomPullServer).

> Only if you have any time left (can be addressed after the end of the GSOC
> project)
>
> 8. Please show the newest records on top (we can configure the preferences
> later on). I think AtomPullServer returns them last but for the display
> purposes I'd prefer the opposite, ex, I had more than 1 page, and was on the
> first one, then tried to get a customer but had to go to the next page in
> order to see the related log entries

Fixed partially. I mean I invert order of entries list - at the top of
the list are entries which are continuation of previous page (other
words older entries). If you think about changing order of pages
(first page contains the newest entries), it's not trivial (I need
more time). Please give me feedback if you thinking about changing
order of pages.

> 9. can you try to enable a login dialog only if the server challenges ?
> See we have two cases : unsecure plain HTTP connection and thus there's no
> point in asking for the name & password info. Or we may have HTTPS and if we
> do then the browser should get back a challenge and then a log-in dialog
> will be shown - this assumes the browser is capable of working with the
> HTTPS endpoints - you can definitely look at it once the project completes,
> as part of enhancing and merging it all to the trunk
>
>
> Please address some of the issues above (say 1, 2 and something from 3-7)
> and I think we can consider this project be a success and then hopefully
> you'll start working on enhancing it a bit more and preparing for the merge
> to the trunk
>
> thanks, Sergey
>
>
> On Sat, Jul 31, 2010 at 6:02 PM, Tomasz Oponowicz <
> tomasz.oponowicz@gmail.com> wrote:
>
>> Hi Sergey,
>>
>> Referring to commit r981073, I introduce as fallows changes (include
>> your comments):
>>
>> - Added word wrap to entry content;
>> - Added fancy exception handler;
>> - Hided security fields in "add/edit endpoint" dialog box;
>> - Added Customer service and client (for easy interact) to sample -
>> service produces log entries which simulate using LogBrowser in
>> production environment;
>> - Updated default AtomPullServer's pageSize from 40 to 25;
>> - Added restoring entry selection when change page;
>> - Added validation for "Copies" fiels in sample;
>> - Added support for arrows in entries list;
>> - Replace cutting message with "title" property;
>> - Added milliseconds to datetime format;
>> - Fixed clearing entries list - added removing all cells rather than
>> clearing content;
>> - Added validation for "name" and "url" in "add/edit endpoint" dialog box;
>>
>> I think all issues and missing features has been resolved. If you mind
>> I'll come back to refactoring, adding documentation etc.
>>
>> Below I gather all your previous comments, which has been resolved in
>> last commit:
>>
>> On Thu, Jul 29, 2010 at 1:38 PM, Sergey Beryozkin <sb...@gmail.com>
>> wrote:
>> >> However I also found issues (I will fix them ASAP):
>> >>
>> >> - Hide security fields (username, password etc) in "Add/Edit endpoint"
>> >> dialog box (because I won't implemented authentication for endpoints
>> >> in the near future,)
>> >> - Add more advanced exception handler for easy investigating exception;
>> >> - Add word wrap to entry content;
>>
>> Done.
>>
>> >> > - the log entry content does not show now date/level but it has some
>> >> > prefixes which I'm not sure about, ex, if the log entry in the list in
>> >> the
>> >> > top right corner reads DEBUG SomeTime "1" then what is displayed below
>> id
>> >> > "[12]1", so no level & time but some bogus "[12]" prefix
>>
>> Done.
>>
>> >> > - GenerateServlet still causes issues for me, had to enter 40 entries
>> 1 by 1
>>
>> Fixed - it should work without any problem, but to make sure I add
>> numbers only ability to input and fail fast when can't parse number in
>> GenerateServlet.
>>
>> >> >  but rather introduce a JAXRS app
>> >> > endpoint which generates some custom log entries and have the browser
>> >> > involking on that endpoint as discussed earlier on.
>>
>> Done.
>>
>> >> > - Update AtomPullServer to have say a 20-25 limit per page by default
>> - I
>> >> > put 40 originally but it is too much..
>>
>> Done.
>>
>> >> > - Key Focus is lost periodically. Example, I have to select an
>> individual
>> >> > log entry in the top right corner. But it has to be selected once I
>> >> select
>> >> > TestEndpoint in the left pane (if the entries already exist) or after
>> >> > Refresh and the focus should stay there on that initial entry. If I
>> now
>> >> > press 'next' I should see the first entry in the next list selected
>> again
>> >> > and the same should happen when I press previous. May be this is not
>> easy
>>
>> Done.
>>
>> >> If possible :-) It would also be nice to be able to browse using just
>> > keyboard (using up and down arrows) - but it would be an additional
>> > enhancement
>>
>> Done.
>>
>> --
>> Best regards,
>> Tomasz Oponowicz
>>
>

-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

I've rebuilt the latest demo yesterday evening and run it but did not finish
this email, sending now - as I've seen a reminder on the mentors list the
code freeze is at 16 Aug. There are still few bits and pieces to improve but
the progress is obvious.

Here're the comments :

1. it's not possible to add more than 1 endpoint; adding a new endpoint
overwrites the new one.

2. please remove milliseconds in dates - they make a single date and hence
the entry in the top right corner to occupy 2 lines; also as long as
AtomPullServer ensures the records follow each other in the order they were
submitted by the log subsystem the milliseconds are not really critical; we
will deal later on with letting users to customize the views so milliseconds
can be dealt with later on

these are less critical :

3. The demo lets users add/get/delete a customer which is fine; there was
still 'Generate log entries' option there, I did not have time to check if
it was handled by GenerateServlet or not. I think it would just make sense
to remove 'Generate log entries' altogether and have logs generated during
customer-related invocations

4. please update the custom endpoint code to generate logs with different
levels (ex INFO, FINE/DEBUG)

5. try to configure the demo to have the log entries produced by the CXF
runtime blocked for now and have only the logs generated by the application
endpoint's code displayed; if you were using Spring then you could've
configured a 'loggers' property on the AtomPullServer bean:

<property name="loggers"
value="org.apache.cxf.systest.jaxrs.JAXRSLoggingAtomPullSpringTest$Resource"/>

You can configure this property in AtomPullServer in your custom Application
explicitly

6.please check how you register JAXRS providers with Application - I can see
warnings that they're both singletons & per-request ones

7. When we have more than 25 records, say 30 then I can see both 'next' &
'last' links. I thought AtomPullServer would offer both links only when the
next page is not the last one, but in this case the next one is the last
one. Please just confirm that the browser does not add the 'last' link
itself

Only if you have any time left (can be addressed after the end of the GSOC
project)

8. Please show the newest records on top (we can configure the preferences
later on). I think AtomPullServer returns them last but for the display
purposes I'd prefer the opposite, ex, I had more than 1 page, and was on the
first one, then tried to get a customer but had to go to the next page in
order to see the related log entries

9. can you try to enable a login dialog only if the server challenges ?
See we have two cases : unsecure plain HTTP connection and thus there's no
point in asking for the name & password info. Or we may have HTTPS and if we
do then the browser should get back a challenge and then a log-in dialog
will be shown - this assumes the browser is capable of working with the
HTTPS endpoints - you can definitely look at it once the project completes,
as part of enhancing and merging it all to the trunk

Please address some of the issues above (say 1, 2 and something from 3-7)
and I think we can consider this project be a success and then hopefully
you'll start working on enhancing it a bit more and preparing for the merge
to the trunk

thanks, Sergey

On Sat, Jul 31, 2010 at 6:02 PM, Tomasz Oponowicz <
tomasz.oponowicz@gmail.com> wrote:

> Hi Sergey,
>
> Referring to commit r981073, I introduce as fallows changes (include
> your comments):
>
> - Added word wrap to entry content;
> - Added fancy exception handler;
> - Hided security fields in "add/edit endpoint" dialog box;
> - Added Customer service and client (for easy interact) to sample -
> service produces log entries which simulate using LogBrowser in
> production environment;
> - Updated default AtomPullServer's pageSize from 40 to 25;
> - Added restoring entry selection when change page;
> - Added validation for "Copies" fiels in sample;
> - Added support for arrows in entries list;
> - Replace cutting message with "title" property;
> - Added milliseconds to datetime format;
> - Fixed clearing entries list - added removing all cells rather than
> clearing content;
> - Added validation for "name" and "url" in "add/edit endpoint" dialog box;
>
> I think all issues and missing features has been resolved. If you mind
> I'll come back to refactoring, adding documentation etc.
>
> Below I gather all your previous comments, which has been resolved in
> last commit:
>
> On Thu, Jul 29, 2010 at 1:38 PM, Sergey Beryozkin <sb...@gmail.com>
> wrote:
> >> However I also found issues (I will fix them ASAP):
> >>
> >> - Hide security fields (username, password etc) in "Add/Edit endpoint"
> >> dialog box (because I won't implemented authentication for endpoints
> >> in the near future,)
> >> - Add more advanced exception handler for easy investigating exception;
> >> - Add word wrap to entry content;
>
> Done.
>
> >> > - the log entry content does not show now date/level but it has some
> >> > prefixes which I'm not sure about, ex, if the log entry in the list in
> >> the
> >> > top right corner reads DEBUG SomeTime "1" then what is displayed below
> id
> >> > "[12]1", so no level & time but some bogus "[12]" prefix
>
> Done.
>
> >> > - GenerateServlet still causes issues for me, had to enter 40 entries
> 1 by 1
>
> Fixed - it should work without any problem, but to make sure I add
> numbers only ability to input and fail fast when can't parse number in
> GenerateServlet.
>
> >> >  but rather introduce a JAXRS app
> >> > endpoint which generates some custom log entries and have the browser
> >> > involking on that endpoint as discussed earlier on.
>
> Done.
>
> >> > - Update AtomPullServer to have say a 20-25 limit per page by default
> - I
> >> > put 40 originally but it is too much..
>
> Done.
>
> >> > - Key Focus is lost periodically. Example, I have to select an
> individual
> >> > log entry in the top right corner. But it has to be selected once I
> >> select
> >> > TestEndpoint in the left pane (if the entries already exist) or after
> >> > Refresh and the focus should stay there on that initial entry. If I
> now
> >> > press 'next' I should see the first entry in the next list selected
> again
> >> > and the same should happen when I press previous. May be this is not
> easy
>
> Done.
>
> >> If possible :-) It would also be nice to be able to browse using just
> > keyboard (using up and down arrows) - but it would be an additional
> > enhancement
>
> Done.
>
> --
> Best regards,
> Tomasz Oponowicz
>

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi Sergey,

Referring to commit r981073, I introduce as fallows changes (include
your comments):

- Added word wrap to entry content;
- Added fancy exception handler;
- Hided security fields in "add/edit endpoint" dialog box;
- Added Customer service and client (for easy interact) to sample -
service produces log entries which simulate using LogBrowser in
production environment;
- Updated default AtomPullServer's pageSize from 40 to 25;
- Added restoring entry selection when change page;
- Added validation for "Copies" fiels in sample;
- Added support for arrows in entries list;
- Replace cutting message with "title" property;
- Added milliseconds to datetime format;
- Fixed clearing entries list - added removing all cells rather than
clearing content;
- Added validation for "name" and "url" in "add/edit endpoint" dialog box;

I think all issues and missing features has been resolved. If you mind
I'll come back to refactoring, adding documentation etc.

Below I gather all your previous comments, which has been resolved in
last commit:

On Thu, Jul 29, 2010 at 1:38 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
>> However I also found issues (I will fix them ASAP):
>>
>> - Hide security fields (username, password etc) in "Add/Edit endpoint"
>> dialog box (because I won't implemented authentication for endpoints
>> in the near future,)
>> - Add more advanced exception handler for easy investigating exception;
>> - Add word wrap to entry content;

Done.

>> > - the log entry content does not show now date/level but it has some
>> > prefixes which I'm not sure about, ex, if the log entry in the list in
>> the
>> > top right corner reads DEBUG SomeTime "1" then what is displayed below id
>> > "[12]1", so no level & time but some bogus "[12]" prefix

Done.

>> > - GenerateServlet still causes issues for me, had to enter 40 entries 1 by 1

Fixed - it should work without any problem, but to make sure I add
numbers only ability to input and fail fast when can't parse number in
GenerateServlet.

>> >  but rather introduce a JAXRS app
>> > endpoint which generates some custom log entries and have the browser
>> > involking on that endpoint as discussed earlier on.

Done.

>> > - Update AtomPullServer to have say a 20-25 limit per page by default - I
>> > put 40 originally but it is too much..

Done.

>> > - Key Focus is lost periodically. Example, I have to select an individual
>> > log entry in the top right corner. But it has to be selected once I
>> select
>> > TestEndpoint in the left pane (if the entries already exist) or after
>> > Refresh and the focus should stay there on that initial entry. If I now
>> > press 'next' I should see the first entry in the next list selected again
>> > and the same should happen when I press previous. May be this is not easy

Done.

>> If possible :-) It would also be nice to be able to browse using just
> keyboard (using up and down arrows) - but it would be an additional
> enhancement

Done.

-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

On Thu, Jul 29, 2010 at 12:25 PM, Tomasz Oponowicz <
tomasz.oponowicz@gmail.com> wrote:

> Hi Sergey,
>
> Thanks for your reply.
>
> I've made a number of commits, but I forgot write what they fixed:
>
> - Refactored code of BootstrapStorage (for easier configuration) and
> "org.apache.cxf.management/web/logging/browser/client/settings"
> package;
> - Moved "static file" servlet to BootstrapStorage as subresource;
> - Removed dependency of XStream from source code and from pom.xml file;
> - Fixed bugs connected with restoring settings from BootstrapStorage;
> - Fixed configuration for logger in sample (for better interaction
> with AtomPullServer);
> - Moved configuration of JSONProvider to BootstrapStorage;
> - Removed "CHECKSTYLE:OFF" attribute from some classes;
> - Added "Copies" input in "generate.html" page for define number of
> copies. "GenerateServlet" class will generate number of message
> (specified in "Copies" field) in one time;
> - Fixed bug with not clearing previous page after going to another. Added
> - Added basic exception basic handler
> - Removed datetime, level from event content.
> - Fixed broken layout of 'settings' tab;
> - Fixed broken layout of 'authentication' tab;
> - Fixed moved 'last' link;
> - Fixed title of the page;
> - Add cutting long message in log entries list;
>
> thanks for the update


> However I also found issues (I will fix them ASAP):
>
> - Hide security fields (username, password etc) in "Add/Edit endpoint"
> dialog box (because I won't implemented authentication for endpoints
> in the near future,)
> - Add more advanced exception handler for easy investigating exception;
> - Add word wrap to entry content;
>
> When I fixed all issues I will come back to refactoring, adding JavaDocs
> etc.
> Below some comments.
>
>
I'd really appreciate you starting addressing the comments first - the above
is important, as far as adding a touch of quality to the UI interface but at
this stage I'd just like to see an end-end demo working really well...More
comments below

> - ManageEndpoint link is 'acting' as a button but not as a link
>
> I think it's good enough. I patterned "logbrowser" user interface upon
> "Google Reader" user interface - they sometimes use links as buttons
> to be more compact.
>
>
Personally I don't like seeing a link but not being able to click on this
link - it's a bit confusing -
but I'm fine with not making a big deal out of it at this stage :-)


> > - the log entry content does not show now date/level but it has some
> > prefixes which I'm not sure about, ex, if the log entry in the list in
> the
> > top right corner reads DEBUG SomeTime "1" then what is displayed below id
> > "[12]1", so no level & time but some bogus "[12]" prefix
>
> It's thread name. I agree with you that it's a little bit enigmatical.
> I will change it into "Thread name: X" and move it into new special
> section within current "entry content" section.
>
> Please don't. I would not just worry at all about thread names just yet;
just hide it for now. Only if the users chooses somehow that it wants to see
a thread id + whatever else SL4J or log4j can offer then we will show it


> > - GenerateServlet still causes issues for me, had to enter 40 entries 1
> by
> > 1. But please don't fix GenerateServlet but rather introduce a JAXRS app
> > endpoint which generates some custom log entries and have the browser
> > involking on that endpoint as discussed earlier on.
>
> I've already added new input "Copies" to "generate.html" page. If you
> enter "40" there, "GenerateServlet" will generate "40" entries in one
> time. Maybe I should rename this input from "Copies" to "Number of
> copies", because at the moment it could be a little bit confusing.
>
>
This just did not work for me, I chose 30, then pressed and then I saw 1
entry being added only.
But again - please don't spend time on fixing GenerateServlet. Replace it
with the JAXWS or JAXRS endpoint because it is mainly about showing the
entries the real CXF endoints produce, inside their own methods or as part
of the invocation, in the CXF interceptors, etc


> > - Update AtomPullServer to have say a 20-25 limit per page by default - I
> > put 40 originally but it is too much..
> >
> > - Key Focus is lost periodically. Example, I have to select an individual
> > log entry in the top right corner. But it has to be selected once I
> select
> > TestEndpoint in the left pane (if the entries already exist) or after
> > Refresh and the focus should stay there on that initial entry. If I now
> > press 'next' I should see the first entry in the next list selected again
> > and the same should happen when I press previous. May be this is not easy
> to
> > do - not a big issue for now...
>
> Great advice! I will fix it ASAP.
>
> If possible :-) It would also be nice to be able to browse using just
keyboard (using up and down arrows) - but it would be an additional
enhancement

thanks, Sergey

Best regards,
> Tomasz Oponowicz
>

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi Sergey,

Thanks for your reply.

I've made a number of commits, but I forgot write what they fixed:

- Refactored code of BootstrapStorage (for easier configuration) and
"org.apache.cxf.management/web/logging/browser/client/settings"
package;
- Moved "static file" servlet to BootstrapStorage as subresource;
- Removed dependency of XStream from source code and from pom.xml file;
- Fixed bugs connected with restoring settings from BootstrapStorage;
- Fixed configuration for logger in sample (for better interaction
with AtomPullServer);
- Moved configuration of JSONProvider to BootstrapStorage;
- Removed "CHECKSTYLE:OFF" attribute from some classes;
- Added "Copies" input in "generate.html" page for define number of
copies. "GenerateServlet" class will generate number of message
(specified in "Copies" field) in one time;
- Fixed bug with not clearing previous page after going to another. Added
- Added basic exception basic handler
- Removed datetime, level from event content.
- Fixed broken layout of 'settings' tab;
- Fixed broken layout of 'authentication' tab;
- Fixed moved 'last' link;
- Fixed title of the page;
- Add cutting long message in log entries list;

However I also found issues (I will fix them ASAP):

- Hide security fields (username, password etc) in "Add/Edit endpoint"
dialog box (because I won't implemented authentication for endpoints
in the near future,)
- Add more advanced exception handler for easy investigating exception;
- Add word wrap to entry content;

When I fixed all issues I will come back to refactoring, adding JavaDocs etc.
Below some comments.

On Thu, Jul 29, 2010 at 12:32 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi Tomasz
>
> I've built a logbrowser demo in the snapshot. UI is getting slicker, very
> good.
> And I've managed to see the prev/next/last links - great stuff.
>
> So things are going well as far as I can see.
> Here are some specific comments :
> - ManageEndpoint link is 'acting' as a button but not as a link

I think it's good enough. I patterned "logbrowser" user interface upon
"Google Reader" user interface - they sometimes use links as buttons
to be more compact.

> - the log entry content does not show now date/level but it has some
> prefixes which I'm not sure about, ex, if the log entry in the list in the
> top right corner reads DEBUG SomeTime "1" then what is displayed below id
> "[12]1", so no level & time but some bogus "[12]" prefix

It's thread name. I agree with you that it's a little bit enigmatical.
I will change it into "Thread name: X" and move it into new special
section within current "entry content" section.

> - GenerateServlet still causes issues for me, had to enter 40 entries 1 by
> 1. But please don't fix GenerateServlet but rather introduce a JAXRS app
> endpoint which generates some custom log entries and have the browser
> involking on that endpoint as discussed earlier on.

I've already added new input "Copies" to "generate.html" page. If you
enter "40" there, "GenerateServlet" will generate "40" entries in one
time. Maybe I should rename this input from "Copies" to "Number of
copies", because at the moment it could be a little bit confusing.

> - Update AtomPullServer to have say a 20-25 limit per page by default - I
> put 40 originally but it is too much..
>
> - Key Focus is lost periodically. Example, I have to select an individual
> log entry in the top right corner. But it has to be selected once I select
> TestEndpoint in the left pane (if the entries already exist) or after
> Refresh and the focus should stay there on that initial entry. If I now
> press 'next' I should see the first entry in the next list selected again
> and the same should happen when I press previous. May be this is not easy to
> do - not a big issue for now...

Great advice! I will fix it ASAP.

> These are all minor issues compared to the overall progress, thanks.
>
> I'll be traveling on Friday back home and have very limited time in the
> evenings next week...
>
> thanks, Sergey
>

-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

I've built a logbrowser demo in the snapshot. UI is getting slicker, very
good.
And I've managed to see the prev/next/last links - great stuff.

So things are going well as far as I can see.
Here are some specific comments :
- ManageEndpoint link is 'acting' as a button but not as a link
- the log entry content does not show now date/level but it has some
prefixes which I'm not sure about, ex, if the log entry in the list in the
top right corner reads DEBUG SomeTime "1" then what is displayed below id
"[12]1", so no level & time but some bogus "[12]" prefix

- GenerateServlet still causes issues for me, had to enter 40 entries 1 by
1. But please don't fix GenerateServlet but rather introduce a JAXRS app
endpoint which generates some custom log entries and have the browser
involking on that endpoint as discussed earlier on.

- Update AtomPullServer to have say a 20-25 limit per page by default - I
put 40 originally but it is too much..

- Key Focus is lost periodically. Example, I have to select an individual
log entry in the top right corner. But it has to be selected once I select
TestEndpoint in the left pane (if the entries already exist) or after
Refresh and the focus should stay there on that initial entry. If I now
press 'next' I should see the first entry in the next list selected again
and the same should happen when I press previous. May be this is not easy to
do - not a big issue for now...

These are all minor issues compared to the overall progress, thanks.

I'll be traveling on Friday back home and have very limited time in the
evenings next week...

thanks, Sergey

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

>
>
> > - how do you consider letting users browse through the entries given that
> a
> > number of entries to be displayed on a page is limited - there should be
> > first/previous/next/last links.
>
> This is already implemented. first/previous/next/last links are
> visible or hidden depend on response from AtomPullServer.
>
> For example:
>
> <feed xmlns="http://www.w3.org/2005/Atom">
>    [...]
>    <link href="http://localhost:8888/log/logs" rel="self"/>
>    <link href="http://localhost:8888/log/logs/alternate/1"
> rel="alternate"/>
>    <link href="http://localhost:8888/log/logs/2" rel="next"/>
>    <link href="http://localhost:8888/log/logs/4" rel="last"/>
>    [...]
> </feed>
>
> There are visible only refresh, next and last links. first and
> previous links are hidden.
>
>
sorry, I guess I should've generated more log entries - will try later...

by the way - given that it is an HTML-aware browser, you may want to use the
'alternate' links to retrieve the content to be displayed, both for the feed
and for individual entries

thanks, Sergey

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi Sergey,

Thanks for your reply. More comments below.

On Wed, Jul 14, 2010 at 12:22 AM, Sergey Beryozkin <sb...@gmail.com> wrote:
> - please consider updating the demo so that the real log entries are
> generated; that is, introduce a basic CXF JAXRS endpoint (or JAXWS endpoint)
> with one or two methods returning some html or xml data and doing some
> logging, and have a user invoking on that endpoint, using a browser, same as
> a user does now when invoking on the generate servlet. The log events
> generated by the endpoints should be caught by the AtomPullServerEndpoint
> and eventually displayed in the browser window (through Refresh for a
> start).

It's great idea. User can see how exactly it'll look like and also he
doesn't have to add log entries by himself.

> - how do you consider letting users browse through the entries given that a
> number of entries to be displayed on a page is limited - there should be
> first/previous/next/last links.

This is already implemented. first/previous/next/last links are
visible or hidden depend on response from AtomPullServer.

For example:

<feed xmlns="http://www.w3.org/2005/Atom">
    [...]
    <link href="http://localhost:8888/log/logs" rel="self"/>
    <link href="http://localhost:8888/log/logs/alternate/1" rel="alternate"/>
    <link href="http://localhost:8888/log/logs/2" rel="next"/>
    <link href="http://localhost:8888/log/logs/4" rel="last"/>
    [...]
</feed>

There are visible only refresh, next and last links. first and
previous links are hidden.

[...]

You can easily test it (because of custom MockReadableLogStorage) when you type:

mvn gwt:run -Pdev

and than go to address in web browser:

http://127.0.0.1:8888/logbrowser/LogBrowser.html?gwt.codesvr=127.0.0.1:9997

> - The actual log entry info (displayed in the right - bottom view) should
> not include date/time - this is already shown in the right-top view; only
> the actual content

Ok, this is quick fix.

> there're few other enhancements I'd  like to discuss - but for now please
> address the above comments - let me know if you have any doubts, etc.
>
> As I said - this is a very good effort on your behalf - thanks
> Sergey
>
>
> On Thu, Jul 8, 2010 at 5:22 PM, Sergey Beryozkin <sb...@gmail.com>wrote:
>
> > Hi Tomasz
> >
> >  > See, I'm not proposing to write a new servlet implementation. First, I'd
> >> > like to understand what you were trying to achieve by introducing
> >> > StaticContentServlet - I can see it's about serving the static content -
> >> but
> >> > what type of content, when exactly it is needed ? Next, I'd like to see
> >> if
> >> > either AbstractHttpServlet [1] or BootstrapStorage endpoint can be
> >> enhanced
> >> > to do what  StaticContentServlet does ?
> >>
> >> At the moment we've got java classes and *.ui.xml files, which are
> >> changed respectively into *.js and *.css files by GWT compiler (it
> >> change java code to javascript).
> >> To be more specified it's done by 'gwt-maven-plugin'. The GWT
> >> dependency has compilation scope - we don't use GWT at runtime. All
> >> these static files are packed into jar file (static flies takes about
> >> 0.5MB).  Because classes from package
> >> "org.apache.cxf.management.web.logging.browser.client.*" are no longer
> >> needed, they aren't packed into jar file.
> >>
> >> Before user can use our LogBrowser, he has to retrieve all HTML, JS
> >> and CSS files - it can be simply done by go to URL (for example):
> >>
> >> <localhost>/logbrowser/LogBrowser.html
> >>
> >> This content is served by StaticContentServlet - the static files are
> >> retrieve from jar file and send as HTTP response. These happens only
> >> once (per browser) because all of these files are highly cached. After
> >> that user sign in and retrieve settings using BootstrapStorage
> >> endpoint.
> >>
> >> thanks for the explanation
> >
> >
> >> However StaticContentServlet and BootstrapStorage endpoints do similar
> >> job - they "init" application. I think extending BootstrapStorage (to
> >> add StaticContentServlet functionality) will be the best solution.
> >>
> >> What do you think about that?
> >>
> >>
> > Please start from having a dedicated resource method in BootstrapStorage
> > endpoint - this is the simplest thing to do at this stage and it should not
> > be time consuming, but perhaps at some later stage AbstractHttpServlet may
> > be enhanced a bit too..
> >
> > thanks, Sergey
> >



--
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

sorry for a  delay - just letting you know that I did run your demo on
weekends - but did not get to writing a feedback.
The demo looked good to me, it is all very impressive, here are some
comments :

- please consider updating the demo so that the real log entries are
generated; that is, introduce a basic CXF JAXRS endpoint (or JAXWS endpoint)
with one or two methods returning some html or xml data and doing some
logging, and have a user invoking on that endpoint, using a browser, same as
a user does now when invoking on the generate servlet. The log events
generated by the endpoints should be caught by the AtomPullServerEndpoint
and eventually displayed in the browser window (through Refresh for a
start).

- how do you consider letting users browse through the entries given that a
number of entries to be displayed on a page is limited - there should be
first/previous/next/last links.

- "ManageEndpoints" - I'm fine for now with a user having to enter new
endpoints in a separate page, but what I'd like to see is "ManageEndpoints"
being a link - it is displayed as a link actually, but it behaves as if it
is a button (same for the first/previous/next/last links).

- The actual log entry info (displayed in the right - bottom view) should
not include date/time - this is already shown in the right-top view; only
the actual content

there're few other enhancements I'd  like to discuss - but for now please
address the above comments - let me know if you have any doubts, etc.

As I said - this is a very good effort on your behalf - thanks
Sergey


On Thu, Jul 8, 2010 at 5:22 PM, Sergey Beryozkin <sb...@gmail.com>wrote:

> Hi Tomasz
>
>  > See, I'm not proposing to write a new servlet implementation. First, I'd
>> > like to understand what you were trying to achieve by introducing
>> > StaticContentServlet - I can see it's about serving the static content -
>> but
>> > what type of content, when exactly it is needed ? Next, I'd like to see
>> if
>> > either AbstractHttpServlet [1] or BootstrapStorage endpoint can be
>> enhanced
>> > to do what  StaticContentServlet does ?
>>
>> At the moment we've got java classes and *.ui.xml files, which are
>> changed respectively into *.js and *.css files by GWT compiler (it
>> change java code to javascript).
>> To be more specified it's done by 'gwt-maven-plugin'. The GWT
>> dependency has compilation scope - we don't use GWT at runtime. All
>> these static files are packed into jar file (static flies takes about
>> 0.5MB).  Because classes from package
>> "org.apache.cxf.management.web.logging.browser.client.*" are no longer
>> needed, they aren't packed into jar file.
>>
>> Before user can use our LogBrowser, he has to retrieve all HTML, JS
>> and CSS files - it can be simply done by go to URL (for example):
>>
>> <localhost>/logbrowser/LogBrowser.html
>>
>> This content is served by StaticContentServlet - the static files are
>> retrieve from jar file and send as HTTP response. These happens only
>> once (per browser) because all of these files are highly cached. After
>> that user sign in and retrieve settings using BootstrapStorage
>> endpoint.
>>
>> thanks for the explanation
>
>
>> However StaticContentServlet and BootstrapStorage endpoints do similar
>> job - they "init" application. I think extending BootstrapStorage (to
>> add StaticContentServlet functionality) will be the best solution.
>>
>> What do you think about that?
>>
>>
> Please start from having a dedicated resource method in BootstrapStorage
> endpoint - this is the simplest thing to do at this stage and it should not
> be time consuming, but perhaps at some later stage AbstractHttpServlet may
> be enhanced a bit too..
>
> thanks, Sergey
>

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

> See, I'm not proposing to write a new servlet implementation. First, I'd
> > like to understand what you were trying to achieve by introducing
> > StaticContentServlet - I can see it's about serving the static content -
> but
> > what type of content, when exactly it is needed ? Next, I'd like to see
> if
> > either AbstractHttpServlet [1] or BootstrapStorage endpoint can be
> enhanced
> > to do what  StaticContentServlet does ?
>
> At the moment we've got java classes and *.ui.xml files, which are
> changed respectively into *.js and *.css files by GWT compiler (it
> change java code to javascript).
> To be more specified it's done by 'gwt-maven-plugin'. The GWT
> dependency has compilation scope - we don't use GWT at runtime. All
> these static files are packed into jar file (static flies takes about
> 0.5MB).  Because classes from package
> "org.apache.cxf.management.web.logging.browser.client.*" are no longer
> needed, they aren't packed into jar file.
>
> Before user can use our LogBrowser, he has to retrieve all HTML, JS
> and CSS files - it can be simply done by go to URL (for example):
>
> <localhost>/logbrowser/LogBrowser.html
>
> This content is served by StaticContentServlet - the static files are
> retrieve from jar file and send as HTTP response. These happens only
> once (per browser) because all of these files are highly cached. After
> that user sign in and retrieve settings using BootstrapStorage
> endpoint.
>
> thanks for the explanation


> However StaticContentServlet and BootstrapStorage endpoints do similar
> job - they "init" application. I think extending BootstrapStorage (to
> add StaticContentServlet functionality) will be the best solution.
>
> What do you think about that?
>
>
Please start from having a dedicated resource method in BootstrapStorage
endpoint - this is the simplest thing to do at this stage and it should not
be time consuming, but perhaps at some later stage AbstractHttpServlet may
be enhanced a bit too..

thanks, Sergey

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi Sergey,

On Wed, Jul 7, 2010 at 11:51 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi Tomasz
>
> you're doing very well and there's absolutely no need to apologize :-).
> Please take your time, this GSOC project is an important project but I
> personally do not expect the result be of the very top quality, no one can
> do it from the first try :-)

Yeah, I know - I just don't like make a "crap" ;-)

> See, I'm not proposing to write a new servlet implementation. First, I'd
> like to understand what you were trying to achieve by introducing
> StaticContentServlet - I can see it's about serving the static content - but
> what type of content, when exactly it is needed ? Next, I'd like to see if
> either AbstractHttpServlet [1] or BootstrapStorage endpoint can be enhanced
> to do what  StaticContentServlet does ?

At the moment we've got java classes and *.ui.xml files, which are
changed respectively into *.js and *.css files by GWT compiler (it
change java code to javascript).
To be more specified it's done by 'gwt-maven-plugin'. The GWT
dependency has compilation scope - we don't use GWT at runtime. All
these static files are packed into jar file (static flies takes about
0.5MB).  Because classes from package
"org.apache.cxf.management.web.logging.browser.client.*" are no longer
needed, they aren't packed into jar file.

Before user can use our LogBrowser, he has to retrieve all HTML, JS
and CSS files - it can be simply done by go to URL (for example):

<localhost>/logbrowser/LogBrowser.html

This content is served by StaticContentServlet - the static files are
retrieve from jar file and send as HTTP response. These happens only
once (per browser) because all of these files are highly cached. After
that user sign in and retrieve settings using BootstrapStorage
endpoint.

However StaticContentServlet and BootstrapStorage endpoints do similar
job - they "init" application. I think extending BootstrapStorage (to
add StaticContentServlet functionality) will be the best solution.

What do you think about that?

> thanks, Sergey
>
> [1]
> http://svn.apache.org/repos/asf/cxf/trunk/rt/transports/http/src/main/java/org/apache/cxf/transport/servlet/AbstractHTTPServlet.java
>
>
> On Wed, Jul 7, 2010 at 10:27 PM, Tomasz Oponowicz <
> tomasz.oponowicz@gmail.com> wrote:
>
>> Hi Sergey,
>>
>> On Wed, Jul 7, 2010 at 10:40 PM, Sergey Beryozkin <sb...@gmail.com>
>> wrote:
>> > thanks - I'll be evaluating the demo these weekends, sorry, won't be able
>> to
>> > get to it earlier, but I'll do it in time so that we can prepare a mid
>> term
>> > evaluation report
>>
>> I hope you will enjoy.
>>
>> > I'd like to clarify the role of StaticContentServlet.java. I'm a bit
>> > concerned about users having to add this servlet entry in addition to two
>> > other ones (one for handling AtomPullServer and the other one for
>> > BootstrapStorage).
>> >
>> > What exactly does this servlet do that can not be done by enhancing say
>> > BootstrapStorage or (CXF) AbstractHttpServlet ?
>>
>> Yes, you've got absolute right. Of course, for end user, easier
>> configuration is better.
>>
>> I've done some mistake - I wrote StaticContentServlet by myself
>> instead of extending AbstractHttpServlet or DefaultServlet. I will
>> fixed it. However I'd like to join StaticContentServlet and
>> BootstrapStorage class into one single class (as you mentioned).
>>
>> This all happened because I've been working in a hurry. Now I'd like
>> to make some major clean up (for example join StaticContentServlet and
>> BootstrapStorage into one class and extending AbstractHttpServlet
>> rather than write code by myself or remove useless dependency - I mean
>> XStream) before mid-term mid-term evaluations deadline.
>>
>> Once again sorry for that mess - at the moment I'm working hard to
>> improve code quality.
>>
>> >
>> > cheers, Sergey
>> >
>> > On Tue, Jul 6, 2010 at 3:00 PM, Tomasz Oponowicz <
>> tomasz.oponowicz@gmail.com
>> >> wrote:
>> >
>> >> Hi,t
>> >> I've just committed basic version of logbrowser [1] (described by my
>> >> proposal).
>> >>
>> >> I also created sample application [2] for easy testing all parts of
>> >> the project.
>> >> However it's more or less what user have to do to integrate logbrowser
>> >> into his application.
>> >> Detailed description, how to run sample application, is here [3].
>> >>
>> >> I'm staring work on [4] and [5] (i.e. refactoring, clean up and
>> >> writing documentation)
>> >> and I'm going to finished those tasks before mid-term evaluations
>> >> deadline (i.e. 16.07.2010).
>> >>
>> >> Next I will add optional features [6].
>> >>
>> >> [1] http://svn.apache.org/viewvc?rev=960895&view=rev
>> >> [2] ./distribution/src/main/release/samples/logbrowser
>> >> [3] ./distribution/src/main/release/samples/logbrowser/README.txt
>> >> [4] https://issues.apache.org/jira/browse/CXF-2881
>> >> [5] https://issues.apache.org/jira/browse/CXF-2882
>> >> [6] https://issues.apache.org/jira/browse/CXF-2883
>> >>
>> >> On Mon, Jun 21, 2010 at 6:55 PM, Tomasz Oponowicz
>> >> <to...@gmail.com> wrote:
>> >> > Hi,
>> >> >
>> >> > I've just commit changes at repository [1]. Changes from last version:
>> >> >
>> >> > - Created Maven project structure;
>> >> > - Configured 'maven-gwt-plugin' for automatic execute GWT compiler (to
>> >> > convert Java to JavaScript);
>> >> > - Added draft implementation of 'BootstrapStorage';
>> >> > - Create sample configuration of 'AtomPullServer';
>> >> > - Added support for HTTP basic authentication (temporary solution, at
>> >> > the end I will replace it with UsernameToken);
>> >> > - Added support for JSON web service (client-side - in GWT);
>> >> > - Added support for XML web service (client-side - in GWT);
>> >> > - Removed GWT-RPC mock web services;
>> >> >
>> >> > Additionally you can easily run application by downloading source code
>> >> and type:
>> >> >
>> >> > $ mvn gwt:run
>> >> >
>> >> > Authentication details:
>> >> >
>> >> > username: "admin"
>> >> > password:"admin";
>> >> >
>> >> > It'll start in debug mode - it's much more slower than production
>> mode.
>> >> >
>> >> > At the moment I'm working to move all source code to Apache CXF
>> sandbox.
>> >> >
>> >> > [1] svn checkout http://cxf-log-browser.googlecode.com/svn/trunk/
>> >> > cxf-log-browser-read-only
>> >> >
>> >> > On Fri, Jun 18, 2010 at 3:29 PM, Daniel Kulp <dk...@apache.org>
>> wrote:
>> >> >> On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
>> >> >>> Hi,
>> >> >>>
>> >> >>> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org>
>> wrote:
>> >> >>> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
>> >> >>> >> Just for the record, Tomasz's project is also going well....
>> >> >>> >
>> >> >>> >Well, for the record, I haven't seen anything on the dev list about
>> it
>> >> >>> >yet. Thus, from CXF/Apache's point of view, it's not going well.
>> >> >>> >Definitely encourage him to get involved here and not send you
>> >> anything
>> >> >>> >off list.
>> >> >>>
>> >> >>> I have created project site and blog, few weeks ago.
>> >> >>> Sorry that I didn't announce about it at mailing list.
>> >> >>>
>> >> >>> I will store documentation and source code on Google Code Project
>> [1].
>> >> >>> Additionally I will announce important events and changes through
>> blog
>> >> >>> [2], which I created for this occasion.
>> >> >>
>> >> >> One of the aspects of GSoC, and in particular Apache's involvement in
>> >> it, that
>> >> >> is often missed is teaching the students how the community works.
>> It's
>> >> not
>> >> >> supposed to be "just do this coding project".    For Apache, it's
>> also
>> >> getting
>> >> >> the student involved in the community and keeping the entire
>> community
>> >> up to
>> >> >> date with what is happening.
>> >> >>
>> >> >> I would strongly suggest that any "import events" and any questions
>> and
>> >> stuff
>> >> >> get posted here on the dev list.   You can add it to the blog as
>> well,
>> >> but
>> >> >> make sure they appear on the dev list.
>> >> >>
>> >> >> There is a saying in Apache:  "if it didn't happen on the dev list,
>> it
>> >> didn't
>> >> >> happen".
>> >> >>
>> >> >> Dan
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>> Currently repository [1] contain draft of all features (on my
>> roadmap
>> >> >>> it's milestone 1).
>> >> >>> There is also "Software Requirements Specification" document
>> >> >>> and  "Software Design Description" document. At the moment I'm
>> working
>> >> to
>> >> >>> fix and refactor source code.
>> >> >>>
>> >> >>> When I finish I will move all source code to CXF sandbox.
>> >> >>>
>> >> >>> Once again sorry for my misunderstanding.
>> >> >>>
>> >> >>> [1] http://code.google.com/p/cxf-log-browser/
>> >> >>> [2] http://cxf-log-browser.blogspot.com/
>> >> >>>
>> >> >>> Best regards,
>> >> >>> Tomasz Oponowicz
>> >> >>
>> >> >> --
>> >> >> Daniel Kulp
>> >> >> dkulp@apache.org
>> >> >> http://dankulp.com/blog
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Pozdrawiam,
>> >> > Tomasz Oponowicz
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Best regards,
>> >> Tomasz Oponowicz
>> >>
>> >
>>
>>
>>
>> --
>> Best regards,
>> Tomasz Oponowicz
>>
>



-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

you're doing very well and there's absolutely no need to apologize :-).
Please take your time, this GSOC project is an important project but I
personally do not expect the result be of the very top quality, no one can
do it from the first try :-)

See, I'm not proposing to write a new servlet implementation. First, I'd
like to understand what you were trying to achieve by introducing
StaticContentServlet - I can see it's about serving the static content - but
what type of content, when exactly it is needed ? Next, I'd like to see if
either AbstractHttpServlet [1] or BootstrapStorage endpoint can be enhanced
to do what  StaticContentServlet does ?

thanks, Sergey

[1]
http://svn.apache.org/repos/asf/cxf/trunk/rt/transports/http/src/main/java/org/apache/cxf/transport/servlet/AbstractHTTPServlet.java


On Wed, Jul 7, 2010 at 10:27 PM, Tomasz Oponowicz <
tomasz.oponowicz@gmail.com> wrote:

> Hi Sergey,
>
> On Wed, Jul 7, 2010 at 10:40 PM, Sergey Beryozkin <sb...@gmail.com>
> wrote:
> > thanks - I'll be evaluating the demo these weekends, sorry, won't be able
> to
> > get to it earlier, but I'll do it in time so that we can prepare a mid
> term
> > evaluation report
>
> I hope you will enjoy.
>
> > I'd like to clarify the role of StaticContentServlet.java. I'm a bit
> > concerned about users having to add this servlet entry in addition to two
> > other ones (one for handling AtomPullServer and the other one for
> > BootstrapStorage).
> >
> > What exactly does this servlet do that can not be done by enhancing say
> > BootstrapStorage or (CXF) AbstractHttpServlet ?
>
> Yes, you've got absolute right. Of course, for end user, easier
> configuration is better.
>
> I've done some mistake - I wrote StaticContentServlet by myself
> instead of extending AbstractHttpServlet or DefaultServlet. I will
> fixed it. However I'd like to join StaticContentServlet and
> BootstrapStorage class into one single class (as you mentioned).
>
> This all happened because I've been working in a hurry. Now I'd like
> to make some major clean up (for example join StaticContentServlet and
> BootstrapStorage into one class and extending AbstractHttpServlet
> rather than write code by myself or remove useless dependency - I mean
> XStream) before mid-term mid-term evaluations deadline.
>
> Once again sorry for that mess - at the moment I'm working hard to
> improve code quality.
>
> >
> > cheers, Sergey
> >
> > On Tue, Jul 6, 2010 at 3:00 PM, Tomasz Oponowicz <
> tomasz.oponowicz@gmail.com
> >> wrote:
> >
> >> Hi,t
> >> I've just committed basic version of logbrowser [1] (described by my
> >> proposal).
> >>
> >> I also created sample application [2] for easy testing all parts of
> >> the project.
> >> However it's more or less what user have to do to integrate logbrowser
> >> into his application.
> >> Detailed description, how to run sample application, is here [3].
> >>
> >> I'm staring work on [4] and [5] (i.e. refactoring, clean up and
> >> writing documentation)
> >> and I'm going to finished those tasks before mid-term evaluations
> >> deadline (i.e. 16.07.2010).
> >>
> >> Next I will add optional features [6].
> >>
> >> [1] http://svn.apache.org/viewvc?rev=960895&view=rev
> >> [2] ./distribution/src/main/release/samples/logbrowser
> >> [3] ./distribution/src/main/release/samples/logbrowser/README.txt
> >> [4] https://issues.apache.org/jira/browse/CXF-2881
> >> [5] https://issues.apache.org/jira/browse/CXF-2882
> >> [6] https://issues.apache.org/jira/browse/CXF-2883
> >>
> >> On Mon, Jun 21, 2010 at 6:55 PM, Tomasz Oponowicz
> >> <to...@gmail.com> wrote:
> >> > Hi,
> >> >
> >> > I've just commit changes at repository [1]. Changes from last version:
> >> >
> >> > - Created Maven project structure;
> >> > - Configured 'maven-gwt-plugin' for automatic execute GWT compiler (to
> >> > convert Java to JavaScript);
> >> > - Added draft implementation of 'BootstrapStorage';
> >> > - Create sample configuration of 'AtomPullServer';
> >> > - Added support for HTTP basic authentication (temporary solution, at
> >> > the end I will replace it with UsernameToken);
> >> > - Added support for JSON web service (client-side - in GWT);
> >> > - Added support for XML web service (client-side - in GWT);
> >> > - Removed GWT-RPC mock web services;
> >> >
> >> > Additionally you can easily run application by downloading source code
> >> and type:
> >> >
> >> > $ mvn gwt:run
> >> >
> >> > Authentication details:
> >> >
> >> > username: "admin"
> >> > password:"admin";
> >> >
> >> > It'll start in debug mode - it's much more slower than production
> mode.
> >> >
> >> > At the moment I'm working to move all source code to Apache CXF
> sandbox.
> >> >
> >> > [1] svn checkout http://cxf-log-browser.googlecode.com/svn/trunk/
> >> > cxf-log-browser-read-only
> >> >
> >> > On Fri, Jun 18, 2010 at 3:29 PM, Daniel Kulp <dk...@apache.org>
> wrote:
> >> >> On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
> >> >>> Hi,
> >> >>>
> >> >>> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org>
> wrote:
> >> >>> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
> >> >>> >> Just for the record, Tomasz's project is also going well....
> >> >>> >
> >> >>> >Well, for the record, I haven't seen anything on the dev list about
> it
> >> >>> >yet. Thus, from CXF/Apache's point of view, it's not going well.
> >> >>> >Definitely encourage him to get involved here and not send you
> >> anything
> >> >>> >off list.
> >> >>>
> >> >>> I have created project site and blog, few weeks ago.
> >> >>> Sorry that I didn't announce about it at mailing list.
> >> >>>
> >> >>> I will store documentation and source code on Google Code Project
> [1].
> >> >>> Additionally I will announce important events and changes through
> blog
> >> >>> [2], which I created for this occasion.
> >> >>
> >> >> One of the aspects of GSoC, and in particular Apache's involvement in
> >> it, that
> >> >> is often missed is teaching the students how the community works.
> It's
> >> not
> >> >> supposed to be "just do this coding project".    For Apache, it's
> also
> >> getting
> >> >> the student involved in the community and keeping the entire
> community
> >> up to
> >> >> date with what is happening.
> >> >>
> >> >> I would strongly suggest that any "import events" and any questions
> and
> >> stuff
> >> >> get posted here on the dev list.   You can add it to the blog as
> well,
> >> but
> >> >> make sure they appear on the dev list.
> >> >>
> >> >> There is a saying in Apache:  "if it didn't happen on the dev list,
> it
> >> didn't
> >> >> happen".
> >> >>
> >> >> Dan
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>> Currently repository [1] contain draft of all features (on my
> roadmap
> >> >>> it's milestone 1).
> >> >>> There is also "Software Requirements Specification" document
> >> >>> and  "Software Design Description" document. At the moment I'm
> working
> >> to
> >> >>> fix and refactor source code.
> >> >>>
> >> >>> When I finish I will move all source code to CXF sandbox.
> >> >>>
> >> >>> Once again sorry for my misunderstanding.
> >> >>>
> >> >>> [1] http://code.google.com/p/cxf-log-browser/
> >> >>> [2] http://cxf-log-browser.blogspot.com/
> >> >>>
> >> >>> Best regards,
> >> >>> Tomasz Oponowicz
> >> >>
> >> >> --
> >> >> Daniel Kulp
> >> >> dkulp@apache.org
> >> >> http://dankulp.com/blog
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Pozdrawiam,
> >> > Tomasz Oponowicz
> >> >
> >>
> >>
> >>
> >> --
> >> Best regards,
> >> Tomasz Oponowicz
> >>
> >
>
>
>
> --
> Best regards,
> Tomasz Oponowicz
>

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi Sergey,

On Wed, Jul 7, 2010 at 10:40 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
> thanks - I'll be evaluating the demo these weekends, sorry, won't be able to
> get to it earlier, but I'll do it in time so that we can prepare a mid term
> evaluation report

I hope you will enjoy.

> I'd like to clarify the role of StaticContentServlet.java. I'm a bit
> concerned about users having to add this servlet entry in addition to two
> other ones (one for handling AtomPullServer and the other one for
> BootstrapStorage).
>
> What exactly does this servlet do that can not be done by enhancing say
> BootstrapStorage or (CXF) AbstractHttpServlet ?

Yes, you've got absolute right. Of course, for end user, easier
configuration is better.

I've done some mistake - I wrote StaticContentServlet by myself
instead of extending AbstractHttpServlet or DefaultServlet. I will
fixed it. However I'd like to join StaticContentServlet and
BootstrapStorage class into one single class (as you mentioned).

This all happened because I've been working in a hurry. Now I'd like
to make some major clean up (for example join StaticContentServlet and
BootstrapStorage into one class and extending AbstractHttpServlet
rather than write code by myself or remove useless dependency - I mean
XStream) before mid-term mid-term evaluations deadline.

Once again sorry for that mess - at the moment I'm working hard to
improve code quality.

>
> cheers, Sergey
>
> On Tue, Jul 6, 2010 at 3:00 PM, Tomasz Oponowicz <tomasz.oponowicz@gmail.com
>> wrote:
>
>> Hi,t
>> I've just committed basic version of logbrowser [1] (described by my
>> proposal).
>>
>> I also created sample application [2] for easy testing all parts of
>> the project.
>> However it's more or less what user have to do to integrate logbrowser
>> into his application.
>> Detailed description, how to run sample application, is here [3].
>>
>> I'm staring work on [4] and [5] (i.e. refactoring, clean up and
>> writing documentation)
>> and I'm going to finished those tasks before mid-term evaluations
>> deadline (i.e. 16.07.2010).
>>
>> Next I will add optional features [6].
>>
>> [1] http://svn.apache.org/viewvc?rev=960895&view=rev
>> [2] ./distribution/src/main/release/samples/logbrowser
>> [3] ./distribution/src/main/release/samples/logbrowser/README.txt
>> [4] https://issues.apache.org/jira/browse/CXF-2881
>> [5] https://issues.apache.org/jira/browse/CXF-2882
>> [6] https://issues.apache.org/jira/browse/CXF-2883
>>
>> On Mon, Jun 21, 2010 at 6:55 PM, Tomasz Oponowicz
>> <to...@gmail.com> wrote:
>> > Hi,
>> >
>> > I've just commit changes at repository [1]. Changes from last version:
>> >
>> > - Created Maven project structure;
>> > - Configured 'maven-gwt-plugin' for automatic execute GWT compiler (to
>> > convert Java to JavaScript);
>> > - Added draft implementation of 'BootstrapStorage';
>> > - Create sample configuration of 'AtomPullServer';
>> > - Added support for HTTP basic authentication (temporary solution, at
>> > the end I will replace it with UsernameToken);
>> > - Added support for JSON web service (client-side - in GWT);
>> > - Added support for XML web service (client-side - in GWT);
>> > - Removed GWT-RPC mock web services;
>> >
>> > Additionally you can easily run application by downloading source code
>> and type:
>> >
>> > $ mvn gwt:run
>> >
>> > Authentication details:
>> >
>> > username: "admin"
>> > password:"admin";
>> >
>> > It'll start in debug mode - it's much more slower than production mode.
>> >
>> > At the moment I'm working to move all source code to Apache CXF sandbox.
>> >
>> > [1] svn checkout http://cxf-log-browser.googlecode.com/svn/trunk/
>> > cxf-log-browser-read-only
>> >
>> > On Fri, Jun 18, 2010 at 3:29 PM, Daniel Kulp <dk...@apache.org> wrote:
>> >> On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
>> >>> Hi,
>> >>>
>> >>> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
>> >>> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
>> >>> >> Just for the record, Tomasz's project is also going well....
>> >>> >
>> >>> >Well, for the record, I haven't seen anything on the dev list about it
>> >>> >yet. Thus, from CXF/Apache's point of view, it's not going well.
>> >>> >Definitely encourage him to get involved here and not send you
>> anything
>> >>> >off list.
>> >>>
>> >>> I have created project site and blog, few weeks ago.
>> >>> Sorry that I didn't announce about it at mailing list.
>> >>>
>> >>> I will store documentation and source code on Google Code Project [1].
>> >>> Additionally I will announce important events and changes through blog
>> >>> [2], which I created for this occasion.
>> >>
>> >> One of the aspects of GSoC, and in particular Apache's involvement in
>> it, that
>> >> is often missed is teaching the students how the community works.   It's
>> not
>> >> supposed to be "just do this coding project".    For Apache, it's also
>> getting
>> >> the student involved in the community and keeping the entire community
>> up to
>> >> date with what is happening.
>> >>
>> >> I would strongly suggest that any "import events" and any questions and
>> stuff
>> >> get posted here on the dev list.   You can add it to the blog as well,
>> but
>> >> make sure they appear on the dev list.
>> >>
>> >> There is a saying in Apache:  "if it didn't happen on the dev list, it
>> didn't
>> >> happen".
>> >>
>> >> Dan
>> >>
>> >>
>> >>
>> >>
>> >>> Currently repository [1] contain draft of all features (on my roadmap
>> >>> it's milestone 1).
>> >>> There is also "Software Requirements Specification" document
>> >>> and  "Software Design Description" document. At the moment I'm working
>> to
>> >>> fix and refactor source code.
>> >>>
>> >>> When I finish I will move all source code to CXF sandbox.
>> >>>
>> >>> Once again sorry for my misunderstanding.
>> >>>
>> >>> [1] http://code.google.com/p/cxf-log-browser/
>> >>> [2] http://cxf-log-browser.blogspot.com/
>> >>>
>> >>> Best regards,
>> >>> Tomasz Oponowicz
>> >>
>> >> --
>> >> Daniel Kulp
>> >> dkulp@apache.org
>> >> http://dankulp.com/blog
>> >>
>> >
>> >
>> >
>> > --
>> > Pozdrawiam,
>> > Tomasz Oponowicz
>> >
>>
>>
>>
>> --
>> Best regards,
>> Tomasz Oponowicz
>>
>



-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Sergey Beryozkin <sb...@gmail.com>.

Hi Tomasz

thanks - I'll be evaluating the demo these weekends, sorry, won't be able to
get to it earlier, but I'll do it in time so that we can prepare a mid term
evaluation report

I'd like to clarify the role of StaticContentServlet.java. I'm a bit
concerned about users having to add this servlet entry in addition to two
other ones (one for handling AtomPullServer and the other one for
BootstrapStorage).

What exactly does this servlet do that can not be done by enhancing say
BootstrapStorage or (CXF) AbstractHttpServlet ?

cheers, Sergey

On Tue, Jul 6, 2010 at 3:00 PM, Tomasz Oponowicz <tomasz.oponowicz@gmail.com
> wrote:

> Hi,t
> I've just committed basic version of logbrowser [1] (described by my
> proposal).
>
> I also created sample application [2] for easy testing all parts of
> the project.
> However it's more or less what user have to do to integrate logbrowser
> into his application.
> Detailed description, how to run sample application, is here [3].
>
> I'm staring work on [4] and [5] (i.e. refactoring, clean up and
> writing documentation)
> and I'm going to finished those tasks before mid-term evaluations
> deadline (i.e. 16.07.2010).
>
> Next I will add optional features [6].
>
> [1] http://svn.apache.org/viewvc?rev=960895&view=rev
> [2] ./distribution/src/main/release/samples/logbrowser
> [3] ./distribution/src/main/release/samples/logbrowser/README.txt
> [4] https://issues.apache.org/jira/browse/CXF-2881
> [5] https://issues.apache.org/jira/browse/CXF-2882
> [6] https://issues.apache.org/jira/browse/CXF-2883
>
> On Mon, Jun 21, 2010 at 6:55 PM, Tomasz Oponowicz
> <to...@gmail.com> wrote:
> > Hi,
> >
> > I've just commit changes at repository [1]. Changes from last version:
> >
> > - Created Maven project structure;
> > - Configured 'maven-gwt-plugin' for automatic execute GWT compiler (to
> > convert Java to JavaScript);
> > - Added draft implementation of 'BootstrapStorage';
> > - Create sample configuration of 'AtomPullServer';
> > - Added support for HTTP basic authentication (temporary solution, at
> > the end I will replace it with UsernameToken);
> > - Added support for JSON web service (client-side - in GWT);
> > - Added support for XML web service (client-side - in GWT);
> > - Removed GWT-RPC mock web services;
> >
> > Additionally you can easily run application by downloading source code
> and type:
> >
> > $ mvn gwt:run
> >
> > Authentication details:
> >
> > username: "admin"
> > password:"admin";
> >
> > It'll start in debug mode - it's much more slower than production mode.
> >
> > At the moment I'm working to move all source code to Apache CXF sandbox.
> >
> > [1] svn checkout http://cxf-log-browser.googlecode.com/svn/trunk/
> > cxf-log-browser-read-only
> >
> > On Fri, Jun 18, 2010 at 3:29 PM, Daniel Kulp <dk...@apache.org> wrote:
> >> On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
> >>> Hi,
> >>>
> >>> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
> >>> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
> >>> >> Just for the record, Tomasz's project is also going well....
> >>> >
> >>> >Well, for the record, I haven't seen anything on the dev list about it
> >>> >yet. Thus, from CXF/Apache's point of view, it's not going well.
> >>> >Definitely encourage him to get involved here and not send you
> anything
> >>> >off list.
> >>>
> >>> I have created project site and blog, few weeks ago.
> >>> Sorry that I didn't announce about it at mailing list.
> >>>
> >>> I will store documentation and source code on Google Code Project [1].
> >>> Additionally I will announce important events and changes through blog
> >>> [2], which I created for this occasion.
> >>
> >> One of the aspects of GSoC, and in particular Apache's involvement in
> it, that
> >> is often missed is teaching the students how the community works.   It's
> not
> >> supposed to be "just do this coding project".    For Apache, it's also
> getting
> >> the student involved in the community and keeping the entire community
> up to
> >> date with what is happening.
> >>
> >> I would strongly suggest that any "import events" and any questions and
> stuff
> >> get posted here on the dev list.   You can add it to the blog as well,
> but
> >> make sure they appear on the dev list.
> >>
> >> There is a saying in Apache:  "if it didn't happen on the dev list, it
> didn't
> >> happen".
> >>
> >> Dan
> >>
> >>
> >>
> >>
> >>> Currently repository [1] contain draft of all features (on my roadmap
> >>> it's milestone 1).
> >>> There is also "Software Requirements Specification" document
> >>> and  "Software Design Description" document. At the moment I'm working
> to
> >>> fix and refactor source code.
> >>>
> >>> When I finish I will move all source code to CXF sandbox.
> >>>
> >>> Once again sorry for my misunderstanding.
> >>>
> >>> [1] http://code.google.com/p/cxf-log-browser/
> >>> [2] http://cxf-log-browser.blogspot.com/
> >>>
> >>> Best regards,
> >>> Tomasz Oponowicz
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org
> >> http://dankulp.com/blog
> >>
> >
> >
> >
> > --
> > Pozdrawiam,
> > Tomasz Oponowicz
> >
>
>
>
> --
> Best regards,
> Tomasz Oponowicz
>

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi,

I've just committed basic version of logbrowser [1] (described by my proposal).

I also created sample application [2] for easy testing all parts of
the project.
However it's more or less what user have to do to integrate logbrowser
into his application.
Detailed description, how to run sample application, is here [3].

I'm staring work on [4] and [5] (i.e. refactoring, clean up and
writing documentation)
and I'm going to finished those tasks before mid-term evaluations
deadline (i.e. 16.07.2010).

Next I will add optional features [6].

[1] http://svn.apache.org/viewvc?rev=960895&view=rev
[2] ./distribution/src/main/release/samples/logbrowser
[3] ./distribution/src/main/release/samples/logbrowser/README.txt
[4] https://issues.apache.org/jira/browse/CXF-2881
[5] https://issues.apache.org/jira/browse/CXF-2882
[6] https://issues.apache.org/jira/browse/CXF-2883

On Mon, Jun 21, 2010 at 6:55 PM, Tomasz Oponowicz
<to...@gmail.com> wrote:
> Hi,
>
> I've just commit changes at repository [1]. Changes from last version:
>
> - Created Maven project structure;
> - Configured 'maven-gwt-plugin' for automatic execute GWT compiler (to
> convert Java to JavaScript);
> - Added draft implementation of 'BootstrapStorage';
> - Create sample configuration of 'AtomPullServer';
> - Added support for HTTP basic authentication (temporary solution, at
> the end I will replace it with UsernameToken);
> - Added support for JSON web service (client-side - in GWT);
> - Added support for XML web service (client-side - in GWT);
> - Removed GWT-RPC mock web services;
>
> Additionally you can easily run application by downloading source code and type:
>
> $ mvn gwt:run
>
> Authentication details:
>
> username: "admin"
> password:"admin";
>
> It'll start in debug mode - it's much more slower than production mode.
>
> At the moment I'm working to move all source code to Apache CXF sandbox.
>
> [1] svn checkout http://cxf-log-browser.googlecode.com/svn/trunk/
> cxf-log-browser-read-only
>
> On Fri, Jun 18, 2010 at 3:29 PM, Daniel Kulp <dk...@apache.org> wrote:
>> On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
>>> Hi,
>>>
>>> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
>>> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
>>> >> Just for the record, Tomasz's project is also going well....
>>> >
>>> >Well, for the record, I haven't seen anything on the dev list about it
>>> >yet. Thus, from CXF/Apache's point of view, it's not going well.
>>> >Definitely encourage him to get involved here and not send you anything
>>> >off list.
>>>
>>> I have created project site and blog, few weeks ago.
>>> Sorry that I didn't announce about it at mailing list.
>>>
>>> I will store documentation and source code on Google Code Project [1].
>>> Additionally I will announce important events and changes through blog
>>> [2], which I created for this occasion.
>>
>> One of the aspects of GSoC, and in particular Apache's involvement in it, that
>> is often missed is teaching the students how the community works.   It's not
>> supposed to be "just do this coding project".    For Apache, it's also getting
>> the student involved in the community and keeping the entire community up to
>> date with what is happening.
>>
>> I would strongly suggest that any "import events" and any questions and stuff
>> get posted here on the dev list.   You can add it to the blog as well, but
>> make sure they appear on the dev list.
>>
>> There is a saying in Apache:  "if it didn't happen on the dev list, it didn't
>> happen".
>>
>> Dan
>>
>>
>>
>>
>>> Currently repository [1] contain draft of all features (on my roadmap
>>> it's milestone 1).
>>> There is also "Software Requirements Specification" document
>>> and  "Software Design Description" document. At the moment I'm working to
>>> fix and refactor source code.
>>>
>>> When I finish I will move all source code to CXF sandbox.
>>>
>>> Once again sorry for my misunderstanding.
>>>
>>> [1] http://code.google.com/p/cxf-log-browser/
>>> [2] http://cxf-log-browser.blogspot.com/
>>>
>>> Best regards,
>>> Tomasz Oponowicz
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org
>> http://dankulp.com/blog
>>
>
>
>
> --
> Pozdrawiam,
> Tomasz Oponowicz
>



-- 
Best regards,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Tomasz Oponowicz <to...@gmail.com>.

Hi,

I've just commit changes at repository [1]. Changes from last version:

- Created Maven project structure;
- Configured 'maven-gwt-plugin' for automatic execute GWT compiler (to
convert Java to JavaScript);
- Added draft implementation of 'BootstrapStorage';
- Create sample configuration of 'AtomPullServer';
- Added support for HTTP basic authentication (temporary solution, at
the end I will replace it with UsernameToken);
- Added support for JSON web service (client-side - in GWT);
- Added support for XML web service (client-side - in GWT);
- Removed GWT-RPC mock web services;

Additionally you can easily run application by downloading source code and type:

$ mvn gwt:run

Authentication details:

username: "admin"
password:"admin";

It'll start in debug mode - it's much more slower than production mode.

At the moment I'm working to move all source code to Apache CXF sandbox.

[1] svn checkout http://cxf-log-browser.googlecode.com/svn/trunk/
cxf-log-browser-read-only

On Fri, Jun 18, 2010 at 3:29 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
>> Hi,
>>
>> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
>> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
>> >> Just for the record, Tomasz's project is also going well....
>> >
>> >Well, for the record, I haven't seen anything on the dev list about it
>> >yet. Thus, from CXF/Apache's point of view, it's not going well.
>> >Definitely encourage him to get involved here and not send you anything
>> >off list.
>>
>> I have created project site and blog, few weeks ago.
>> Sorry that I didn't announce about it at mailing list.
>>
>> I will store documentation and source code on Google Code Project [1].
>> Additionally I will announce important events and changes through blog
>> [2], which I created for this occasion.
>
> One of the aspects of GSoC, and in particular Apache's involvement in it, that
> is often missed is teaching the students how the community works.   It's not
> supposed to be "just do this coding project".    For Apache, it's also getting
> the student involved in the community and keeping the entire community up to
> date with what is happening.
>
> I would strongly suggest that any "import events" and any questions and stuff
> get posted here on the dev list.   You can add it to the blog as well, but
> make sure they appear on the dev list.
>
> There is a saying in Apache:  "if it didn't happen on the dev list, it didn't
> happen".
>
> Dan
>
>
>
>
>> Currently repository [1] contain draft of all features (on my roadmap
>> it's milestone 1).
>> There is also "Software Requirements Specification" document
>> and  "Software Design Description" document. At the moment I'm working to
>> fix and refactor source code.
>>
>> When I finish I will move all source code to CXF sandbox.
>>
>> Once again sorry for my misunderstanding.
>>
>> [1] http://code.google.com/p/cxf-log-browser/
>> [2] http://cxf-log-browser.blogspot.com/
>>
>> Best regards,
>> Tomasz Oponowicz
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>



-- 
Pozdrawiam,
Tomasz Oponowicz

Re: [GSOC] Simple and lightweight HTML-based browser for surveying Apache CXF logs

Posted by Daniel Kulp <dk...@apache.org>.

On Thursday 17 June 2010 5:15:24 pm Tomasz Oponowicz wrote:
> Hi,
> 
> On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp <dk...@apache.org> wrote:
> > On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
> >> Just for the record, Tomasz's project is also going well....
> >
> >Well, for the record, I haven't seen anything on the dev list about it
> >yet. Thus, from CXF/Apache's point of view, it's not going well.  
> >Definitely encourage him to get involved here and not send you anything
> >off list.
> 
> I have created project site and blog, few weeks ago.
> Sorry that I didn't announce about it at mailing list.
> 
> I will store documentation and source code on Google Code Project [1].
> Additionally I will announce important events and changes through blog
> [2], which I created for this occasion.

One of the aspects of GSoC, and in particular Apache's involvement in it, that 
is often missed is teaching the students how the community works.   It's not 
supposed to be "just do this coding project".    For Apache, it's also getting 
the student involved in the community and keeping the entire community up to 
date with what is happening.   

I would strongly suggest that any "import events" and any questions and stuff 
get posted here on the dev list.   You can add it to the blog as well, but 
make sure they appear on the dev list.   

There is a saying in Apache:  "if it didn't happen on the dev list, it didn't 
happen".

Dan

> Currently repository [1] contain draft of all features (on my roadmap
> it's milestone 1).
> There is also "Software Requirements Specification" document
> and  "Software Design Description" document. At the moment I'm working to
> fix and refactor source code.
> 
> When I finish I will move all source code to CXF sandbox.
> 
> Once again sorry for my misunderstanding.
> 
> [1] http://code.google.com/p/cxf-log-browser/
> [2] http://cxf-log-browser.blogspot.com/
> 
> Best regards,
> Tomasz Oponowicz

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog