Whoa - stepping through a Tapestry request cycle, now that is alot of
dynamic code! It was a bit difficult to follow all that jit thread-specific
object creation ... especially since things were happening in placed I
didn't have breakcpoints ... but eventually, I think I got what I needed.
Basical
>
> Ah - (#1) I thought this was going to work - since only one or the other
> block would be used at any given time. Since we are using the same java
> class for either / or block ... it strikes me that I can't reuse t:id.
>
> It doesn't matter if you use a component or not, they should have uniq
Em Tue, 17 Feb 2009 20:25:49 -0300, Luther Baker
escreveu:
I had to strip a few parameters out and print literals for now. My next
question ... is how to get MY data into that class.
That's why @Environmental private PropertyEditContext context is there. ;)
It is the bridge that takes you
Got it! I can see my blocks rendering appropriately for both editable and
non-editable fields.
To come full circle, I need to better understand AppPropertyEditBlock.java.
I had to strip a few parameters out and print literals for now. My next
question ... is how to get MY data into that class.
p
Em Tue, 17 Feb 2009 18:42:22 -0300, Luther Baker
escreveu:
You guys are great! Making more sense all the time...
You have just said nonsense! :p
Create and Edit (uses editable block) pages - Tapestry can't seem to
find: AppPropertyEditBlocks.tml
AppPropertyEditBlocks, or any other name
You guys are great! Making more sense all the time...
Ok, here is a small remaining problem and it is related to finding the
AppPropertyEditBlocks (tml and java) artifacts. I've included each step here
just to be sure I understand how the fit together. I intentionally left off
the SelectModel for
Em Tue, 17 Feb 2009 18:13:51 -0300, Luther Baker
escreveu:
It trickie since it seems that Tapestry could call toString() on anything
without requiring this registration step. In this simplistic case,
registration didn't really tell it anything. But - given this
registration
step - a few th
@Uli
false - that makes sense. I will apply it in my next post which actually
uses this method.
@Thiago
>> I'm not sure why assigning the name "classification" Classification
suddenly makes this work ...
> I guess it works because someone told Tapestry that it is a known type.
Yes - but doesn
If you want to specify a block for displaying your type, you just do the
same as with the editor but instead you contribute it with
public static void
contributeBeanBlockSource(Configuration
configuration)
{
configuration.add(new BeanBlockContribution("school",
"AppPropertyEditBlocks", "
Em Tue, 17 Feb 2009 16:55:03 -0300, Luther Baker
escreveu:
If I am happy with using an Entities toString() method ... is this safe
to say:
I guess so.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
-
Em Tue, 17 Feb 2009 16:48:05 -0300, Luther Baker
escreveu:
Now consider List.tml:
If I use a t:Grid out of the box, I get a runtime complaint when I try to
display a Topic,
"does not contain a property named 'classification'"
I assume this is because 'Classification' is not on the list
If I am happy with using an Entities toString() method ... is this safe to
say:
For DISPLAYing an Entity via its "toString" method in something like t:Grid
or t:BeanDisplay
(1) add a line to AppModule.contributeDefaultDataTypeAnalyzer and
(2) implement toString() on the entity.
/**
* A
Thanks both of you for your explanations - if you've got a bit of patience
with me, I need to walk through my thoughts to better understand the big
picture here. Thanks in advance for your points and help - they are very
helpful.
Ok, to set the stage in a little more detail: consider a basic GRAI
Here is your overview (assuming that you want to render your list of
schools using a select component):
SelectModel
This is a model of the data you want to render. This could be backed by
a list or some other collection type (there is a type coercer from list
to selectmodel build into tapestr
Em Mon, 16 Feb 2009 22:25:14 -0300, Luther Baker
escreveu:
I want to pass something like this into a BeanEditForm and have the it
invoke school.toString() or possibly, school.getName().
Is not that simple. Besides the label, you need to map from object to
value (option HTML tag) and value
Given two hibernate objects and a many-to-one relationship
school
{
name
}
student
{
firstname
@ManyToOne
school
}
I want to pass something like this into a BeanEditForm and have the it
invoke school.toString() or possibly, school.getName().
I know I can add a t:Parameter to t:BeanEdi
16 matches
Mail list logo
