Re: RE: Re: object life

> I think part of the problem is the way I have > configured the abstract > class for Class::DBI. I don't know if there's > another way of doing it, > but I Have it read my config file for that > particular instance to figure > out paths and databases etc. This is, in my opinion, a bad idea. Clas

Re: Re: object life

Hi Daniel, I hope this helps, I've had to make some assumptions, so please feel free to correct me.. Firstly, the bad news. > Is there no way to turn that 'off' ? No:-) (none that I know of that are actually worth it) I think you have a fundamental problem that cannot be solved without some r

RE: Cookies not set

Forgive the daft question, but are the cookies only failing to be set on Internet Explorer 6 ? It could be that some of the users have Medium high or High Privacy settings, and you're not sending a P3P header.. so Internet explorer just ignores the set cookie Headers... Just a thought.. Regards

Re: Apache::DBI

Can you make sure its the very first PerlModule command? Usually this happens when a prior PerlModule command (or nested module) is calling "use DBI;" before the Apache::DBI module is loaded... this causes Apache::DBI to be disabled.. It must be called before any use DBI. And it is then universal

Embperl::Execute + mod_perl + POST

Hi all, I'm having some issues with Getting Embperl's fdat to work when I call Embperl::Execute from within a mod perl handler. I want to do this:- Embperl::Execute({ #req_rec=>$self->request, inputfile=>'/www/components/nav/htmlhe

RE: changing $req_rec

Hi Gerald.. If it's any help I tried writing a subclass of Embperl.pm and overriding the handler() method and putting in a call to Apache::Request->instance, but it just segfaulted... I then tried writing a handler that simply created the Apache::Request->instance and then called Embperl::handle

Re: changing $req_rec

Cheers Angus, That Makes a bucket load of common sense. :-) FYI the Apache::Request->instance() method - if used everywhere - makes sure that the $r you are using is a singleton (the same Apache->request object) throughout your handlers. Allowing the caching of data across handlers using pnotes..

Re: changing $req_rec

l script... Marty --- Martin Moss <[EMAIL PROTECTED]> wrote: > All, > > I have a legacy system with a lot of code. I'm > starting to use some mod perl handlers for PerlInit > & > PerlAuthen and possibly PerlTrans... The problem I > have is that $req_rec in any Embperl c

changing $req_rec

All, I have a legacy system with a lot of code. I'm starting to use some mod perl handlers for PerlInit & PerlAuthen and possibly PerlTrans... The problem I have is that $req_rec in any Embperl code is always based on an Apache->request object (or at least thats the impression I get)... What I wou

RE: 56: : Unknown Provider eprun

Yes, use Embperl; is almost at the top of our startup.pl script, just after Apache::DBI Marty > > First of all make sure that you have a > > PerlModule Embperl > > Or > > use Embperl ; > > Somewhere in your startup code of httpd. Do you have > it? > > Gerald > > > > > > -

ERR: 56: : Unknown Provider eprun

Hi, I've seen some posts on the web about this startup error. But no solution.. I'm wondering if it's simply a red herring message - and the real problem is something like a syntax error - simillar to the seg faulting (unstructured backward jump) issues we've experienced? Gerald, did you have any

Re: Embperl Session handling DISABLED because ...

It looks like you're running the latest version of embperl, but this latest version no longer supports Embperl::Session... (Or so I gathered from hunting google). I think you could replace it with Apache::SessionX, to get rid of your error, but as thats the stage I've just reached I haven't got a

Re: [RESEND] Trapping errors

> Instead use > > Execute({inputfile => '*', options => > Embperl::Constant::optReturnError, > errors => [EMAIL PROTECTED]) ; > if (@errors) { > Execute ( > } > I've been doing something recently with Execute and @errors, and I noticed that the @errors array also contained any 'warnin

Re: Req_rec undefined when calling Embperl::Execute from within a mod_perl Method handler

No worries, thanks Gerald, Marty --- Gerald Richter <[EMAIL PROTECTED]> wrote: > Hi, > > I have found the problem and trying to resolve it. > Just give me a few days > time... > > Gerald > > > Am Donnerstag, 17. Februar 2005 15:18 schrieb Martin > M

RE: Req_rec undefined when calling Embperl::Execute from within a mod_perl Method handler

Hi Gerald, We're using :- Apache 1.3.33, mod_perl-1.29, perl v5.8.6 on SunOS 5.7 Generic_106541-10 sun4u sparc SUNW,UltraSPARC-IIi-cEngine Regards Marty --- Gerald Richter <[EMAIL PROTECTED]> wrote: > > > > I'm trying to call Embperl::Execute to run an epl > from within > > a mod perl meth

Req_rec undefined when calling Embperl::Execute from within a mod_perl Method handler

All, I'm trying to call Embperl::Execute to run an epl from within a mod perl method handler, and when the script runs ---snip print STDERR Dumper($r); Embperl::Execute({ req_rec=>$r, inputfile=>'/www/components/nav/htmlhead.epl',