Re: Tapestry ClassLoading errors

2014-05-31 Thread Chris Mylonas
What if you move your classes from tapestry.utility to
tapestry.base.utility which is controlled by tapestrymaybe

http://tapestry.apache.org/class-reloading.html
On 01/06/2014 4:58 am, "Boris Horvat"  wrote:

> In what package should I put this component? Currently it resides in
>
> package com.bomahabo.flow.tapestry.utility
>
> and it uses
>
> private AjaxResponseRenderer ajaxResponseRenderer;
> private Request request;
> private JavaScriptSupport javascript;
>
> Should I move it outside of the tapestry in order to help with this issue?
>
>
> On Tue, May 27, 2014 at 5:50 PM, Thiago H de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
> > On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat <
> horvat.z.bo...@gmail.com>
> > wrote:
> >
> >  But it is only triggered in class re loading
> >>
> >
> > It could be a reloadable service being used both injected from
> > Tapestry-IoC and directly, not through T-IoC. If something is live class
> > reloadable, you should always access it though Tapestry (classes in
> > controlled packages) or Tapestry-IoC (injected services).
> >
> > --
> > Thiago H. de Paula Figueiredo
> > Tapestry, Java and Hibernate consultant and developer
> > http://machina.com.br
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
>
> --
> Sincerely
> *Boris Horvat*
>


Re: Refreshing a from in a Zone

