EmbperlObject, embpexec.pl, and logs

[James Churchill <ja...@corvu.com.au>]

Hi.

I've been preparing a site using 2.0b2 and EmbperlObject, and it seems to
work great.

The main problem I'm having is with trying to generate a page offline. I set
the embperl environment variables up the same as in my httpd.conf, however
embpexec.pl just gives me back a verbatim copy of the file I pass to it -
completely ignoring the base.epl.

I've tried setting every EMBPERL variable that seems even remotely
applicable, to no avail. If I can't get this going I will have to resort to
the small perl script I wrote to do a quick and dirty conversion of a page
into a valid document. Hardly the most elegant solution... :S

My other problem is with the embperl log file. I discovered today that every
page request dumps 30k or so of text into the logs... eek. Most of the log
text is either lines like this:

[20214]TOKEN:  [+ ... +]  unesc=1 nodetype=1, cdatatype=4, nodename=<null>

or lines like this:

[20214]CUP: Ignore Execute because it's imported

I'm hoping it's a simple configuration error on my part (my debug level is
already at 0.) In the interim I'm just going to have to redirect the logfile
to /dev/null. :(

----
James Churchill
jamesc@corvu.com.au


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org

Re: EmbperlObject, embpexec.pl, and logs

[Gerald Richter <ri...@ecos.de>]

Hi.
>
> I've been preparing a site using 2.0b2 and EmbperlObject, and it seems to
> work great.
>

I recommend to upgrade to 2.0b3 because it contains some important bug fixes

> The main problem I'm having is with trying to generate a page offline.

embpexec.pl only works for normal Embperl pages (not EmbperlObject).

The simplest way to use EmbperlObject offline, is to use the
HTML::EmbperlObject::Execute function and pass your configuration as
parameters

>
> My other problem is with the embperl log file. I discovered today that
every
> page request dumps 30k or so of text into the logs... eek.

Some of this output may disapear by upgrade to 2.0b3, but there is still
some debugging code in it, so redir to /dev/null is the safe solution. Of
course this debugging output  will disapear totaly within some of the nexts
betas and before the final release version

Gerald


-------------------------------------------------------------
Gerald Richter    ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de         Voice:    +49 6133 925131
WWW:        http://www.ecos.de      Fax:      +49 6133 925152
-------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org