tapestry5.4 and PersistenceConstants.FLASH

2013-11-21 Thread Zhou Yongcheng 
Hi All,

I think that the following is a problem(bug) with tapestry5.4 persist
strategy flash.
---
problem description:  two fields with FLASH stratege, one is String,
another is ListString. when i submit form, ListSting works, but String
field disapper. following is the code. please help me solve this
problem.Thanks.
--
public class Persist1 {
 @Property
@Persist(PersistenceConstants.FLASH)
private ListString mails;
 @Property
@Persist(PersistenceConstants.FLASH)
private String username;
 @Property
@Persist(PersistenceConstants.FLASH)
private String address;
 @Property
private String mail;
 @Inject
private Logger log;
 @Log
void setupRender() {
if (!isEmpty()) {
mails.add(xx);
}
}
 @Log
void onSuccess() {
address = yunnan;
if (mails == null) {
mails = new ArrayListString();
mails.add(xxx...@gmail.com);
mails.add(y...@hotmail.com);
}
}
 public boolean isEmpty() {
return (mails == null || mails.size() == 0);
}
}

Persist.tml-
!doctype html
html xmlns:t=http://tapestry.apache.org/schema/tapestry_5_3.xsd;
head
meta charset=UTF-8 /
titlePersistence Test/title
/head
body
div class=container
form class=form-signin t:type=form t:id=inputForm
t:errors /
input type=text t:type=textfield t:id=username
class=form-control placeholder=please enter your username / br /
your address is : ${address}
br /


button class=btn btn-lg btn-primary btn-block
type=submitSign in/button
/form
t:if test=!empty
   t:loop source=mails value=mail
   ${mail}
   /t:loop
/t:if
/div
div class=vimiumReset vimiumHUD style=right: 150px; opacity: 0;
display: none;/div
/body
/html

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

2013-11-21 Thread Kalle Korhonen 
At a first glance, it'd  looks like federatedaccounts-core in your
classpath is a pre 0.4 version, based on:
Type
org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
not present

Is it possible you have multiple versions of the relevant libraries in your
classpath?

Kalle



On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina borut.bolc...@gmail.comwrote:

 Hi Kalle,

 I just tried the 0.4.3 version (before I had 0.2.0) and I get this
 exception below. Is there something quick I can fix in my code?

 2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
 java.lang.RuntimeException: Exception loading module(s) from manifest

 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
 Failure loading Tapestry IoC module class

 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
 Type

 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
 not present
 java.lang.RuntimeException: Exception loading module(s) from manifest

 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
 Failure loading Tapestry IoC module class

 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
 Type

 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
 not present
 at

 org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
 at

 org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
 at

 org.apache.tapestry5.internal.TapestryAppInitializer.init(TapestryAppInitializer.java:124)
 at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
 at
 org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
 at

 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
 at

 org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
 at

 org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
 at

 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
 at

 org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
 at
 org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
 at

 org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
 at

 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
 at

 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
 at

 org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
 at

 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
 at

 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
 at

 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
 at

 org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
 at org.eclipse.jetty.server.Server.doStart(Server.java:280)
 at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
 at

 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
 at

 org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520)
 at

 org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
 at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
 at

 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
 at

 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
 at

 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at

 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at

 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at

 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
 at

 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
 at

 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
 at

Re: Web frameworks

2013-11-21 Thread Peter Hvass 
Wooow! What is this inane crap? :D This is hilarious in general on all sides! 


The best bit was discovering this wiki page; 
http://wiki.apache.org/tapestry/Tapestry5Trolls 


Have been giggling with a colleague over this today. :) 

- Original Message -

From: ICE Ernesto Arteaga Zavala arterza...@gmail.com 
To: Tapestry users users@tapestry.apache.org 
Sent: Thursday, November 21, 2013 1:03:04 AM 
Subject: Re: Web frameworks 

Emmanuel, 

Then have sex with Wicket and let us work with the framework we 
prefer... 