2014-05-31 Thread Boris Horvat
Here is the code that will trigger the issue (I needed a bit of time to
isolate everything sorry for the delay.

The fact that loop is around  element is what is triggering the issue

  




${values}






refresh






@Inject
private AjaxResponseRenderer ajaxResponseRenderer;
@InjectComponent
private Zone zone;

@Persist
@Property
private List> values; //ItemSingleHolder is a
generic class that is just used to hold objects
@Property
private ItemSingleHolder value;

@OnEvent(value = EventConstants.SUCCESS, component = "form")
public void form() {
System.out.println(values);
ajaxResponseRenderer.addRender(zone);
}

@SetupRender
public void setup() {
values = new LinkedList>();
values.add(new ItemSingleHolder(true));
values.add(new ItemSingleHolder(true));
values.add(new ItemSingleHolder(false));
values.add(new ItemSingleHolder(true));
}

public ValueEncoder> getEncoder() {
return new ItemHolderEncoder>(values); //
generic encoder for the holder class
}



On Sat, May 31, 2014 at 10:09 PM, Boris Horvat 
wrote:

> Hi, thanks for the quick response
>
> Thiago, the entire form is already in a zone.
>
> I don't think that stack trace will help but here it is
>
> Stack trace
>
>-
>
> org.apache.tapestry5.corelib.components.Form.executeStoredActions(Form.java:649)
>-
>
> org.apache.tapestry5.corelib.components.Form.advised$onAction_3a65a93609ae0(Form.java:539)
>- 
> org.apache.tapestry5.corelib.components.Form$Invocation_onAction_3a65a93609adf.proceedToAdvisedMethod(Unknown
>Source)
>-
>
> org.apache.tapestry5.internal.plastic.AbstractMethodInvocation.proceed(AbstractMethodInvocation.java:84)
>-
>
> org.apache.tapestry5.ioc.internal.services.LoggingAdvice.advise(LoggingAdvice.java:37)
>-
>
> org.apache.tapestry5.internal.plastic.AbstractMethodInvocation.proceed(AbstractMethodInvocation.java:86)
>- org.apache.tapestry5.corelib.components.Form.onAction(Form.java)
>-
>
> org.apache.tapestry5.corelib.components.Form.dispatchComponentEvent(Form.java)
>-
>
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl.dispatchEvent(ComponentPageElementImpl.java:940)
>-
>
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl.processEventTriggering(ComponentPageElementImpl.java:1117)
>-
>
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$3100(ComponentPageElementImpl.java:61)
>-
>
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl$5.invoke(ComponentPageElementImpl.java:1062)
>-
>
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl$5.invoke(ComponentPageElementImpl.java:1059)
>-
>
> org.apache.tapestry5.internal.structure.ComponentPageElementResourcesImpl.invoke(ComponentPageElementResourcesImpl.java:146)
>-
>
> org.apache.tapestry5.internal.structure.ComponentPageElementImpl.triggerContextEvent(ComponentPageElementImpl.java:1058)
>-
>
> org.apache.tapestry5.internal.services.AjaxComponentEventRequestHandler.handle(AjaxComponentEventRequestHandler.java:110)
>-
>
> org.apache.tapestry5.internal.services.ajax.AjaxFormUpdateFilter.handle(AjaxFormUpdateFilter.java:56)
>-
>
> org.apache.tapestry5.internal.services.AjaxFilter.handle(AjaxFilter.java:42)
>-
>
> org.apache.tapestry5.upload.internal.services.UploadExceptionFilter.handle(UploadExceptionFilter.java:75)
>-
>
> org.apache.tapestry5.services.TapestryModule$41.handle(TapestryModule.java:2476)
>-
>
> org.apache.tapestry5.internal.services.ComponentRequestHandlerTerminator.handleComponentEvent(ComponentRequestHandlerTerminator.java:43)
>-
>
> com.bomahabo.flow.services.security.AllowSuspendedStudioFilter.handleComponentEvent(AllowSuspendedStudioFilter.java:65)
>-
>
> com.bomahabo.flow.services.security.RequiresProjectFilter.handleComponentEvent(RequiresProjectFilter.java:65)
>-
>
> org.apache.tapestry5.services.InitializeActivePageName.handleComponentEvent(InitializeActivePageName.java:39)
>-
>
> org.tynamo.security.SecurityComponentRequestFilter.handleComponentEvent(SecurityComponentRequestFilter.java:41)
>-
>
> org.apache.tapestry5.internal.services.ComponentEventDispatcher.dispatch(ComponentEventDispatcher.java:46)
>-
>
> org.apache.tapestry5.services.TapestryModule$RequestHandlerTerminator.service(TapestryModule.java:302)
>-
>
> org.apache.tapestry5.internal.services.RequestErrorFilter.service(R

Re: Refreshing a from in a Zone

2014-05-31 Thread Boris Horvat
Hi, thanks for the quick response

Thiago, the entire form is already in a zone.

I don't think that stack trace will help but here it is

Stack trace

   -
   
org.apache.tapestry5.corelib.components.Form.executeStoredActions(Form.java:649)
   -
   
org.apache.tapestry5.corelib.components.Form.advised$onAction_3a65a93609ae0(Form.java:539)
   - 
org.apache.tapestry5.corelib.components.Form$Invocation_onAction_3a65a93609adf.proceedToAdvisedMethod(Unknown
   Source)
   -
   
org.apache.tapestry5.internal.plastic.AbstractMethodInvocation.proceed(AbstractMethodInvocation.java:84)
   -
   
org.apache.tapestry5.ioc.internal.services.LoggingAdvice.advise(LoggingAdvice.java:37)
   -
   
org.apache.tapestry5.internal.plastic.AbstractMethodInvocation.proceed(AbstractMethodInvocation.java:86)
   - org.apache.tapestry5.corelib.components.Form.onAction(Form.java)
   -
   
org.apache.tapestry5.corelib.components.Form.dispatchComponentEvent(Form.java)
   -
   
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.dispatchEvent(ComponentPageElementImpl.java:940)
   -
   
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.processEventTriggering(ComponentPageElementImpl.java:1117)
   -
   
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.access$3100(ComponentPageElementImpl.java:61)
   -
   
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$5.invoke(ComponentPageElementImpl.java:1062)
   -
   
org.apache.tapestry5.internal.structure.ComponentPageElementImpl$5.invoke(ComponentPageElementImpl.java:1059)
   -
   
org.apache.tapestry5.internal.structure.ComponentPageElementResourcesImpl.invoke(ComponentPageElementResourcesImpl.java:146)
   -
   
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.triggerContextEvent(ComponentPageElementImpl.java:1058)
   -
   
org.apache.tapestry5.internal.services.AjaxComponentEventRequestHandler.handle(AjaxComponentEventRequestHandler.java:110)
   -
   
org.apache.tapestry5.internal.services.ajax.AjaxFormUpdateFilter.handle(AjaxFormUpdateFilter.java:56)
   -
   org.apache.tapestry5.internal.services.AjaxFilter.handle(AjaxFilter.java:42)
   -
   
org.apache.tapestry5.upload.internal.services.UploadExceptionFilter.handle(UploadExceptionFilter.java:75)
   -
   
org.apache.tapestry5.services.TapestryModule$41.handle(TapestryModule.java:2476)
   -
   
org.apache.tapestry5.internal.services.ComponentRequestHandlerTerminator.handleComponentEvent(ComponentRequestHandlerTerminator.java:43)
   -
   
com.bomahabo.flow.services.security.AllowSuspendedStudioFilter.handleComponentEvent(AllowSuspendedStudioFilter.java:65)
   -
   
com.bomahabo.flow.services.security.RequiresProjectFilter.handleComponentEvent(RequiresProjectFilter.java:65)
   -
   
org.apache.tapestry5.services.InitializeActivePageName.handleComponentEvent(InitializeActivePageName.java:39)
   -
   
org.tynamo.security.SecurityComponentRequestFilter.handleComponentEvent(SecurityComponentRequestFilter.java:41)
   -
   
org.apache.tapestry5.internal.services.ComponentEventDispatcher.dispatch(ComponentEventDispatcher.java:46)
   -
   
org.apache.tapestry5.services.TapestryModule$RequestHandlerTerminator.service(TapestryModule.java:302)
   -
   
org.apache.tapestry5.internal.services.RequestErrorFilter.service(RequestErrorFilter.java:26)
   -
   
org.apache.tapestry5.services.TapestryModule$3.service(TapestryModule.java:902)
   -
   
org.apache.tapestry5.services.TapestryModule$2.service(TapestryModule.java:892)
   -
   
org.apache.tapestry5.internal.services.StaticFilesFilter.service(StaticFilesFilter.java:90)
   -
   
org.apache.tapestry5.internal.services.CheckForUpdatesFilter$2.invoke(CheckForUpdatesFilter.java:105)
   -
   
org.apache.tapestry5.internal.services.CheckForUpdatesFilter$2.invoke(CheckForUpdatesFilter.java:95)
   -
   
org.apache.tapestry5.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:85)
   -
   
org.apache.tapestry5.internal.services.CheckForUpdatesFilter.service(CheckForUpdatesFilter.java:119)
   -
   
org.apache.tapestry5.services.TapestryModule$HttpServletRequestHandlerTerminator.service(TapestryModule.java:253)
   -
   
org.got5.tapestry5.jquery.services.AjaxUploadServletRequestFilter.service(AjaxUploadServletRequestFilter.java:27)
   -
   org.apache.tapestry5.internal.gzip.GZipFilter.service(GZipFilter.java:53)
   -
   
org.tynamo.resteasy.ResteasyRequestFilter.service(ResteasyRequestFilter.java:100)
   -
   
org.tynamo.security.services.impl.SecurityConfiguration$1.call(SecurityConfiguration.java:56)
   -
   
org.tynamo.security.services.impl.SecurityConfiguration$1.call(SecurityConfiguration.java:54)
   -
   
org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
   -
   
org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
   -
   
org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:380)
   -
   
