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]



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]



selecting stylesheets

2003-06-25 Thread Robert Ferney
Another question.

is it possible to use the directives..

AxAdd*Processor

AxAddDynamicProcessor

and more than one of 

AxAddPlugin Apache::AxKit::StyleChooser::*

modules together in the same pipeline, such that each stage controls the
choice of stylesheet(s) for it's section?

I think there was one that would let you specify style sheets according
to which browser the client was using as well. 





-
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
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 ..


http://www.w3.org/1999/XSL/Transform";
version="1.0">

http://www.w3.org/TR/REC-html40/loose.dtd";
cdata-section-elements = ""
indent = "yes"
media-type = "text/html" /> 


  

  
  




  



  
  
  
  
  
  






  

  


  mailto:{.}";>

  





  

  


  





   
 
   




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

Re: Provider Problems

2003-06-25 Thread Robert Ferney
PS: I tried making a plain on disk xml file in another directory like
such..
---



  rob
  Robert
  Robert William Ferney
  Ferney
  [EMAIL PROTECTED]


and it works

On Wed, 2003-06-25 at 17:19, Robert Ferney wrote:
> I'm having trouble using a Provider, when I try to specify a Stylesheet.
> 
> my .htaccess file looks like this.
> -
> 
>   PerlHandler AxKit
>   AxProvider Edu::Provider::Student
> 
> #  AxAddProcessor text/xsl /xslt/user.xsl
> 
>   AddType text/xml .xml
>   AddHandler axkit .xml
> 
> -
> The Provider output looks like this.
> -
> 
> 
>   rob
>   Robert
>   Robert William Ferney
>   Ferney
>   [EMAIL PROTECTED]
> 
> -
> When I uncomment the AxAddProcessor I get the following error in my
> apache error log.
> --
> compilation error: file /user/rob.xml element users
> xsltParseStylesheetProcess : document is not a stylesheet
> [Wed Jun 25 17:00:01 2003] [error] [client 192.168.0.4] [AxKit] [Error]
> Can't call method "transform" on an undefined value at
> /usr/lib/perl5/site_perl/5.6.1/i386-linux/Apache/AxKit/Language/LibXSLT.pm line 120.
> --
> Any ideas as to what is going on?
> 
> 
> 
> 
> -
> 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]



Provider Problems

2003-06-25 Thread Robert Ferney
I'm having trouble using a Provider, when I try to specify a Stylesheet.

my .htaccess file looks like this.
-

  PerlHandler AxKit
  AxProvider Edu::Provider::Student

#  AxAddProcessor text/xsl /xslt/user.xsl

  AddType text/xml .xml
  AddHandler axkit .xml

-
The Provider output looks like this.
-


  rob
  Robert
  Robert William Ferney
  Ferney
  [EMAIL PROTECTED]

-
When I uncomment the AxAddProcessor I get the following error in my
apache error log.
--
compilation error: file /user/rob.xml element users
xsltParseStylesheetProcess : document is not a stylesheet
[Wed Jun 25 17:00:01 2003] [error] [client 192.168.0.4] [AxKit] [Error]
Can't call method "transform" on an undefined value at
/usr/lib/perl5/site_perl/5.6.1/i386-linux/Apache/AxKit/Language/LibXSLT.pm line 120.
--
Any ideas as to what is going on?




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



Re: processing instruction question

2003-06-25 Thread Matt Sergeant
On Wednesday, Jun 25, 2003, at 16:09 Europe/London, Ken Burcham wrote:

I feel like I'm simply missing something here.  Is there some easy way
to do what I'm trying to do?
You want AxAddDynamicProcessor.

Matt.

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


processing instruction question

2003-06-25 Thread Ken Burcham

Ok, this is probably the completely wrong way to do it.  So I look
forward to the gentle correction.  O

I'd like to use one xsp as my 'controller' and have it decide what to do
based on some action.  That action returns xml as its result.  I then
want the controller to pick the appropriate 'view' based on what the
action was and maybe a return code.  I'd like that 'view' to be an xsl
that is first in the pipeline before any other PI's that might already
exist for that xsp.

Any way of doing that?

I can't seem to see any way of defining a PI to work in Axkit
dynamically from within the xsp.  I tried a bunch of different things
but usually something like:


  my.xsl
  text/xsl


or I saw somewhere

"href=my.xsl, type=text/xsl"

I couldn't really find any documentation on it that had any examples of
what I'm trying to do.  Which always makes me suspect I'm trying to do
The Wrong Thing.  But in some cocoon stuff it sounded like that was
supposed to work?

Anyhow...  One alternative is to use AddAxkitRootProcessors for a given
xml root tag and then wrap some arbitrary xml element to trigger the
right xsl.  But that feels wrong.  (also, doesn't that work only against
the root element?  So if I have an xsp I would have already defined the
root and couldn't dynamically name it anyway).

So I'm left with making an xsp per each action and then specifying
(hardcoded-ly) in the top of the xsp the xsl I want it to be rendered
with first.  But of course that still doesn't give me the dynamic thing
I'm looking for.  

I feel like I'm simply missing something here.  Is there some easy way
to do what I'm trying to do?  

Thanks!

Ken.


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