2013/11/20 Emmanuel Sowah eso...@gmail.com 

 And let me clarify some more about live class reloading in Wicket. Wicket 
 has 2 modes- development and production. When you turn on development mode, 
 it reloads classes live. So don't fool yourself and others to think 
 Tapestry is the only framework that does live class reloading. 
 
 
 On Wed, Nov 20, 2013 at 10:18 PM, Thiago H de Paula Figueiredo  
 thiag...@gmail.com wrote: 
 
  On Wed, 20 Nov 2013 19:04:30 -0200, Emmanuel Sowah eso...@gmail.com 
  wrote: 
  
  Don't listen to Thiago, he is just blowing hot air. Tapestry is no more 
  relevant, as can be seen in the article: 
  http://zeroturnaround.com/rebellabs/the-2014-decision- 
  makers-guide-to-java-web-frameworks/ 
  As you may see, Tapestry is not mentioned anywhere in that article. 
  
  
  A single article shouldn't be the single decision point of any decision. 
  Not to mention that ZeroTurnaround provides a tool that provides live 
 class 
  reloading, which Tapestry already does for some scenarios. 
  
  
  What about Vaadin, GWT or Wicket? 
  
  
  Drink another shot! :D 
  
  
  Thiago, please stop misleading people. 
  
  
  Now you're calling me a liar or something by accusing me of misleading 
  people. That's rude, specially in a medium which is archived for many 
 years 
  to come, and most people don't like rude people. You're being so pathetic 
  the only feeling I have right now about you isn't anger. It's pity. 
  
  
  Tapestry is just dying a slow death. 
  Even Howard admitted that in a recent interview. 
  
  
  [citation needed] 
  
  
  -- 
  Thiago H. de Paula Figueiredo 
  Tapestry, Java and Hibernate consultant and developer 
  http://machina.com.br 
  
  - 
  To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org 
  For additional commands, e-mail: users-h...@tapestry.apache.org 
  
  
 



-- 
Saludos, 

--- 
Nada que se consiga sin pena y sin trabajo 
es verdaderamente valioso. 
Joseph Addison 
--- 

ICE Ernesto Arteaga Zavala 
Ingeniero de Desarrollo

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

2013-11-21 Thread Borut Bolčina 
Yes, indeed, another dependent project brought in the 0.2.0 version of
federatedaccounts-core.

Now I am having another issue:
configuration.add(FederatedAccountSymbols.SUCCESSURL, /prijavaRedirect);

SUCCESSURL is not a field anymore.


2013/11/21 Kalle Korhonen kalle.o.korho...@gmail.com

 At a first glance, it'd  looks like federatedaccounts-core in your
 classpath is a pre 0.4 version, based on:
 Type

 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
 not present

 Is it possible you have multiple versions of the relevant libraries in your
 classpath?

 Kalle



 On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina borut.bolc...@gmail.com
 wrote:

  Hi Kalle,
 
  I just tried the 0.4.3 version (before I had 0.2.0) and I get this
  exception below. Is there something quick I can fix in my code?
 
  2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
  java.lang.RuntimeException: Exception loading module(s) from manifest
 
 
 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
  Failure loading Tapestry IoC module class
 
 
 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
  Type
 
 
 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
  not present
  java.lang.RuntimeException: Exception loading module(s) from manifest
 
 
 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
  Failure loading Tapestry IoC module class
 
 
 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
  Type
 
 
 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
  not present
  at
 
 
 org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
  at
 
 
 org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
  at
 
 
 org.apache.tapestry5.internal.TapestryAppInitializer.init(TapestryAppInitializer.java:124)
  at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
  at
  org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
  at
 
 
 org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
  at
 
 
 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
  at
 
 
 org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
  at
  org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
  at
 
 
 org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
  at
 
 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
  at org.eclipse.jetty.server.Server.doStart(Server.java:280)
  at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520)
  at
 
 
 org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
  at
 org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
  at
 
 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
  at
 
 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
  at
 
 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
  at
 
 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
  at
 
 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
  at
 
 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
  at
 
 
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
  at

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

2013-11-21 Thread Borut Bolčina 
And indeed in 0.4.3 there is a class with commented field. How to replace
this functionality?

public class FederatedAccountSymbols {
// public static final String SUCCESSURL =
federatedaccounts.successurl;

public static final String COMMITAFTER_OAUTH =
federatedaccounts.commitafteroauth;

public static final String HTTPCLIENT_ON_GAE = httpclient.gae;

public static final String DEFAULT_RETURNPAGE =
federatedaccounts.default_returnpage;

public static final String DEFAULT_REMEMBERME =
federatedaccounts.default_rememberme;

public static final String LOCALACCOUNT_REALMNAME =
federatedaccounts.localaccount_realmname;
}


