T5 has a very nice usability feature, on a form it puts the cursor in
the first empty textfield.
But this seems not to work, if there is a FormFragment involved.
On the LoginPage, where I have a form with username and password and a
FormFragment with
email (to request password reset), the non
Based on the example from Hugo Palma (see
http://markmail.org/message/4bdwo2yrx6tavdgh)
I implemented a dependend checkbox.
Event handling is fine, but I lost hours finding out while
response.evalJSON() fails and I still have no clue...
Im always getting this erreor;
Error communication
I have written two blog articles about using T5 to write an
iPhone application to get easy and quick access to all your
coustomer contact data residing in your CRM.
I used iWebkit for GUI design, the blog is focused on the
efficiency and elegance of Tapestry 5 regarding components
and Hibernate
Try this one:
mvn archetype:create
-DarchetypeGroupId=org.apache.tapestry
-DarchetypeVersion=5.0.18
-DarchetypeArtifactId=quickstart
-DgroupId=org.apache.tapestry
-DartifactId= tutorial1
-DpackageName=org.apache.tapestry5.tutorial
Max
-Ursprüngliche Nachricht-
Von: Angelo Chen
Is there a special meaning to the expansion of ${name} ?
Cause I have a very strange problem.
If I use ${getNode().getName()} in my template, all is ok.
If I use ${node.getName()} in my template, all is ok.
If I use ${node.name} I do not get the expected value, instead
the name of the
set it to filter the
resources, that may be the cause.
On Wed, Dec 10, 2008 at 2:28 PM, Maximilian Weißböck
[EMAIL PROTECTED] wrote:
Is there a special meaning to the expansion of ${name} ?
Cause I have a very strange problem.
If I use ${getNode().getName()} in my template, all is ok
best
practice, but if it works for you, have fun. I still expect it will
only work for components, not pages. Howard? True?
Christian.
On 5-Dec-08, at 06:05 , Maximilian Weißböck wrote:
I would much prefer solution number 1. as it keeps things
on the same place that belong together
I would much prefer solution number 1. as it keeps things
on the same place that belong together.
Sadly maven build does not work with this solution.
Is there any maven guru how knows how to fix this?
Thanks, Max
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL
not be an Interface? No default coercion?
You can have interface parameters, but the problem here is that you define
a
parameter of type PageDelegate, and try to assign a default value of
string
false to that parameter. Perhaps you meant @Property(required=false) ?
- Ville
Maximilian
I have a component that has a delegate as parameter binding like this:
@Parameter(false)
@Property
private PageDelegate pageDelegate;
Inside the page I'm testing if the delegate is set (only then an ActionLink
will be shown)
t:if test=pageDelegate
PageDelegate is
in the onProvideCopletionsFrom(String partial) methode but is
broken
on the web page. All pages and content type is encoded utf-8
Thanks, Max
DI Maximilian Weißböck
Competence Center Manager
Sphinx IT Consulting GmbH
A-1060 Wien, Mariahilfer Straße 103
T +43
a JIRA issue on that point, it has been fixed in a snapshot of
5.0.16. What version are you using ?
José
Maximilian Weißböck a écrit :
We are having trouble with UTF-8 encoded Strings like Weißböck using
the t:mixins=autocomplete.
Using a grid the name is all ok, no encoding problem
As I have to support german localization and IE, I think
1) and 2) is a must have for 5.0
3) would be great, but is not a must have for 5.0 I think
I also think Geoff is right with is argument:
ApplicationStateObject is a misleading term
https://issues.apache.org/jira/browse/TAPESTRY-2703
and
Put me on the me to List ;-)
We have a (very possible) project where the customer want's us to
use Struts2 - but we hope we can convince him to Tapestry5.
But if localization is still such an issue, this will be really hard...
Max
PS: I already voted long time ago...
-Ursprüngliche
-Ursprüngliche Nachricht-
Von: Kristian Marinkovic [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. September 2008 15:19
An: Tapestry users
Betreff: Re: T5: ApplicationStateObject is misleading
I'm no native speaker but ApplicationStateObject is quite fine for
me... it
, when you submit the issue in
jira please send a ping here, so that I can vote :)
Cheers,
Martin
On Wed, 2008-07-09 at 18:23 +0200, Maximilian Weißböck wrote:
Palette Component behaves different in FireFox then it does in Safari and IE
If palette item is moved in FireFox the following
Palette Component behaves different in FireFox then it does in Safari and IE
If palette item is moved in FireFox the following events are triggered
onSuccess()
onSubmit()
If palette item is moved in Safari or IE none of the above events is triggered.
Is this suggested to be
an application with utf-8 properties-files without any
problems.
This strange behavior can only be found in anatoher application.
Maximilian Weißböck wrote:
Do you read this values from a property file?
Property files in Java may not be utf-8 encoded.
The have to be iso-8859-1 encoded.
Many
be a
general Java problem even though in 99% of cases my special characters are
displayed properly.
Maximilian Weißböck wrote:
The load and store methods load and store properties in a simple
line-oriented format specified below. This format uses the ISO 8859-1
character encoding. Characters
Did you have a look at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding
Max
-Ursprüngliche Nachricht-
Von: Sebastian Altmann [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 7. Juli 2008 14:06
An: users@tapestry.apache.org
Betreff: Strange behavior of special characters
Hi,
we
circumstances.
Another thing that confuses me is that for example in löschen not just the
ö isn't displayed correct
but also the 3 following characters (sch).
This happens to every string with special characters (mostly not the next 3
but the next 2 characters ).
Maximilian Weißböck wrote:
Did you
+1 for this
keep it simple and clear!
Max
-Ursprüngliche Nachricht-
Von: Don Ryan [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 25. Juni 2008 13:08
An: Tapestry users
Betreff: Re: What if Page was removed from page names?
On 25 Jun 2008, at 01:12, Filip S. Adamsen wrote:
As long
stringent your requirements are, but I know
with 5.0.7 the
bubbles go away by setting clientValidation=false on
the form component.
Of course, this means that the page submits to validate...
-Original Message-
From: Maximilian Weißböck [mailto:[EMAIL PROTECTED]
Sent
There shold be an easy way to use normal text as replacement
for the popup bubbles, as we have the need to build our WebApps
conforming to WAI (Web Accessibility Initiative).
Any change to get this? We have WAI conformant Apps running
with T3 and T4 and would very much preferr to build the
If you use Java property files, there is something very special.
Property files in Java loaded by the default class loader may NOT be encoded
in UTF-8. They always must be encoded in ISO-8859-1 or you have to use
Unicode escape sequences.
See:
As interesting the HiberTapestry approach sounds, it is nothing we can
use. We have a strict rule, the service layer is completly independent
from the view layer.
But we also use the OSIV setup (as we must navigate in our rich
domain model without pain), so we have the very same problem
as
I'm just starting with T5 and did my first experiments with 5.0.5 and now
upgraded to 5.0.6.
I used Howards tutorial, and as far as I can remember, the localization of
Enums inside BeanEditForm just worked.
But now with version 5.0.6 it seems no longer to work. Anything changed in
Oh yes, this is really a problem we actually had in a Tapestry 4
Application. We had to use (ugly) DTO Objects to avoid this problem.
As far as I can remember, this problem is addressed in JSF with its complex
render cycle. Values are stored in intermediate objects until
validation is completed
We have a T3 and a T4 Appliaction in production
and hopefully will start a T5 development soon.
I do not see a real big problem in this versions not beeing
compatible.
I also think you compare different kind of beasts if you compare
Websphere with Tapestry.
It's more like EJB 2.x to EJB 3 -
to use the new 2.7.1-SNAPSHOT version to see
the fixes. (which is deployed to the maven2 snapshot repo
http://opencomponentry.com/repository/m2-snapshot-repo/ )
On 6/27/07, Maximilian Weißböck
[EMAIL PROTECTED] wrote:
We just upgraded to Tapestry 4.1.2 but have some ognl problems.
So
We have another ognl problem with Tapestry 4.1.2.
We use the expression ognl:ordersPerShopLoop.index % 2 == 0 (for even/odd
style in a table)
and get the following error (see below). Any hints how to prevent this or how
we have to rewrite the
above ognl expression?
Thanks, Max
2007-06-27
is
ognl:ordersPerShopLoop.index % 2 == 0
and it throws this error: Caused by: compile error: invalid types for ==
Has the syntax of ognl canged in 2.7, and if yes, where can I find the doc?
Thanks, Max
---
Maximilian Weißböck
Sphinx IT Consulting GmbH
Just to keep the list informed ...
Application works with IE if we do NOT use a proxy.
It breaks in IE if we use the proxy (we use the squid proxy).
BUT: If you set in IE the internet option use HTTP 1.1 for proxy connections
(don't know the exact wording since I have only a german IE
Hello Francesco,
we use the open session in view filter and have no real problems so far.
But what we also do, we define database views for joining the values we need,
we do not join very much in hibernate.
Somtimes I have the feeling, that people try to do to much in hibernate
and they
-Ursprüngliche Nachricht-
Von: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 21. März 2007 19:44
An: Tapestry users
Betreff: Re: Tapestry 4.1.1 / dojo broken on IE? - IE freezing!
IE is a little less forgiving with javascript errors, so if
you get one all other
35 matches
Mail list logo