org.tynamo.security.services.impl.SecurityConfigurati

Re: Refreshing a from in a Zone

2014-05-31 Thread Thiago H de Paula Figueiredo
The easiest solution is to wrap the whole form inside a Zone and update  
this zone.


On Sat, 31 May 2014 15:55:10 -0300, Boris Horvat  
 wrote:



Hi everyone,

I have form that basically displays couple of checkboxs that user can
select/deselect. Once he is made his choice he clicks a button and a form
is submited, zone is refreshed (include the form).

All of the data is nicely displayed but a second submissions throws the
error

Forms require that the request method be POST and that the t:formdata  
query

parameter have values.

Am I doing something wrong? Is my scenario possible?

Let me know if you need code samples

Cheers




--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Refreshing a from in a Zone

2014-05-31 Thread Kalle Korhonen
On Sat, May 31, 2014 at 11:55 AM, Boris Horvat 
wrote:

> I have form that basically displays couple of checkboxs that user can
> select/deselect. Once he is made his choice he clicks a button and a form
> is submited, zone is refreshed (include the form).
> All of the data is nicely displayed but a second submissions throws the
> error
> Forms require that the request method be POST and that the t:formdata query
> parameter have values.
> Am I doing something wrong? Is my scenario possible?
> Let me know if you need code samples
>