2013/11/21 Borut Bolčina borut.bolc...@gmail.com

 Yes, indeed, another dependent project brought in the 0.2.0 version of
 federatedaccounts-core.

 Now I am having another issue:
 configuration.add(FederatedAccountSymbols.SUCCESSURL, /prijavaRedirect);

 SUCCESSURL is not a field anymore.


 2013/11/21 Kalle Korhonen kalle.o.korho...@gmail.com

 At a first glance, it'd  looks like federatedaccounts-core in your
 classpath is a pre 0.4 version, based on:
 Type

 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
 not present

 Is it possible you have multiple versions of the relevant libraries in
 your
 classpath?

 Kalle



 On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina borut.bolc...@gmail.com
 wrote:

  Hi Kalle,
 
  I just tried the 0.4.3 version (before I had 0.2.0) and I get this
  exception below. Is there something quick I can fix in my code?
 
  2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
  java.lang.RuntimeException: Exception loading module(s) from manifest
 
 
 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
  Failure loading Tapestry IoC module class
 
 
 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
  Type
 
 
 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
  not present
  java.lang.RuntimeException: Exception loading module(s) from manifest
 
 
 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
  Failure loading Tapestry IoC module class
 
 
 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
  Type
 
 
 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
  not present
  at
 
 
 org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
  at
 
 
 org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
  at
 
 
 org.apache.tapestry5.internal.TapestryAppInitializer.init(TapestryAppInitializer.java:124)
  at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
  at
  org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
  at
 
 
 org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
  at
 
 
 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
  at
 
 
 org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
  at
  org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
  at
 
 
 org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
  at
 
 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
  at org.eclipse.jetty.server.Server.doStart(Server.java:280)
  at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520)
  at
 
 
 org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
  at
 org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
  at

[5.4.25] Ajax submit with Radiogroup submits all values

2013-11-21 Thread Magnus Kvalheim 
Hi guys.

Just notised a strange issue with radio ajax/zone submit. It submits all
values - selected and not selected.

- If I disable javascript - then it submits single value. Correct
- If I remove form t:zone then it also submits fine. Correct

If I enable t:zone then it submits all possible radio values.


Please let me know if anyone can confirm.

Thanks
Magnus

The Rise and Fall of Tapestry

2013-11-21 Thread Emmanuel Sowah 
Hi guys,

Tapestry did not make it to a recent Web frameworks report released by
Zeroturnaround found here:
http://zeroturnaround.com/rebellabs/the-2014-decision-makers-guide-to-java-web-frameworks/
.

This to me, and many others, is the clearest evidence yet that Tapestry has
failed and that Tapestry is no more relevant. Tapestry, once a rising star
with huge following, is reduced to rags with a very small cult following.
Users of Tapestry now are mostly newbies to Java or just finished school
and playing about with some home hobby projects. Or people, like Thiago H
de Paula Figueiredo, who write applications not used by more than 3 people.

Now, to hammer the last nails on Tapestry's coffin, I've decide to write a
blog with the title: *The Rise and Fall of Tapestry*. The paragraphs I
would discuss include:

1. The begin
2. How Tapestry betrayed it's users by breaking existing code base at any
major release.
3. The arrogance of Howard Lewis *Ship*
4. When the 'H' in Howard became 'C' to form Coward.
5. When the Ship sank.
4. How Tapestry became a one-man project
5. Migration path to other web frameworks
6. How Tapestry would be remembered.
7. Why Howard finally embraced Wicket and started using it in his clients'
projects.
8. When Tapestry became Wicketstry or Tapwickstry.
...

I want to have 10 points to write about in my blog. Please feel free to
suggest some other points for me.

I have to mention that I will strictly moderate comments on my blog in
order to filter out venomous comments from Tapestry cult trolls like the
ones I've seen here the last few days.

Please contribute.

Cheers

Re: Custom Validator 5.4

2013-11-21 Thread George Christman 
I was looking at the validator js on github

