Re: Avoiding session creation for DirectActions

2016-05-31 Thread Mark Wardle
Don’t create sessions in your Direct Actions. Use existingSession() rather than session() (latter will create one if there isn’t one). For example: /** * Do we have a current and valid logged in user? * This method is careful not to create a session if one does not

Re: Deployment on CentOS 7 [Was: Re: Modern Deployment presentation]

2016-05-31 Thread Pascal Robert
> Le 30 mai 2016 à 21:53, Theodore Petrosky a écrit : > > Is there something special that I am missing. This is the first time I am > using a VM. I am running ESXi and I have a Centos 7 VM. It doesn’t matter if it’s a VM or not, it would been the same thing on a physical

Re: Deployment on CentOS 7 [Was: Re: Modern Deployment presentation]

2016-05-31 Thread Theodore Petrosky
> On May 31, 2016, at 12:05 AM, Paul Hoadley wrote: > > Hi Ted, > > On 31 May 2016, at 11:23 am, Theodore Petrosky > wrote: > >> Is there something special that I am missing. > > It’s hard to say. There’s no single way to

Re: WOLips server

2016-05-31 Thread Ramsey Gurley
Oh. Sorry. I thought it opened both. Been a while since I used it.On May 30, 2016 3:30 PM, Hugi Thordarson wrote: > > Does it? It only opens components for me, i.e. not the components’ java > classes but the WOComponent editor. > > - hugi > > > > > On 30. maí 2016, at 15:56,

Avoiding session creation for DirectActions

2016-05-31 Thread Musall Maik
Hi all, in an application that gets frequent DirectAction calls from other applications, I'd like to reduce the overhead of creating a new session for every request. Currently I'm setting a short timeout, but creating and removing all those sessions seems like avoidable overhead. How about

Re: Avoiding session creation for DirectActions

2016-05-31 Thread Hugi Thordarson
Hi Maik, Sounds like your application doesn't actually need sessions. I’d start by looking at where sessions are being created and then try to eliminate session creation altogether. Unless session() is explicitly invoked in your DAs or components, requests will generally not create new

Re: Avoiding session creation for DirectActions

2016-05-31 Thread Michael Kondratov
Maik, Why not use stateless components and avoid session creation all together? Michael Kondratov Aspire Auctions, Inc. 216-231-5515 > On May 31, 2016, at 11:35 AM, Musall Maik wrote: > > Hi all, > > in an application that gets frequent DirectAction calls from

Re: WOLips server

2016-05-31 Thread Hugi Thordarson
Still a good pointer. Opening and manipulating a java editor can’t be that much different from opening the component editor. Time to dig around in the code. Cheers, - hugi > On 31. maí 2016, at 14:03, Ramsey Gurley wrote: > > Oh. Sorry. I thought it opened both. Been

Re: New RPM package for the woadaptor for Apache 2.4

2016-05-31 Thread Elizabeth Lynch
Hi Pascal Installing this new RPM package didn’t work correctly on our CentOS7 Apache 2.4 servers. I’m not sure whether it’s something to do with my setup, or more general. On updating via yum update, the download and install appeared to go fine - but in fact the process deleted

Re: Avoiding session creation for DirectActions

2016-05-31 Thread Hugi Thordarson
…but if you want to discover where sessions are being created, Application.createSessionForRequest() is certainly an excellent way to do it. @Override public WOSession createSessionForRequest( WORequest request ) { Thread.dumpStack(); return super.createSessionForRequest( request