(I apologize in advance but couldn't resist...). Yes, you need to fix the
error. Let me know if you need better instructions.

In all seriousness, yes of course we need code samples and a bare minimum
is you tell us which error you are seeing, e.g. a stack trace.

Kalle


Re: Tapestry ClassLoading errors

2014-05-31 Thread Boris Horvat
In what package should I put this component? Currently it resides in

package com.bomahabo.flow.tapestry.utility

and it uses

private AjaxResponseRenderer ajaxResponseRenderer;
private Request request;
private JavaScriptSupport javascript;

Should I move it outside of the tapestry in order to help with this issue?


On Tue, May 27, 2014 at 5:50 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:

> On Tue, 27 May 2014 10:29:09 -0300, Boris Horvat 
> wrote:
>
>  But it is only triggered in class re loading
>>
>
> It could be a reloadable service being used both injected from
> Tapestry-IoC and directly, not through T-IoC. If something is live class
> reloadable, you should always access it though Tapestry (classes in
> controlled packages) or Tapestry-IoC (injected services).
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>


-- 
Sincerely
*Boris Horvat*


Refreshing a from in a Zone

2014-05-31 Thread Boris Horvat
Hi everyone,

I have form that basically displays couple of checkboxs that user can
select/deselect. Once he is made his choice he clicks a button and a form
is submited, zone is refreshed (include the form).

All of the data is nicely displayed but a second submissions throws the
error

Forms require that the request method be POST and that the t:formdata query
parameter have values.

Am I doing something wrong? Is my scenario possible?

Let me know if you need code samples

Cheers

-- 
Sincerely
*Boris Horvat*


Re: Grids Bean Model does not support "is" methods

2014-05-31 Thread Thiago H de Paula Figueiredo
On Sat, 31 May 2014 07:51:56 -0300, Muhammad Gelbana   
wrote:



I don't see a reason why Tapestry doesn't support such a case. Unless
Tapestry uses a 3rd party library that strictly complies with the java
beans specifications to read getters\setters,


Tapestry doesn't use a 3rd party library. It uses the classes in the  
java.beans package. That's a 1st party library in the Java world. Classes  
from Java itself. So the source code generator is actually wrong (at least  
in the configuration that generated isXXX() methods returning Boolean).


In this very specific case, I think the JavaBeans specification is  
correct: Boolean isn't actually a boolean type, because it has three  
values: true, false and null. So it doesn't make any sense an isXXX()  
method which can return something which isn't true nor false.


--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Grids Bean Model does not support "is" methods

2014-05-31 Thread Muhammad Gelbana
I don't see a reason why Tapestry doesn't support such a case. Unless
Tapestry uses a 3rd party library that strictly complies with the java
beans specifications to read getters\setters, It would be a pleasure for
Tapestry users to find Tapestry going an extra mile to make their lives
easier, that's why we are using Tapestry in the first place, Its awesome.

I personally don't see a reason why a "is" methods should support primitive
boolean only. I won't be surprised if the specs change in the future to
support Boolean objects too, but should we wait for that to happen to
change how Tapestry works ?!

*-*
*Muhammad Gelbana*
http://www.linkedin.com/in/mgelbana


On Fri, May 30, 2014 at 9:29 PM, Erich Gormann  wrote:

> Thanks Howard,
>
> we fixed the way CXF generates our webservice types and now we have the
> desired getter.
> Of course it was not compliant to the bean spec before, but I saw no way
> to change the generation behavior.
>
> Regards
> Eric
>
> Am 30.05.2014 18:43, schrieb Howard Lewis Ship:
>
>  If you getter method is "is", not "get", prefixed then the type MUST be
>> boolean, not Boolean.  That's well defined in the Java Beans
>> specification.
>>
>>
>> On Thu, May 29, 2014 at 12:41 AM, Lance Java
>> wrote:
>>
>>  Eg: https://gist.github.com/uklance/0d461f9618b3a131ca3b
>>>   On 28 May 2014 12:43, "Lance Java"  wrote:
>>>
>>>  Another solution is to override / decorate BeanModelSource. The easiest
 solution is call the default implementation then add the extra
 PropertyModel(s) to the BeanModel.


>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>