[T5] Integration of Guice in the domain model?

2007-08-09 Thread Donyee
Hi all, I want to use the guice in my t5 app?
does anyone got ideas to use it like  tapestry-spring?



徐 依伟


Re: [T5] Integration of Guice in the domain model?

2007-08-09 Thread Nick Westgate
I haven't looked into it, but search this list.
Back in April Leon Pennings posted about it.

Cheers,
Nick.


Donyee wrote:
 Hi all, I want to use the guice in my t5 app?
 does anyone got ideas to use it like  tapestry-spring?
 
 
 
 徐 依伟

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: createReadOnlyBindingException help!

2007-08-09 Thread Martino Piccinato
Hi Andy,

I do not agree, it's not just a documentation problem I've opened a
bug for the specific Dialog problem:

https://issues.apache.org/jira/browse/TAPESTRY-1699

I think default use just doesn't behave the way you expect it to
behave (that is a bug, even though a minor one).

But I think there's also a generic enhancement to parameters that
could be made that I describe in

https://issues.apache.org/jira/browse/TAPESTRY-1700

I think this could provide a new interesting feature and many
misunderstanding like the one me and Andrea (I guess) had.

If you think it's useful I could provide some code


On 8/9/07, andyhot [EMAIL PROTECTED] wrote:
 Well, it looks like the hidden parameter is an in-out one,
 and it's probably that way by design I guess. The 'value' and 'index'
 parameters of @For
 work similarly but that's more straightforward after reading the docs.

 Anyway, I think we should just document this.

 Martino Piccinato wrote:
  Finally I think we were both wrong and that I opened two useless tickets:
 
  in fact, as stated in the documentation default-value attribute now
  accept any kind of binding and actually CREATES the binding if no
  other binding is present.
 
  In your case:
 
  org.apache.tapestry.binding.AbstractBinding.createReadOnlyBindingException(
  AbstractBinding.java:115)) when I call into my rewindFormComponent method
  this code:
 
  setStartRow(sliderValue);
 
  and I set into jwc file:
  parameter name=startRow required=no cache=true
  default-value=ognl:0/
 
  means that at some point, during rewind, some of your code/components
  is calling a setStartRow to update the binding but the binding is
  invariant (ognl:0 is a costant!) so it's a read only binding (you
  can't change the value of a constant) so the
  ReadOnlyBindingException is correctly throwned.
 
  What you should do (if you really need to change the bound value) is
  bind to a containing component method (e.g. value=ognl:currentRow)
  that will contain the logic of when to return the default value and
  when not to.
 
  It's also possible NOT TO BIND the parameter by default, initializing
  the parameter method after the component finishLoad() phase, in your
  case it would be:
 
  In jwc:
  parameter name=startRow/
 
  In component:
 
  public void finishLoad() {
super.finishLoad();
setStartRow(0);
  }
 
 
  The fact is that default-value with invariant values (literal,
  ognl:constant, ecc.) make sense just if it's a read only binding, At
  the same time default-value with ognl expressions referring to
  containing component methods would break component encapsulation
  making assumptions on the exact method signature the containing
  component should implement (also its optional/default status would be
  questionable...).
 
  As for my specific Dialog component problem I think there's still a
  bug because the component IS actually trying to write the invariant
  default-value binding in hide/show methods so after 2 invalid ticket I
  hope I'm goig to open a valid one now.
 
 
 
  On 7/30/07, Martino Piccinato [EMAIL PROTECTED] wrote:
 
  Posted one for the parameter issue
 
  https://issues.apache.org/jira/browse/TAPESTRY-1682
 
  and another one for the Dialog component:
 
  https://issues.apache.org/jira/browse/TAPESTRY-1683
 
  I didn't do it first because I was trying to investigate myself but I
  really have no time to do this now.
 
  Ciao
 
  Martino
 
  On 7/30/07, Andrea Chiumenti [EMAIL PROTECTED] wrote:
 
  Well, I try to investigate into this, meanwhile if you could be so kind to
  post a jira...
 
  ciao,
  kiuma
 
  On 7/30/07, Martino Piccinato [EMAIL PROTECTED] wrote:
 
  Well, I'm having a very similar behaviour with Dialog component that
  by default has a true parameter for optional parameter hidden.
 
  parameter name=hidden default-value=true /
 
  It seems that if you set a constant value (ognl:0 or true) to a
  parameter then the parameter itself is regarded as Invariant by
  AbstractBinding that will refuse you to use any setter on it (it does
  not have a reference to a method but to a... constant) and throw the
  exception.
  I don't have the exception if I just override the constant default
  value with an ognl reference to a couple of setters/getters method
  (returning the default value in case the property is not initialized).
 
  In my opinion this is a bug with parameter but I haven't been able
  to investigate more and I'm quite surprised nobody stepped into this
  problem before, see my neglected Dialog mails  of some days ago :-)
 
 
 
  On 7/30/07, Andrea Chiumenti [EMAIL PROTECTED] wrote:
 
  this is the stack trace
 
 
 
  org.apache.tapestry.binding.AbstractBinding.createReadOnlyBindingException
  (
 
  AbstractBinding.java:115)
  org.apache.tapestry.binding.ExpressionBinding.setObject(
  ExpressionBinding.java:196)
  $EditTable_16.setStartRow($EditTable_16.java)
  org.jfly.web.components.edittable.EditTable.rewindFormComponent(
  

Re: [T5] Integration of Guice in the domain model?

2007-08-09 Thread Donyee
Thanks, I got the idea!

2007/8/9, Nick Westgate [EMAIL PROTECTED]:
 I haven't looked into it, but search this list.
 Back in April Leon Pennings posted about it.

 Cheers,
 Nick.


 Donyee wrote:
  Hi all, I want to use the guice in my t5 app?
  does anyone got ideas to use it like  tapestry-spring?
 
 
 
  徐 依伟

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
徐 依伟


[T4.1]Returning a list to a page

2007-08-09 Thread Paolo Scopa

Hi all,
got a bit blocked here: i need to return a value to the invoking page.
Page A calls page B -
in Page B I select a list of item from a longer list
when I press OK on page B, the browser returns to page A where the list is
set according to the selection made.
I can set the returning page but cant find a way to set there the value to
return.

I tried different ways but cant find a solution.
Any help ?

Paolo

-- 
View this message in context: 
http://www.nabble.com/-T4.1-Returning-a-list-to-a-page-tf4242051.html#a12070675
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1]Returning a list to a page

2007-08-09 Thread Ulrich Stärk
You'll have a property for the list in page A and an abstract setter for this property. So now in 
page B just inject page A using the @InjectPage annotation, call the setter for this list and return 
the page object in your listener method.
Or use the PropertyUtils.write(pageObject, propertyName, valueObject) method in the 
org.apache.hivemind.util package.


Uli

Paolo Scopa schrieb:

Hi all,
got a bit blocked here: i need to return a value to the invoking page.
Page A calls page B -
in Page B I select a list of item from a longer list
when I press OK on page B, the browser returns to page A where the list is
set according to the selection made.
I can set the returning page but cant find a way to set there the value to
return.

I tried different ways but cant find a solution.
Any help ?

Paolo




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1]Returning a list to a page

2007-08-09 Thread Patrick Klein
Hello Paolo,

page a should hold an (persist) abstract getter and setter for the list,
page b hold a persist abstract getter and setter for the name of the
calling page which is set when page b is accessed and maybe reset if
needed in the button's listener.
When you are done with compiling your list on page be and the button is
pressed, do something like the following in the button's listener:

(page b)
public void buttonListener(IRequestCycle cycle) {
[...]
IPage page = cycle.getPage(getPageNameOfA());
page.setList(composedList);
[...]
cycle.activate(page);
}

Regards,
Patrick
 Hi all,
 got a bit blocked here: i need to return a value to the invoking page.
 Page A calls page B -
 in Page B I select a list of item from a longer list
 when I press OK on page B, the browser returns to page A where the list is
 set according to the selection made.
 I can set the returning page but cant find a way to set there the value to
 return.

 I tried different ways but cant find a solution.
 Any help ?

 Paolo

   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1]Returning a list to a page

2007-08-09 Thread Paolo Scopa

Thanks Patrick,
this helps, except that the IPage does not expose the setList method, so i
don't think it would work the
page.setList(composedList);
maybe not even compile.
Paolo


Patrick Klein wrote:
 
 Hello Paolo,
 
 page a should hold an (persist) abstract getter and setter for the list,
 page b hold a persist abstract getter and setter for the name of the
 calling page which is set when page b is accessed and maybe reset if
 needed in the button's listener.
 When you are done with compiling your list on page be and the button is
 pressed, do something like the following in the button's listener:
 
 (page b)
 public void buttonListener(IRequestCycle cycle) {
 [...]
 IPage page = cycle.getPage(getPageNameOfA());
 page.setList(composedList);
 [...]
 cycle.activate(page);
 }
 
 Regards,
 Patrick
 Hi all,
 got a bit blocked here: i need to return a value to the invoking page.
 Page A calls page B -
 in Page B I select a list of item from a longer list
 when I press OK on page B, the browser returns to page A where the list
 is
 set according to the selection made.
 I can set the returning page but cant find a way to set there the value
 to
 return.

 I tried different ways but cant find a solution.
 Any help ?

 Paolo

   
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-T4.1-Returning-a-list-to-a-page-tf4242051.html#a12071237
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1]Returning a list to a page

2007-08-09 Thread Paolo Scopa

Thanks Uli,
only problem is that i was planning to call page B from different pages, so
i dont know which one to inject.
Maybe will try the PropertyUtils.write, even if it seems to be a little
unsafe (does not assure that the property exists in page A when compile).
Paolo


Ulrich Stärk wrote:
 
 You'll have a property for the list in page A and an abstract setter for
 this property. So now in 
 page B just inject page A using the @InjectPage annotation, call the
 setter for this list and return 
 the page object in your listener method.
 Or use the PropertyUtils.write(pageObject, propertyName, valueObject)
 method in the 
 org.apache.hivemind.util package.
 
 Uli
 
 Paolo Scopa schrieb:
 Hi all,
 got a bit blocked here: i need to return a value to the invoking page.
 Page A calls page B -
 in Page B I select a list of item from a longer list
 when I press OK on page B, the browser returns to page A where the list
 is
 set according to the selection made.
 I can set the returning page but cant find a way to set there the value
 to
 return.
 
 I tried different ways but cant find a solution.
 Any help ?
 
 Paolo
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-T4.1-Returning-a-list-to-a-page-tf4242051.html#a12071279
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1]Returning a list to a page

2007-08-09 Thread Patrick Klein
Hello Paolo,

mea culpa, you are correct abot that :)
replace IPage with the A's class (implementing IPage) and cast the
result of cycle.getPage(...) accordingly

Regards,
Patrick
 Thanks Patrick,
 this helps, except that the IPage does not expose the setList method, so i
 don't think it would work the
 page.setList(composedList);
 maybe not even compile.
 Paolo


 Patrick Klein wrote:
   
 Hello Paolo,

 page a should hold an (persist) abstract getter and setter for the list,
 page b hold a persist abstract getter and setter for the name of the
 calling page which is set when page b is accessed and maybe reset if
 needed in the button's listener.
 When you are done with compiling your list on page be and the button is
 pressed, do something like the following in the button's listener:

 (page b)
 public void buttonListener(IRequestCycle cycle) {
 [...]
 IPage page = cycle.getPage(getPageNameOfA());
 page.setList(composedList);
 [...]
 cycle.activate(page);
 }

 Regards,
 Patrick
 
 Hi all,
 got a bit blocked here: i need to return a value to the invoking page.
 Page A calls page B -
 in Page B I select a list of item from a longer list
 when I press OK on page B, the browser returns to page A where the list
 is
 set according to the selection made.
 I can set the returning page but cant find a way to set there the value
 to
 return.

 I tried different ways but cant find a solution.
 Any help ?

 Paolo

   
   
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 

   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Memory leaks in Tapestry 4.1

2007-08-09 Thread munich
Have you ever observed the memory usage for your Tapestry application?

For example, make a simple HelloWorld Application and load the page regularly 
using HTTP_LOAD. Then watch how the memory consumption grows and grows  
especially after an hour.

Has anyone got a solution how avoid this leakage?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1]Returning a list to a page

2007-08-09 Thread Paolo Scopa

And you are right, actually i cant make it working.
It seems that IPage is not serializable, so i cant use the
@Persist(client)

The problem using a string is that, when i return the string from my onOk
listener, the calling page A is activated, but after the return statement
it is too late to set the property we are talking about.
What am i missing?
Paolo
p.s.: thanks for your patience...



Ulrich Stärk wrote:
 
 Where's the problem to do the same thing with the name of the calling 
 page? Store the name in a string property of page B before activating
 it...
 
 Uli
 
 Paolo Scopa schrieb:
 No prob.
 As i said to uli, i might call B from different pages, not only A.
 Maybe i should use a common interface for those pages.
 Ill try and let you know
 Paolo
 
 
 Patrick Klein wrote:
 Hello Paolo,

 mea culpa, you are correct abot that :)
 replace IPage with the A's class (implementing IPage) and cast the
 result of cycle.getPage(...) accordingly

 Regards,
 Patrick
 Thanks Patrick,
 this helps, except that the IPage does not expose the setList method,
 so
 i
 don't think it would work the
 page.setList(composedList);
 maybe not even compile.
 Paolo


 Patrick Klein wrote:
   
 Hello Paolo,

 page a should hold an (persist) abstract getter and setter for the
 list,
 page b hold a persist abstract getter and setter for the name of the
 calling page which is set when page b is accessed and maybe reset if
 needed in the button's listener.
 When you are done with compiling your list on page be and the button
 is
 pressed, do something like the following in the button's listener:

 (page b)
 public void buttonListener(IRequestCycle cycle) {
 [...]
 IPage page = cycle.getPage(getPageNameOfA());
 page.setList(composedList);
 [...]
 cycle.activate(page);
 }

 Regards,
 Patrick
 
 Hi all,
 got a bit blocked here: i need to return a value to the invoking
 page.
 Page A calls page B -
 in Page B I select a list of item from a longer list
 when I press OK on page B, the browser returns to page A where the
 list
 is
 set according to the selection made.
 I can set the returning page but cant find a way to set there the
 value
 to
 return.

 I tried different ways but cant find a solution.
 Any help ?

 Paolo

   
   
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 
   

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-T4.1-Returning-a-list-to-a-page-tf4242051.html#a12072218
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Kristian Marinkovic
do you have Tapestry caching deactivated?




andyhot [EMAIL PROTECTED] 
Gesendet von: Andreas Andreou [EMAIL PROTECTED]
09.08.2007 15:28
Bitte antworten an
Tapestry users users@tapestry.apache.org


An
Tapestry users users@tapestry.apache.org
Kopie

Thema
Re: Memory leaks in Tapestry 4.1






