On Fri, 07 Dec 2012 20:05:45 -0200, Ken in Nashua
wrote:
The problem I have with these replies...
Is no body wants to demonstrate with syntax using code
Are you sure we're talking about the same user mailing list?
Its guesswork
sure I have used block component before but semantically how
In 5.3.6, I got this error if I use a form based submission. How do I avoid
this? There was no such error prior to 5.3.6.
Thanks.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Forms-require-that-the-request-method-be-POST-and-that-the-t-formdata-query-parameter-have-va
*
You are closing the t:beaneditor element.
*
**
On Fri, Dec 7, 2012 at 5:22 PM, Ken in Nashua wrote:
>
> Well here is the code...
>
> It yeilds same solution from Josh snippet.
>
>
>
>
>
>
This code is so long in the past (5+ years?) that it is hard to recollect
what's going on here.
I can't think of anything that would cause this normally. I'd have to check
the rendered markup page to see if anything odd is going on there.
On Fri, Dec 7, 2012 at 8:00 AM, mr...@renovosoftware.com
Well here is the code...
It yeilds same solution from Josh snippet.
or
${message:org.tynamo.i18n.
Thanks josh...
there is a bit of confusion on my part...
block
block parameter
block component
concepts and terms
my fault...
and if the code wasnt up to snuff I can fix that easy too.
I will give that a shot
Hey Ken.
Your question was poorly formatted. You didn't include the code that was
failing except the snippet that was reported in the exception. Extracting
that code is extra work that I have to do to figure out what you're doing
wrong.
If you aren't going to take the time to format good question
The problem I have with these replies...
Is no body wants to demonstrate with syntax using code
Its guesswork
sure I have used block component before but semantically how ?
I wish things could be more generous.
On Fri, 07 Dec 2012 17:53:48 -0200, Howard Lewis Ship
wrote:
I believe the tacit understanding is that if you are adding fields to a
component, your are responsible for them operating correctly in
production. Generally speaking, fields are only added to support
injected data needed
by an
I believe the tacit understanding is that if you are adding fields to a
component, your are responsible for them operating correctly in production.
Generally speaking, fields are only added to support injected data needed
by an instance at runtime.
This must be documented better; the question is w
Sorry for how old of a version this is in regards to (4.1.6), but this is the
version which the company I work for uses, and I am tasked with getting it
to work as intended.
After reviewing the logs from one of our clients, I noticed a number of
exceptions being thrown by the DataSqueezer, like t
On Fri, 07 Dec 2012 10:51:44 -0200, captain_rhino
wrote:
Embedded components
It's a little weird to talk in Tapestry about embedded components because
all components can be used inside another component and pages are 99% the
same as components.
How can I pass the Text field component
Hi,
first remove the id parameter from the @Component annotation; this is
only needed if the field name in the java class is different from the
t:id attribute in the template.
second because you already defined your component in the template you
don't have to declare it in your java class; so you
Embedded components
I have a page (welcome) in which I am looking to use a custom
simpletextfiled component to display numerous text fields (in the future I
envisage simpledate and simple select components, The simpleTextfield
contains numerous other divs, css and other components).
public class
Hmm... looks like a bug. PlasticClassImpl uses this.fields in
getUnclaimedFields() but never adds to this.fields in introduceField().
public PlasticField introduceField(String className, String
suggestedName)
{
check();
assert PlasticInternalUtils.isNonBlank(className);
I did not see it ! you have to put the parameter block inside the
beaneditor component.
2012/12/7 Thiago H de Paula Figueiredo
> On Fri, 07 Dec 2012 09:00:21 -0200, Ken in Nashua
> wrote:
>
> classpath:org/tynamo/examples/**hibernatesecurity/pages/Edit.**tml: Block
>> parameters are only allo
On Fri, 07 Dec 2012 09:00:21 -0200, Ken in Nashua
wrote:
classpath:org/tynamo/examples/hibernatesecurity/pages/Edit.tml: Block
parameters are only allowed directly within component elements.
The error message is very clear. :)
--
Thiago H. de Paula Figueiredo
-
I have a question (possibly a bug) for the UnclaimedFieldWorker class.
Suppose i have a worker class implementing ComponentClassTransformWorker2,
this class adds extra fields to the class using plastic:
plasticClass.introduceField
Now it looks like this field is gonna be missed in the UnclaimedFi
Thanks Manu...
But it leads to another new error.
?
org.apache.tapestry5.ioc.internal.OperationExceptionFailure
parsing template
classpath:org/tynamo/examples/hibernatesecurity/pages/Edit.tml: Block
parameters are only allowed directly within component
elements.locationclasspath:org/tynamo
Have you tried this syntax ?
Manu
2012/12/7 Ken in Nashua
> editor field.
>
> Can anyone post the proper syntax? I have searched all messages and posts.
> It is
>
--
Emmanuel DEMEY
Ingénieur Etude et Développement
ATOS Worldline
+33 (0)6 47 47 42 02
demey.emman...@gmail.com
http://em
Hi Folks,
I am receiving the following error when attempting to model a different
bean-editor field.
Can anyone post the proper syntax? I have searched all messages and posts. It
isn't clear to me how to specify proper syntax in order to override property
fields.
Thanks
Ken
87.04% unrealiz
Update: "Clicking the link, it shortly fades
out the zone and then it appears normal." -> solved: by adding to the
eventlink the parameter t:zone with the appropriate id name.
Now I run into the next issue: "Element theZone does not have an associated
Tapestry.ZoneManager object"
What is it about
Hi Lance, thanks for the explanation, will try the workaround in the JIRA.
Adam.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-3-6-AfterRenderTemplate-getElement-returns-element-of-parent-component-tp7583912p7583931.html
Sent from the Tapestry Users mailing list
It also seems the ZoneUpdater.js is not a declared script on the page. Where
should this js be located in the project source tree?
- Original Message -
From: John
To: Tapestry users
Sent: Friday, December 07, 2012 8:16 AM
Subject: Re: ZoneUpdater js issue
I'm using Tpaetsr
I'm using Tpaetsry with jQuery as $T, also found this from IE, maybe my app
module is not configured properly?
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0;
GTB7.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; MDDR;
.NET CLR
When I click on a user on the select id=user component in the form below, I get
an error "Unable to locate Ajax Zone '' for dynamic update.".
Any ideas why please?
26 matches
Mail list logo