https://github.com/apache/tapestry-5/blob/bb255c0a144a19939d357c0f071570eea272c918/tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/validation.coffee

but found myself lost in the coffee script. Now if I understand you
correctly, when the fields are rendered, data- attributes are added to the
fields and then used by my validation js?

Thanks Guys,


On Thu, Nov 21, 2013 at 1:53 PM, Thiago H de Paula Figueiredo 
thiag...@gmail.com wrote:

 On Thu, 21 Nov 2013 15:55:33 -0200, George Christman 
 gchrist...@cardaddy.com wrote:

  Hello, I'm trying to build a custom validator but noticed some changes
 regarding the js in 5.4.


  Does anybody know of a simple approach to handling the js piece of the
 code?

 javaScriptSupport.require(t5/core/validation);
 writer.attributes(DataConstants.VALIDATION_ATTRIBUTE, true,
 data-validate-maxscale, constraintValue.toString(),
 data-maxscale-message, buildMessage(formatter,
 field, constraintValue));


 I'm sorry, I'm not sure I know what you're asking. Anyway, just think that
 the data you need to perform the validation client-side now follows the way
 better approach of being located in data-* attributes instead of variables.
 Now just make your validation JavaScript code search for elements with the
 data-* attributes you're adding and add the validation hooks to  them. Have
 you checked how the Tapestry validators are written? That's what I'd do
 until the documentation about it isn't available.



  I'm not sure if I should be using coffee or what I'm suppose to be doing.


 You don't need to use CoffeeScript yourself.

 --
 Thiago H. de Paula Figueiredo
 Tapestry, Java and Hibernate consultant and developer
 http://machina.com.br

 -
 To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
 For additional commands, e-mail: users-h...@tapestry.apache.org




-- 
George Christman
www.CarDaddy.com
P.O. Box 735
Johnstown, New York

Re: Version 2 of Eclipse Tapestry5 Plugin available for download

2013-11-21 Thread Peter Hvass 
Thanks for this Dmitry - been using it a few weeks now. The Ctrl+R and such 
things slowly 
working their way into my muscle memory. :) 


- Original Message -

From: Charlouze m...@charlouze.com 
To: Tapestry users users@tapestry.apache.org 
Sent: Thursday, November 21, 2013 2:51:22 PM 
Subject: Re: Version 2 of Eclipse Tapestry5 Plugin available for download 

Great news ! Seems to be very nice :) Thanks for your work. 


2013/11/21 Dmitry Gusev dmitry.gu...@gmail.com 

 I'm happy to present you new version of Eclipse Tapestry5 Plugin with 
 another big feature -- Tapestry Project Outline 
 
 This feature brings support for 3rd party Tapestry modules. It analyses 
 project's classpath and finds project's modules so you can see the context 
 of your project same as Tapestry see it. 
 
 As result you can now CMD+Hover over tapestry core and 3rd party components 
 in your TML files and quickly navigate to their sources. 
 
 Tapestry Context also works in 3rd party JARs now. 
 
 Please note that analysis or 3rd party modules will only work if you have 
 sources attached to your JARs in Eclipse (which is the default if you 
 import your project via './gradlew eclipse' or 'mvn eclipse:eclipse 
 -DdownloadSources=true'. 
 
 As usual you can see screenshots and brief description of new features on 
 the GitHub: 
 
 https://github.com/anjlab/eclipse-tapestry5-plugin#tapestry-project-outline 
 
 Version 2.0.9 is the first public release, so many improvements still need 
 to be done, but it should work for most cases. 
 
 Installation instructions can be found here: 
 
 https://github.com/anjlab/eclipse-tapestry5-plugin#install 
 
 Upgrade notes: 
 If install this update your Tapestry Context view won't work after restart, 
 you need to close it and open it once again via Window - Show View - 
 Tapestry Context. 
 
 -- 
 Dmitry Gusev 
 
 AnjLab Team 
 http://anjlab.com

Re: Version 2 of Eclipse Tapestry5 Plugin available for download

2013-11-21 Thread Charlouze 
Great news ! Seems to be very nice :) Thanks for your work.


