Do i see a Patch comming in from matej? ;)The contract is more or less this:if you pass null into the call then the model object is guaranteed to give the root object of the model.The root object is pretty much always the object that is specified through the constructor.
And yes this also is true
Can you give examples of those objects? Can't you put them in the
scope of the components they are needed for?
One trick is to use an object that contains the objects you plan to
work with, and make your models work on that.
Eelco
On 5/31/06, Vincent Jenks [EMAIL PROTECTED] wrote:
I've got a
+1
On Wed, 2006-05-31 at 20:47 -0600, VGJ wrote:
I might just be nit-picking here...but it might be nice to have a parameter-less override of getObjectjust for prettiness ;) It might be more intuitive for the first-time user as well? It would be more apparent, IMO, if you could just
and what should that paremeterless override pass in to the getObject(Component c)? null? that will work, but will break down if you have a compound model - and more often then not you do.so i dont know if this is such a good thing
-IgorOn 6/1/06, Aaron Hiniker [EMAIL PROTECTED] wrote:
Plus those methods are redundant. It would just clutter the interface.
The contract is well defined. Maybe javadoc of get/setModelObject should
be improved a little and state explicitly what the argument is and how
it is used?
-Matej
Igor Vaynberg wrote:
and what should that paremeterless
Enhanced JavaDoc for IModel would be very useful. When I started with
Wicket, this took quite some time for me to grasp. After that, a lot
of problems I had where suddenly easy to solve :)
--
greetings from Berlin,
Rüdiger Schulz
Matej Knopp wrote on 01.06.2006 at 18:46:
Plus those methods
Agreed, the solution was absurdly simpleI was just entirely unsure
what to pass for the argnull seems very counter-intuitive to the
framework *user*.
On 6/1/06, Rüdiger Schulz [EMAIL PROTECTED] wrote:
Enhanced JavaDoc for IModel would be very useful. When I started with
Wicket, this
pass in the component that is accessing the model - that is whatever component is calling getObject-IgorOn 6/1/06, Vincent Jenks
[EMAIL PROTECTED] wrote:Agreed, the solution was absurdly simpleI was just entirely unsure
what to pass for the argnull seems very counter-intuitive to
That wasn't my point, really. I'm not saying null doesn't work...I'm
just talking purely about elegance here...getObject() is sexier ;)
It also just makes sense to the user.
What can I say...I'm picky.
On 6/1/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
pass in the component that is accessing
But getObject() can't work if you have a property model. It will only
work with simple models.
-Matej
Vincent Jenks wrote:
That wasn't my point, really. I'm not saying null doesn't work...I'm
just talking purely about elegance here...getObject() is sexier ;)
It also just makes sense to the
Point takenno biggie.
On 6/1/06, Matej Knopp [EMAIL PROTECTED] wrote:
But getObject() can't work if you have a property model. It will only
work with simple models.
-Matej
Vincent Jenks wrote:
That wasn't my point, really. I'm not saying null doesn't work...I'm
just talking purely
I've got a page where I need to call data from the EntityManger (EJB3)
several times in a single pagewhich means I'd need to have several
detached-models in the page.
Once I put these objects and/or collections of objects into a
detachable model, what's the best way to cast them back out to
I'm not sure I understand you but you load the collections separately?
Can't you just do something like this?
class MyPage extends Page {
public MyPage() {
IModel m1 = new LoadableDetachableModel() {
Object load() {
return [load collection 1];
}
}
add(new
If I were just displaying the lists in a ListView that'd be fine,
however I'm not using it that way.
Suppose myDetachedModel is being displayed in a ListView and on each
iteration, I'm grabbing a value from the database (here's where I need
another detachable model) and doing calculations
Suppose you have
IModel model = new LoadableDetachableModel() { ...
you can get the model any time:
ListItem myItems = (ListItem) model.getObject(null).
First time you call getObject the model is attached (list is loaded).
Until it's detached, getObject(null) will always return the loaded
Excellent, that's perfect. The part I was unsure about was what to
pass for the arguement for getObject()
Thanks Matej!
On 5/31/06, Matej Knopp [EMAIL PROTECTED] wrote:
Suppose you have
IModel model = new LoadableDetachableModel() { ...
you can get the model any time:
ListItem myItems =
:) Yeah, getObject is a little confusing at the beginning. The parameter
is mostly used in compound models (CompoundPropertyModel) where the
model is shared between multiple components to determine which component
is setting/getting the value.
-Matej
Vincent Jenks wrote:
Excellent, that's
A trick that work even better is to wrap the models you want to work
with in a model for the sake of passing detach to the wrapped models.
That wrapper model would have a couple of convenience methods to get
the values of the wrapped models, and the wrapper model would be the
model to set on your
I might just be nit-picking here...but it might be nice to have a parameter-less override of getObjectjust for prettiness ;) It might be more intuitive for the first-time user as well? It would be more apparent, IMO, if you could just call model.getObject()
Just a thought...
On Wed,
19 matches
Mail list logo
