Hi Vjeran,
probably is spring mvc handling the multipart request before tapestry, try
adding the following property in you springboot property file:
#This is extremely important otherwise Spring mvc will parse multipart request
and T5 file upload won't see them
spring.http.multipart.enabled=fal
... then this might save you some time:
The easiest way is to setup one vhost for HTTP and another for HTTPS in apache.
Terminate and handle the TLS/SSl connection in the apache HTTPS vhost as you
seem to be doing now
The two vhost should forward (Proxy pass) request to two distinct Tomcat
conne
Hi,
couldn't it be related to the servlet container config?
As far as I remember tapestry uses information provided by the servlet
container [1] to determinate if a given request is happening over a secure
connection or not.
So you might want to double check your container config.
Assuming you'
Hi Thiago,
did you had time to review my work?
I'm happy to finalize it if you think it's worth including.
Let me know,
Luca
Luca Menegus
D.B.M. S.r.l
Via Enrico Noe, 23 - 20133 Milano (MI) Italy.
Phone: +39 02 26600525
Mobile: +39 3346220663
- Original Message -
>
close and link TAP5-311 and TAP5-983 to the
new issue once created.
Luca
(*) while implementing the new test case I found out that two tests in
org.apache.tapestry5.integration.app1.BeanEditorTests
are not run because they miss the @Test annotation.
Luca Menegus
D.B.M. S.r.l
Via Enrico Noe
ect: Re: [T53] [BUG] Beandisplay can't be used inside a form
>
> On Fri, 01 Nov 2013 16:00:43 -0200, Luca Menegus wrote:
>
> > Hi all,
>
> Hi!
>
> > in
> > tapestry-core/src/main/resources/org/apache/tapestry5/corelib/components/BeanDisplay.tml
&g
Hi all,
in
tapestry-core/src/main/resources/org/apache/tapestry5/corelib/components/BeanDisplay.tml
the loop component has the formState parameter set to "ITERATION" while
(probably) should be set to "NONE".
I'm appending [3] a really simple example showing that this bug prevents the
Beandis
I think this affects checkboxes too...
Anyone interest in taking a look?
Luca
- Original Message -
> From: "Luca Menegus"
> To: "Tapestry users"
> Sent: Monday, September 2, 2013 9:50:28 PM
> Subject: Re: [T5.3.7 BUG] RadioGroup doesn't honor
... If you're going to use the example classes I provided note that method
onActionFromResetvalues should also reset the vowel var
public void onActionFromResetvalues() {
booleanValue = null;
textValue = null;
vowel = null; //<< From: "Luca Menegus"
Hi all,
I just found a bug with RadioGroup/Radio not honoring their disabled state (It
drove me quite mad...).
In RadioGroup submission is processed regardless of the disabled parameter
value.
In Fields derived from AbstractField submission processing is skipped
altogether when the field is
Hi,
can someone fix TAP5-1926 and have a look at the problem I reported on
BeanEditor and BeanValidation [1]?
And yes, Everything's stable with rc-7!
[1]
http://tapestry.1045711.n5.nabble.com/BeanEditor-should-always-provide-a-new-BeanValidationContext-JSR-303-tp5713975.html
- Original
Noboy intrested in using BeanEditor with JSR-303?
At the moment even:
Is not (bean)validating properly
Luca
- Original Message -
> From: "Luca Menegus"
> To: "Tapestry users"
> Sent: Tuesday, 19 June, 2012 12:49:52 PM
> Subject: BeanEd
Hi,
we are starting to use tapestry-beanvalidator and found that the current
BeanEditor implementation can't be used with complex beans (beans that contain
other beans) for beanvalidation.
The problem is that BeanEditor doesn't provide the correct
BeanValidationContext to the validation framew
> Thanks! By the way, DateFormats not being thread-safe is a huge WTF.
IMHO the whole Date, Calendar and DateFormat stuff are not really usable (or at
least are REALLY error prone).
What do you think about implementing first class support for joda-time [1] in
tapestry?
Cons:
* That would introd
> Please add an issue in JIRA and this will be fixed. Good catch.
>
> On Tue, May 8, 2012 at 10:03 AM, Luca Menegus
> wrote:
> > Hi,
> > in class org.apache.tapestry5.corelib.pages.PropertyDisplayBlocks
> > the DateFormat is declared as :
> >
> > private f
Hi,
in class org.apache.tapestry5.corelib.pages.PropertyDisplayBlocks the
DateFormat is declared as :
private final DateFormat dateFormat =
DateFormat.getDateInstance(DateFormat.MEDIUM, locale);
Which is not correct because DateFormat is not thread safe and pages aren't
pooled any more.
R
Hi all,
tapestry-spring (5.2.6) depends on spring 3 and not spring 2.5, this poses no
problems when injecting spring 2.5 beans into tapestry, but fails when trying
to inject tapestry services into spring (2.5.x):
Caused by: java.lang.NoSuchMethodError:
org.springframework.beans.factory.config.
11 at 9:11 AM, Howard Lewis Ship
> wrote:
> > My mistake, will fix shortly.
> >
> > On Apr 23, 2011 4:24 PM, "Luca Menegus" wrote:
> >> Hi,
> >> I've noticed that the latest tapx 1.1 snapshot [1] deployed into
> >> http://howardlewisship.
Hi,
I've noticed that the latest tapx 1.1 snapshot [1] deployed into
http://howardlewisship.com/snapshot-repository/ repository depends on
T5.3.0-SNAPSHOT and not on T5.2.x.
In facts it is no more usable with T5.2:
It throws IncompatibleClassChangeError when trying to load
com.howardlewisship.
Hi all,
don't know if this has been already reported but the new datefield
component's not working for me. The problem seems to lie in the onParse
methos of the org.apache.tapestry5.corelib.components.DateField class
which reads:
JSONObject onParse()
{
String input = request.getPara
20 matches
Mail list logo
