Thanks for the suggestions.
I decided to put it on the Google app engine.
This appears to be free for my simple app.
The app is running smoothly with the following VM specs:
CPU 600MHz
RAM 128MB
It was very easy to set up with a Maven plugin or jetbrains Idea 12U.
Also they use a DNS Cname handle
Hi,
Thanks, yes I've used both these approaches. Assigning a page property is the
neater one IMO.
The Tapestry ways are better than defining stuff in the template and creating
clutter.
John
- Original Message -
From: Chris Poulsen
To: Tapestry users
Sent: Sunday, April 28, 2
Hi, Boris!
I did something similar in my recent project:
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/How-to-change-HTML-form-action-Or-is-there-any-better-option-td5720723.html
Maybe you find this useful.
On Sunday, April 28, 2013, Boris Horvat wrote:
> I need to forward
I need to forward some data to a given url (external to my application).
However I dont want to create a normal form as then I wont be able to use
tapestry mixins and such on field elements.
How can I achieve this to forward form process to an external url?
Cheers
--
Sincerely
*Boris Horvat*
You might find this page useful
http://tapestry.apache.org/tapestry-for-jsf-users.html
On 28 April 2013 10:43, Chris Poulsen wrote:
> Hi,
>
> You could get/set the bean instance in a page field before rendering the
> page. Then you would only perform the expensive get once.
>
> Or you could use
I've just committed changes to tapestry-cometd to support page activation
context in push events. I've deployed version 0.9.16 to my github maven
repository. Please increase your dependency version and give it a whirl.
Cheers,
Lance.
Hi,
You could get/set the bean instance in a page field before rendering the
page. Then you would only perform the expensive get once.
Or you could use @Cached for the bean getter.
--
Chris
On Sun, Apr 28, 2013 at 11:27 AM, John wrote:
> I'd like to be able to assign a bean to page scope so
I'd like to be able to assign a bean to page scope so that the property getter
is not repeatedly invoked. I'm guessing this might not be compatible with
Tapestry practice, but anyway.
I suppose I could assign a member as a persistent property and then switch it
as required, but I'd like to do s
Congrats!
And thanks for the great library!
On Sat, Apr 27, 2013 at 10:21 PM, Kalle Korhonen wrote:
> Oops, we did it again! We cleaned the security component issue list and cut
> a new release with a few nice little improvements. 0.5.0 was released a few
> months before but never announced. 0.