Well, we did lots of tests with 4.1.2 and
have yet to observe such memory leaks.

[EMAIL PROTECTED] wrote:
 Have you ever observed the memory usage for your Tapestry application?

 For example, make a simple HelloWorld Application and load the page 
regularly using HTTP_LOAD. Then watch how the memory consumption grows and 
grows  especially after an hour.

 Has anyone got a solution how avoid this leakage?


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: createReadOnlyBindingException help!

2007-08-09 Thread andyhot

I'm not against 1699 at all!
I'm just saying that it's also a documentation problem

As for 1700, I think the traditional way of doing something like that
has been to declare and use both a parameter and a property... so
i'm not sure if what you're suggesting will help or confuse users - 
waiting for

more comments on this.

Martino Piccinato wrote:

Hi Andy,

I do not agree, it's not just a documentation problem I've opened a
bug for the specific Dialog problem:

https://issues.apache.org/jira/browse/TAPESTRY-1699

I think default use just doesn't behave the way you expect it to
behave (that is a bug, even though a minor one).

But I think there's also a generic enhancement to parameters that
could be made that I describe in

https://issues.apache.org/jira/browse/TAPESTRY-1700

I think this could provide a new interesting feature and many
misunderstanding like the one me and Andrea (I guess) had.

If you think it's useful I could provide some code


On 8/9/07, andyhot [EMAIL PROTECTED] wrote:
  

Well, it looks like the hidden parameter is an in-out one,
and it's probably that way by design I guess. The 'value' and 'index'
parameters of @For
work similarly but that's more straightforward after reading the docs.

Anyway, I think we should just document this.

Martino Piccinato wrote:


Finally I think we were both wrong and that I opened two useless tickets:

in fact, as stated in the documentation default-value attribute now
accept any kind of binding and actually CREATES the binding if no
other binding is present.

In your case:

org.apache.tapestry.binding.AbstractBinding.createReadOnlyBindingException(
AbstractBinding.java:115)) when I call into my rewindFormComponent method
this code:

setStartRow(sliderValue);

and I set into jwc file:
parameter name=startRow required=no cache=true
default-value=ognl:0/

means that at some point, during rewind, some of your code/components
is calling a setStartRow to update the binding but the binding is
invariant (ognl:0 is a costant!) so it's a read only binding (you
can't change the value of a constant) so the
ReadOnlyBindingException is correctly throwned.

What you should do (if you really need to change the bound value) is
bind to a containing component method (e.g. value=ognl:currentRow)
that will contain the logic of when to return the default value and
when not to.

It's also possible NOT TO BIND the parameter by default, initializing
the parameter method after the component finishLoad() phase, in your
case it would be:

In jwc:
parameter name=startRow/

In component:

public void finishLoad() {
  super.finishLoad();
  setStartRow(0);
}


The fact is that default-value with invariant values (literal,
ognl:constant, ecc.) make sense just if it's a read only binding, At
the same time default-value with ognl expressions referring to
containing component methods would break component encapsulation
making assumptions on the exact method signature the containing
component should implement (also its optional/default status would be
questionable...).

As for my specific Dialog component problem I think there's still a
bug because the component IS actually trying to write the invariant
default-value binding in hide/show methods so after 2 invalid ticket I
hope I'm goig to open a valid one now.



On 7/30/07, Martino Piccinato [EMAIL PROTECTED] wrote:

  

Posted one for the parameter issue

https://issues.apache.org/jira/browse/TAPESTRY-1682

and another one for the Dialog component:

https://issues.apache.org/jira/browse/TAPESTRY-1683

I didn't do it first because I was trying to investigate myself but I
really have no time to do this now.

Ciao

Martino

On 7/30/07, Andrea Chiumenti [EMAIL PROTECTED] wrote:



Well, I try to investigate into this, meanwhile if you could be so kind to
post a jira...

ciao,
kiuma

On 7/30/07, Martino Piccinato [EMAIL PROTECTED] wrote:

  

Well, I'm having a very similar behaviour with Dialog component that
by default has a true parameter for optional parameter hidden.

parameter name=hidden default-value=true /

It seems that if you set a constant value (ognl:0 or true) to a
parameter then the parameter itself is regarded as Invariant by
AbstractBinding that will refuse you to use any setter on it (it does
not have a reference to a method but to a... constant) and throw the
exception.
I don't have the exception if I just override the constant default
value with an ognl reference to a couple of setters/getters method
(returning the default value in case the property is not initialized).

In my opinion this is a bug with parameter but I haven't been able
to investigate more and I'm quite surprised nobody stepped into this
problem before, see my neglected Dialog mails  of some days ago :-)



On 7/30/07, Andrea Chiumenti [EMAIL PROTECTED] wrote:



this is the stack trace



  

org.apache.tapestry.binding.AbstractBinding.createReadOnlyBindingException
(


Re: [T4.1]Returning a list to a page

2007-08-09 Thread Martino Piccinato
If I got right what's your case you could use the following pattern:


  public interface CalledPageCallback extends ICallback {

   public void setMyObject(MyClass myObject);

  }


   public class CallingPageCallback implements CalledPageCallback {

 private MyClass _myObject;

 public void setMyObject(MyClass myObject) {
 this._myObject = myObject;
 }

@Override
public void performCallback(IRequestCycle cycle) {
Defense.notNull(cycle, cycle);
CallingPage page = 
cycle.getPage(CallingPage.class.simpleName());
page.setNeededObject(_myObject);
activatePage(cycle,page);
}



   }

public class CalledPage extends BasePage {

   @Persist(client)
   public CalledPageCallback getCalledPageCallback()
   public abstract void setCalledPageCallback(CalledPageCallback cb)

   public abstract MyClass getSelectedObject();
   public abstract void setSelectedObject(MyClass selectedObject);



public void onSubmit(IRequestCycle cycle) {
   callback = this.getCalledPageCallBack();
   callback.setMyObject(getSelectedObject());
   callback.performCallBack(cycle);
}

}


Obviously when calling the CalledPage from the Calling page you'll
have to set the callback but at the same time you can have other
implementation of CalledPageCallback used from other different calling
pages.

We have used this pattern with success on our application, hope it can
be of some help.

On 8/9/07, Paolo Scopa [EMAIL PROTECTED] wrote:

 And you are right, actually i cant make it working.
 It seems that IPage is not serializable, so i cant use the
 @Persist(client)

 The problem using a string is that, when i return the string from my onOk
 listener, the calling page A is activated, but after the return statement
 it is too late to set the property we are talking about.
 What am i missing?
 Paolo
 p.s.: thanks for your patience...



 Ulrich Stärk wrote:
 
  Where's the problem to do the same thing with the name of the calling
  page? Store the name in a string property of page B before activating
  it...
 
  Uli
 
  Paolo Scopa schrieb:
  No prob.
  As i said to uli, i might call B from different pages, not only A.
  Maybe i should use a common interface for those pages.
  Ill try and let you know
  Paolo
 
 
  Patrick Klein wrote:
  Hello Paolo,
 
  mea culpa, you are correct abot that :)
  replace IPage with the A's class (implementing IPage) and cast the
  result of cycle.getPage(...) accordingly
 
  Regards,
  Patrick
  Thanks Patrick,
  this helps, except that the IPage does not expose the setList method,
  so
  i
  don't think it would work the
  page.setList(composedList);
  maybe not even compile.
  Paolo
 
 
  Patrick Klein wrote:
 
  Hello Paolo,
 
  page a should hold an (persist) abstract getter and setter for the
  list,
  page b hold a persist abstract getter and setter for the name of the
  calling page which is set when page b is accessed and maybe reset if
  needed in the button's listener.
  When you are done with compiling your list on page be and the button
  is
  pressed, do something like the following in the button's listener:
 
  (page b)
  public void buttonListener(IRequestCycle cycle) {
  [...]
  IPage page = cycle.getPage(getPageNameOfA());
  page.setList(composedList);
  [...]
  cycle.activate(page);
  }
 
  Regards,
  Patrick
 
  Hi all,
  got a bit blocked here: i need to return a value to the invoking
  page.
  Page A calls page B -
  in Page B I select a list of item from a longer list
  when I press OK on page B, the browser returns to page A where the
  list
  is
  set according to the selection made.
  I can set the returning page but cant find a way to set there the
  value
  to
  return.
 
  I tried different ways but cant find a solution.
  Any help ?
 
  Paolo
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

 --
 View this message in context: 
 http://www.nabble.com/-T4.1-Returning-a-list-to-a-page-tf4242051.html#a12072218
 Sent from the Tapestry - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, 