2013/11/21 Dmitry Gusev dmitry.gu...@gmail.com

 I'm happy to present you new version of Eclipse Tapestry5 Plugin with
 another big feature -- Tapestry Project Outline

 This feature brings support for 3rd party Tapestry modules. It analyses
 project's classpath and finds project's modules so you can see the context
 of your project same as Tapestry see it.

 As result you can now CMD+Hover over tapestry core and 3rd party components
 in your TML files and quickly navigate to their sources.

 Tapestry Context also works in 3rd party JARs now.

 Please note that analysis or 3rd party modules will only work if you have
 sources attached to your JARs in Eclipse (which is the default if you
 import your project via './gradlew eclipse' or 'mvn eclipse:eclipse
 -DdownloadSources=true'.

 As usual you can see screenshots and brief description of new features on
 the GitHub:

 https://github.com/anjlab/eclipse-tapestry5-plugin#tapestry-project-outline

 Version 2.0.9 is the first public release, so many improvements still need
 to be done, but it should work for most cases.

 Installation instructions can be found here:

 https://github.com/anjlab/eclipse-tapestry5-plugin#install

 Upgrade notes:
 If install this update your Tapestry Context view won't work after restart,
 you need to close it and open it once again via Window - Show View -
 Tapestry Context.

 --
 Dmitry Gusev

 AnjLab Team
 http://anjlab.com

Re: Web frameworks

2013-11-21 Thread Muhammad Gelbana 
Tapestry is an idea Mr. Emmanuel and Ideas are troll proof.

*-*
*Muhammad Gelbana*
http://www.linkedin.com/in/mgelbana


On Thu, Nov 21, 2013 at 1:05 PM, Peter Hvass p.hv...@albourne.com wrote:

 Wooow! What is this inane crap? :D This is hilarious in general on all
 sides!


 The best bit was discovering this wiki page;
 http://wiki.apache.org/tapestry/Tapestry5Trolls


 Have been giggling with a colleague over this today. :)

 - Original Message -

 From: ICE Ernesto Arteaga Zavala arterza...@gmail.com
 To: Tapestry users users@tapestry.apache.org
 Sent: Thursday, November 21, 2013 1:03:04 AM
 Subject: Re: Web frameworks

 Emmanuel,

 Then have sex with Wicket and let us work with the framework we
 prefer...


 2013/11/20 Emmanuel Sowah eso...@gmail.com

  And let me clarify some more about live class reloading in Wicket. Wicket
  has 2 modes- development and production. When you turn on development
 mode,
  it reloads classes live. So don't fool yourself and others to think
  Tapestry is the only framework that does live class reloading.
 
 
  On Wed, Nov 20, 2013 at 10:18 PM, Thiago H de Paula Figueiredo 
  thiag...@gmail.com wrote:
 
   On Wed, 20 Nov 2013 19:04:30 -0200, Emmanuel Sowah eso...@gmail.com
   wrote:
  
   Don't listen to Thiago, he is just blowing hot air. Tapestry is no more
   relevant, as can be seen in the article:
   http://zeroturnaround.com/rebellabs/the-2014-decision-
   makers-guide-to-java-web-frameworks/
   As you may see, Tapestry is not mentioned anywhere in that article.
  
  
   A single article shouldn't be the single decision point of any
 decision.
   Not to mention that ZeroTurnaround provides a tool that provides live
  class
   reloading, which Tapestry already does for some scenarios.
  
  
   What about Vaadin, GWT or Wicket?
  
  
   Drink another shot! :D
  
  
   Thiago, please stop misleading people.
  
  
   Now you're calling me a liar or something by accusing me of misleading
   people. That's rude, specially in a medium which is archived for many
  years
   to come, and most people don't like rude people. You're being so
 pathetic
   the only feeling I have right now about you isn't anger. It's pity.
  
  
   Tapestry is just dying a slow death.
   Even Howard admitted that in a recent interview.
  
  
   [citation needed]
  
  
   --
   Thiago H. de Paula Figueiredo
   Tapestry, Java and Hibernate consultant and developer
   http://machina.com.br
  
   -
   To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
   For additional commands, e-mail: users-h...@tapestry.apache.org
  
  
 



 --
 Saludos,

 ---
 Nada que se consiga sin pena y sin trabajo
 es verdaderamente valioso.
 Joseph Addison
 ---

 ICE Ernesto Arteaga Zavala
 Ingeniero de Desarrollo

