You're right - casting componentResources#getPage works fine.
> @InjectContainer does indeed inject the "parent" of the component. For
> InnerLayout this is the page alright, but for Layout it's actually the
> InnerLayout because Layout is contained in InnerLayout.
Could you clarify the meanin
Hi Filip
That's a typo. The Layout class name should read 'Layout' and not
'InnerLayout' but the relevant code is the same.
> A potential solution would be to use ComponentResources#getPage to get
> your page in a getter and just use that in your layout.
Unfortunately, that won't work. Compo
em to be a conflict).
Should this work?
Richard Hoberman
Page template:
-
//page contents
Inner layout template:
--
//inner layout markup including
Layout template:
//layout markup including
Inner La
rovides a loop field "_pageName", which is not
marked as a property. Would this field need to be cleared via pageDetach to
avoid state hanging around in the pool?
Richard Hoberman
--
View this message in context:
http://www.nabble.com/-T5--Loops---implicit-value--tp19011764p19011764.html
property
expression 'getTitle()').
Where the page class has a simple (non-property) method:
public class MyPage {
...
public String getTitle() {
return "title";
}
...
}
It works fine from within the page and the expansion
${componentResources.page} shows t
o 1.1 are you looking for? I have to say that while
> I've
> been using 1.0 in some projects, 0.4.3 has generally worked for me
> extremely
> well.
>
> Kalle
>
>
> On Mon, Jul 21, 2008 at 2:50 AM, Richard Hoberman <
> [EMAIL PROTECTED]> wrote:
>
, how much
interest is there in co-operating on creating one?
Thanks
Richard Hoberman
FYI, this was discussed at:
[1] http://www.nabble.com/T4.1.3---Upgrade-Dojo-td13621341.html#a14341740
[2]
http://www.nabble.com/-T4.1--Alternate-JS-library-and-tapestry.event.buildEventProperties-td15470996.html
to setup, but it has been much more
> flexible and robust for our needs.
>
> HTH
>
> Ben
>
> On Wed, Jul 2, 2008 at 2:55 AM, Richard Hoberman
> <[EMAIL PROTECTED]> wrote:
>>
>> Hi All
>>
>> Under certain conditions, the autocompleter ig
.
I'm going to file a bug report, but I'd like to know whether anyone else has
encountered this problem and whether there are any workarounds.
Thanks
Richard Hoberman
--
View this message in context:
http://www.nabble.com/Autocompleter%3A-value-ignored-when-dismissing-dropdown-tp1823215
should work.
A workaround is to have the script you want to execute already in the
template and conditionally render it
On Feb 5, 2008 1:20 PM, Richard Hoberman <[EMAIL PROTECTED]> wrote:
Hi
I'm using Tapestry 4.1.3.
I'm trying unsuccessfully to invoke some javascript after
Hi All
I'm trying to use the "index" and "id" attributes of the "For" component
to create predictable (parseable) ids. I'm getting the following
sequence: item_0, item_0_0, item_1. I was expecting item_0, item_1,
item_2, etc.
Relevant code belo
ans array
.. php recognizes this if input name edns with "[]"
Davor Hrg
On Feb 6, 2008 12:27 PM, Richard Hoberman
<[EMAIL PROTECTED]> wrote:
Thanks (again), Andreas. You are right and I have found a way that
doesn't require using these pairs. I assumed that the POST protocol
I'd prefer not to tie the js so much
to tapestry's internals...
On Feb 6, 2008 12:22 PM, Richard Hoberman
<[EMAIL PROTECTED]> wrote:
Hi All
Below is a form snippet followed by the html generated by Tapestry
4.1.5. The LI element ids are sensibly "For_0" through &quo
as to correspond with
the LI ids?
Am I missing something?
Richard Hoberman
updateComponents="jwcidcityList">
value="ognl:ordering"/>
h this
by setting the custom id on the first child of the "li".
Ultimately I think your first solution is better, because it doesn't
rely on any properties of the model. It's up to the server-side code to
decide how to implement the re-ordering.
Best regards
Rich
Tapestry moves these controls? As far as I can
tell, it is perfectly legal to place an input control of type hidden
within any inline or block content.
Thanks
Richard Hoberman
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additi
meone mentioned that something like this now should work.
A workaround is to have the script you want to execute already in the
template and conditionally render it
On Feb 5, 2008 1:20 PM, Richard Hoberman <[EMAIL PROTECTED]> wrote:
Hi
I'm using Tapestry 4.1.3.
I'm trying unsucces
eRenderSupportImpl (_prs).
Am I approaching this the right way? Any pointers appreciated.
Richard Hoberman
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
18 matches
Mail list logo