Re: [T4.1]Returning a list to a page

2007-08-09 Thread Lutz Hühnken
I'm not sure if I understand that correctly... I think the idea was
not return the page name as a string from a submit method, but to set
it..

in page A:
- inject page B
- set the name of page A as a property in page B
- activate (or redirect to) B

in page B:
- do not inject page A, but get it by name through cycle.getPage..
- set the list as a property in page A
- activate (or redirect to) A

To add to the confusion.. if you access that list from many pages,
wouldn't it be better to store it as an application state object
(ASO)?

Hth,

Lutz


On 8/9/07, Paolo Scopa [EMAIL PROTECTED] wrote:

 And you are right, actually i cant make it working.
 It seems that IPage is not serializable, so i cant use the
 @Persist(client)

 The problem using a string is that, when i return the string from my onOk
 listener, the calling page A is activated, but after the return statement
 it is too late to set the property we are talking about.
 What am i missing?
 Paolo
 p.s.: thanks for your patience...



 Ulrich Stärk wrote:
 
  Where's the problem to do the same thing with the name of the calling
  page? Store the name in a string property of page B before activating
  it...
 
  Uli
 
  Paolo Scopa schrieb:
  No prob.
  As i said to uli, i might call B from different pages, not only A.
  Maybe i should use a common interface for those pages.
  Ill try and let you know
  Paolo
 
 
  Patrick Klein wrote:
  Hello Paolo,
 
  mea culpa, you are correct abot that :)
  replace IPage with the A's class (implementing IPage) and cast the
  result of cycle.getPage(...) accordingly
 
  Regards,
  Patrick
  Thanks Patrick,
  this helps, except that the IPage does not expose the setList method,
  so
  i
  don't think it would work the
  page.setList(composedList);
  maybe not even compile.
  Paolo
 
 
  Patrick Klein wrote:
 
  Hello Paolo,
 
  page a should hold an (persist) abstract getter and setter for the
  list,
  page b hold a persist abstract getter and setter for the name of the
  calling page which is set when page b is accessed and maybe reset if
  needed in the button's listener.
  When you are done with compiling your list on page be and the button
  is
  pressed, do something like the following in the button's listener:
 
  (page b)
  public void buttonListener(IRequestCycle cycle) {
  [...]
  IPage page = cycle.getPage(getPageNameOfA());
  page.setList(composedList);
  [...]
  cycle.activate(page);
  }
 
  Regards,
  Patrick
 
  Hi all,
  got a bit blocked here: i need to return a value to the invoking
  page.
  Page A calls page B -
  in Page B I select a list of item from a longer list
  when I press OK on page B, the browser returns to page A where the
  list
  is
  set according to the selection made.
  I can set the returning page but cant find a way to set there the
  value
  to
  return.
 
  I tried different ways but cant find a solution.
  Any help ?
 
  Paolo
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

 --
 View this message in context: 
 http://www.nabble.com/-T4.1-Returning-a-list-to-a-page-tf4242051.html#a12072218
 Sent from the Tapestry - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: createReadOnlyBindingException help!

2007-08-09 Thread Martino Piccinato
You mean you could do something like

property name=hidden initial-value=true /
parameter name=hidden/

?? (don't think so).

Or you just refer about playing with properties and paramters?

I know there are other ways to achieve 1700 but I thought an
initial-value might be clearer,  just because it seems to me that
also the creatot of Dialog got confused with that :-)
To me that default-value instead of default-binding was very
confusing and I think it was the same kind of confusion.

Well, let's see if anybody think this is interesting, otherwise it was
just a good occasion for me to have a look at wonderful Tapestry code
:-)



On 8/9/07, andyhot [EMAIL PROTECTED] wrote:
 I'm not against 1699 at all!
 I'm just saying that it's also a documentation problem

 As for 1700, I think the traditional way of doing something like that
 has been to declare and use both a parameter and a property... so
 i'm not sure if what you're suggesting will help or confuse users -
 waiting for
 more comments on this.

 Martino Piccinato wrote:
  Hi Andy,
 
  I do not agree, it's not just a documentation problem I've opened a
  bug for the specific Dialog problem:
 
  https://issues.apache.org/jira/browse/TAPESTRY-1699
 
  I think default use just doesn't behave the way you expect it to
  behave (that is a bug, even though a minor one).
 
  But I think there's also a generic enhancement to parameters that
  could be made that I describe in
 
  https://issues.apache.org/jira/browse/TAPESTRY-1700
 
  I think this could provide a new interesting feature and many
  misunderstanding like the one me and Andrea (I guess) had.
 
  If you think it's useful I could provide some code
 
 
  On 8/9/07, andyhot [EMAIL PROTECTED] wrote:
 
  Well, it looks like the hidden parameter is an in-out one,
  and it's probably that way by design I guess. The 'value' and 'index'
  parameters of @For
  work similarly but that's more straightforward after reading the docs.
 
  Anyway, I think we should just document this.
 
  Martino Piccinato wrote:
 
  Finally I think we were both wrong and that I opened two useless tickets:
 
  in fact, as stated in the documentation default-value attribute now
  accept any kind of binding and actually CREATES the binding if no
  other binding is present.
 
  In your case:
 
  org.apache.tapestry.binding.AbstractBinding.createReadOnlyBindingException(
  AbstractBinding.java:115)) when I call into my rewindFormComponent method
  this code:
 
  setStartRow(sliderValue);
 
  and I set into jwc file:
  parameter name=startRow required=no cache=true
  default-value=ognl:0/
 
  means that at some point, during rewind, some of your code/components
  is calling a setStartRow to update the binding but the binding is
  invariant (ognl:0 is a costant!) so it's a read only binding (you
  can't change the value of a constant) so the
  ReadOnlyBindingException is correctly throwned.
 
  What you should do (if you really need to change the bound value) is
  bind to a containing component method (e.g. value=ognl:currentRow)
  that will contain the logic of when to return the default value and
  when not to.
 
  It's also possible NOT TO BIND the parameter by default, initializing
  the parameter method after the component finishLoad() phase, in your
  case it would be:
 
  In jwc:
  parameter name=startRow/
 
  In component:
 
  public void finishLoad() {
super.finishLoad();
setStartRow(0);
  }
 
 
  The fact is that default-value with invariant values (literal,
  ognl:constant, ecc.) make sense just if it's a read only binding, At
  the same time default-value with ognl expressions referring to
  containing component methods would break component encapsulation
  making assumptions on the exact method signature the containing
  component should implement (also its optional/default status would be
  questionable...).
 
  As for my specific Dialog component problem I think there's still a
  bug because the component IS actually trying to write the invariant
  default-value binding in hide/show methods so after 2 invalid ticket I
  hope I'm goig to open a valid one now.
 
 
 
  On 7/30/07, Martino Piccinato [EMAIL PROTECTED] wrote:
 
 
  Posted one for the parameter issue
 
  https://issues.apache.org/jira/browse/TAPESTRY-1682
 
  and another one for the Dialog component:
 
  https://issues.apache.org/jira/browse/TAPESTRY-1683
 
  I didn't do it first because I was trying to investigate myself but I
  really have no time to do this now.
 
  Ciao
 
  Martino
 
  On 7/30/07, Andrea Chiumenti [EMAIL PROTECTED] wrote:
 
 
  Well, I try to investigate into this, meanwhile if you could be so kind 
  to
  post a jira...
 
  ciao,
  kiuma
 
  On 7/30/07, Martino Piccinato [EMAIL PROTECTED] wrote:
 
 
  Well, I'm having a very similar behaviour with Dialog component that
  by default has a true parameter for optional parameter hidden.
 
  parameter name=hidden default-value=true /
 
  It seems that if you 