Re: Custom Validator 5.4

2013-11-21 Thread Thiago H de Paula Figueiredo 
On Thu, 21 Nov 2013 15:55:33 -0200, George Christman  
gchrist...@cardaddy.com wrote:



Hello, I'm trying to build a custom validator but noticed some changes
regarding the js in 5.4.


Does anybody know of a simple approach to handling the js piece of the  
code?


javaScriptSupport.require(t5/core/validation);
writer.attributes(DataConstants.VALIDATION_ATTRIBUTE, true,
data-validate-maxscale, constraintValue.toString(),
data-maxscale-message, buildMessage(formatter,  
field, constraintValue));


I'm sorry, I'm not sure I know what you're asking. Anyway, just think that  
the data you need to perform the validation client-side now follows the  
way better approach of being located in data-* attributes instead of  
variables. Now just make your validation JavaScript code search for  
elements with the data-* attributes you're adding and add the validation  
hooks to  them. Have you checked how the Tapestry validators are written?  
That's what I'd do until the documentation about it isn't available.




I'm not sure if I should be using coffee or what I'm suppose to be doing.


You don't need to use CoffeeScript yourself.

--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Version 2 of Eclipse Tapestry5 Plugin available for download

2013-11-21 Thread Dmitry Gusev 
I'm happy to present you new version of Eclipse Tapestry5 Plugin with
another big feature -- Tapestry Project Outline

This feature brings support for 3rd party Tapestry modules. It analyses
project's classpath and finds project's modules so you can see the context
of your project same as Tapestry see it.

As result you can now CMD+Hover over tapestry core and 3rd party components
in your TML files and quickly navigate to their sources.

Tapestry Context also works in 3rd party JARs now.

