[ http://issues.apache.org/jira/browse/BEEHIVE-884?page=all ]
     
Nathan Jantz closed BEEHIVE-884:
--------------------------------


This fix has been verified as of svn 239233.  It was verified by removing the 
required tokens {url:path} and  {url:queryString} from a template in the 
beehive-url-template-config.xml file.  Then building and redeploying the 
webapp.  With a log4j.xml in place, the following errors get output to the 
console:

ERROR URLTemplate []: Required token, {url:path}, not found in template: 
http://{url:domain}:{url:port}/?URLTEMPLATE=action&{url:queryString}

ERROR URLTemplate []: Required token, {url:queryString}, not found in template: 
http://{url:domain}:{url:port}/{url:path}?URLTEMPLATE=action&;

But these errors do not prevent the webapp from deploying to Tomcat. as 
expected.  No IllegalStateException is thrown as expected.

Closing issue.

> Change URLTemplate.verify() to log template errors rather than throw 
> IllegalStateException
> ------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-884
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-884
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: v1m1
>     Reporter: Carlin Rogers
>     Assignee: Nathan Jantz
>     Priority: Minor
>      Fix For: V1
>  Attachments: j884-patch.txt
>
> Currently URLTemplate.verify()  throws an IllegalStateException if there's a 
> problem finding a
> required token (or verifying a known token). The exception is not caught, 
> even in the 
> PageFlowContextListener, during the Servlet initialization and other 
> processing of the URL
> template config file. The URLTemplatesFactory logs errors for missing values 
> or names
> etc.
> To be consistent, I'd like to change the URLTemplate.verify() method so that 
> it just logs
> errors, and the remainder of the initialization process can continue on.

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

Reply via email to