Debugging strange problems, unwanted persistance and similar (was: Re: Provider problems)

2003-10-13 Thread Jörg Walter
On Thursday, 09. October 2003 21:37, Christian Jaeger wrote:
 - Problem: somehow new requests depend on previous requests. Some
 state information is preserved between requests. When I request an
 .xml file as .html, then even subsequent .xml requests yield the
 .html. In spite of AxNocache On in the apache condig, so it
 doesn't seem like a cache problem (though that's prolly an unsolved
 problem still).

See http://www.axkit.org/wiki/view/AxKit/DebuggingStrangeProblems

-- 
CU
  Joerg

PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc
PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E  7779 CDDC 41A4 4C48 6F94


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Provider problems

2003-10-09 Thread Christian Jaeger
At 21:38 Uhr +0200 09.10.2003, Christian Jaeger wrote:
sub get_styles {
my $self=shift;
if ($$self{cjfile_media} eq 'html') {
$$self{apache}-content_type(text/html);
}
my $res= $myowntypemap{ $$self{cjfile_sourcetype} }{$$self{cjfile_media}};
if (!$res) {
warn CJ get_styles: fallback to super, since type/media
$$self{cjfile_sourcetype}/$$self{cjfile_media} not found;
$res= $self-SUPER::get_styles;
}
BTW:  I *have* to call $self-SUPER::get_styles for not providing any 
style at all. Returning [] or undef does not work, throwing an 
exception neither, the only thing is SUPER::get_styles since that one 
calls into an XS getstyle function witch seems to work.  This looks 
very strange to me and definitely looks like an unnecessary 
restriction (bug?). (Using AxKit CVS from a few weeks ago.)

Christian.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Provider Problems

2003-06-25 Thread Robert Ferney
On Wed, 2003-06-25 at 17:24, Michael Chamberlain wrote:
  Any ideas as to what is going on?
 
 
 I'd guess that your stylesheet isn't valid xml.
 
 Mike.

I thought of that, but when I test the same stylesheet by using an
on-disk version of the xml file the provider is generating and specify
the stylesheet either with the 
  AxAddProcessor text/xsl /xslt/user.xsl
or by adding the specification in via the xml header stylesheet
directive it works, without errors.. 
the stylesheet isn't changing, just not using the provider, which also
works by itself.. ie: I can browse to the provided file, as long as I
don't try to apply a stylesheet.

Attaching the stylesheet ..

?xml version=1.0?
xsl:stylesheet 
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
version=1.0

xsl:output 
method = html
version = 1.0
encoding = utf-8
omit-xml-declaration = yes
standalone = yes
doctype-public = -//W3C//DTD HTML 4.01 Transitional//EN
doctype-system = http://www.w3.org/TR/REC-html40/loose.dtd;
cdata-section-elements = 
indent = yes
media-type = text/html / 

xsl:template match=/
  html
head
  titlexsl:value-of select=/page/title //title
  link rel=stylesheet type=text/css href=/css/style.css /
/head
body
  marginheight=0 
  vlink=#003f7f 
  topmargin=0 
  leftmargin=0 
  marginwidth=0 
  bgcolor=#ff 
  link=#003f7f

xsl:apply-templates /
/body
  /html
/xsl:template

xsl:template match=users
  table border=0
  xsl:apply-templates select=username/
  xsl:apply-templates select=firstname/
  xsl:apply-templates select=surname/
  xsl:apply-templates select=email/
  /table
/xsl:template

xsl:template match=users/password
/xsl:template

xsl:template match=users/email
  tr
th
  xsl:value-of select=name()/
/th
td
  a href=mailto:{.};
xsl:apply-templates/
  /a
/td
  /tr  
/xsl:template

xsl:template match=users/*
  tr
th
  xsl:value-of select=name()/
/th
td
  xsl:apply-templates/
/td
  /tr  
/xsl:template

xsl:template match=@*|node()
   xsl:copy
 xsl:apply-templates select=@*|node()/
   /xsl:copy
/xsl:template

/xsl:stylesheet

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Provider Problems

2003-06-25 Thread Robert Ferney
I took a closer look at the error log.
It appears that the Provider is trying to handle the request for the
stylesheet even though the request is outside of the location that it is
supposed be handling,

so, perhaps more relevant question.
How do you get your provider to ignore requests for stuff it shouldn't
be handling in the first place.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Provider Problems

2003-06-25 Thread Robert Ferney
Ok, found the documentation for this..
http://www.axkit.org/wiki/view/AxKit/Apache::AxKit::Provider#
silly me.

On Wed, 2003-06-25 at 18:28, Robert Ferney wrote:
 I took a closer look at the error log.
 It appears that the Provider is trying to handle the request for the
 stylesheet even though the request is outside of the location that it is
 supposed be handling,
 
 so, perhaps more relevant question.
 How do you get your provider to ignore requests for stuff it shouldn't
 be handling in the first place.
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Provider Problems

2003-06-25 Thread Robert Ferney
Sorry for the mail spam yall.

ended up digging through the source for 
package Apache::AxKit::Provider::File;
...
sub get_strref {
...
throw Apache::AxKit::Exception::IO(
  -text = $self-{file} is a directory - please overload File
provider and use AxContentProvider option);
...
}

I think my problem was that my configuration was using 
AxProvider My::Provider
instead of 
AxContentProvider My::Provider

Changed that and now it works.

On Wed, 2003-06-25 at 18:48, Robert Ferney wrote:
 Ok, found the documentation for this..
 http://www.axkit.org/wiki/view/AxKit/Apache::AxKit::Provider#
 silly me.
 
 On Wed, 2003-06-25 at 18:28, Robert Ferney wrote:
  I took a closer look at the error log.
  It appears that the Provider is trying to handle the request for the
  stylesheet even though the request is outside of the location that it is
  supposed be handling,
  
  so, perhaps more relevant question.
  How do you get your provider to ignore requests for stuff it shouldn't
  be handling in the first place.
  
  
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]