Hi,
If you are using message catalog then Tapestry should be able to load proper
value fir the grid column.
So let's assume that in your data dource object you have property
firstName, i.e. you have method in POJO getFirstName()
Add such record to the UserList.properties:
Also don't forget to encode property file in UTF-8. You can use native2ascii
tool from JDK to convert native encoded file to Unicode encoded file.
On Tue, Mar 25, 2008 at 12:15 AM, Yura Tkachenko
[EMAIL PROTECTED] wrote:
Hi,
If you are using message catalog then Tapestry should be able to
Hi,
Go grab Wicket of GWT. It's better documented and questions like what you
asked won't refer you to source code but to a well documented examples.
Above all the users of those lists are far, far more friendly.
Rob
On Mon, Mar 24, 2008 at 5:27 PM, osamuo [EMAIL PROTECTED]
wrote:
How long
TROLL
go away
On Tue, Mar 25, 2008 at 9:33 AM, Rob Smeets [EMAIL PROTECTED] wrote:
Hi,
Go grab Wicket of GWT. It's better documented and questions like what you
asked won't refer you to source code but to a well documented examples.
Above all the users of those lists are far, far more
kranga wrote:
T5 uses Prototype and Scriptaculous for client side validation/ajax
stuff. Our experience with Prototype and Scriptaculous has not been
that great, especially when it comes to upgrading versions. Is there
any way to disable the use of those libraries and/or the use of a
Thank you, but did u read my post carefully?
I DID add a properties file encoding in UTF-8, and add a something-lable
which matches the data source column name.
It changed the column's title, but displayed some text which I don't expect.
2008/3/25, Yura Tkachenko [EMAIL PROTECTED]:
Hi,
If
Hi all,
I am including lots of javascript in my code through e.g.
span jwcid=@Script script=/script/myscript.xml /
Tapestry includes the whole source of the javascript files in the page
source,
which results in pages whose source may be consisting of hundreds of lines
of java code.
Is there
Hi Angelo,
If you use PageRenderSupport to do anything script related, or if you
use @IncludeJavaScriptLibrary, then it will be included in the resulting
page automatically. If for some reason you need to explicitly include
it, then you can annotate your page class with
There we go again, when someone raises a legitimate concern he is easily
labeled a Troll. You had been more productive by telling me I'm wrong on
what I said and give me some reasons why. Again, this proves how arrogant
and unfriendly Tapestry mailing list members are. Fortunately, I'm not the
Tobias Marx wrote:
Wouldn't it be useful to make the @Cache annotation the default annotation
for all methods?
I can not imagine a case where it would make sense that during the rendering of
a page returns different results...
Just an example : you are in a loop (or grid or a beaneditor any
Hello there,
I have a t:beaneditformwith multiple selectObject components (custom
component;
http://wiki.apache.org/tapestry/Tapestry5HowtoSelectWithObjects ), each
in a t:parameter.
Now when the value of the first selectObject changes, I want the (two)
other t:parameter to be updated.
Yes, you are right. But loops are usually inside of components and pages
contain those componentsbut all methods in the page itself could be @Cache
methods in my opinion if you do a component based approach and always package
logical widgets into a component.
Original-Nachricht
Dude, if your backward compatibility is such an issue stop trolling
and maybe learn to program Java, get productive, fork Tap 3, fork Tap
4, get famous and be happy to keep Tapestry going the way YOU want it.
Your trolling only shows you have NO CLUE what open source is. Stop
wasting everybody's
First of all: Overall is Tapestry 5 in general and the the Grid
component in particular an amazing piece of software. So this is *not*
complaints, just an attempt to sort things out, to share my experiences
and check that I understand things correctly.
I have a use case where I'm about to
Rob smeets (and maybe few more aliases) is definitely a TROLL,
those interested in details read the rest of the mail...
Yes,
there we go again,
again you waste our time, spreading fud,
and the article you mention is far from unbiased, and most likely
even posted by you (using another alias).
[EMAIL PROTECTED] wrote:
Yes, you are right. But loops are usually inside of components and pages contain those
componentsbut all methods in the page itself could be @Cache methods in my opinion if
you do a component based approach and always package logical widgets into a
component.
Alec Leamas wrote:
- The paging policy with a fixed number of numbered pages is hardcoded
and can't be changed. Other policies e. g., overlap between pages
Isn't that something you can handle inside your own GridDataSource? With the
page number, the number of results per page, the number of
caching every method by default is definitely too error prone,
and unexpected for most people.
On Tue, Mar 25, 2008 at 3:23 PM, Francois Armand [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Yes, you are right. But loops are usually inside of components and pages
contain those
Yes, It's an absolutely great feature!
:clap:
Moritz Gmelin wrote:
Hi,
I just tried the new Zone component which is just about great!
But when I tried to return a Block from my ActionListener that
contains a Grid, I get the following Exception
Rob Smeets wrote:
There we go again, when someone raises a legitimate concern he is easily
labeled a Troll.
So, once and for all, please prove us you are not the same childish
anonymous coward A.K.A Emmanuel Sowah A.K.A. Francis Amanfo
Hi,
When i use zone in component , the json response is :
Tapestry.initializeZones([{\div\:\output:118e6af4fe4\}], [[
\form:118e6af4fe4\,\output\]]);,content: ..
there should be:
Tapestry.initializeZones([{\div\:\output:118e6af4fe4\}], [[
Sorry if this has been mentioned before, but I couldn't find any information
about it in my searches (which is perhaps the answer already). I noticed on
Howard's blog he condemned the use of Maven2, and I was wondering if there
have been any changes to Tapestry5 that make it less maven-centric, or
Not possible?
Sometimes a validator needs to look at input from another field to see
if it is valid (ie password/confirmPassword). I know it's easy to do
in onValidateForm, but I'd like to see how to do it in a nice modular
Validator. I'm looking for something like:
public void
Sorry, those APIs are not in place yet. I have JIRA issue add
optional validators, which is a loose, general term for what you are
aiming for (password is required if userName is given).
I think some relationships may not be expressable using the @Validate
annotation, i.e., the string
Is the way I'm building my custom select model the approved Tap 5
way? My concern is if OptionModelImpl and SelectModelImpl are still
considered internal Tapestry classes and should be avoided? This stuff
works fine for me and it's fairly elegant (IMHO), I just want to know
if there is a better
Does anyone have suggestions for running/debugging Tapestry using Tomcat
5.5 and working in Eclipse?
IE:
a) Should you create the eclipse project as a dynamic web project
or just a java project or some sort of J2EE project?
b) Does a maven-built project map over to the type of
http://tapestry.apache.org/tapestry4.1/usersguide/script.html
see the include-script element
On Tue, Mar 25, 2008 at 1:15 PM, Grigoris Ioannou
[EMAIL PROTECTED] wrote:
Hi all,
I am including lots of javascript in my code through e.g.
span jwcid=@Script script=/script/myscript.xml /
Horay to that!
It would also be great if someone could help me and vote on
http://opensource.atlassian.com/projects/hibernate/browse/HV-44 (Make
Hibernate Validator multi-lingual).
Regards,
Olle
2008/3/24, Howard Lewis Ship [EMAIL PROTECTED]:
Eventually, it would be nice if we could come up
Use of internal classes isn't forbidden, but there's no promise of
backwards compatibility. We may rename, move, refactor or change those
classes at any time and with no notice.
Because backwards compatibility is so hard, it's limited to as few
classes, interfaces and annotations as possible,
I could agree to Howards despair over some of the Maven oddities, but
all-in-all I think Maven2 is a very good tool. We use it on all our
products, ranging from 5 to 20 modules.
We have recently converted from Ant+Ivy, and I surely don''t want to go
back!
Regards,
Olle
2008/3/25, Peter Beshai
Ok no worries.
On a related note, where do you put the messages file for a custom
validator? In the example below, which looks for a key called
'confirm', I have tried Confirm.properties (in same package as
validator called Confirm.java), Signup.properties (the page using the
validator)
Bruce Petro a écrit :
Does anyone have suggestions for running/debugging Tapestry using Tomcat
5.5 and working in Eclipse?
IE:
a) Should you create the eclipse project as a dynamic web project
or just a java project or some sort of J2EE project?
b) Does a maven-built project
AFAIK maven2 is still being used for the project, although a jar
apparently for maven ant tasks appeared in the repo not too long ago. My
understanding is that T5 will continue to be distributed by way of maven
+ repos - poms and all (based on HLS' own responses on this list). I
think maven
hi all,
is there a way to extend the tapestry 5 upload component for some sort of ajax progress. seems that
commons fileupload allows to hook in a ProgressListener for ServletFileUpload.
My second question is, how can i set the initial sortorder for a grid in
tapestry 5.0.11?
thank you for
Jesper Zedlitz wrote:
Alec Leamas wrote:
- The paging policy with a fixed number of numbered pages is hardcoded
and can't be changed. Other policies e. g., overlap between pages
Isn't that something you can handle inside your own GridDataSource? With the
page number, the number of
Peter,
Howard's frustration with Maven comes in the development OF Tapestry, as
opposed to development WITH Tapestry. Things that once worked suddenly
break as Maven plugins get updated. This has come up from time to time in
the Dev list.
I've hit similar things, but the visibility (I'm not
If Page or Component defines Enum internally, Tapestry throws a
ClassCastException the moment said page or component class (or even
the template) is hot reloaded due to any kind of change.
Can this be fixed/change to allow inner Enums?
-adam
as of 5.0.11
I'm kind of surprised about that; are you storing the enum values
outside of the page instance (i.e. in the session?)
Inner classes are loaded by the disposable component class loader (the
class loader that handles retry logic and class transformation). When
a class changes, the class loader,
We're using/investigating Tapestry5 by using our own Ivy repository,
which has the required dependencies installed.
Working your way through Tapestry (luckily) doesn't force you in using
Maven - I gave up on that piece of junk long time ago.
Peter Beshai wrote:
Sorry if this has been
This is most likely due to serialization of the enum in the session,
I use a workarround that does not affect the code too much,
and I can track references to the enum.
I persist a string variable, but always use enum.name()
to change the variable.
I use this to keep track of major blocks that
That makes totally perfect sense, and yes, I am storing an enum value
in session. So I had enum defined internally in the page, and then
@Persist on its value... I understand the limitation, and I can only
image what cool things could be accomplished if Tapestry was budnled
with embedded
Yeah, I haven't thought of that. I'll give it a shot, it just may work for us :)
On Tue, Mar 25, 2008 at 5:03 PM, Davor Hrg [EMAIL PROTECTED] wrote:
This is most likely due to serialization of the enum in the session,
I use a workarround that does not affect the code too much,
and I can
An idea:
I belive it has many pitfalls :(, but might be useful an idea,
tapestry could for example extend such enum (persist worker might trigger
it)
and add serialization code to it. Then when reloading it could force
serializing enum values, plus if the value gets serialized outside tapestry
it
There's certainly an issue that if the Grid component grew to
encompass every possible user's most remote needs, the end result
would not be useable by anybody (a Grid component with 27 required
parameters of which six are detailed interfaces, etc., etc.). The
point is, the common components need
Hi,
Can we access multiple databases with Tapestry-Hibernate? any tips to do
this? Thanks.
--
View this message in context:
http://www.nabble.com/t5%3A-multiple-databases-with-Tapestry-Hibernate-tp16294517p16294517.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
Actually, I was able to get this done.
I had to contributeValidationMessagesSource to get the messages.
And to get to the current page component from within the Validator, I
was able to do this:
public static void contributeFieldValidatorSource
(MappedConfigurationString, Validator
Angelo,
I do this routinely using Hibernate via Spring and tapestry-spring, but I
haven't tried it with tapestry-hibernate. Looking at the source:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-hibernate/src
So to finish this thread, the workaround is to create your own
component, copy the entire Select component source, and make one change:
void beginRender(MarkupWriter writer) {
writer.element(select, name, getControlName(), id,
getClientId());
_validate.render(writer);
Hey guys,
I think I found an easy solution for IE7. Just put the following line on
top of the HTML you spit out.
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN
http://www.w3.org/TR/html4/strict.dtd;
--
View this message in context:
49 matches
Mail list logo