distributed systems have a particular architecture. Web applications can be
classified according to the MVC-pattern. I know how that looks in Tapestry.
my professor wants a classification by fat-clint or fat-server. The
structure of an application.
I guess that is not express this in just a few a
many thanks @ all for the reply.
I know that tapestry is a web framework. I meant the classification of the
finished application. I think you have helped me already. many thanks.
I try to describe a little bit.
Let's see what my professor says. :)
I am not a theorist. My Tapestry application is
I'm currently writing a bachelor thesis about tapestry.
I'm trying to classify tapestry by JEE standard. But I can't find any
information about it.
A tapestry application is based on the Java-Servlet-API, but unlike servlets
tapestry pages are no singletons.
Could you please give me information a
Thanks for your answer,
i just found jira issue for that problem.
https://issues.apache.org/jira/browse/TAPESTRY-1928
(and that you can't override the built-in coercion)
So i try it with enums...
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/null-value-in-Boolean-tp571
I'm writing a web application with Apache Tapestry 5.3.
I use in my web application a radio group (2 radio button) which saves in a
java.lang.Boolean object. I have some problems when saving the data.
Test.java
__
@Property
private Boolean surgery;
.
@CommitAfter
public Object onSucces