Re: best way of incorporating static pages?
Maybe it's just me and I didn't see the problem, but can't you just link to the cms content? The cms content has a link so why should tapestry service it? Is it on the same base domain? Then use request services to generate an absolute url. -magnus HTC one Den 12. juni 2013 13:07 skrev "John" følgende: > Hi, > > I have a need to link to some static HTML generated by a CMS app. Assuming > this content is in a directory outside my Tapestry app, what would be the > best way of linking/serving it via Tapestry? > > Perhaps I should just configure a seperate Jetty context and provide > absolute URLs in someway? > > I'd also consider the static content being part of the projects Java > resources, not so keen though. > > John
Re: Adding tapestry project to Cpanel
I'd recommend you to try some PaaS solution. They usually provide everything you need to host and scale your applications without deep knowledge of infrastructure. Trade offs are some restrictions that concrete PaaS solution may impose. On Sat, Jun 15, 2013 at 8:56 PM, Nomen Nomanum wrote: > Hi, Michael and thanks for reply. I was thinking, what about nginx, is > that also good reliable option to go? > > > From: michael.r.presc...@gmail.com > > Date: Sat, 15 Jun 2013 11:06:44 -0400 > > Subject: Re: Adding tapestry project to Cpanel > > To: users@tapestry.apache.org > > > > A search of this list will turn up some options, people were talking > about > > this within the last couple of months. I have an app running within > Jetty > > as a custom app on Webfaction. > > > > > > On 15 June 2013 11:00, Nomen Nomanum wrote: > > > > > Hi. > > > I have finished my first app, I am s happy and now I am in dilemma > how > > > and where to deploy it on the web. I have bought some server, and I > thought > > > to implement it in Cpanel, although it can get nasty while setup, not > to > > > mention Cpanel might not work around mydomain.com/8080:myApp problem. > > > ROOT.war won't work there. So for me it's yes or no now. I would be so > > > grateful, if you share some of your ideas about how and on what to > deploy. > > > > > -- Dmitry Gusev AnjLab Team http://anjlab.com
RE: Adding tapestry project to Cpanel
Hi, Michael and thanks for reply. I was thinking, what about nginx, is that also good reliable option to go? > From: michael.r.presc...@gmail.com > Date: Sat, 15 Jun 2013 11:06:44 -0400 > Subject: Re: Adding tapestry project to Cpanel > To: users@tapestry.apache.org > > A search of this list will turn up some options, people were talking about > this within the last couple of months. I have an app running within Jetty > as a custom app on Webfaction. > > > On 15 June 2013 11:00, Nomen Nomanum wrote: > > > Hi. > > I have finished my first app, I am s happy and now I am in dilemma how > > and where to deploy it on the web. I have bought some server, and I thought > > to implement it in Cpanel, although it can get nasty while setup, not to > > mention Cpanel might not work around mydomain.com/8080:myApp problem. > > ROOT.war won't work there. So for me it's yes or no now. I would be so > > grateful, if you share some of your ideas about how and on what to deploy. > >
Re: Adding tapestry project to Cpanel
A search of this list will turn up some options, people were talking about this within the last couple of months. I have an app running within Jetty as a custom app on Webfaction. On 15 June 2013 11:00, Nomen Nomanum wrote: > Hi. > I have finished my first app, I am s happy and now I am in dilemma how > and where to deploy it on the web. I have bought some server, and I thought > to implement it in Cpanel, although it can get nasty while setup, not to > mention Cpanel might not work around mydomain.com/8080:myApp problem. > ROOT.war won't work there. So for me it's yes or no now. I would be so > grateful, if you share some of your ideas about how and on what to deploy. >
Adding tapestry project to Cpanel
Hi. I have finished my first app, I am s happy and now I am in dilemma how and where to deploy it on the web. I have bought some server, and I thought to implement it in Cpanel, although it can get nasty while setup, not to mention Cpanel might not work around mydomain.com/8080:myApp problem. ROOT.war won't work there. So for me it's yes or no now. I would be so grateful, if you share some of your ideas about how and on what to deploy.
Re: Disabling filling form with old values on validation failure
You can reset field recorded value by calling recordInput method with null parameter value: tracker.recordInput(myField, null); The same way to reset recorded error for field: tracker.recordError(myField, null); On Fri, Jun 14, 2013 at 2:11 AM, Ryan How wrote: > It's really simple to make a validation tracker!. I'd just make your own > one to do what you want. Will take you less than 5 minutes I'm sure! > > But yes the tapestry auto tracking thing is a pain in the bum sometimes, > I've always struggled with it being too smart and not being able to turn it > off easily. Especially with AJAX because it doesn't work as 2 requests like > usual tapestry request, so storing the values in a flash variable then > resets the form the following request and arrgg! > > > > > On 14/06/2013 12:39 AM, Muhammad Gelbana wrote: > >> I haven't tried this but in your validation method, have you tried >> clearing >> the variable bound to your field ? >> >> >> On Thu, Jun 13, 2013 at 6:24 PM, Ryon Day wrote: >> >> I have a situation where the old form values are absolutely NOT helpful >>> in >>> any way after a validation failure; I cannot find a way to prevent >>> tapestry >>> from autofilling the old form values. >>> >>> Is this a possibility or am I going to have to subclass the validation >>> tracker implementation to provide value clearing? I do not want to clear >>> the whole tracker because I want to form to be in error, but I do not >>> want >>> the old input in the form fields. >>> >>> Thanks! >>> >>> >>> --**--** >>> - >>> To unsubscribe, e-mail: >>> users-unsubscribe@tapestry.**apache.org >>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >>> >>> > > > --**--**- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- BR Ivan
