add following instruction after you have started the thread:
Thread.currentThread().join()
changes are good that you main program (process) is terminated
before the thread is started.
g,
kris
hua.jiang [EMAIL PROTECTED]
10.09.2008 04:35
Bitte antworten an
Tapestry users
I have a page with:
@Secured(User.ROLE_USER)
public class Page1 extends MyAbstractPage {
void onActivate(long someId) {
Some initialization takes place here. No check against user role, cause
we believe we're secured!
}
}
If I call this without context like this:
Hello,
I want to know what values can be assigned to
@OnEvent(value=???, component=somecomponent) i kwon only selected and
submit
any event that the referenced component can fire :)
ActionLink - onEvent(value=action,component=actionlink)
Form - onEvent(value=prepare,component=form)
...
the possible events should be documented by the component reference
(see ActionLink or Form component reference for example)
g,
kris
Wow. Lots of changes since 5.0.6.
For starters, at 5.0.12, the root package for Tapestry code changed to
org.apache.tapestry5.
Take a look at:
http://tapestry.apache.org/tapestry5/upgrade.html
I mix m2eclipse and command-line maven. I find m2eclipse handy for
on-the-fly additions, but I
Following up on my previous post, there was a thread back around 5/21 where
HLS gave the following tip for updating the package names:
find . -name \*.java -o -name \*.xml -o -name \*.properties |
xargs sed -i s/org\\.apache\\.tapestry\\./org.apache.tapestry5./g
-Original Message-
I really can't believe that the code has changed so much that the tutorial on:
http://wiki.apache.org/tapestry/Tapestry5Training
does not work with the latest Tapestry5.
Why were the package names changes to tapestry5 ?
Has anyone a working version of this tutorial?
Well Still no solution except for brute force specifying commons-pool-1.4 in my
webapp pom.
commons-dbcp-1.2.2 has nothing to do with it but shows up as a parent in the
tree for it.
Still do not know whats pulling commons-pool-1.3 in.
Here is the tree...
I'm not sure why Maven would favor 1.3 over 1.4... You could either
explicitly add commons-pool 1.4 to your pom, or exclude 1.3 from your
commons-dbcp dependency so that it will be ignored. Off the top of my
head, something like this:
dependency
...
artifactIdcommons-dbcp/artifactId
Well, those wiki articles are only accurate as long as someone keeps them up to date with all the
framework changes. In this case this wiki article was written against 5.0.7 and there have been lots
of changes since then which is normal for a framework still in development.
I warmly recommend
there is an updated (mavenized) package for using with
tapestry5.0.15-SNAPSHOT
at http://wiki.apache.org/tapestry/Tapestry5Training
2008/9/10 [EMAIL PROTECTED]
I really can't believe that the code has changed so much that the tutorial
on:
http://wiki.apache.org/tapestry/Tapestry5Training
Hi,
take a look at this article if you interested.
http://joshuajava.wordpress.com/2008/09/11/a-glimpse-of-wicket-14-and-tapestry-5/
--
sincerely yours
M. H. Shamsi
It's a good comparison.
I'll probe at the job to see if I can publish some of the internal analysis
that led to the selection of Wicket over Seam Tapestry as the web
framework for future development (initially internally, later external).
Some of the conclusions there were quite practical, and
13 matches
Mail list logo