Please note that analysis or 3rd party modules will only work if you have
sources attached to your JARs in Eclipse (which is the default if you
import your project via './gradlew eclipse' or 'mvn eclipse:eclipse
-DdownloadSources=true'.

As usual you can see screenshots and brief description of new features on
the GitHub:

https://github.com/anjlab/eclipse-tapestry5-plugin#tapestry-project-outline

Version 2.0.9 is the first public release, so many improvements still need
to be done, but it should work for most cases.

Installation instructions can be found here:

https://github.com/anjlab/eclipse-tapestry5-plugin#install

Upgrade notes:
If install this update your Tapestry Context view won't work after restart,
you need to close it and open it once again via Window - Show View -
Tapestry Context.

-- 
Dmitry Gusev

AnjLab Team
http://anjlab.com

Re: Custom Validator 5.4

2013-11-21 Thread Thiago H de Paula Figueiredo 
On Thu, 21 Nov 2013 17:10:22 -0200, George Christman  
gchrist...@cardaddy.com wrote:



I was looking at the validator js on github

https://github.com/apache/tapestry-5/blob/bb255c0a144a19939d357c0f071570eea272c918/tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/validation.coffee

but found myself lost in the coffee script. Now if I understand you
correctly, when the fields are rendered, data- attributes are added to  
the fields and then used by my validation js?


Yep!

--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Custom Validator 5.4

2013-11-21 Thread George Christman 
Hello, I'm trying to build a custom validator but noticed some changes
regarding the js in 5.4. Does anybody know of a simple approach to handling
the js piece of the code?

javaScriptSupport.require(t5/core/validation);
writer.attributes(DataConstants.VALIDATION_ATTRIBUTE, true,
data-validate-maxscale, constraintValue.toString(),
data-maxscale-message, buildMessage(formatter, field,
constraintValue));

I'm not sure if I should be using coffee or what I'm suppose to be doing.

Thanks.

Re: [ANNOUNCEMENT] tynamo-federatedaccounts 0.4.3 released!

2013-11-21 Thread Alejandro Scandroli 
Hi Borut


The FacebookOauthSignIn has a new parameter returnPageName.
If the parameter is not specified the component will use the value of
the FederatedAccountSymbols.DEFAULT_RETURNPAGE symbol.

Alejandro.

On Thu, Nov 21, 2013 at 12:17 PM, Borut Bolčina borut.bolc...@gmail.com wrote:
 And indeed in 0.4.3 there is a class with commented field. How to replace
 this functionality?

 public class FederatedAccountSymbols {
 // public static final String SUCCESSURL =
 federatedaccounts.successurl;

 public static final String COMMITAFTER_OAUTH =
 federatedaccounts.commitafteroauth;

 public static final String HTTPCLIENT_ON_GAE = httpclient.gae;

 public static final String DEFAULT_RETURNPAGE =
 federatedaccounts.default_returnpage;

 public static final String DEFAULT_REMEMBERME =
 federatedaccounts.default_rememberme;

 public static final String LOCALACCOUNT_REALMNAME =
 federatedaccounts.localaccount_realmname;
 }


 2013/11/21 Borut Bolčina borut.bolc...@gmail.com

 Yes, indeed, another dependent project brought in the 0.2.0 version of
 federatedaccounts-core.

 Now I am having another issue:
 configuration.add(FederatedAccountSymbols.SUCCESSURL, /prijavaRedirect);

 SUCCESSURL is not a field anymore.


 2013/11/21 Kalle Korhonen kalle.o.korho...@gmail.com

 At a first glance, it'd  looks like federatedaccounts-core in your
 classpath is a pre 0.4 version, based on:
 Type

 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
 not present

 Is it possible you have multiple versions of the relevant libraries in
 your
 classpath?

 Kalle



 On Wed, Nov 20, 2013 at 11:41 PM, Borut Bolčina borut.bolc...@gmail.com
 wrote:

  Hi Kalle,
 
  I just tried the 0.4.3 version (before I had 0.2.0) and I get this
  exception below. Is there something quick I can fix in my code?
 
  2013-11-20 17:00:57.566:WARN:oejuc.AbstractLifeCycle:FAILED app:
  java.lang.RuntimeException: Exception loading module(s) from manifest
 
 
 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
  Failure loading Tapestry IoC module class
 
 
 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
  Type
 
 
 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
  not present
  java.lang.RuntimeException: Exception loading module(s) from manifest
 
 
 jar:file:/C:/Users/bolcinab/.m2/repository/org/tynamo/security/tynamo-federatedaccounts-facebook/0.4.3/tynamo-federatedaccounts-facebook-0.4.3.jar!/META-INF/MANIFEST.MF:
  Failure loading Tapestry IoC module class
 
 
 org.tynamo.security.federatedaccounts.facebook.services.FacebookFederatedAccountsModule:
  Type
 
 
 org.tynamo.security.federatedaccounts.services.FederatedSignInComponentBlockSource
  not present
  at
 
 
 org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
  at
 
 
 org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
  at
 
 
 org.apache.tapestry5.internal.TapestryAppInitializer.init(TapestryAppInitializer.java:124)
  at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
  at
  org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:719)
  at
 
 
 org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
  at
 
 
 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
  at
 
 
 org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:710)
  at
  org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
  at
 
 
 org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:293)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
  at
 
 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at
 
 
 org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
  at org.eclipse.jetty.server.Server.doStart(Server.java:280)
  at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
  at
 
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
  at

Re: The Rise and Fall of Tapestry

2013-11-21 Thread George Christman 
I'd just like to say I currently use Tapestry in some very large projects
without issue. I'm not sure why your wasting your time trolling this
mailing list.


On Thu, Nov 21, 2013 at 5:31 PM, Emmanuel Sowah eso...@gmail.com wrote:

 Hi guys,

 Tapestry did not make it to a recent Web frameworks report released by
 Zeroturnaround found here:

 http://zeroturnaround.com/rebellabs/the-2014-decision-makers-guide-to-java-web-frameworks/
 .

 This to me, and many others, is the clearest evidence yet that Tapestry has
 failed and that Tapestry is no more relevant. Tapestry, once a rising star
 with huge following, is reduced to rags with a very small cult following.
 Users of Tapestry now are mostly newbies to Java or just finished school
 and playing about with some home hobby projects. Or people, like Thiago H
 de Paula Figueiredo, who write applications not used by more than 3 people.

 Now, to hammer the last nails on Tapestry's coffin, I've decide to write a
 blog with the title: *The Rise and Fall of Tapestry*. The paragraphs I
 would discuss include:

 1. The begin
 2. How Tapestry betrayed it's users by breaking existing code base at any
 major release.
 3. The arrogance of Howard Lewis *Ship*
 4. When the 'H' in Howard became 'C' to form Coward.
 5. When the Ship sank.
 4. How Tapestry became a one-man project
 5. Migration path to other web frameworks
 6. How Tapestry would be remembered.
 7. Why Howard finally embraced Wicket and started using it in his clients'
 projects.
 8. When Tapestry became Wicketstry or Tapwickstry.
 ...

 I want to have 10 points to write about in my blog. Please feel free to
 suggest some other points for me.

 I have to mention that I will strictly moderate comments on my blog in
 order to filter out venomous comments from Tapestry cult trolls like the
 ones I've seen here the last few days.

 Please contribute.

 Cheers