Re: [ANN]T5 book: reviewers are needed

2007-08-09 Thread Howard Lewis Ship
I'd be happy to review the book, of course!

On 8/2/07, Kolesnikov, Alexander GNI [EMAIL PROTECTED] wrote:

 I am writing a book on T5 and the publisher is looking for technical
 reviewers for this book.
 Please contact me directly if you want to review the book or if you have
 any questions.

 Cheers,

 Alexander


 --
 CONFIDENTIALITY NOTICE: If you have received this email in error, please
 immediately notify the sender by e-mail at the address shown.  This email
 transmission may contain confidential information.  This information is
 intended only for the use of the individual(s) or entity to whom it is
 intended even if addressed incorrectly.  Please delete it from your files if
 you are not the intended recipient.  Thank you for your
 compliance.  Copyright 2007 CIGNA

 ==




-- 
Howard M. Lewis Ship
Partner and Senior Architect at Feature50

Creator Apache Tapestry and Apache HiveMind


Re: createReadOnlyBindingException help!

2007-08-09 Thread Andreas Andreou
No, i just meant playing with properties and parameters :)


On 8/9/07, Martino Piccinato [EMAIL PROTECTED] wrote:

 You mean you could do something like

 property name=hidden initial-value=true /
 parameter name=hidden/

 ?? (don't think so).

 Or you just refer about playing with properties and paramters?

 I know there are other ways to achieve 1700 but I thought an
 initial-value might be clearer,  just because it seems to me that
 also the creatot of Dialog got confused with that :-)
 To me that default-value instead of default-binding was very
 confusing and I think it was the same kind of confusion.

 Well, let's see if anybody think this is interesting, otherwise it was
 just a good occasion for me to have a look at wonderful Tapestry code
 :-)



 On 8/9/07, andyhot [EMAIL PROTECTED] wrote:
  I'm not against 1699 at all!
  I'm just saying that it's also a documentation problem
 
  As for 1700, I think the traditional way of doing something like that
  has been to declare and use both a parameter and a property... so
  i'm not sure if what you're suggesting will help or confuse users -
  waiting for
  more comments on this.
 
  Martino Piccinato wrote:
   Hi Andy,
  
   I do not agree, it's not just a documentation problem I've opened a
   bug for the specific Dialog problem:
  
   https://issues.apache.org/jira/browse/TAPESTRY-1699
  
   I think default use just doesn't behave the way you expect it to
   behave (that is a bug, even though a minor one).
  
   But I think there's also a generic enhancement to parameters that
   could be made that I describe in
  
   https://issues.apache.org/jira/browse/TAPESTRY-1700
  
   I think this could provide a new interesting feature and many
   misunderstanding like the one me and Andrea (I guess) had.
  
   If you think it's useful I could provide some code
  
  
   On 8/9/07, andyhot [EMAIL PROTECTED] wrote:
  
   Well, it looks like the hidden parameter is an in-out one,
   and it's probably that way by design I guess. The 'value' and 'index'
   parameters of @For
   work similarly but that's more straightforward after reading the
 docs.
  
   Anyway, I think we should just document this.
  
   Martino Piccinato wrote:
  
   Finally I think we were both wrong and that I opened two useless
 tickets:
  
   in fact, as stated in the documentation default-value attribute now
   accept any kind of binding and actually CREATES the binding if no
   other binding is present.
  
   In your case:
  
  
 org.apache.tapestry.binding.AbstractBinding.createReadOnlyBindingException
 (
   AbstractBinding.java:115)) when I call into my rewindFormComponent
 method
   this code:
  
   setStartRow(sliderValue);
  
   and I set into jwc file:
   parameter name=startRow required=no cache=true
   default-value=ognl:0/
  
   means that at some point, during rewind, some of your
 code/components
   is calling a setStartRow to update the binding but the binding is
   invariant (ognl:0 is a costant!) so it's a read only binding (you
   can't change the value of a constant) so the
   ReadOnlyBindingException is correctly throwned.
  
   What you should do (if you really need to change the bound value) is
   bind to a containing component method (e.g. value=ognl:currentRow)
   that will contain the logic of when to return the default value and
   when not to.
  
   It's also possible NOT TO BIND the parameter by default,
 initializing
   the parameter method after the component finishLoad() phase, in your
   case it would be:
  
   In jwc:
   parameter name=startRow/
  
   In component:
  
   public void finishLoad() {
 super.finishLoad();
 setStartRow(0);
   }
  
  
   The fact is that default-value with invariant values (literal,
   ognl:constant, ecc.) make sense just if it's a read only binding,
 At
   the same time default-value with ognl expressions referring to
   containing component methods would break component encapsulation
   making assumptions on the exact method signature the containing
   component should implement (also its optional/default status would
 be
   questionable...).
  
   As for my specific Dialog component problem I think there's still a
   bug because the component IS actually trying to write the
 invariant
   default-value binding in hide/show methods so after 2 invalid ticket
 I
   hope I'm goig to open a valid one now.
  
  
  
   On 7/30/07, Martino Piccinato [EMAIL PROTECTED] wrote:
  
  
   Posted one for the parameter issue
  
   https://issues.apache.org/jira/browse/TAPESTRY-1682
  
   and another one for the Dialog component:
  
   https://issues.apache.org/jira/browse/TAPESTRY-1683
  
   I didn't do it first because I was trying to investigate myself but
 I
   really have no time to do this now.
  
   Ciao
  
   Martino
  
   On 7/30/07, Andrea Chiumenti [EMAIL PROTECTED] wrote:
  
  
   Well, I try to investigate into this, meanwhile if you could be so
 kind to
   post a jira...
  
   ciao,
   kiuma
  
   On 

Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread munich
We have tried both enabling and disabling the cache. The same effect...
it is only leaking a little bit slower in the other case.

 Original-Nachricht 
