[jira] [Closed] (TAP5-1220) write an introductory text for the main page
[ https://issues.apache.org/jira/browse/TAP5-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Harner closed TAP5-1220. > write an introductory text for the main page > > > Key: TAP5-1220 > URL: https://issues.apache.org/jira/browse/TAP5-1220 > Project: Tapestry 5 > Issue Type: Sub-task >Reporter: Ulrich Stärk > > We need a short and descriptive introductory text for the new main page. -- 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] [Resolved] (TAP5-1220) write an introductory text for the main page
[ https://issues.apache.org/jira/browse/TAP5-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Harner resolved TAP5-1220. -- Resolution: Fixed Done long ago > write an introductory text for the main page > > > Key: TAP5-1220 > URL: https://issues.apache.org/jira/browse/TAP5-1220 > Project: Tapestry 5 > Issue Type: Sub-task >Reporter: Ulrich Stärk > > We need a short and descriptive introductory text for the new main page. -- 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-1836) "LocalhostOnly" WhitelistAnalyzer check "0:0:0:0:0:0:0:1%0" ip address instead "0:0:0:0:0:0:0:1"
"LocalhostOnly" WhitelistAnalyzer check "0:0:0:0:0:0:0:1%0" ip address instead "0:0:0:0:0:0:0:1" Key: TAP5-1836 URL: https://issues.apache.org/jira/browse/TAP5-1836 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.1 Reporter: Mihail Slobodyanuk "LocalhostOnly" WhitelistAnalyzer check "0:0:0:0:0:0:0:1%0" ip address but my request object return "0:0:0:0:0:0:0:1" and pages not whitelisted on localhost -- 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] [Commented] (TAP5-1834) Warn user or disallow zone with randomly generated id
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194782#comment-13194782 ] Thiago H. de Paula Figueiredo commented on TAP5-1834: - On Fri, 27 Jan 2012 11:32:36 -0200, Denis Stepanov Just provide a client id and Tapestry won't change it. I agree that the documentation should warn about components without developer-provided ids inside zones. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br > Warn user or disallow zone with randomly generated id > - > > Key: TAP5-1834 > URL: https://issues.apache.org/jira/browse/TAP5-1834 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.3, 5.2.5 >Reporter: Denis Stepanov > > Zone with an id generated randomly(ajax request) is useless and confusing > developers, is such case there should be a warning or even an exception. > TAP5-1746 > http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html -- 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] [Commented] (TAP5-1834) Warn user or disallow zone with randomly generated id
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194703#comment-13194703 ] Denis Stepanov commented on TAP5-1834: -- You have only explained why there are random ids, I'm not saying there are bad just in this case a zone with a random id is useless. There is only one way how to use random id zone is to extract its id after rendering and honestly I don't think is the right way. Most developers will not understand why a zone inside a zone doesn't work without knowing all nuances, some kind of warning or even error which will tell to provide explicit id whould be nice. On 27.1.2012, at 13:32, Thiago H. de Paula Figueiredo wrote: > Warn user or disallow zone with randomly generated id > - > > Key: TAP5-1834 > URL: https://issues.apache.org/jira/browse/TAP5-1834 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.3, 5.2.5 >Reporter: Denis Stepanov > > Zone with an id generated randomly(ajax request) is useless and confusing > developers, is such case there should be a warning or even an exception. > TAP5-1746 > http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html -- 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] [Commented] (TAP5-1834) Warn user or disallow zone with randomly generated id
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194664#comment-13194664 ] Thiago H. de Paula Figueiredo commented on TAP5-1834: - On Fri, 27 Jan 2012 07:56:41 -0200, Denis Stepanov (Created) (JIRA) It isn't (I've explained it in this thread: http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html), otherwise Tapestry committers wouldn't care to implement. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br > Warn user or disallow zone with randomly generated id > - > > Key: TAP5-1834 > URL: https://issues.apache.org/jira/browse/TAP5-1834 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-core >Affects Versions: 5.3, 5.2.5 >Reporter: Denis Stepanov > > Zone with an id generated randomly(ajax request) is useless and confusing > developers, is such case there should be a warning or even an exception. > TAP5-1746 > http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html -- 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] [Commented] (TAP5-1522) Tapestry-spring does not support using Spring JavaConfig (AnnotationConfigWebApplicationContext)
[ https://issues.apache.org/jira/browse/TAP5-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194615#comment-13194615 ] Markus Schmitt commented on TAP5-1522: -- So the issue is still not on the roadmap of 5.4... In my opinion it will be a great improvement, concerning java bases config, having the issue into a release candidate. > Tapestry-spring does not support using Spring JavaConfig > (AnnotationConfigWebApplicationContext) > > > Key: TAP5-1522 > URL: https://issues.apache.org/jira/browse/TAP5-1522 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-spring >Affects Versions: 5.2 >Reporter: DI Florian Hackenberger > Attachments: java-config-support.patch > > > Tapestry-spring currently requires that the context class extends > TapestryApplicationContext. In order to use JavaConfig support (without going > through an intermediate spring xml file), you would have to use > AnnotationConfigWebApplicationContext as a base class and add the tapestry > features on top (like TapestryApplicationContext does). Unfortunately that's > impossible, as TapestryApplicationContext is not an interface. -- 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-1835) Logical page name strip order
Logical page name strip order - Key: TAP5-1835 URL: https://issues.apache.org/jira/browse/TAP5-1835 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.2.5 Reporter: Vladimir Velikiy I have page in library with prefix requests. Its logical path is: requests/requeststatus/RequestStatusView. After stripping logical page name by ComponentClassResolver I see the following result: requests/requeststatus/tatusView. This is because the terms of the path prefix are processed in direct order: requests, requeststatus. It would be more correct way to handle the terms in reverse order: requeststatus, request, which will give more correct result: requests/requeststatus/View. The last term in the path prefix has a close value to the name of the page than the previous. -- 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-1834) Warn user or disallow zone with randomly generated id
Warn user or disallow zone with randomly generated id - Key: TAP5-1834 URL: https://issues.apache.org/jira/browse/TAP5-1834 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.2.5, 5.3 Reporter: Denis Stepanov Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception. TAP5-1746 http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html -- 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
svn commit: r1236574 - /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/services/OperationAdvisorImpl.java
Author: uli
Date: Fri Jan 27 08:20:05 2012
New Revision: 1236574
URL: http://svn.apache.org/viewvc?rev=1236574&view=rev
Log:
nothing to override here...
Modified:
tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/services/OperationAdvisorImpl.java
Modified:
tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/services/OperationAdvisorImpl.java
URL:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/services/OperationAdvisorImpl.java?rev=1236574&r1=1236573&r2=1236574&view=diff
==
---
tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/services/OperationAdvisorImpl.java
(original)
+++
tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/services/OperationAdvisorImpl.java
Fri Jan 27 08:20:05 2012
@@ -39,7 +39,6 @@ public class OperationAdvisorImpl implem
{
return new Runnable()
{
-@Override
public void run()
{
invocation.proceed();
@@ -56,7 +55,6 @@ public class OperationAdvisorImpl implem
this.description = description;
}
-@Override
public void advise(MethodInvocation invocation)
{
tracker.run(description, toRunnable(invocation));
@@ -72,7 +70,6 @@ public class OperationAdvisorImpl implem
this.format = format;
}
-@Override
public void advise(MethodInvocation invocation)
{
Object[] parameters = extractParameters(invocation);
@@ -97,7 +94,6 @@ public class OperationAdvisorImpl implem
}
}
-@Override
public void addOperationAdvice(MethodAdviceReceiver receiver)
{
for (Method m : receiver.getInterface().getMethods())
@@ -114,7 +110,6 @@ public class OperationAdvisorImpl implem
}
}
-@Override
public MethodAdvice createAdvice(String description)
{
assert InternalUtils.isNonBlank(description);
