[jira] Created: (FOR-770) Locationmaplogs should show which sitemap the request is coming from

Locationmaplogs should show which sitemap the request is coming from
--------------------------------------------------------------------

         Key: FOR-770
         URL: http://issues.apache.org/jira/browse/FOR-770
     Project: Forrest
        Type: Improvement
  Components: Locationmap  
    Versions: 0.8-dev    
    Reporter: Ross Gardler
     Fix For: 0.8-dev


With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.

This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "proect.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap

If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:

"Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"



--
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

     [ http://issues.apache.org/jira/browse/FOR-770?page=all ]

Tim Williams updated FOR-770:
-----------------------------

    Fix Version: 0.9
                     (was: 0.8-dev)

Delay the enhancement until the next release.

> Locationmaplogs should show which sitemap the request is coming from
> --------------------------------------------------------------------
>
>          Key: FOR-770
>          URL: http://issues.apache.org/jira/browse/FOR-770
>      Project: Forrest
>         Type: Improvement

>   Components: Locationmap
>     Versions: 0.8-dev
>     Reporter: Ross Gardler
>      Fix For: 0.9

>
> With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.
> This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "proect.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap
> If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:
> "Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"

--
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

     [ https://issues.apache.org/jira/browse/FOR-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-770:
-------------------------------

          Description:
With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap, exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.

This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "project.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap

If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:

"Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"



  was:
With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.

This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "proect.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap

If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:

"Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"



    Affects Version/s: 0.9-dev
              Summary: Locationmap logs should show which sitemap the request is coming from  (was: Locationmaplogs should show which sitemap the request is coming from)

Edited description which had a confusing typo. Set Fix-version to 0.9-dev

> Locationmap logs should show which sitemap the request is coming from
> ---------------------------------------------------------------------
>
>                 Key: FOR-770
>                 URL: https://issues.apache.org/jira/browse/FOR-770
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Locationmap
>    Affects Versions: 0.8, 0.9-dev
>            Reporter: Ross Gardler
>             Fix For: 0.9-dev
>
>
> With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap, exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.
> This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "project.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap
> If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:
> "Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"

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

    [ https://issues.apache.org/jira/browse/FOR-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573232#action_12573232 ]

crossley edited comment on FOR-770 at 2/28/08 10:12 PM:
--------------------------------------------------------------

Edited description which had a confusing typo (changed "proect.foo" to "project.foo"). Ross, please say if this was intentional.


      was (Author: crossley):
    Edited description which had a confusing typo. Set Fix-version to 0.9-dev
 

> Locationmap logs should show which sitemap the request is coming from
> ---------------------------------------------------------------------
>
>                 Key: FOR-770
>                 URL: https://issues.apache.org/jira/browse/FOR-770
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Locationmap
>    Affects Versions: 0.8, 0.9-dev
>            Reporter: Ross Gardler
>             Fix For: 0.9-dev
>
>
> With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap, exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.
> This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "project.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap
> If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:
> "Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"

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

    [ https://issues.apache.org/jira/browse/FOR-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775256#action_12775256 ]

Tim Williams commented on FOR-770:
----------------------------------

I'm not sure exactly where to start on this as I can't find any useful context in the model map passed in.  So, I've asked for help...

http://old.nabble.com/InputModule-assistance-to26277348.html

--tim

> Locationmap logs should show which sitemap the request is coming from
> ---------------------------------------------------------------------
>
>                 Key: FOR-770
>                 URL: https://issues.apache.org/jira/browse/FOR-770
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Locationmap
>    Affects Versions: 0.8, 0.9-dev
>            Reporter: Ross Gardler
>             Fix For: 0.9-dev
>
>
> With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap, exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.
> This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "project.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap
> If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:
> "Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"

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

     [ https://issues.apache.org/jira/browse/FOR-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-770:
-----------------------------

    Fix Version/s:     (was: 0.9-dev)
                   0.10

Not going to happen for this release, pushing to .10.  

> Locationmap logs should show which sitemap the request is coming from
> ---------------------------------------------------------------------
>
>                 Key: FOR-770
>                 URL: https://issues.apache.org/jira/browse/FOR-770
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Locationmap
>    Affects Versions: 0.8, 0.9-dev
>            Reporter: Ross Gardler
>             Fix For: 0.10
>
>
> With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap, exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.
> This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "project.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap
> If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:
> "Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"

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