-- 
George Christman
www.CarDaddy.com
P.O. Box 735
Johnstown, New York

5.4 Bug with select nested inside form loop.

2013-11-21 Thread George Christman 
Hello, I have an ajaxformloop with a nested select menu loaded from the
database.

Lets say we have two rows in the list and both select menus have selected
values. When I remove the first row everything works as desired. If I
refresh the page I'm finding my now single row ajaxformloop select menu
sets the selected value to the now deleted rows selected value. Despite
page refreshes, the value remained. Now I found if I altered the id in the
select menu and then refreshed the page, the select menu now properly set
the selected value.

It seems as if the selected value is being cached, does anybody know what
might be going on?

Re: The Rise and Fall of Tapestry

2013-11-21 Thread Peter Hvass 
You are my guiding light Emmanuel - I look forward to absorbing any and all 
nuggets of wisdom you post on your blog. I am so glad that finally someone 
with enough time on their hands has come to speak the truth about the evil 
demon enclosure that is Tapestry with its patron lord of darkness Howard. 


Yours eternally, 
Peter 

- Original Message -

From: George Christman gchrist...@cardaddy.com 
To: Tapestry users users@tapestry.apache.org 
Sent: Friday, November 22, 2013 7:46:55 AM 
Subject: Re: The Rise and Fall of Tapestry 

I'd just like to say I currently use Tapestry in some very large projects 
without issue. I'm not sure why your wasting your time trolling this 
mailing list. 


On Thu, Nov 21, 2013 at 5:31 PM, Emmanuel Sowah eso...@gmail.com wrote: 

 Hi guys, 
 
 Tapestry did not make it to a recent Web frameworks report released by 
 Zeroturnaround found here: 
 
 http://zeroturnaround.com/rebellabs/the-2014-decision-makers-guide-to-java-web-frameworks/
  
 . 
 
 This to me, and many others, is the clearest evidence yet that Tapestry has 
 failed and that Tapestry is no more relevant. Tapestry, once a rising star 
 with huge following, is reduced to rags with a very small cult following. 
 Users of Tapestry now are mostly newbies to Java or just finished school 
 and playing about with some home hobby projects. Or people, like Thiago H 
 de Paula Figueiredo, who write applications not used by more than 3 people. 
 
 Now, to hammer the last nails on Tapestry's coffin, I've decide to write a 
 blog with the title: *The Rise and Fall of Tapestry*. The paragraphs I 
 would discuss include: 
 
 1. The begin 
 2. How Tapestry betrayed it's users by breaking existing code base at any 
 major release. 
 3. The arrogance of Howard Lewis *Ship* 
 4. When the 'H' in Howard became 'C' to form Coward. 
 5. When the Ship sank. 
 4. How Tapestry became a one-man project 
 5. Migration path to other web frameworks 
 6. How Tapestry would be remembered. 
 7. Why Howard finally embraced Wicket and started using it in his clients' 
 projects. 
 8. When Tapestry became Wicketstry or Tapwickstry. 
 ... 
 
 I want to have 10 points to write about in my blog. Please feel free to 
 suggest some other points for me. 
 
 I have to mention that I will strictly moderate comments on my blog in 
 order to filter out venomous comments from Tapestry cult trolls like the 
 ones I've seen here the last few days. 
 
 Please contribute. 
 
 Cheers 
 



-- 
George Christman 
www.CarDaddy.com 
P.O. Box 735 
Johnstown, New York