Datum: Thu, 9 Aug 2007 15:33:43 +0200
Von: Kristian Marinkovic [EMAIL PROTECTED]
An: Tapestry users users@tapestry.apache.org
Betreff: Re: Memory leaks in Tapestry 4.1

 do you have Tapestry caching deactivated?
 
 
 
 
 andyhot [EMAIL PROTECTED] 
 Gesendet von: Andreas Andreou [EMAIL PROTECTED]
 09.08.2007 15:28
 Bitte antworten an
 Tapestry users users@tapestry.apache.org
 
 
 An
 Tapestry users users@tapestry.apache.org
 Kopie
 
 Thema
 Re: Memory leaks in Tapestry 4.1
 
 
 
 
 
 
 Well, we did lots of tests with 4.1.2 and
 have yet to observe such memory leaks.
 
 [EMAIL PROTECTED] wrote:
  Have you ever observed the memory usage for your Tapestry application?
 
  For example, make a simple HelloWorld Application and load the page 
 regularly using HTTP_LOAD. Then watch how the memory consumption grows and
 grows  especially after an hour.
 
  Has anyone got a solution how avoid this leakage?
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread munich
Within one day it rises slowly from 100 MByte to about 1 Gigabyte at night when 
it crashes due to the limt that was set to the virtual machine. It could be 
increased - but only with the effect of having an additional day or so before 
it crashes again.restarting Tomcat is also not a viable solution.

 Original-Nachricht 
Datum: Thu, 09 Aug 2007 17:01:19 +0200
Von: [EMAIL PROTECTED]
An: Tapestry users users@tapestry.apache.org
Betreff: Re: Memory leaks in Tapestry 4.1

 We have tried both enabling and disabling the cache. The same effect...
 it is only leaking a little bit slower in the other case.
 
  Original-Nachricht 
 Datum: Thu, 9 Aug 2007 15:33:43 +0200
 Von: Kristian Marinkovic [EMAIL PROTECTED]
 An: Tapestry users users@tapestry.apache.org
 Betreff: Re: Memory leaks in Tapestry 4.1
 
  do you have Tapestry caching deactivated?
  
  
  
  
  andyhot [EMAIL PROTECTED] 
  Gesendet von: Andreas Andreou [EMAIL PROTECTED]
  09.08.2007 15:28
  Bitte antworten an
  Tapestry users users@tapestry.apache.org
  
  
  An
  Tapestry users users@tapestry.apache.org
  Kopie
  
  Thema
  Re: Memory leaks in Tapestry 4.1
  
  
  
  
  
  
  Well, we did lots of tests with 4.1.2 and
  have yet to observe such memory leaks.
  
  [EMAIL PROTECTED] wrote:
   Have you ever observed the memory usage for your Tapestry application?
  
   For example, make a simple HelloWorld Application and load the page 
  regularly using HTTP_LOAD. Then watch how the memory consumption grows
 and
  grows  especially after an hour.
  
   Has anyone got a solution how avoid this leakage?
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
   
  
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Jonathan Glanz
Have you tried pulling heap dumps and anaylizing them ?
Sent via BlackBerry by ATT

-Original Message-
From: [EMAIL PROTECTED]

Date: Thu, 09 Aug 2007 17:04:21 
To:Tapestry users users@tapestry.apache.org
Subject: Re: Memory leaks in Tapestry 4.1


Within one day it rises slowly from 100 MByte to about 1 Gigabyte at night when 
it crashes due to the limt that was set to the virtual machine. It could be 
increased - but only with the effect of having an additional day or so before 
it crashes again.restarting Tomcat is also not a viable solution.

 Original-Nachricht 
Datum: Thu, 09 Aug 2007 17:01:19 +0200
Von: [EMAIL PROTECTED]
An: Tapestry users users@tapestry.apache.org
Betreff: Re: Memory leaks in Tapestry 4.1

 We have tried both enabling and disabling the cache. The same effect...
 it is only leaking a little bit slower in the other case.
 
  Original-Nachricht 
 Datum: Thu, 9 Aug 2007 15:33:43 +0200
 Von: Kristian Marinkovic [EMAIL PROTECTED]
 An: Tapestry users users@tapestry.apache.org
 Betreff: Re: Memory leaks in Tapestry 4.1
 
  do you have Tapestry caching deactivated?
  
  
  
  
  andyhot [EMAIL PROTECTED] 
  Gesendet von: Andreas Andreou [EMAIL PROTECTED]
  09.08.2007 15:28
  Bitte antworten an
  Tapestry users users@tapestry.apache.org
  
  
  An
  Tapestry users users@tapestry.apache.org
  Kopie
  
  Thema
  Re: Memory leaks in Tapestry 4.1
  
  
  
  
  
  
  Well, we did lots of tests with 4.1.2 and
  have yet to observe such memory leaks.
  
  [EMAIL PROTECTED] wrote:
   Have you ever observed the memory usage for your Tapestry application?
  
   For example, make a simple HelloWorld Application and load the page 
  regularly using HTTP_LOAD. Then watch how the memory consumption grows
 and
  grows  especially after an hour.
  
   Has anyone got a solution how avoid this leakage?
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
   
  
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Jesse Kuhnert
Tapestry 4.1.2 has no memory leaks.  Each and every object created /
managed is accounted for and known.   I've done a lot of analysis in
this area lately which is why I'm so sure.

On 8/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Within one day it rises slowly from 100 MByte to about 1 Gigabyte at night 
 when it crashes due to the limt that was set to the virtual machine. It could 
 be increased - but only with the effect of having an additional day or so 
 before it crashes again.restarting Tomcat is also not a viable solution.

  Original-Nachricht 
 Datum: Thu, 09 Aug 2007 17:01:19 +0200
 Von: [EMAIL PROTECTED]
 An: Tapestry users users@tapestry.apache.org
 Betreff: Re: Memory leaks in Tapestry 4.1

  We have tried both enabling and disabling the cache. The same effect...
  it is only leaking a little bit slower in the other case.
 
   Original-Nachricht 
  Datum: Thu, 9 Aug 2007 15:33:43 +0200
  Von: Kristian Marinkovic [EMAIL PROTECTED]
  An: Tapestry users users@tapestry.apache.org
  Betreff: Re: Memory leaks in Tapestry 4.1
 
   do you have Tapestry caching deactivated?
  
  
  
  
   andyhot [EMAIL PROTECTED]
   Gesendet von: Andreas Andreou [EMAIL PROTECTED]
   09.08.2007 15:28
   Bitte antworten an
   Tapestry users users@tapestry.apache.org
  
  
   An
   Tapestry users users@tapestry.apache.org
   Kopie
  
   Thema
   Re: Memory leaks in Tapestry 4.1
  
  
  
  
  
  
   Well, we did lots of tests with 4.1.2 and
   have yet to observe such memory leaks.
  
   [EMAIL PROTECTED] wrote:
Have you ever observed the memory usage for your Tapestry application?
   
For example, make a simple HelloWorld Application and load the page
   regularly using HTTP_LOAD. Then watch how the memory consumption grows
  and
   grows  especially after an hour.
   
Has anyone got a solution how avoid this leakage?
   
   
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
   
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [ANN]T5 book: reviewers are needed

2007-08-09 Thread Kolesnikov, Alexander GNI
Phew... The publisher has actually contacted me a few days ago to tell
me that he's got many more reviewer volunteers than he ever expected,
and so he selected only three of them. But it will be an honor for both
me and them to have you as a reviewer. I will contact them now and try
to convince to increase the number of reviewers!

-Original Message-
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] 
Sent: 09 August 2007 15:42
To: Tapestry users
Subject: Re: [ANN]T5 book: reviewers are needed


I'd be happy to review the book, of course!

On 8/2/07, Kolesnikov, Alexander GNI [EMAIL PROTECTED]
wrote:

 I am writing a book on T5 and the publisher is looking for technical 
 reviewers for this book. Please contact me directly if you want to 
 review the book or if you have any questions.

 Cheers,

 Alexander


 --
 
 CONFIDENTIALITY NOTICE: If you have received this email in error,
