[jira] [Created] (TAP5-2559) Allow modification of Tomcat instance in TomcatRunner
quurks created TAP5-2559: Summary: Allow modification of Tomcat instance in TomcatRunner Key: TAP5-2559 URL: https://issues.apache.org/jira/browse/TAP5-2559 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-test Affects Versions: 5.5.0 Reporter: quurks Priority: Minor It would be nice to be able to configure the Tomcat instance in TomcatRunner before its started, basically adapting the API from JettyRunner: - a seperate no-args constructor to construct the instance - a configure method serving the purpose of the old constructor - a seperate start method - a getter for the Tomcat instance This would allow for modification while maintaining backwards-compatibility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAP5-2466) Include tapestry-ioc-jcache = Construction of service 'AssetObjectProvider' has failed due to recursion
[
https://issues.apache.org/jira/browse/TAP5-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
quurks updated TAP5-2466:
-
Attachment: jetty-output.txt
Operation trace+ stacktrace
Include tapestry-ioc-jcache = Construction of service 'AssetObjectProvider'
has failed due to recursion
Key: TAP5-2466
URL: https://issues.apache.org/jira/browse/TAP5-2466
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-ioc
Affects Versions: 5.4
Reporter: quurks
Attachments: jetty-output.txt
Reproduce:
Add tapestry-ioc-jcache to a tapestry project
Expected:
Application still works
Actual:
Application fails to start:
Construction of service 'AssetObjectProvider' has failed due to recursion:
the service depends on itself in some way. Please check
org.apache.tapestry5.internal.services.AssetObjectProvider(AssetSource,
TypeCoercer, SymbolSource) (at AssetObjectProvider.java:45) via
org.apache.tapestry5.modules.TapestryModule.bind(ServiceBinder) (at
TapestryModule.java:311) for references to another service that is itself
dependent on service 'AssetObjectProvider'.
Probably caused by @Match('*') in JCacheModule. Solution could be something
like
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Service-Advisors-recursive-problem-td5720755.html#a5720781
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TAP5-2466) Include tapestry-ioc-jcache = Construction of service 'AssetObjectProvider' has failed due to recursion
quurks created TAP5-2466:
Summary: Include tapestry-ioc-jcache = Construction of service
'AssetObjectProvider' has failed due to recursion
Key: TAP5-2466
URL: https://issues.apache.org/jira/browse/TAP5-2466
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-ioc
Affects Versions: 5.4
Reporter: quurks
Reproduce:
Add tapestry-ioc-jcache to a tapestry project
Expected:
Application still works
Actual:
Application fails to start:
Construction of service 'AssetObjectProvider' has failed due to recursion: the
service depends on itself in some way. Please check
org.apache.tapestry5.internal.services.AssetObjectProvider(AssetSource,
TypeCoercer, SymbolSource) (at AssetObjectProvider.java:45) via
org.apache.tapestry5.modules.TapestryModule.bind(ServiceBinder) (at
TapestryModule.java:311) for references to another service that is itself
dependent on service 'AssetObjectProvider'.
Probably caused by @Match('*') in JCacheModule. Solution could be something
like
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Service-Advisors-recursive-problem-td5720755.html#a5720781
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TAP5-2451) tapestry-ioc-jcache tests arent run
[ https://issues.apache.org/jira/browse/TAP5-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14328838#comment-14328838 ] quurks commented on TAP5-2451: -- The tests still dont seem to run: tapestry-ioc-jcache:compileJavawarning: org/jsr107/ri/annotations/InterceptorType.class(org/jsr107/ri/annotations:InterceptorType.class): major version 51 is newer than 50, the highest major version supported by this compiler. It is recommended that the compiler be upgraded. tapestry-ioc-jcache tests arent run --- Key: TAP5-2451 URL: https://issues.apache.org/jira/browse/TAP5-2451 Project: Tapestry 5 Issue Type: Bug Components: tapestry-ioc Affects Versions: 5.4 Reporter: quurks Assignee: Jochen Kemnade tapestry-ioc-jcache tests dont seem to run. There is nothing for jcache in https://builds.apache.org/job/tapestry-trunk-freestyle/lastStableBuild/testReport/ Probably caused because the tests are junit-based, but there is no useJUnit() in tapesty-ioc-jcache/build.gradle If I add useJunit() all tests seem to get excluded by AbstractTestExcluder, but that might be a configuration problem on my end. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TAP5-2412) Expose Exception - String conversion from ExceptionReporterImpl
[ https://issues.apache.org/jira/browse/TAP5-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317137#comment-14317137 ] quurks commented on TAP5-2412: -- Seems to be resolved by ede56bc6fb85694b969a1ffd348960e72a04f936 Expose Exception - String conversion from ExceptionReporterImpl Key: TAP5-2412 URL: https://issues.apache.org/jira/browse/TAP5-2412 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.4 Reporter: quurks It would be nice to have some way to convert an exception in a String representation (not just a Stacktrace) for i.e. email warnings. This is already done in ExceptionReporterImpl, but in private methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TAP5-2412) Expose Exception - String conversion from ExceptionReporterImpl
[ https://issues.apache.org/jira/browse/TAP5-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] quurks closed TAP5-2412. Expose Exception - String conversion from ExceptionReporterImpl Key: TAP5-2412 URL: https://issues.apache.org/jira/browse/TAP5-2412 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.4 Reporter: quurks Fix For: 5.4 It would be nice to have some way to convert an exception in a String representation (not just a Stacktrace) for i.e. email warnings. This is already done in ExceptionReporterImpl, but in private methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TAP5-2412) Expose Exception - String conversion from ExceptionReporterImpl
[ https://issues.apache.org/jira/browse/TAP5-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] quurks resolved TAP5-2412. -- Resolution: Fixed Fix Version/s: 5.4 Expose Exception - String conversion from ExceptionReporterImpl Key: TAP5-2412 URL: https://issues.apache.org/jira/browse/TAP5-2412 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.4 Reporter: quurks Fix For: 5.4 It would be nice to have some way to convert an exception in a String representation (not just a Stacktrace) for i.e. email warnings. This is already done in ExceptionReporterImpl, but in private methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TAP5-2451) tapestry-ioc-jcache tests arent run
quurks created TAP5-2451: Summary: tapestry-ioc-jcache tests arent run Key: TAP5-2451 URL: https://issues.apache.org/jira/browse/TAP5-2451 Project: Tapestry 5 Issue Type: Bug Components: tapestry-ioc Affects Versions: 5.4 Reporter: quurks tapestry-ioc-jcache tests dont seem to run. There is nothing for jcache in https://builds.apache.org/job/tapestry-trunk-freestyle/lastStableBuild/testReport/ Probably caused because the tests are junit-based, but there is no useJUnit() in tapesty-ioc-jcache/build.gradle If I add useJunit() all tests seem to get excluded by AbstractTestExcluder, but that might be a configuration problem on my end. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TAP5-2449) PropertyConduitSource cant see Java 8 default methods
quurks created TAP5-2449:
Summary: PropertyConduitSource cant see Java 8 default methods
Key: TAP5-2449
URL: https://issues.apache.org/jira/browse/TAP5-2449
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: quurks
*Stets to reproduce:*
Class with
{code}
public class TestDefaultMethod {
@Property private TestData testData = new TestData();
public static interface TestInterface {
public default String getTestString() {
return Alpha;
}
}
public static class TestData implements TestInterface {
}
}
{code}
Template with
{code}
${testData.testString}
{code}
*Expected*:
Alpha is put in the website
*Actual*:
Exception type: org.apache.tapestry5.ioc.util.UnknownValueException
Message: Class com.example.pages.TestDefaultMethod$TestData does not
contain a property (or public field) named 'testString'.
availableValues: AvailableValues\[Properties (and public fields): class]
It works with
{code}
${testData.getTestString()}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TAP5-2436) Dont throw an IllgealArgumentException on illegal chars in the url
quurks created TAP5-2436: Summary: Dont throw an IllgealArgumentException on illegal chars in the url Key: TAP5-2436 URL: https://issues.apache.org/jira/browse/TAP5-2436 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.4 Reporter: quurks A few days ago some tool tried to find vulnerabilites by checking urls like /pageid=9' . This lead to dozens of exception reports like Exception type: java.lang.IllegalArgumentException Message: Input string 'pageid=9'' is not valid; the character '=' at position 7 is not valid. This should either be a custom exception type, so it can be handled without parsing the IllegalArgumentException message or it should be a 400 - Bad request, which would also allow for a custom error page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TAP5-2412) Expose Exception - String conversion from ExceptionReporterImpl
quurks created TAP5-2412: Summary: Expose Exception - String conversion from ExceptionReporterImpl Key: TAP5-2412 URL: https://issues.apache.org/jira/browse/TAP5-2412 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.4 Reporter: quurks It would be nice to have some way to convert an exception in a String representation (not just a Stacktrace) for i.e. email warnings. This is already done in ExceptionReporterImpl, but in private methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TAP5-2404) Allow modifying AJAX requests before sending
quurks created TAP5-2404: Summary: Allow modifying AJAX requests before sending Key: TAP5-2404 URL: https://issues.apache.org/jira/browse/TAP5-2404 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.4 Reporter: quurks I'm trying to upload files via t5/core/ajax to a component event. For this its required to modify the request before its send in t5/core/dom (processData=false, set custom headers) Possible solution: Allow setting of beforeSend callback in jQuery (onCreate or onUninitialized seems to be the Prototype equivalent) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAP5-2404) Allow modifying AJAX requests before sending
[ https://issues.apache.org/jira/browse/TAP5-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] quurks updated TAP5-2404: - Description: I'm trying to upload files via t5/core/ajax to a component event. For this its required to modify the request before its send in t5/core/dom (processData=false, set custom headers) -Possible solution: Allow setting of beforeSend callback in jQuery (onCreate or onUninitialized seems to be the Prototype equivalent)- Its not possible to set everything in beforeSend, the raw xhr request cant be modified (required to add progress listener). To allow this its required to be able to modify the object passed to $.ajax directly, maybe via options.rawOptions which is added to the original $.ajax options object.. was: I'm trying to upload files via t5/core/ajax to a component event. For this its required to modify the request before its send in t5/core/dom (processData=false, set custom headers) Possible solution: Allow setting of beforeSend callback in jQuery (onCreate or onUninitialized seems to be the Prototype equivalent) Allow modifying AJAX requests before sending Key: TAP5-2404 URL: https://issues.apache.org/jira/browse/TAP5-2404 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.4 Reporter: quurks I'm trying to upload files via t5/core/ajax to a component event. For this its required to modify the request before its send in t5/core/dom (processData=false, set custom headers) -Possible solution: Allow setting of beforeSend callback in jQuery (onCreate or onUninitialized seems to be the Prototype equivalent)- Its not possible to set everything in beforeSend, the raw xhr request cant be modified (required to add progress listener). To allow this its required to be able to modify the object passed to $.ajax directly, maybe via options.rawOptions which is added to the original $.ajax options object.. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TAP5-2394) onUploadException doesn't work in Components
[ https://issues.apache.org/jira/browse/TAP5-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169584#comment-14169584 ] quurks commented on TAP5-2394: -- Yes, but is it intended behavior? onUploadException doesn't work in Components - Key: TAP5-2394 URL: https://issues.apache.org/jira/browse/TAP5-2394 Project: Tapestry 5 Issue Type: Bug Components: tapestry-upload Affects Versions: 5.4 Reporter: quurks onUploadException doesn't work in Components; it just is not triggered. Copy Pasting the method in the containing page works fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TAP5-2394) onUploadException doesn't work in Components
quurks created TAP5-2394: Summary: onUploadException doesn't work in Components Key: TAP5-2394 URL: https://issues.apache.org/jira/browse/TAP5-2394 Project: Tapestry 5 Issue Type: Bug Components: tapestry-upload Affects Versions: 5.4 Reporter: quurks onUploadException doesn't work in Components; it just is not triggered. Copy Pasting the method in the containing page works fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAP5-2394) onUploadException doesn't work in Components
[ https://issues.apache.org/jira/browse/TAP5-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] quurks updated TAP5-2394: - Labels: (was: patch) onUploadException doesn't work in Components - Key: TAP5-2394 URL: https://issues.apache.org/jira/browse/TAP5-2394 Project: Tapestry 5 Issue Type: Bug Components: tapestry-upload Affects Versions: 5.4 Reporter: quurks onUploadException doesn't work in Components; it just is not triggered. Copy Pasting the method in the containing page works fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TAP5-2388) Impossible to show error page after component id not found
[ https://issues.apache.org/jira/browse/TAP5-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14140395#comment-14140395 ] quurks commented on TAP5-2388: -- Im fine with a 404. My Problem: I cant display it because the 404 is completly blank. The unkown component id triggers a 404, which should trigger the error404 page, but it is not displayed because the request attribute indicating an invalid component id is still set. Impossible to show error page after component id not found -- Key: TAP5-2388 URL: https://issues.apache.org/jira/browse/TAP5-2388 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.4 Reporter: quurks *Steps to reproduce:* Use Quickstart template for 5.4-beta-22 (Using the error page recipe) Enable Production mode (dev has no problem) Open an url with a unkown component id (/index.html) *Expected:* See the error page with information /index.html was not found *Actual:* Blank Page with 404 Status *Possible Reason:* ProductionModeUnknownComponentFilter#handleComponentEvent doenst find html - request.setAttribute(InternalConstants.REFERENCED_COMPONENT_NOT_FOUND, true) - ComponentEventDispatcher#dispatch returns false - Request for Error404 by Container - PageRenderDispatcher#dispatch checks for REFERENCED_COMPONENT_NOT_FOUND and its still there- returns false - error404 is not displayed Tomcat version: 7.0.55 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAP5-2388) Impossible to show error page after component id not found
[ https://issues.apache.org/jira/browse/TAP5-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] quurks updated TAP5-2388: - Description: *Steps to reproduce:* Use Quickstart template for 5.4-beta-22 (Using the error page recipe) Enable Production mode (dev has no problem) Open an url with a unkown component id (/index.html) *Expected:* Error404 page with information /index.html was not found *Actual:* *Blank* Page with 404 Status *Possible Reason:* ProductionModeUnknownComponentFilter#handleComponentEvent doenst find html - request.setAttribute(InternalConstants.REFERENCED_COMPONENT_NOT_FOUND, true) - ComponentEventDispatcher#dispatch returns false - Request for Error404 by Container - PageRenderDispatcher#dispatch checks for REFERENCED_COMPONENT_NOT_FOUND and its still there- returns false - error404 is not displayed Tomcat version: 7.0.55 was: *Steps to reproduce:* Use Quickstart template for 5.4-beta-22 (Using the error page recipe) Enable Production mode (dev has no problem) Open an url with a unkown component id (/index.html) *Expected:* See the error page with information /index.html was not found *Actual:* Blank Page with 404 Status *Possible Reason:* ProductionModeUnknownComponentFilter#handleComponentEvent doenst find html - request.setAttribute(InternalConstants.REFERENCED_COMPONENT_NOT_FOUND, true) - ComponentEventDispatcher#dispatch returns false - Request for Error404 by Container - PageRenderDispatcher#dispatch checks for REFERENCED_COMPONENT_NOT_FOUND and its still there- returns false - error404 is not displayed Tomcat version: 7.0.55 Impossible to show error page after component id not found -- Key: TAP5-2388 URL: https://issues.apache.org/jira/browse/TAP5-2388 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.4 Reporter: quurks *Steps to reproduce:* Use Quickstart template for 5.4-beta-22 (Using the error page recipe) Enable Production mode (dev has no problem) Open an url with a unkown component id (/index.html) *Expected:* Error404 page with information /index.html was not found *Actual:* *Blank* Page with 404 Status *Possible Reason:* ProductionModeUnknownComponentFilter#handleComponentEvent doenst find html - request.setAttribute(InternalConstants.REFERENCED_COMPONENT_NOT_FOUND, true) - ComponentEventDispatcher#dispatch returns false - Request for Error404 by Container - PageRenderDispatcher#dispatch checks for REFERENCED_COMPONENT_NOT_FOUND and its still there- returns false - error404 is not displayed Tomcat version: 7.0.55 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TAP5-2388) Impossible to show error page after component id not found
quurks created TAP5-2388: Summary: Impossible to show error page after component id not found Key: TAP5-2388 URL: https://issues.apache.org/jira/browse/TAP5-2388 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.4 Reporter: quurks *Steps to reproduce:* Use Quickstart template for 5.4-beta-22 (Using the error page recipe) Enable Production mode (dev has no problem) Open an url with a unkown component id (/index.html) *Expected:* See the error page with information /index.html was not found *Actual:* Blank Page with 404 Status *Possible Reason:* ProductionModeUnknownComponentFilter#handleComponentEvent doenst find html - request.setAttribute(InternalConstants.REFERENCED_COMPONENT_NOT_FOUND, true) - ComponentEventDispatcher#dispatch returns false - Request for Error404 by Container - PageRenderDispatcher#dispatch checks for REFERENCED_COMPONENT_NOT_FOUND and its still there- returns false - error404 is not displayed Tomcat version: 7.0.55 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TAP5-2386) UnknownActivationContextCheck breaks ActivationRequestParameter when used with PageActivationContext
quurks created TAP5-2386:
Summary: UnknownActivationContextCheck breaks
ActivationRequestParameter when used with PageActivationContext
Key: TAP5-2386
URL: https://issues.apache.org/jira/browse/TAP5-2386
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: quurks
{code}
@UnknownActivationContextCheck(false|true)
public class TestPage {
@ActivationRequestParameter private String arp;
@PageActivationContext private String pac;
public String getMessage() {
return String.format(ActivationRequestParameter: %s,
PageActivationContext: %s, arp, pac);
}
}
{code}
||Expected||UnknownActivationContextCheck||URL||ActivationRequestParameter||PageActivationContext||
|yes|false|/test/Alpha?arp=Beta|Beta|Alpha|
|yes|true|/test?arp=Beta|Beta|null|
|*no*|true|/test/Alpha?arp=Beta|{color:red}null{color}|Alpha|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TAP5-2386) UnknownActivationContextCheck breaks ActivationRequestParameter when used with PageActivationContext
[
https://issues.apache.org/jira/browse/TAP5-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
quurks updated TAP5-2386:
-
Description:
{code}
@UnknownActivationContextCheck(false|true)
public class TestPage {
@ActivationRequestParameter private String arp;
@PageActivationContext private String pac;
public String getMessage() {
return String.format(ActivationRequestParameter: %s,
PageActivationContext: %s, arp, pac);
}
}
{code}
||Expected
Result?||UnknownActivationContextCheck||URL||ActivationRequestParameter||PageActivationContext||
|yes|false|/test/Alpha?arp=Beta|Beta|Alpha|
|yes|true|/test?arp=Beta|Beta|null|
|*no*|true|/test/Alpha?arp=Beta|{color:red}null{color}|Alpha|
was:
{code}
@UnknownActivationContextCheck(false|true)
public class TestPage {
@ActivationRequestParameter private String arp;
@PageActivationContext private String pac;
public String getMessage() {
return String.format(ActivationRequestParameter: %s,
PageActivationContext: %s, arp, pac);
}
}
{code}
||Expected||UnknownActivationContextCheck||URL||ActivationRequestParameter||PageActivationContext||
|yes|false|/test/Alpha?arp=Beta|Beta|Alpha|
|yes|true|/test?arp=Beta|Beta|null|
|*no*|true|/test/Alpha?arp=Beta|{color:red}null{color}|Alpha|
UnknownActivationContextCheck breaks ActivationRequestParameter when used
with PageActivationContext
Key: TAP5-2386
URL: https://issues.apache.org/jira/browse/TAP5-2386
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.4
Reporter: quurks
{code}
@UnknownActivationContextCheck(false|true)
public class TestPage {
@ActivationRequestParameter private String arp;
@PageActivationContext private String pac;
public String getMessage() {
return String.format(ActivationRequestParameter: %s,
PageActivationContext: %s, arp, pac);
}
}
{code}
||Expected
Result?||UnknownActivationContextCheck||URL||ActivationRequestParameter||PageActivationContext||
|yes|false|/test/Alpha?arp=Beta|Beta|Alpha|
|yes|true|/test?arp=Beta|Beta|null|
|*no*|true|/test/Alpha?arp=Beta|{color:red}null{color}|Alpha|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TAP5-1927) PeriodicExecutor drops exceptions without any notice.
[
https://issues.apache.org/jira/browse/TAP5-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271296#comment-13271296
]
quurks commented on TAP5-1927:
--
I understand why the exception is caught. But a log entry would be nice. Maybe
only a trace.
PeriodicExecutor drops exceptions without any notice.
-
Key: TAP5-1927
URL: https://issues.apache.org/jira/browse/TAP5-1927
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-ioc
Affects Versions: 5.3
Reporter: quurks
Assignee: Howard M. Lewis Ship
PeriodicExecutorImpl:176-185
try
{
runnableJob.run();
} finally
{
cleanupAfterExecution();
}
That means every occuring exception is simply skipped. It would be nice if it
was logged.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TAP5-1927) PeriodicExecutor drops exceptions without any notice.
quurks created TAP5-1927:
Summary: PeriodicExecutor drops exceptions without any notice.
Key: TAP5-1927
URL: https://issues.apache.org/jira/browse/TAP5-1927
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-ioc
Affects Versions: 5.3
Reporter: quurks
PeriodicExecutorImpl:176-185
try
{
runnableJob.run();
} finally
{
cleanupAfterExecution();
}
That means every occuring exception is simply skipped. It would be nice if it
was logged.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
