i have an admin page that creates a link that would reside on another
page and refer to a component on that other page. i implemented it by
injecting the page loader and the link source and creating the link that
way. however, both the page loader and link source are internal
services which
(you can use single quotes
interchangably).
Use RenderSupport to add a $('id').observe("click", someFunction); and avoid
inline JavaScript.
On Tue, Jun 16, 2009 at 3:58 PM, Tom Zurkan wrote:
i can't find who the culprit is yet. but, by the time i am out of
AjaxPartial
i can't find who the culprit is yet. but, by the time i am out of
AjaxPartialResponseRendererImpl, the content has been changed so that
double quotes are replaced. this seems to cause some problem with
enclosed javascript such as onclick="somefunction('var');" becomes
onclick='somefunction('
here are syntax errors....
Thanks!
Tom Zurkan
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
so, i have a page that has many components with zones and blocks. the
page loads fine, but, when i try and submit on a form that uses a zone i
get javascript errors while rendering the block. these are probably my
own javascript problems, but, the ie script debugger is not finding the
right l
Fantastic idea! Worked like a charm.
Thanks,
Tom
Robert Zeigler wrote:
Sure... contribute a custom ValueEncoder for your data type? :)
Robert
On May 29, 2009, at 5/293:44 PM , Tom Zurkan wrote:
ah, knew it was something like that... thank you! gotta change all
my loops to use formState
nevermind... my bad... we are decorating the asset source and i didn't
implement the new getResource method... works now... that had me stumped
for a while... :)
thanks for the great learning experience!
tom
Tom Zurkan wrote:
deleted my repository and rebuilt it to make sure that
deleted my repository and rebuilt it to make sure that only 5.1.0.5 was
available. still got the same problem. i have the following in my
classpath for tapestry:
develop/m2repo/repository/org/apache/tapestry/tapestry-core/5.1.0.5/tapestry-core-5.1.0.5.jar
:/develop/m2repo/repository/org/apach
rt
On May 29, 2009, at 5/291:06 PM , Tom Zurkan wrote:
Yep. I stumbled on that in the component docs and that did the
trick. I was wondering what had changed?
Siddhartha Argollo wrote:
Have you tried to set the property formState of the Loop component
to LoopFormState.NONE? That worked for
Yep. I stumbled on that in the component docs and that did the trick.
I was wondering what had changed?
Siddhartha Argollo wrote:
Have you tried to set the property formState of the Loop component to
LoopFormState.NONE? That worked for me.
Tom Zurkan wrote:
it appears that the encoder
it appears that the encoder/decoder now uses the type coercer. did it
use that before? i thought it used serialization or simply toString as
the default. anyway, when decoding the object, it fails because it does
find JDO->Id->Long->String to encode. but, it does not have String->JDO
decode
xplain() method that is useful for
getting it to explain what set of coercions will be used.
On Wed, May 27, 2009 at 2:17 PM, Tom Zurkan
wrote:
more info.. this is apparently coming from a form submit... and it was
going...
String->Long->Id but, it is failing going from String (which is
more info.. this is apparently coming from a form submit... and it was
going...
String->Long->Id but, it is failing going from String (which is the
id (i.e. long)) to a JDO.
Thiago H. de Paula Figueiredo wrote:
Em Wed, 27 May 2009 17:34:15 -0300, Tom Zurkan
escreveu:
basica
basically, a jdoid...
Thiago H. de Paula Figueiredo wrote:
Em Wed, 27 May 2009 17:13:49 -0300, Tom Zurkan
escreveu:
updating from 5.0.1.8 to 5.1.0.5 String->Long->Id used to work
but now it does not. i am putting in the String->Id coercer but am
wondering why this stoppe
updating from 5.0.1.8 to 5.1.0.5 String->Long->Id used to work but
now it does not. i am putting in the String->Id coercer but am
wondering why this stopped working?
thanks,
tom
-
To unsubscribe, e-mail: users-unsubscr..
Looked through the classpath and everything is using 5.1.0.5
Thiago H. de Paula Figueiredo wrote:
Em Fri, 22 May 2009 22:59:16 -0300, Tom Zurkan
escreveu:
i am upgrading from 5.0.18 to 5.1.05. any ideas would be appreciated.
Make sure you only have 5.0.1.5 JARs in your classpath. A
i keep getting an exception when trying to create the
ComponentMessagesSource
/ public ComponentMessagesSourceImpl(
@Symbol(SymbolConstants.APPLICATION_CATALOG)
Resource appCatalogResource,
ClasspathURLConverter classpathURLConverter)
{
this(appCatalo
i am upgrading from 5.0.18 to 5.1.05. any ideas would be appreciated.
thanks,
tom
2009-05-22 18:51:34,709 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - No service implements the interface
org.apache.tapestry5.ioc.Resource.
2009-05-22 18:51:34,709 [btpool0-1] ERROR
org.apache.tapestr
Since contributeMetaDataLocator defines meta that cannot be overridden
with anything other than a @Meta tag, is there a way to define defaults
that can be overridden by contributeMetaDataLocator or equivalent?
Thanks,
Tom Zurkan
Just used a decorator on ComponentClassResolver
Thanks,
Tom Zurkan
Tom Zurkan wrote:
How can I guarantee that my LibraryMapping is going to override the
Tapestry Module LibraryMapping since the contribution's ordering is
random?
I am contributing a componentClassResolver LibraryMa
or a
component. This worked in Tapestry 5.11 but doesn't in 5.16. Was it
just by chance that it worked before?
Any help would be greatly appreciated.
Thanks,
Tom Zurkan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Why are application defaults not overridable? It seems perfectly
logical that you would define something as a default in a sub module and
then want to override it in the base application module. Am I missing
something?
Thanks,
Tom
---
FYI:
Event.stop(domevent) is throwing an exception in firefox 2. It works in
IE as the comment in the code suggests and it might work if it was
domevent.stop(). But, the exception is what I'm seeing right now.
Hope this makes sense.
Thanks,
Tom
Tom Zurkan wrote:
By the way this
;
}
preventSubmission is equal to true.
Tom Zurkan wrote:
I've been adding log statements to the tapestry.js and everything is
set up correctly. However, the event comes in as undefined which I
think causes the submission to go through (not sure about this because
the xhr call is not happening). But
.stop(domevent). I have seen this work intermittently on firefox
2.0. Works fine on ie. Help!
thanks,
tom
Tom Zurkan wrote:
I am calling form.onsubmit through javascript. I am having problems
with forms and zones on firefox 2. I get "event has no properties" in
prototype.js(line 38
I am including the annotation SubModule In one of the sub modules I
call contributeMetaDataLocator and set up default values for my meta
data. In my AppModule, I also call contributeMetaDataLocator to
override the default. The problem is that my AppModule contribute is
being called first
I am calling form.onsubmit through javascript. I am having problems
with forms and zones on firefox 2. I get "event has no properties" in
prototype.js(line 3801). The thing is, it works on IE 7 with no
javascript errors. Anyone else aware of this problem? This also worked
on tapestry5.11.
27 matches
Mail list logo