please
 immediately notify the sender by e-mail at the address shown.  This
email
 transmission may contain confidential information.  This information
is
 intended only for the use of the individual(s) or entity to whom it is
 intended even if addressed incorrectly.  Please delete it from your
files if
 you are not the intended recipient.  Thank you for your
 compliance.  Copyright 2007 CIGNA

 ==
 




-- 
Howard M. Lewis Ship
Partner and Senior Architect at Feature50

Creator Apache Tapestry and Apache HiveMind

--
CONFIDENTIALITY NOTICE: If you have received this email in error, please 
immediately notify the sender by e-mail at the address shown.  This email 
transmission may contain confidential information.  This information is 
intended only for the use of the individual(s) or entity to whom it is intended 
even if addressed incorrectly.  Please delete it from your files if you are not 
the intended recipient.  Thank you for your compliance.  Copyright 2007 CIGNA
==


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [ANN]T5 book: reviewers are needed

2007-08-09 Thread Thiago H de Paula Figueiredo
On Thu, 09 Aug 2007 12:28:41 -0300, Kolesnikov, Alexander  GNI  
[EMAIL PROTECTED] wrote:



Phew... The publisher has actually contacted me a few days ago to tell
me that he's got many more reviewer volunteers than he ever expected,
and so he selected only three of them. But it will be an honor for both
me and them to have you as a reviewer. I will contact them now and try
to convince to increase the number of reviewers!


Can you tell us who the chosen reviewers are? :)

--
Thiago H. de Paula Figueiredo
Desenvolvedor, Instrutor e Consultor de Tecnologia
Eteg Tecnologia da Informação Ltda.
http://www.eteg.com.br

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Todd Orr
We've run into this problem on a production system. It was a not a
good situation. One of our developers narrowed down the issue to
Hivemind. There is some Map that continually grows and grows (I can
speak to our dev to get more detail). After some research into similar
posts it became evident that this issue was brought up to HLS, but the
bug's existence was denied. We've since dropped Tapestry for mission
critical apps. I'm hoping this is no longer an issue in future
versions of Tapestry, but time will tell.

On 8/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
 Tapestry 4.1.2 has no memory leaks.  Each and every object created /
 managed is accounted for and known.   I've done a lot of analysis in
 this area lately which is why I'm so sure.

 On 8/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  Within one day it rises slowly from 100 MByte to about 1 Gigabyte at night 
  when it crashes due to the limt that was set to the virtual machine. It 
  could be increased - but only with the effect of having an additional day 
  or so before it crashes again.restarting Tomcat is also not a viable 
  solution.
 
   Original-Nachricht 
  Datum: Thu, 09 Aug 2007 17:01:19 +0200
  Von: [EMAIL PROTECTED]
  An: Tapestry users users@tapestry.apache.org
  Betreff: Re: Memory leaks in Tapestry 4.1
 
   We have tried both enabling and disabling the cache. The same effect...
   it is only leaking a little bit slower in the other case.
  
    Original-Nachricht 
   Datum: Thu, 9 Aug 2007 15:33:43 +0200
   Von: Kristian Marinkovic [EMAIL PROTECTED]
   An: Tapestry users users@tapestry.apache.org
   Betreff: Re: Memory leaks in Tapestry 4.1
  
do you have Tapestry caching deactivated?
   
   
   
   
andyhot [EMAIL PROTECTED]
Gesendet von: Andreas Andreou [EMAIL PROTECTED]
09.08.2007 15:28
Bitte antworten an
Tapestry users users@tapestry.apache.org
   
   
An
Tapestry users users@tapestry.apache.org
Kopie
   
Thema
Re: Memory leaks in Tapestry 4.1
   
   
   
   
   
   
Well, we did lots of tests with 4.1.2 and
have yet to observe such memory leaks.
   
[EMAIL PROTECTED] wrote:
 Have you ever observed the memory usage for your Tapestry application?

 For example, make a simple HelloWorld Application and load the page
regularly using HTTP_LOAD. Then watch how the memory consumption grows
   and
grows  especially after an hour.

 Has anyone got a solution how avoid this leakage?


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



   
   
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Jesse Kuhnert
 Tapestry/Dojo team member/developer

 Open source based consulting work centered around
 dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Ben Tomasini
I have used both Tapestry and HiveMind under high production loads and have
never found any memory leaks in the frameworks themselves.  This includes
memory intensive, high volume workflow and image processing applications for
large financial institutions.

However, nearly every application I have worked on has experienced memory
leaks at times, often times severe.  Sometimes it was my own code.  Often it
was 3rd party libraries like caching frameworks (ehcache constructs had a
badly leaking MutexCache implementation - fixed last year), dao frameworks
(iBatis had an LRU cache which did not properly invalidate every other
expired entry - also fixed), JDBC drivers (just worked with a version of an
AS/400 driver which leaked live a sieve - recently fixed), and the JDK
(StringBuffer in 1.4 anyone? - how about using Java 2D?).  My experience
tells me that if you haven't run your application through JProfiler and
looked for leaks, there is a *very* good chance your app is leaking memory,
often times in unexpected places.

Just because your application is a Tapestry application does not mean the
leak is caused by Tapestry - odds are against you on that.

My suggestion would be to run your application under JProfiler and put some
load on it.  It is very simple to do.  Watch the heap telemetry and see if
it grows monotonically.  Watch the object allocations and sizes for the
same.

If you have some empirical evidence to support a suspected leak in Tapestry,
then present it here.  I assure you Jesse and the other developers would be
eager to fix them.

HTH,

Ben



On 8/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Have you ever observed the memory usage for your Tapestry application?

 For example, make a simple HelloWorld Application and load the page
 regularly using HTTP_LOAD. Then watch how the memory consumption grows and
 grows  especially after an hour.

 Has anyone got a solution how avoid this leakage?


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Todd Orr
True enough. I'll get more details from our side. I was merely
pointing in that direction based on experience.

On 8/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
 Whatever this mysterious issue is that you seem to think exists it'd
 be impossible to fix whatever memory leaks you think you have found
 without knowing about them.

 There is a map that grows as large as the system using it internally
 to javassist of various cached reflection info - but it doesn't leak
 in any way.

 Anyways,  vague comments with no specific versions or specific issues
 that you have faced don't really help anyone.

 On 8/9/07, Todd Orr [EMAIL PROTECTED] wrote:
  We've run into this problem on a production system. It was a not a
  good situation. One of our developers narrowed down the issue to
  Hivemind. There is some Map that continually grows and grows (I can
  speak to our dev to get more detail). After some research into similar
  posts it became evident that this issue was brought up to HLS, but the
  bug's existence was denied. We've since dropped Tapestry for mission
  critical apps. I'm hoping this is no longer an issue in future
  versions of Tapestry, but time will tell.
 
  On 8/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
   Tapestry 4.1.2 has no memory leaks.  Each and every object created /
   managed is accounted for and known.   I've done a lot of analysis in
   this area lately which is why I'm so sure.
  
   On 8/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Within one day it rises slowly from 100 MByte to about 1 Gigabyte at 
night when it crashes due to the limt that was set to the virtual 
machine. It could be increased - but only with the effect of having an 
additional day or so before it crashes again.restarting Tomcat is 
also not a viable solution.
   
 Original-Nachricht 
