omfg, you guys COULD just use PropertyListView
-igor
On Wed, Apr 2, 2008 at 5:55 AM, Maurice Marrink <[EMAIL PROTECTED]> wrote:
> You mean item.setModel(new CompoundPropertyModel(item.getModel()));, right? ;)
>
> And no wicket does not keep string references, it uses models so it
> won't have
that 10MB what kind of file is that?
that is the pm-x file?
That always grows to 10MB but that is not the session size
That is a file that holds the last X pages that it can hold in 10MB
so yes by default it will always grow to 10MB as more and more pages will be
added and then it will truncate
j
You mean item.setModel(new CompoundPropertyModel(item.getModel()));, right? ;)
And no wicket does not keep string references, it uses models so it
won't have to. you are jut not using them correct.
Maurice
On Wed, Apr 2, 2008 at 1:58 PM, Java Programmer <[EMAIL PROTECTED]> wrote:
> After all the
After all the answers, I start to think that maybe my question was a bit wrong.
First I put all the hints you were provided into work eg:
item.setModel(new CompoundPropertyModel(item.getModelObject()));
item.add(description = new MultiLineLabel(DESCRIPTION));
but still have in session files (pm-nul
Actually i copied it from my next big commit for wicket, which i'll
send now ;)
Oops i hope i did not forget to make that change.
Maurice
On Wed, Apr 2, 2008 at 1:45 PM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> On 4/2/08, Maurice Marrink <[EMAIL PROTECTED]> wrote:
> > Right Martij
On 4/2/08, Maurice Marrink <[EMAIL PROTECTED]> wrote:
> Right Martijn :) quick copy paste error :)
I hope the copy didn't come from our code
/me eyes his code base...
Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Oh and just in case you were using your carpart object somewhere else
in onpopulate.
Never use final on your jpa objects, instead if you must you can use
final on the model (or the item if you are in a list view)
Right Martijn :) quick copy paste error :)
Maurice
On Wed, Apr 2, 2008 at 1:35 PM,
item.setModel() I suppose?
On 4/2/08, Maurice Marrink <[EMAIL PROTECTED]> wrote:
> It should be:
>
> protected void populateItem(Item item)
> {
>
> item.setModelObject(new CompoundPropertyModel(item.getModel()));
> .
> }
>
>
> Maurice
>
>
> On Wed, Apr 2, 2008 at 1:23 PM, Java Program
It should be:
protected void populateItem(Item item)
{
item.setModelObject(new CompoundPropertyModel(item.getModel()));
.
}
Maurice
On Wed, Apr 2, 2008 at 1:23 PM, Java Programmer <[EMAIL PROTECTED]> wrote:
> I have narrowed my code to:
>
> protected void populateItem(Item item) {
>
>
I have narrowed my code to:
protected void populateItem(Item item) {
final CarPart carPart = (CarPart) item.getModelObject();
item.setModelObject(new CompoundPropertyModel(carPart));
item.add(description = new MultiLineLabel(DESCRIPTION));
Nino Saturnino Martinez Vazquez Wael wrote:
Java Programmer wrote:
I'm little confused now about not using detachable model in places you
have marked - I have in first place to pull the object from item:
Yup thats right. But after that you use that CarPart object raw. When
you provide it
Java Programmer wrote:
I'm little confused now about not using detachable model in places you
have marked - I have in first place to pull the object from item:
Yup thats right. But after that you use that CarPart object raw. When
you provide it to the components...
final CarPart carPart =
I'm little confused now about not using detachable model in places you
have marked - I have in first place to pull the object from item:
final CarPart carPart = (CarPart) item.getModelObject();
which is load() object correctly - i tested it by quickly putting:
@Override
And this way to wrap the detachablemodel:
item.setModel(new CompoundModel(item.getModel()));
Im a little quick on the trigger today..
Nino Saturnino Martinez Vazquez Wael wrote:
And dada, I of course meant compoundpropertymodel.
Nino Saturnino Martinez Vazquez Wael wrote:
How large are the s
And dada, I of course meant compoundpropertymodel.
Nino Saturnino Martinez Vazquez Wael wrote:
How large are the size of your list? Generally you use raw string
values instead of detachablemodels..'
I'd suggest doing it another way, by using a compoundmodel:
protected void populateItem(It
How large are the size of your list? Generally you use raw string values
instead of detachablemodels..'
I'd suggest doing it another way, by using a compoundmodel:
protected void populateItem(Item item) {
final CarPart carPart = (CarPart) item.getModelObject();
item.setM
On Wed, Apr 2, 2008 at 11:38 AM, Nino Saturnino Martinez Vazquez Wael
<[EMAIL PROTECTED]> wrote:
> Are you really sure that your detachablemodels are being used all over?
We create it in CarPartDataProvider from my first post, next we create
DataView based on this provider we implement populate me
Are you really sure that your detachablemodels are being used all over?
Java Programmer wrote:
On Wed, Apr 2, 2008 at 11:15 AM, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
from JPA experience, eager loading of List of Entities is part of what hogs
memory. I have profiles an application bef
On Wed, Apr 2, 2008 at 11:15 AM, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> from JPA experience, eager loading of List of Entities is part of what hogs
> memory. I have profiles an application before that the memory usage just
> kept growing each time my page reference a particular entity th
from JPA experience, eager loading of List of Entities is part of what hogs
memory. I have profiles an application before that the memory usage just
kept growing each time my page reference a particular entity that eager
loads other collection of entities. As soon as I removed the eager load
annot
Hello,
We have problem with serializing webpages - the user session files
growing rapidly (each request about 100KB), we don't know what we have
did wrong - system is based on examples from wicket.apache.org, so it
should work but this large files (10-20MB for some time, after many
request) slows i
21 matches
Mail list logo
