You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/07/24 23:00:46 UTC

[jira] Created: (GERONIMO-807) Better handling for system log viewer portlet render requests

Better handling for system log viewer portlet render requests
-------------------------------------------------------------

         Key: GERONIMO-807
         URL: http://issues.apache.org/jira/browse/GERONIMO-807
     Project: Geronimo
        Type: Bug
  Components: management, usability  
    Versions: 1.0-M5    
    Reporter: Aaron Mulder
    Priority: Minor


If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasad Kashyap updated GERONIMO-807:
------------------------------------

    Fix Version/s:     (was: 2.0-M5)
                   2.0
         Assignee: Rakesh Midha

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>                 Key: GERONIMO-807
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-807
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, usability
>    Affects Versions: 1.0-M5
>            Reporter: Aaron Mulder
>            Assignee: Rakesh Midha
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: jira807.patch
>
>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Joe Bohn (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-807?page=comments#action_12332588 ] 

Joe Bohn commented on GERONIMO-807:
-----------------------------------

IMHO the settings should be retained for the session.  Since we exploiting a portal server,  the user expectation regarding these settings  would normally be for the duration of the session.  For anything beyond that a portal user would typically personalize the portlet using edit mode or persist their session (neither of which are currently supported in the Geronimo console).

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>          Key: GERONIMO-807
>          URL: http://issues.apache.org/jira/browse/GERONIMO-807
>      Project: Geronimo
>         Type: Bug
>   Components: usability, console
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.0

>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Barry van Someren (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-807?page=comments#action_12332591 ] 

Barry van Someren commented on GERONIMO-807:
--------------------------------------------

I'm going to assign this one to me and will most likely deliver a patch tonight (it's a small fix)


> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>          Key: GERONIMO-807
>          URL: http://issues.apache.org/jira/browse/GERONIMO-807
>      Project: Geronimo
>         Type: Bug
>   Components: usability, console
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.0

>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-807?page=all ]

Matt Hogstrom updated GERONIMO-807:
-----------------------------------

    Fix Version/s: Wish List
                       (was: 1.2)

It's been a long night...

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>                 Key: GERONIMO-807
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-807
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: usability, console
>    Affects Versions: 1.0-M5
>            Reporter: Aaron Mulder
>            Priority: Minor
>             Fix For: Wish List
>
>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-807?page=all ]

Aaron Mulder updated GERONIMO-807:
----------------------------------

    Fix Version: 1.1
                     (was: 1.0)
      Assign To:     (was: Aaron Mulder)

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>          Key: GERONIMO-807
>          URL: http://issues.apache.org/jira/browse/GERONIMO-807
>      Project: Geronimo
>         Type: Bug
>   Components: usability, console
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.1

>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Rakesh Midha (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rakesh Midha updated GERONIMO-807:
----------------------------------

    Attachment: jira807.patch


Attached is the patch to take care of not only just default values, but also take care of

1. Remember the last values in case of refresh and reload in same session
2. Take care of invalid values
3. Solve the above problem for Log Manager, Web Access logger and derby logger

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>                 Key: GERONIMO-807
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-807
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, usability
>    Affects Versions: 1.0-M5
>            Reporter: Aaron Mulder
>         Assigned To: Rakesh Midha
>            Priority: Minor
>             Fix For: Wish List
>
>         Attachments: jira807.patch
>
>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-807?page=all ]

Dain Sundstrom reassigned GERONIMO-807:
---------------------------------------

    Assign To: Aaron Mulder

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>          Key: GERONIMO-807
>          URL: http://issues.apache.org/jira/browse/GERONIMO-807
>      Project: Geronimo
>         Type: Bug
>   Components: usability, console
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.0

>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Rakesh Midha (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rakesh Midha reassigned GERONIMO-807:
-------------------------------------

    Assignee: Rakesh Midha

Quite long....Let me try to end this night....

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>                 Key: GERONIMO-807
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-807
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, usability
>    Affects Versions: 1.0-M5
>            Reporter: Aaron Mulder
>         Assigned To: Rakesh Midha
>            Priority: Minor
>             Fix For: Wish List
>
>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-807?page=all ]

Aaron Mulder updated GERONIMO-807:
----------------------------------

    Component: console
                   (was: management)

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>          Key: GERONIMO-807
>          URL: http://issues.apache.org/jira/browse/GERONIMO-807
>      Project: Geronimo
>         Type: Bug
>   Components: usability, console
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Priority: Minor

>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Hogstrom closed GERONIMO-807.
----------------------------------

    Resolution: Fixed

Applied patch and tested and it works.  The text for criteria is still wiped out when navigating to different portlets.  Given the longevity of this issue I'm going to close it and open a separate issue to be tracked independently.

Thanks Rakesh!

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>                 Key: GERONIMO-807
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-807
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, usability
>    Affects Versions: 1.0-M5
>            Reporter: Aaron Mulder
>            Assignee: Rakesh Midha
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: jira807.patch
>
>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Barry van Someren (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-807?page=comments#action_12332583 ] 

Barry van Someren commented on GERONIMO-807:
--------------------------------------------

Since I can reproduce this problem, I'm interested in fixing it.
Any objections?

At what level should the settings be retained (during the current session, the lifetime of the application server or even beyond?)


> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>          Key: GERONIMO-807
>          URL: http://issues.apache.org/jira/browse/GERONIMO-807
>      Project: Geronimo
>         Type: Bug
>   Components: usability, console
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.0

>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-807?page=all ]

Aaron Mulder updated GERONIMO-807:
----------------------------------

    Fix Version: 1.0

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>          Key: GERONIMO-807
>          URL: http://issues.apache.org/jira/browse/GERONIMO-807
>      Project: Geronimo
>         Type: Bug
>   Components: usability, console
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Priority: Minor
>      Fix For: 1.0

>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (GERONIMO-807) Better handling for system log viewer portlet render requests

Posted by "Rakesh Midha (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rakesh Midha updated GERONIMO-807:
----------------------------------

       Patch Info: [Patch Available]
    Fix Version/s:     (was: Wish List)
                   2.0-M2
         Assignee:     (was: Rakesh Midha)


Unassigning and marking patch available

Please review and commit

> Better handling for system log viewer portlet render requests
> -------------------------------------------------------------
>
>                 Key: GERONIMO-807
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-807
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, usability
>    Affects Versions: 1.0-M5
>            Reporter: Aaron Mulder
>            Priority: Minor
>             Fix For: 2.0-M2
>
>         Attachments: jira807.patch
>
>
> If you interact with a different portal on the log page, the system log viewer portlet reverts to its default filter settings.  It should instead default to the same values used previously (if there are previous search criteria and if none of the criteria were submitted in the request). See LogViewerPortlet.java:73 or so

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.