You can read some of the discussion leading up to this change here:
http://markmail.org/thread/kf7jgc6oesbnjbfu
As far as I'm aware there isn't a setting that will let you turn it
back on other than running with production mode turned off. But I
might be wrong about that.
Mark
On Mon, Jun 27, 2
On Fri, 04 Mar 2011 06:11:59 -0300, Dany wrote:
Hi,
Hi!
This works an data don´t blood in requester but at the you have to
controll in your code. We follow this pattern because our application is
complex and we have to make component, following 3 layers (with EJB
(business logic) + hib
Hi,
Ok i provide you an example. Our objective is to build small component like
personal data, address etc... This small components are included in a Page.
Page will controller the validation for all components and general events.
For example:Page Tml
>
>
>
>
>
Page POJ
To reiterate: your code was broken in 5.1, just not as obviously as in 5.2.
On Wed, Mar 2, 2011 at 3:06 AM, Thiago H. de Paula Figueiredo
wrote:
> On Tue, 01 Mar 2011 23:30:42 -0300, Dany wrote:
>
>> Hi,
>
> Hi!
>
>> @Property
>> Private LoginVo loginVo;
>>
>> @Log
>>
On Tue, 01 Mar 2011 23:30:42 -0300, Dany wrote:
Hi,
Hi!
@Property
Private LoginVo loginVo;
@Log
@PageLoaded
void pageLoaded()
{
loginVo =new LoginVo();
}
@PageLoaded is triggered just once, when the page is instantia
Hi Howard,
Thanks for you soon reply. I have a doubt with repesct to you reply. If in
tapestry 5.2 it works with only one instance (like in a servlet) then it is
imposible to make the maching in a POJO/tml because this elements always is
going to be a mutable objects (in the same way that a servle
Yes, this is a subtle offshoot of the 5.2 changes. What you've done
is identify that single instance of LoginVO as the default value for
the loginVo field.
In 5.1, your bug was that different clients who accessed the same page
instance sequentially would see data bleed from one request to the
nex
I've made a little fix in Form component:
/**
* Id parameter
*/
@Parameter
private String id;
void beginRender(MarkupWriter writer)
{
if (null != id && !"".equals(id.trim())) {
clientId = id;
} else {
clientId = javascriptSupport.alloca
Entire form is inside the zone component, including submit button.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-Disable-element-id-autogeneration-tp3347539p3347955.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Put the submit button inside the zone as well, then it will link to the new
id.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Tapestry-5-2-Disable-element-id-autogeneration-tp5938959p5939355.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
---
Hi
just run
mvn javadoc:aggregate
in tapestry-project
regards
taha
On Sat, Dec 11, 2010 at 12:29 PM, Yohan Yudanara
wrote:
> Hi.
>
> I've just download tapestry-src-5.2.4.
> How can I generate documentation for offline reading?
>
> Should I run "mvn site" on every subfolder of tapestry-src-5
Hello,
You can take inspiration from this simple demo application :
http://github.com/lguerin/tapestwitter
This application is build on the following stack :
- Tapestry 5.2.0
- Spring (IoC and Spring Security)
- JPA (with Hibernate implementation)
- Unitils for Unit tests
- Selenium for Integrati
That's great news ... thanks for being a guinea pig on this. I
suspect you'll see a bit more PermGen usage, the same amount of thrash
in the eden space (mostly DOM nodes and temporary strings), but a lot
less in the long-lived heap.
On Wed, Oct 27, 2010 at 4:14 AM, Blower, Andy
wrote:
> First in
Only if you enable the pool again. It is deisabled by default.
On Wed, Oct 27, 2010 at 1:14 PM, Blower, Andy wrote:
> First indications show that the move away from page pooling has
> dramatically decreased the memory required by our Tapestry app. Thank you
> Howard. I've not been able to spend l
I am using PipedInputStream and PipedOutputStream to convert a large
OutputStream to StreamResponse, that needs a new thread.
For me, there is no problem with the new approach, just want framework
which is already very great to be perfect.
Yunhua
On Mon, Sep 27, 2010 at 4:57 PM, Howard Lewis Shi
True, there are some leaky abstractions related to the new approach;
there was a different set in the 5.1 version of the page lifecycle.
I've never felt the need to start up a thread from the middle of a
page. I'm curious what your use case is, and whether it wouldn't be
better handled
using Thre
Hi Thiago,
Thanks for your response. Yes, the code looks not nice, however, there
is nothing wrong with it. I knew there was a refactoring of changing
pool to singleton recently, so I was able to come up with a workaround
quickly, but for a Tapestry newbie, he/she might not know what's going
on, t
On Mon, 27 Sep 2010 16:47:38 -0300, Yunhua Sang
wrote:
Hi everyone,
Hi!
The field is always null when printing it out within run method; a
workaround is to define a local variable then access this variable in
new thread.I am wondering whether it's an expected behaviour or not.
It's expe
We're working to get the documentation up to snuff and to fix a few
more bugs before the beta release.
On Wed, Sep 15, 2010 at 4:50 AM, Everton Agner wrote:
> It's the reason I'm not using it yet, though
>
> ___
> Everton Agner Ramos
>
>
> 2010/9/15 Yohan Yudanara
>
>> Why no
It's the reason I'm not using it yet, though
___
Everton Agner Ramos
2010/9/15 Yohan Yudanara
> Why not publish it on tapestry homepage as 5.2 stable ?
>
> On Wed, Sep 15, 2010 at 3:05 PM, Massimo Lusetti
> wrote:
> >
> > Tapestry trunk is _very_ stable...
> >
> > Cheers
>
Why not publish it on tapestry homepage as 5.2 stable ?
On Wed, Sep 15, 2010 at 3:05 PM, Massimo Lusetti wrote:
>
> Tapestry trunk is _very_ stable...
>
> Cheers
> --
> Massimo
> http://meridio.blogspot.com
>
> -
> To unsubscribe
On Wed, Sep 15, 2010 at 8:26 AM, Sha Aith wrote:
> Is a stable version of Tapestry 5.2 expected anytime soon?
Tapestry trunk is _very_ stable...
Cheers
--
Massimo
http://meridio.blogspot.com
-
To unsubscribe, e-mail: users-un
Hi,
this is Igor Drobiazko's blog. Igor has written a very good book about
tapestry in german. As he told in another post, the book will be
published in english in some time!
Greetings
On 18.08.2010 17:55, 9902468 wrote:
Hi,
I know that this is little bit of and advertisement, but I just
On Thu, 12 Aug 2010 18:56:44 -0300, Darren Williams
wrote:
Thanks Thiago,
Hi!
we were trying to avoid rebuilding the beanModelSource on each render,
because it is backed by a large dataset.
I can't see the relation between a large data set and the BeanModel
creation. The same BeanMod
Thanks Thiago,
we were trying to avoid rebuilding the beanModelSource on each render, because
it is backed by a large dataset. We have modified your suggestion as shown
below. Is this the best technique to persist this value like we have here,
instead of constantly creating?
@Persist
On Thu, 12 Aug 2010 17:46:55 -0300, Darren Williams
wrote:
When upgrading to Tapestry 5.2 the inPlace Ajax grid no longer works. It
appears to be related to the sorting and the fact that the _grid sort
model gets reset to null when using the navigation. It works fine if you
don't use the
Raising this one from the dead.
I've followed all these instructions on the 5.2 alpha and I can't get
anything to work. The primary issue is that Tapestry appears to have
no knowledge of any of the security services. I receive this error in
the browser on load:
Exception assembling root component
No, tested in tomcat and jetty 6.
Plain old war packaged webapp...
2010/7/22 Sha Aith
>
> Thanks for the update. But I'm using Spring DM server in an OSGi
> environment.
> Are you using the same?
>
>
> Magnus Kvalheim-3 wrote:
> >
> > I'm using 5.1.0.5 with Spring 3 (in production).
> >
> > The
Thanks for the update. But I'm using Spring DM server in an OSGi environment.
Are you using the same?
Magnus Kvalheim-3 wrote:
>
> I'm using 5.1.0.5 with Spring 3 (in production).
>
> The key thing is the TapestyBeanFactory which was incompatible with spring
> 3.
>
> If I remember correctly -
I'm using 5.1.0.5 with Spring 3 (in production).
The key thing is the TapestyBeanFactory which was incompatible with spring
3.
If I remember correctly - the steps I did was:
1. copy 5.2 version of beanfactory:
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-spring/src/main/java/org
Thanks for the update. I'm using tapestry 5.0.18 and experiencing a lot of
performance issues. I thought of upgrading to 5.1.0.5 but dont want to do it
now because there are some bugs in 5.1.0.5. We also have plans to move to
Spring 3.0. I saw that 5.1 is not compatible with Spring 3. So, I'm eage
The aim is to release 5.2 before JavaOne which is in September.
On Wed, Jul 21, 2010 at 9:19 AM, Sha Aith wrote:
>
> When will a stable version of Tapestry 5.2 be released?
> --
> View this message in context:
> http://old.nabble.com/tapestry-5.2-tp29222616p29222616.html
> Sent from the Tapestry
Check http://old.nabble.com/Tapestry---Dev-f339.html
> http://old.nabble.com/Tme-for-an-alpha--ts29178526.html
== http://wiki.apache.org/tapestry/Tapestry5ModuleRegistry
== http://wiki.apache.org/tapestry/Tapestry5OpensourceApps
== http://wiki.apache.org/tapestry/Tapestry5HowTos
Sha Aith wrote:
The fix in
http://www.mail-archive.com/users@tapestry.apache.org/msg9.html is now
applied in 3.0-SNAPSHOT.
Regards,
Alex K
On Sun, Jun 27, 2010 at 11:30 PM, ebt wrote:
>
> Since there is not that much documentation out there concerning integrating
> the latest and greatest afore-mentioned
You can use eclipse quick fix to ignore this error.
2010/3/27, Peter Kanze :
> I solved the problem using this blog:
> http://dmitrygusev.blogspot.com/2009/10/develope-java-applications-with-gae-sdk.html
>
> I added the AppEngineDevAgent class (see below) to my project. But now I get
> this error
I solved the problem using this blog:
http://dmitrygusev.blogspot.com/2009/10/develope-java-applications-with-gae-sdk.html
I added the AppEngineDevAgent class (see below) to my project. But now I get
this error in Eclipse:
java.lang.instrument.Instrumentation is not supported by Google App Engine
36 matches
Mail list logo
