P.P.S. Howard pointed out my error with how updateComponents works... Should
be much easier now. Ie instead of :
updateComponents="ognl:{'compA','compB'}"
it's:
updateComponents="compA,compB"
OR
updateComponents="compA"
On 10/14/06, Josh Long <[EMAIL PROTECTED]> wrote:
Hiya Jesse,
OK, th
Ah. Damnit, next time josh...next time...
Fixed and deploy(ing/ed) ;)
On 10/14/06, Josh Long <[EMAIL PROTECTED]> wrote:
Hiya Jesse,
OK, the page you linked me to does indeed work while the page I
presented in a previous email continues to not work..
According to the src for the tapestry-exam
Hiya Jesse,
OK, the page you linked me to does indeed work while the page I
presented in a previous email continues to not work..
According to the src for the tapestry-examples app (Last Changed Date:
2006-10-14 19:52:26 -0700 (Sat, 14 Oct 2006) by jkunhert) Dates.html
that I have the form is up
First things first: have a lot of System.out.printlns or log statements to
see what's going on.
Anyway, I observe that you have a dependency on this code to return a List
succsessfully
setChannelSetup(getCello6DAO().getChannelSetup(getCelloSerialNumber()));
Have you verified that the DAO indee
Yep..
In fact, I just updated the demo pages yesterday, so if you can get this
page to do the same thing I'll believe you ;) :
http://opencomponentry.com:8080/workbench/Home,$Border.pageLink.sdirect?sp=SDates
The submission happens through a Form with async=true
updateComponents=itself as well
No luck there, sad to report.. I flushed the browser session and
everything (which in turn logged me out of gmail!) and the same
problem persists: one ajax request for free and then its all hard
reloads from there...
Anyway, any help is always appreciated, thanks,
Josh
Wait, so you're saying you
muahah! nice catch!
The version of the source i have looks identical to what you just sent
me (ie, its calling dojo.log.debug for the
dojo.log.debug("registerForm(" + id + ") Form already registered,
ignoring."); part, though I confess I didn't bother with a diff.
However, this does remind me of
Did you say "warning" ? Because the latest source I deployed should be using
"info" as the log level. Maybe I need to re-deploy?
http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-framework/src/js/tapestry/form.js?view=markup
On 10/14/06, Josh Long <[EMAIL PROTECTED]> wrote:
I defi
I definitely do... It's happening in IE 6 / FF 1.5. I cleaned out
history/offline files/cookies, etc, etc in both IE and FF..
In IE 6, after the very first page rerender thanks fto the form using
the code I sent you (perhaps as well in FF, but I dont see it as it
may be being intercepted by FireB
And you "definitely" have your browser cache cleared out? Hmm.I can't
reproduce this.
On 10/14/06, Josh Long <[EMAIL PROTECTED]> wrote:
Same old thing, Im afraid. the first time it updates and no form
submit. The second time i click on submit, it does a hard reload...
Thanks,
Josh
On 10/1
Same old thing, Im afraid. the first time it updates and no form
submit. The second time i click on submit, it does a hard reload...
Thanks,
Josh
On 10/14/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
What happens if you change updateComponents to be :
updateComponents="container"
?
On 10/14/
What happens if you change updateComponents to be :
updateComponents="container"
?
On 10/14/06, Josh Long <[EMAIL PROTECTED]> wrote:
An update: I removed the updateComponents parameter and the listener
did indeed run onthe server and no hard refresh was forced. But, of
course, this is still n
An update: I removed the updateComponents parameter and the listener
did indeed run onthe server and no hard refresh was forced. But, of
course, this is still not what is desired, as we need to update the
gui, too..
Thanks,
Josh
On 10/14/06, Josh Long <[EMAIL PROTECTED]> wrote:
At least for me
At least for me, I'm afraid the bug is still present, Jesse.. :-(
I downloaded the latest and greatest iteration of Tapestry snapshot
(org.apache.tapestry tapestry-framework, 4.1.1-SNAPSHOT ) and flushed
out my maven repository to confirm I had the latest and greatest
jars...
The following co
Sure, sounds like you want a numeric-only string. Tapestry has a
Pattern validator, but I don't know if you can specify the pattern
inside your 'validators:' value. I always set up pattern validators
as beans and then reference them in the 'validators:' value, like so:
class="org.apac
Ryan,
Hello again. Is it possible to use a regular expression with a
textfield? I don't want to use it to read a number, but a string.
Thanks
On 14/10/06, Ryan Holmes <[EMAIL PROTECTED]> wrote:
Change this:
to this:
The 'omitZero' property in
org.apache.tapestry.form.translator.NumberTra
Ryan,
Here is some more of my code
public void pageBeginRender(PageEvent pageEvent){
if (!pageEvent.getRequestCycle().isRewinding()){
// if doing a render and the channel list is empty then
obtain a
new channel list and persist.
Without seeing more of your code, my guess it that you are
unconditionally calling setChannelSetup() in your pageBeginRender
method. Something like this:
public void pageBeginRender(PageEvent event) {
setChannelSetup(new ArrayList());
}
Remember that pageBeginRender is called *every
I don't think you need to do any of that configuration anymore as it is
handled by AjaxShellDelegate (which Shell defers this to):
http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-examples/TimeTracker/src/context/WEB-INF/
All available parameters to control these things should be f
Hello,
Quick question with tapestry 4.1.1 - is there a default border
component or do I still have to write my own?
Using my existing border component which worked with Tapestry 4.0.x
and Dojo I now get:
FATAL: Could not load 'dojo.logging.Logger'; last tried
'__package__.js'
FATAL: C
Change this:
to this:
value="translator:number,pattern=#.#,omitZero=false"/>
The 'omitZero' property in
org.apache.tapestry.form.translator.NumberTranslator is true by
default. Paul Ferraro (who I believe contributed much of the
translation and validation system for Tap 4.0) argues tha
Hello,
I've been struggling all day editing persistent page properties and
finding that the values of the properties is not what I expected after
the render phases
The persistant page property is
@Persist
public abstract List getChannelSetup();
public abstract void setChannel
Actually, eclipse will pick up @Component 'type' values during
refactoring if you check the "Update textual occurrences in comments
and strings" option when you rename a component class.
The "bug" you illustrate is a good example of why the type parameter
should be required, at least for th
Oops. The textfield component definition is
On 14/10/06, Jabbar <[EMAIL PROTECTED]> wrote:
Hello again,
I have another problem. It concerns the textfield the defi
Hello again,
I have another problem. It concerns the textfield the definition is
when value is numeric 0 then the textfield also shows a blank. I don't
understand this! Anybody got any ideas?
--
Thank
Jesse,
Can I just take a tapestry 4.0.1 app and drop in the 4.1.1 jars and
make it work?
Thanks
On 14/10/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
It should be I think. If you are comfortable putting tacos into production
then you should feel very safe putting 4.1.1 into production.
For la
It should be I think. If you are comfortable putting tacos into production
then you should feel very safe putting 4.1.1 into production.
For lack of a better analogy you could say that tacos is like the karate kid
- lots of heart .. but when you're ready to totally flip out on someone you
want a
Hello all,
Is there anybody using tapestry 4.1.1 in production? I want to use it
for a production system which is going to be released on Wednesday and
want to create ajax type effects.
--
Thanks
A Jabbar Azam
-
To unsubscribe,
you're not the only one - it takes time to get a hang of PropSelModel - but
once the functionality of PropSel is clear, it's a breeze.
by the way - HL Ship's tapestry in action has a really nice explanation of
PropSel - worth a read.
all the best.
On 10/14/06, Jabbar <[EMAIL PROTECTED]> wrote:
29 matches
Mail list logo