[ http://issues.apache.org/jira/browse/TAPESTRY-946?page=all ]
Jesse Kuhnert resolved TAPESTRY-946.
------------------------------------
Resolution: Fixed
> Log message for synthesizing application file should be a higher priority
> -------------------------------------------------------------------------
>
> Key: TAPESTRY-946
> URL: http://issues.apache.org/jira/browse/TAPESTRY-946
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0.2
> Environment: All
> Reporter: Brian K. Wallace
> Priority: Minor
> Fix For: 4.1.1
>
>
> Currently, if an application file isn't found, the following DEBUG message is
> printed:
> Could not find an application specification for application servlet
> <servlet-name>
> Considering the ramifications of not finding an application file, this
> message should be upgraded to WARN and changed to the following so users
> won't get too concerned if they truly don't have one:
> Could not find an application specification for application servlet
> <servlet-name>. Continuing using defaults.
> The current DEBUG level leaves users with either a tremendous amount of
> messages to sift through, or no indication of a very important aspect of
> their runtime configuration when the usual problem is a naming discrepancy
> between the servlet name and the application file name.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