Datum: Thu, 09 Aug 2007 17:01:19 +0200
Von: [EMAIL PROTECTED]
An: Tapestry users users@tapestry.apache.org
Betreff: Re: Memory leaks in Tapestry 4.1
   
 We have tried both enabling and disabling the cache. The same 
 effect...
 it is only leaking a little bit slower in the other case.

  Original-Nachricht 
 Datum: Thu, 9 Aug 2007 15:33:43 +0200
 Von: Kristian Marinkovic [EMAIL PROTECTED]
 An: Tapestry users users@tapestry.apache.org
 Betreff: Re: Memory leaks in Tapestry 4.1

  do you have Tapestry caching deactivated?
 
 
 
 
  andyhot [EMAIL PROTECTED]
  Gesendet von: Andreas Andreou [EMAIL PROTECTED]
  09.08.2007 15:28
  Bitte antworten an
  Tapestry users users@tapestry.apache.org
 
 
  An
  Tapestry users users@tapestry.apache.org
  Kopie
 
  Thema
  Re: Memory leaks in Tapestry 4.1
 
 
 
 
 
 
  Well, we did lots of tests with 4.1.2 and
  have yet to observe such memory leaks.
 
  [EMAIL PROTECTED] wrote:
   Have you ever observed the memory usage for your Tapestry 
   application?
  
   For example, make a simple HelloWorld Application and load the 
   page
  regularly using HTTP_LOAD. Then watch how the memory consumption 
  grows
 and
  grows  especially after an hour.
  
   Has anyone got a solution how avoid this leakage?
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
  
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
   
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
   --
   Jesse Kuhnert
   Tapestry/Dojo team member/developer
  
   Open source based consulting work centered around
   dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Jesse Kuhnert
 Tapestry/Dojo team member/developer

 Open source based consulting work centered around
 dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, 

[4.0] session expiration

2007-08-09 Thread Ed Cohen
In Tapestry 4.0.2, what controls the session expiration, and how can it
be increased?

 

Thanks,

Ed



Re: [4.0] session expiration

2007-08-09 Thread Jacob von Eyben
 In Tapestry 4.0.2, what controls the session expiration, and how can it
 be increased?
The session timeout specified in your web.xml as in any other webapplication.

Your visit object is just placed in the http session.

Regards
Jacob von Eyben
http://ancientprogramming.blogspot.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



T4: Client urls for listeners?

2007-08-09 Thread Bill Holloway
In a component class, I need to be able to generate a client URL to put into
a JSON object that links to a server-side listener method.

Didn't see this in the wiki or first search in mailing list.  Ideas?

Bill


Re: Memory leaks in Tapestry 4.1

2007-08-09 Thread Hans Jörg Hessmann
There is an excellent tool for post-mortem memory analyzation:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0eaafd5-6ffd-2910-019c-9007a92b392f.
Just add -XX:+HeapDumpOnOutOfMemoryError to the startup parameters of
your JVM. This will produce a memory dump when your JVM dies because of
an OutOfMemoryError. With the memory analyzer you can see which objects
consumed all the memory and find out the cause for the the garbage
collector not collecting them. (See the corresponding documentation and
the wiki to find out how to do this.)

Todd Orr wrote:
 True enough. I'll get more details from our side. I was merely
 pointing in that direction based on experience.

 On 8/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
   
 Whatever this mysterious issue is that you seem to think exists it'd
 be impossible to fix whatever memory leaks you think you have found
 without knowing about them.

 There is a map that grows as large as the system using it internally
 to javassist of various cached reflection info - but it doesn't leak
 in any way.

 Anyways,  vague comments with no specific versions or specific issues
 that you have faced don't really help anyone.

 On 8/9/07, Todd Orr [EMAIL PROTECTED] wrote:
 
 We've run into this problem on a production system. It was a not a
 good situation. One of our developers narrowed down the issue to
 Hivemind. There is some Map that continually grows and grows (I can
 speak to our dev to get more detail). After some research into similar
 posts it became evident that this issue was brought up to HLS, but the
 bug's existence was denied. We've since dropped Tapestry for mission
 critical apps. I'm hoping this is no longer an issue in future
 versions of Tapestry, but time will tell.

 On 8/9/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
   
 Tapestry 4.1.2 has no memory leaks.  Each and every object created /
 managed is accounted for and known.   I've done a lot of analysis in
 this area lately which is why I'm so sure.

 On 8/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
 Within one day it rises slowly from 100 MByte to about 1 Gigabyte at 
 night when it crashes due to the limt that was set to the virtual 
 machine. It could be increased - but only with the effect of having an 
 additional day or so before it crashes again.restarting Tomcat is 
 also not a viable solution.

  Original-Nachricht 
 Datum: Thu, 09 Aug 2007 17:01:19 +0200
 Von: [EMAIL PROTECTED]
 An: Tapestry users users@tapestry.apache.org
 Betreff: Re: Memory leaks in Tapestry 4.1

   
 We have tried both enabling and disabling the cache. The same effect...
 it is only leaking a little bit slower in the other case.

  Original-Nachricht 
 Datum: Thu, 9 Aug 2007 15:33:43 +0200
 Von: Kristian Marinkovic [EMAIL PROTECTED]
 An: Tapestry users users@tapestry.apache.org
 Betreff: Re: Memory leaks in Tapestry 4.1

 
 do you have Tapestry caching deactivated?




 andyhot [EMAIL PROTECTED]
 Gesendet von: Andreas Andreou [EMAIL PROTECTED]
 09.08.2007 15:28
 Bitte antworten an
 Tapestry users users@tapestry.apache.org


 An
 Tapestry users users@tapestry.apache.org
 Kopie

 Thema
 Re: Memory leaks in Tapestry 4.1






 Well, we did lots of tests with 4.1.2 and
 have yet to observe such memory leaks.

 [EMAIL PROTECTED] wrote:
   
 Have you ever observed the memory usage for your Tapestry application?

 For example, make a simple HelloWorld Application and load the page
 
 regularly using HTTP_LOAD. Then watch how the memory consumption grows
   
 and
 
 grows  especially after an hour.
   
 Has anyone got a solution how avoid this leakage?


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


   
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


   
 --
 Jesse Kuhnert
 Tapestry/Dojo team member/developer

 Open source based consulting work centered around
 dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL 

Re: T3: How to capture time

2007-08-09 Thread Nick Westgate

Search the list for old posts (2004) about DateTimePicker.
The component jar is still here, I believe:
http://myworkspace.sourceforge.net/component-library.html

Cheers,
Nick.


Nazmul Bhuiyan wrote:

Hello,

I'm using DatePicker to capture dates. Is there any component to capture
time?

Thanks

naz



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: T3: How to capture time

2007-08-09 Thread Robert Zeigler
The Calendar component on tassel also wraps (a newer version of)  
the same js calendar that DateTimePicker wraps.
But the component as written in tassel doesn't do the time. Some time  
ago, I took it and revamped it somewhat for my own needs to allow for  
time selection as well as date selection, and also allow for choosing  
which theme to use.  I sent the changes back to the original  
usc_calendar component author (at least, I'm pretty sure I did...  
if he's around and I'm wrong, let me know and I'll send them. This  
was many moons ago. ;) but I don't think they ever got incorporated  
into the version on tassel.
If you're interested, shoot me an e-mail off list and I'll send you  
what I have.


Robert

On Aug 9, 2007, at 8/910:12 PM , Nick Westgate wrote:


Search the list for old posts (2004) about DateTimePicker.
The component jar is still here, I believe:
http://myworkspace.sourceforge.net/component-library.html

Cheers,
Nick.


Nazmul Bhuiyan wrote:

Hello,
I'm using DatePicker to capture dates. Is there any component to  
capture

time?
Thanks
naz


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]