Re: AxKit2, Apache and all that
As I understand it, you have a couple of choices. 1) You can run both apache1 and apache2 on the same server. But one of them will have to run on a different port. 2) Switch to axkit2, but use apache2 to handle certain things using ProxyPass and reverse proxying. I've heard of people even setting it up to handle static content like images and pdfs from apache and dynamic content through the proxy, but I've never done it. I think people using rails do that to speed stuff up. --simon -- http://simonwoodside.com On Jun 7, 2007, at 1:23 PM, Martijn wrote: Hello. I've been happily using AxKit for about five months now. It was installed and set up by someone who has left the company long ago, so I haven't set it up myself, but that usually doesn't give problems. Right now we are rebuilding our web server to a newer OS and I thought it would make sense to upgrade the software as well. So I upgraded from Apache1 to Apache2, from mod_perl1 tot mod_perl2 and... well, I think this meant I had not choice but to move to AxKit2 as well. So I downloaded it, installed some missing perl modules, ran the demo, which all worked well. And then I wanted to integrate it into the new web server. And this is when I started to panic a bit. 'AxKit2 does away with Apache', the wiki says. I have to admit that this very statement puzzled me at first, as I had always though of AxKit as just a mod_perl/Apache module but, if I understand correctly, it is actually working alongside Apache, only taking care of (in our case) the XML-to-XML-via-XSLT process? Okay, that makes sense. But still, I'd like Apache and mod_perl to do all the other things -serving images, pdfs, taking care of authentication etc.- they have been doing so nicely for me all this time. But I am kind of confused about where to start. Or, since I would like to keep using various existing AxKit plugins and taglibs, is the whole idea to move to AxKit2 right now just not very clever? I apologise if this is a very low-level question. I will happily share anything I learn by editing the wiki and, who knows, share new/changed modules with the community. Martijn. - 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: Axkit2 wiki
I just added this to the trac front page and made a link GettingStarted where we can put info about how to you know get started. --simon -- http://simonwoodside.com On Jan 18, 2007, at 11:09 AM, [EMAIL PROTECTED] wrote: Ants, you're right, I could've but I felt a bit of an idiot as no one else was asking the basic questions. What is the url to get the code out of svn ... if that's still the way it's done. I'll try and have another look at it. heh, Don't let that stop you. I frequently look an idiot. (see posts passim). I even had to ask the syntax of the svn command. How's that for basic? svn co svn://axkit.org/axkit2 John - 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]
bus error on OS X
I'm trying axkit2, you can see what I'm doing with http://trac.axkit.org/axkit2/wiki/GettingStarted Anyway, I installed XML::LibXML using the package in macports because 1.63 won't install in CPAN. I also used CPAN to install AxKit2 so that I would get the dependencies. Now when I run axkit and run the XSLT example I get good output in the browser, but afterwards axkit crashes with a Bus Error (see log below). Anyone else running on OS X? Can someone put up a list on the wiki with the important CPAN modules and what versions they have, for their working system? --simon [simons-tibook:new.semacode.org/axkit2/trunk] woodside% ./axkit L7 request_log register_hook: response_sent = hook_response_sent L7 stats register_hook: response_sent = hook_response_sent L7 stats register_hook: error = hook_error L7 error_xml register_hook: error = hook_error L7 fast_mime_map register_hook: mime_map = hook_mime_map L7 uri_to_file register_hook: uri_translation = hook_uri_translation L7 uri_to_file register_hook: fixup = hook_fixup L7 serve_cgi register_hook: body_data = hook_body_data L7 serve_cgi register_hook: response = hook_response L7 serve_file register_hook: write_body_data = hook_write_body_data L7 serve_file register_hook: response = hook_response1 L7 serve_file register_hook: response = hook_response2 L7 demo::serve_xslt register_hook: xmlresponse = hook_xmlresponse L7 demo::doc_viewer register_hook: xmlresponse = hook_xmlresponse 127.0.0.1:54480 L6 Connection from 127.0.0.1:54480 127.0.0.1:54480 L6 uri_to_file uri_translation translate: /xslt/ Root: /xslt 127.0.0.1:54480 L7 uri_to_file uri_translation Translated / to / Volumes/MacintoshHD/Users/woodside/Sites/new.semacode.org/axkit2/ trunk/demo/xslt/01.xml (request uri: /xslt/, path info: ) 127.0.0.1:54480 L7 demo::serve_xslt xmlresponse XSLT Transform 127.0.0.1:54480 L7 demo::serve_xslt xmlresponse Does /Volumes/ MacintoshHD/Users/woodside/Sites/new.semacode.org/axkit2/trunk/demo/ xslt/01.xml match (?-xism:.*\.xml$)? 127.0.0.1:54480 L6 Transformer::XSLT(/Volumes/MacintoshHD/Users/ woodside/Sites/new.semacode.org/axkit2/trunk/demo/xslt/stylesheets/ 01.xsl) running 127.0.0.1:54480 L7 Response sent Bus error [simons-tibook:new.semacode.org/axkit2/trunk] woodside% -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status Update: Docs!
You mean svn co svn://axkit.org/axkit2 ?? Just a little snark because you didn't give the svn location --simon On Aug 16, 2006, at 12:13 AM, Matt Sergeant wrote: So download (still only from svn) and run: -- http://simonwoodside.com
axkit2 won't start
Just did % svn co svn://axkit.org/axkit2 % cd axkit2/trunk/ % cp etc/axkit.conf.sample etc/axkit.conf % ./axkit Base class package Danga::Socket is empty. (Perhaps you need to 'use' the module which defines that package first.) at lib/AxKit2/Connection.pm line 37 BEGIN failed--compilation aborted at lib/AxKit2/Connection.pm line 37. Compilation failed in require at lib/AxKit2/Server.pm line 23. BEGIN failed--compilation aborted at lib/AxKit2/Server.pm line 23. Compilation failed in require at lib/AxKit2.pm line 21. BEGIN failed--compilation aborted at lib/AxKit2.pm line 21. Compilation failed in require at ./axkit line 19. BEGIN failed--compilation aborted at ./axkit line 19. I then used cpan to install Danga::Socket but that doesn't seem to have helped. --simon -- http://simonwoodside.com
Re: Q on semacode site using axkit /. effect
On Aug 13, 2006, at 7:33 PM, [EMAIL PROTECTED] wrote: Hi Simon, Oh and if you haven't already seen it in operation, visit my site below or http://semacode.org I was checking out semacode (cool software btw) the other day noticed you had a post on being /.'d was it the sheer number of hits on the server swamping the server or AxKit not being able to serve the results? (or something else). Well, I mean, it was linked to by slashdot. The site stayed up no problem, actually... I've had two /.ings on my creaky old server and AxKit has always held up under the load without breaking a sweat. My normal # of pages / day is about 4000 (3/minute), that particular /. wasn't too much, 1 pages on one day (7/minute), back in 2004 I had 20 000 pages (14/minute) in a day. Really not that much, I guess. Of course the peak loads were much higher. I don't have the stats for exactly how much higher but I'd expect 10x higher. So I guess I've probably served up to 3 pages / second on my creaky setup. (Note that's pages, not hits. Also, I haven't done load testing to determine the maximum. I imagine it's at least 10x more than that though.) It's 100% XML/XSLT and a little bit of mod_rewrite. Is there any areas you can think of that AxKit 2 may improve on compared to 1? Well I'd like to see working axkit: URIs :-) --simon -- http://simonwoodside.com
axkit weblog example
Matt I think that you mentioned that you want to put together a package of examples, including a weblog. I've got the code for my weblog in CVS. It's 100% XML/XSLT and a little bit of mod_rewrite. Do you want to use it? http://simonwoodside.com/cvs specifically look at http://simonwoodside.com/cgi-bin/viewcvs.cgi/simonwoodside/weblog/ and http://simonwoodside.com/cgi-bin/viewcvs.cgi/siteware-shared/ weblog/xsl/ The important files are - weblog.xml -- the data store - weblog.xsl -- the code - .htaccess -- the mod_rewrite rules Features: - RSS feed - multiple views: -- latest posts -- browse by day -- summary of latest posts -- just latest post titles - tagging: -- tag browser -- tag labels with number of other posts for each tag -- two-level tagging system (somewhat unique feature) Non-features: - no online blog post/editor -- currently have to edit the XML directly (I use oXygen) Anyway it's not exactly packaged but you can probably pull it out without too much trouble. Oh and if you haven't already seen it in operation, visit my site below or http://semacode.org --simon -- http://simonwoodside.com
Re: AxKit2 - a status update
First, I have to admit I'm nowhere near as savvy on the latest web
technologies as you are. I'm focused on other things at the
moment ... image recognition and my business ... but I am trying to
keep up with the latest web 2.0 stuff etc.
So, my use of AxKit1 right now: it's all XSLT and apache .htaccess
files. That's it, I have no perl, no XSP, nothing. I do however have
some pretty complex pipelines or actually pipeline trees to assemble
the final documents on http://semacode.org (100% axkit/xslt/apache)
like the front page which is assembled in maybe a dozen different
XSLT transforms from various files.
What I like about my system:
- it's 100% cached by axkit so it scales effortlessly
- since it's apache, I can mix in .php to send email, and I can use
mod_rewrite, etc, etc
What I don't like:
- it seems to be impossible to have such wonderful caching and also
have interactivity at the same time
So, for example, if I wanted to add a user login ... well, I was
thinking that for the pages that are static content, I could use AJAX
to do a user-side include for the dynamic content (like the
username, you have new messages, etc.) and keep the content largely
statically cached.
But what you're talking about seems like a major divergence. That's
cool, because I can't wait to see how it's all going to turn out. I'm
sure it will be interesting. But will it be a solution that I'll want
to use?
It seems like you're more abandoning the use of caching as a valuable
tool for scalability for example ... also it looks like I'll have to
write perl code to do anything (true?)
Anyway, my main interest is in continuing to explore the use of XSLT
pipeline/trees. I'd rather avoid writing procedural code (perl or
whatever). Is there something else that I should switch to? Will
AxKit1 be maintained?
--simon
On Jul 27, 2006, at 7:29 PM, Matt Sergeant wrote:
Well every once in a while someone still asks about AxKit 2. I know
this project has mostly floundered and people have gone on to other
things, but I still find some value in the XML paradigm for web
development - specifically in saving me from worrying about XSS
errors, but also it looks really useful for AJAX stuff.
Anyway... Where is AxKit 2.0?
Well it's coming. In the last few days I've thrown together a few
bits of code that are the framework for AxKit 2.0.
First things first: AxKit 2.0 is nothing like AxKit 1. It doesn't
even remotely resemble it. That's both a bad thing and a good
thing. I'll explain why.
But first, what does it look like? Well I spent a long time
thinking about what it meant to be AxKit, and I also spent a long
time thinking about how could I make it easier to use and install
in these days of quick setup frameworks like Ruby on Rails. Sadly
mod_perl is not quick to setup. Neither is Apache. These are large
complicated frameworks with lots of features I don't need on my
application server. Instead, AxKit2 has its own httpd. You can read
a bit about it here: http://use.perl.org/~Matts/journal/30438
Having our own httpd means that development and deployment is much
easier. Plus it frees us of the ties of Apache upgrade cycles and
mod_perl changes. I did not want to be stuck for an AxKit3 when
Apache 3.x comes out!
So I wrote a simple pluggable scalable httpd. It's all pure perl,
so no nasty compilation required (except obviously you still have
to compile XML::LibXML etc). Plugins can trivially add
configuration directives, making development of new subsystems fast
and easy.
And yes it's buggy as all hell right now. But it'll get better I
promise.
Now, on to what the AxKit part looks like. Well I decided that
I'd had enough of special cases and extra wrapper code inside the
AxKit internals - we spend so much effort in there making sure
dependencies are logged and checked, and caching is done at every
step of the way and so on. All this actually slows the whole thing
down, and makes the code really ugly. So it's gone. If you want to
cache from now on it will be DIY.
And all that config directives stuff to setup pipelines - that got
really ugly if you wanted alternate pipelines. So that's all gone
too. Instead AxKit becomes an API for setting up the transformation
pipelines, and a bunch of utility modules for helping that out.
Everyone can write perl, and if you can't the examples will be
simple enough, or someone will write a plugin to set all this up
via config directives.
So let's do a quick example. Say you want to do XSP - XSLT - XSLT
- HTML. Here's what the code you'll write will look like:
sub hook_response {
my $self = shift;
my $file = $self-{headers_in}-filename;
# setup the processor
my $proc = AxKit2::Processor-new($file);
my $s1 = /path/to/xslt1.xsl;
my $s2 = /path/to/xslt2.xsl;
# run the transform ($out is an AxKit2::Processor also)
my $out =
Re: AxKit2 - a status update
OK, as long as the caching is better then that's OK I guess... I did some work on mediawiki a few months ago when they were having trouble keeping up with scaling and really solidified my previous opinion that scaling well is all about static caching. I mean, putting off anything dynamic to be as late in the pipeline and as small as possible. In the case of wikipedia, their code is just a nasty nightmare spaghetti monster... that I don't have the time to untangle right now. But with my own stuff on semacode.org I do want to add user logins and interactive features eventually. On the other hand, I don't want to use AxKit for everything, at least for the foreseeable future. For example I've adopted Sympa as my mailing list manager. It's really good, too. I'd like to build bridges between these different platforms and I'm still trying to figure out how that's going to work (some kind of common auth framework presumably is needed). I don't want to have to use the AxKit MLM (since there isn't one now anyway...) but I do want to be able to integrate everything seamlessly. --simon On Aug 6, 2006, at 10:11 AM, Matt Sergeant wrote: On 6-Aug-06, at 3:28 AM, S. Woodside wrote: But what you're talking about seems like a major divergence. That's cool, because I can't wait to see how it's all going to turn out. I'm sure it will be interesting. But will it be a solution that I'll want to use? I hope so. :-) It seems like you're more abandoning the use of caching as a valuable tool for scalability for example ... No, that's not quite right. I'm abandoning AxKit's crazy efforts it goes to to try and ensure the cache is used in the right places. Instead you control the cache. Think of it as a pipeline you can inject the cache into - if you want it - and where you want it. Scalability should be much better with AxKit2. I haven't done any real comparisons yet, but I see no reason that it shouldn't be much improved. There's so much less baggage with AxKit2. also it looks like I'll have to write perl code to do anything (true?) If you want to do anything out of the ordinary yes - but you can already use the demo XSLT plugin if all you want to do is XSLT and everything then is setup in axkit.conf. The thing was - if you wanted to do stuff out of the ordinary with AxKit1 it was a really difficult mix of providers, plugins, and so on. My aim is to make that simpler, plus provide some very cool tools for building applications (maybe a hook to Catalyst or Jifty or something else entirely new). Anyway, my main interest is in continuing to explore the use of XSLT pipeline/trees. I'd rather avoid writing procedural code (perl or whatever). Is there something else that I should switch to? Will AxKit1 be maintained? AxKit1 will probably have one more release. There's no reason there shouldn't be an AxKit1 maintainence track, but new development won't happen there. -- http://simonwoodside.com
Re: document() problems
On Jan 1, 2006, at 2:19 PM, Lars Skjærlund wrote:
apply-templates select=document('menu.xml')/* /,
this will start off at the root.
Right you are - that did the trick. I'm not sure I quite understand
why
(yet), but that will come, I hope.
You're selecting into the new document. So then you can write
templates that catch whatever elements are in the new document.
One problem you will typically have is that you want a different set
of templates to match on the secondary document (menu.xml or
whatever). What I usually do is either use a different namespace for
the second file ... or, I use template modes:
apply-templates mode=FOO select=document('menu.xml')/some/path/
--simon
--
http://simonwoodside.com
Re: Slow response time
On Oct 21, 2005, at 1:53 PM, Michael A Nachbaur wrote: I would say that the most likely culprits would be either your XSL stylesheet processing taking up an inordinate amount of time or a slow net connection. If it's XSL then you can profile your code with % xsltproc --profile I found it very easy to use. Also badly written SQL queries are a common cause of slowness in web apps... --simon -- http://simonwoodside.com
Re: xsl document(test.xml?style=test) - the stylechooser is not applied
This is a FAQ now :-)
you need this:
AxAddPlugin Apache::AxKit::Plugin::AddXSLParams::Request
PerlSetVar AxAddXSLParamGroups VerboseURI
then for it to cache those pages you need this:
AxAddPlugin Apache::AxKit::Plugin::QueryStringCache
--simon
On Aug 24, 2005, at 7:41 PM, Tom Kirkpatrick wrote:
I should have done a copy paste job when writing this out to the
mailing list - my fault... My document() call actually looks like
this:
xsl:copy-of select=document('http://localhost/articles/
testpage.xml?style=html')/
ie. it does use the complete URL, thus forcing AxKit to do a full
request. However, the querystring is not being passed on - The
error logs show the request for the URL as 'articles/testpage.xml'
Could this be a bug in libXSLT?
On 24 Aug 2005, at 06:39, [EMAIL PROTECTED] wrote:
I am trying to include a fragment of an XML document using the XSL
document() function. I need to be able to use a querystring in
the URI in
order to select the appropriate style via the StyleChooser module.
I have the following code:
xsl:copy-of select=document('testpage.xml?style=html')/
xsl:copy-of select=document('testpage.xml?style=meta')/
However both requests ignore the querystring and the default
style is
applied to each.
Unfortunately the only way to get querystring params applied is to
do a full request, i.e. using the http: scheme. The default
implementation with no scheme is sort of like file:, but within
the web filesystem hierarchy.
Matt.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
It's fast, it's easy and it's free. Get MSN Messenger 7.0 today!
http://messenger.msn.co.uk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://simonwoodside.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache::SubRequest
This is the best info I could find on Apache::SubRequest objects. http://www.samspublishing.com/articles/article.asp? p=27110seqNum=17rl=1 simon -- Simon Woodside - Founder Semacode Corporation http://semacode.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: help with AxKit warning messages
This indicates that there was an exception, axkit crashed, and what
you're looking at is the stack trace.
simon
On May 16, 2005, at 7:28 AM, [EMAIL PROTECTED] wrote:
It seems that for every single page request I make, AxKit throws up a
lot
or warnings in my httpd.errorlog file. I have several steps in my
transformation pipeline, and it seems that every single stage throws up
warnings similar to the one I have detailed below. (To get this one, I
disabled all but one very basic transformation stage).
I have absolutely noea what any of this means... It seems to display
the
page ok though... Is this normal? Can I suppress these messages
somehow?
Can anyone tell me what it actually means?
[Mon May 16 12:04:37 2005] [warn] [client 10.33.1.178] [AxKit] fast
handler called for /index.xml
some condition failed. recreating output
parser match_cb: at
/usr/local/lib/perl5/site_perl/5.8.5/mach/Apache/AxKit/Language/
LibXSLT.pm
line 55.
at
/usr/local/lib/perl5/site_perl/5.8.5/mach/Apache/AxKit/Language/
LibXSLT.pm
line 55
Apache::AxKit::Language::LibXSLT::handler('Apache::AxKit::Language::
LibXSLT',
'AxKit::Apache=SCALAR(0xce16d48)',
'Apache::AxKit::Provider::File=HASH(0xce16e68)',
'Apache::AxKit::Provider::File=HASH(0xcfd6b08)', 1) called at
/usr/local/lib/perl5/site_perl/5.8.5/mach/AxKit.pm line 759
AxKit::process_request('AxKit::Apache=SCALAR(0xce16d48)',
'Apache::AxKit::Provider::File=HASH(0xce16e68)', 'ARRAY(0xcf3947c)',
'undef') called at /usr/local/lib/perl5/site_perl/5.8.5/mach/AxKit.pm
line
474
AxKit::run_axkit_engine('AxKit::Apache=SCALAR(0xce16d48)',
'Apache::AxKit::Provider::File=HASH(0xce16e68)') called at
/usr/local/lib/perl5/site_perl/5.8.5/mach/AxKit.pm line 300
eval {...} called at
/usr/local/lib/perl5/site_perl/5.8.5/mach/AxKit.pm line 291
AxKit::main_handler('AxKit::Apache=SCALAR(0xce16d48)',
'Apache::AxKit::Provider::File=HASH(0xce16e68)') called at
/usr/local/lib/perl5/site_perl/5.8.5/mach/AxKit.pm line 204
AxKit::fast_handler('AxKit::Apache=SCALAR(0xce16d48)') called
at
/dev/null line 0
eval {...} called at /dev/null line 0
Bad free() ignored (PERL_CORE) at
/usr/local/lib/perl5/site_perl/5.8.5/mach/Apache/AxKit/Language/XSP.pm
line 108.
for refereince-
[xsltproc --version
Using libxml 20619, libxslt 10114 and libexslt 812
xsltproc was compiled against libxml 20619, libxslt 10114 and libexslt
812
libxslt 10114 was compiled against libxml 20619
libexslt 812 was compiled against libxml 20619]
Many thanks
--
Tom David Kirkpatrick
Virus Bulletin Web Developer, Virus Bulletin
Tel: +44 1235 555139
Web: www.virusbtn.com
--
Tom David Kirkpatrick
Virus Bulletin Web Developer, Virus Bulletin
Tel: +44 1235 555139
Web: www.virusbtn.com
-
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: mailing list archives
On May 16, 2005, at 12:23 PM, fess wrote:
On May 15, 2005, at 12:46 PM, S. Woodside wrote:
I moved my investigation into axkit: URIs over to
axkit-dev@xml.apache.org btw.
I'm excited to see you working on this.
As I had ended up getting too confused trying to figure it out.
As you know, I did figure out that using old versions of things worked,
but I found a situation where even that broke, and the work around was
to add an extra xslt transformation.
here's the post I had put out on that:
http://maclux-rz.uibk.ac.at/maillists/axkit-users/msg07580.shtml
Not sure if it will be of any help to you, but perhaps it might ring
some bell.
Hi fess!
Damn, I just spent the whole weekend and got to exactly the same spot
you did. I'm a bit lost too, but maybe together we can figure it out?
(without the real developers who seem to be asleep at the wheel :-P )
You wrote:
So,
I setup a provider, that returned XML, in a scalar reference.
OK, in my case I'm just using the LibXSLT.pm provider.
I then tried to access this provider from within XSLT using an axkit
provider.
and I would get:
[Error] input callback died: axkit:/attachments.xml?filename=03.jpg
internal request didn't store anything in dom_tree or xml_string at
[.../]Language/LibXSLT.pm
For me, I'm getting the stack trace that you saw in my earlier message.
However I have determined something interesting, which is that at some
latish stage, LibXSLT is playing with the right stylesheet but the
wrong XML document.
In other words, there is XML in pnotes('xml_string') but it's the wrong
stuff. Weird eh?
So, I added some debugging in Axkit.pm::get_axkit_uri()
and I found that
OK, this code you're quoting is actually in Provider.pm get_xml_info()
isn't it?
if ($@) {
eval {
my $pstr = $provider-get_strref;
$str = $$pstr;
print STDERR Debug: $str\n;
$r-pnotes('xml_string', $str);
print STDERR Debug: , $r-pnotes('xml_string'), \n;
print STDERR Debug: , ref($r), \n
$result_code = OK;
};
if ($@) {
$result_code = 'provider_declined';
}
}
even though, my scalar reference is being returned, and it has the xml
snippet in it,
it's not being stored in the pnotes, as that comes out empty, when
trying to read it
back. I'm not sure what the issue is. $r is an Apache::SubRequest
object,
so I guess it's possible that that has something to do with it.
Yeah, that's exactly where I wound up. (see my post on axkit-dev
yesterday,
http://mail-archives.apache.org/mod_mbox/xml-axkit-dev/200505.mbox/
[EMAIL PROTECTED] )
I'm not like a perl expert, but how can you have this:
my $str_ref = $self-get_strref();
$r-pnotes('xml_string', ${$str_ref});
and then check $r-pnotes('xml_string') and there's nothing there??? It
doesn't make sense...
Does this mean that there's a bug in Apache::SubRequest? Oddly that
module doesn't seem to be in CPAN.. .hmm.. there is
Apache2::SubRequest...
hmm... there is a test in make test for subrequests, which seems to be
failing for me. I'm working off the latest CVS by the way.
No, I'm afraid I can't find anything called Apache::SubRequest. Are
you sure that's the type?
I have to stop playing with this on my new server and set it up for
production, but, I can continue to investigate on my home machine if
you have any useful feedback.
--simon
I didn't have time to do further testing, but I wanted to point this
out
in case it rang any bells with anyone.
I found a work around, which was to add an xslt stylesheet to the
pipeline
on top of my provider, this caused things to work, not sure why.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: axkit exception with latest CVS
[Cross posting to axkit-dev as I'm not sure which list to use for this.]
OK, I think I've made some headway in debugging this problem.
On May 13, 2005, at 10:57 PM, S. Woodside wrote:
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
LibXSLT match_uri: axkit:/xinc/sitemenu.xml
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
get_axkit_uri(axkit:/xinc/sitemenu.xml)
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
get_axkit_uri looking up abs: '/xinc/sitemenu.xml'
Note the document in question here is /xinc/sitemenu.xml
This document is located (temporarily for the moment) at
http://semacode.netdirect.ca/xinc/sitemenu.xml
If you follow that link you will see that processing that file directly
works perfectly. It's just XML with a single XSLT processing it,
nothing fancy.
[...]
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] [uri]
File Provider looking up uri /xsl/sitemenu.xsl
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] [uri]
File Provider set filename to /var/www/semacode.org/xsl/sitemenu.xsl
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] about
to execute: Apache::AxKit::Language::LibXSLT::handler
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
[LibXSLT] getting the XML
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
[LibXSLT] parsing stylesheet
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
[LibXSLT] parsing stylesheet /xsl/sitemenu.xsl
here it grabs the right stylesheet...
[...]
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
[LibXSLT] storing results in pnotes(dom_tree)
(AxKit::Apache=SCALAR(0x842f9ac))
note the result is in pnotes(dom_tree)
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
Apache::AxKit::Language::LibXSLT::handler finished with code 0
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
execution of: Apache::AxKit::Language::LibXSLT::handler finished
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
get_axkit_uri returning (str): '?xml version=1.0 encoding=UTF-8?
[...]
get_axkit_uri returning (str):
AHA!
AxKit.pm (in CVS) line 581:
if ( my $str = $r-pnotes('xml_string') ) {
# NB: this is naive, but 0 isn't valid XML anyway
$r-pnotes('xml_string', undef);
AxKit::Debug(10, get_axkit_uri returning (str): '$str');
return $str;
}
elsif ($r-pnotes('dom_tree')) {
my $str = $r-pnotes('dom_tree')-toString;
$r-pnotes('dom_tree', undef);
AxKit::Debug(10, get_axkit_uri returning (dom): '$str');
return $str;
}
So it's reading the result out of pnotes('xml_string') which is the
WRONG place ! :-) It should be reading out of pnotes('dom_tree').
Anyway, the XML result is clearly the wrong one. It's actually the XML
from the very start of the pipeline, it's NOT sitemenu.xml or the
processed output of sitemenu.xml, which would look like this (again
from http://semacode.netdirect.ca/xinc/sitemenu.xml ) :
?xml version=1.0?
pagexhtmldiv id=sitemenu
div class=sitemenuitemba href=/software title=Semacode
software for downloadSoftware/a/b for download/div
div class=sitemenuitemba href=/about title=What is
SemacodeAbout/a/b what is it?/div
div class=sitemenuitemba href=/about/apps title=What can
you do with SemacodeApplications/a/b of semacode/div
div class=sitemenuitemba href=/create title=Make a
semacodeCreate/a/b online/div
br/
div class=sitemenuitemba href=/weblog title=Weblog with
news and thoughtsSemablog/a/b latest news and thoughts/div
div class=sitemenuitemba href=/support title=Get help with
semacodeSupport/a/b /div
div class=sitemenuitemba href=/about/contact title=Contact
usContact/a/b /div
/div/xhtml/page
So it seems as though the test, if ( my $str = $r-pnotes('xml_string')
) isn't valid any more. It seems that at some previous date, it was
correct to assume that pnotes('xml_string') would return 0 if the
result was actually in dom_tree. But now there is XML in
pnotes('xml_string') ... just not the right stuff.
--simon
\n?xml-stylesheet type=text/xsl href=/xsl/site.xsl ?\n\npage\n
header\ntitleURL barcodes | practical ubicomp/title\n
/header\n sidebarincludeblog//sidebar\n xhtml\n\n\ndiv
class=floating_right\ndiv class=menuicons\n a
href=/software/readerimg src=/software/images/reader.gif
alt=//a\n a href=/software/serverimg
src=/software/images/server.gif alt=//a\n a
href=/software/sdkimg src=/software/images/sdk.gif
alt=//a\n br/\n a href=/about/technicalimg
src=/about/images/technical.gif alt=//a\n a
href=/about/hardwareimg src=/about/images/hardware.gif
alt=//a\n a href=/about/platformimg
src=/about/images/platform.gif alt=//a\n br/\n a
href=/about/apps/cases/2004_10_09img src=/images/conqwest.gif
alt=//a\n a href=/about/apps
Re: Installation on RHEL3
On May 4, 2005, at 2:16 AM, Kjetil Kjernsmo wrote: On tirsdag 03 mai 2005, 13:53, Martin Oldfield wrote: I've got to install AxKit on an RHEL3 box. OMG! Has anyone done this recently ? Yeah. It was a full night in intense agony... RH apparently had no intention of making that easy. Essentially, I had to hand-compile Apache 1 and mod_perl 1 from clean sources. Then, AxKit itself is straightforward. I was trying this week to install onto FCS3 and gave up because I didn't feel like building apache1 yet again by hand (done it too many times on OS X ...) I just dumped FCS3 and went to debian. I thought I'd mess with Fedora but ... ehh... it's not a desktop so debian still rulez. --simon -- Simon Woodside - Founder Semacode Corporation http://semacode.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Installation on RHEL3
On May 5, 2005, at 5:18 AM, Alex Sergeyev wrote: Hi, In order to have axkit uris work, I had to downgrade to: libxml2 2.5.10-1 libxslt 1.0.33-2 perl-XML-LibXML 1.56-1 perl-XML-LibXSLT 1.53-1 Guys, do you have any ideas about lenght of this period and happy day in future, when axkit:// URI (and other AxKit things) will work with actual newest libraries? So is this a problem with the libraries, or a problem with AxKit? I mean, thinking that maybe I might try to fix it myself. simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axkit exception with latest CVS
Hi I'm setting up a new server. I will be moving semacode.org to this
server as soon as it's ready. It's debian testing fresh install. I
installed apache, libxml, etc. from apt-get.
% xsltproc -V
Using libxml 20616, libxslt 10112 and libexslt 810
xsltproc was compiled against libxml 20616, libxslt 10112 and libexslt
810
libxslt 10112 was compiled against libxml 20616
libexslt 810 was compiled against libxml 20616
Then I installed AxKit from CPAN and got a problem with axkit: URIs
which I use heavily... I think I remember reading a known bug on the
list... so I decided to give AxKit from CVS a shot. I got myself the
latest AxKit from the anon cvs. When I built it I got one error in the
test:
t/xslt-basic/05_params.APXS
(/usr/local/apache/bin/apxs) query for SBINDIR failed
Anyway, I went ahead and installed it, following the instructions at
http://axkit.org/cvs.xml
Now I get an error again the apache error log. The log is at the bottom
because it's pretty long.
The file sitemenu.xml verifies with xmllint and anyway, it works on my
laptop with an older AxKit. Anyway the pipeline is just index.html
(which is actually XML) being processed with site.xsl. Looking at the
log it seems like it's processing the axkit: URI which is in the my
site.xsl (xsl:copy-of
select=document('axkit:/xinc/sitemenu.xml')/page/xhtml/*/) but then
I don't know... it's saying get_axkit_uri returning (str): '...' which
is the untransformed index.html. And then it complains about line 1 of
sitemenu.xml which is valid XML.
simon
log:
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
handler called for /index.html
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
Running plugin: Apache::AxKit::Plugin::AddXSLParams::Request
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
Running plugin: Apache::AxKit::Plugin::QueryStringCache
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
Content Provider Override: Apache::AxKit::Provider::File
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
decoding from UTF-8
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] [req]
File Provider given $r: /var/www/semacode.org/index.html
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
checking if we process this resource
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] media:
screen, preferred style: #default
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] Cache:
key = db0175a0eeefeb05dc8728cc792698a5
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
getting styles and external entities from the XML
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] styles
not cached - calling $provider-get_styles()
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
encoding to UTF-8
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] using
XS get_styles (libxml2)
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
calling xs_get_styles_fh()
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] using
XS get_styles (libxml2)
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
calling xs_get_styles_str()
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
parse_pi: type = text/xsl
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
parse_pi: href = /xsl/site.xsl
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
xs_get_styles returned: , , page
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
Calling GetMatchingProcessors with (screen, , , , page)
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
get_styles: loading style modules
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
get_styles: looking for mapping for style type: 'text/xsl'
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] cache
doesn't exist
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] some
condition failed. recreating output
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
styles: Apache::AxKit::Language::LibXSLT(/xsl/site.xsl)
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] Style
Provider Override: Apache::AxKit::Provider::File
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] [uri]
File Provider looking up uri /xsl/site.xsl
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] [uri]
File Provider set filename to /var/www/semacode.org/xsl/site.xsl
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit] about
to execute: Apache::AxKit::Language::LibXSLT::handler
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
[LibXSLT] getting the XML
[Fri May 13 18:08:31 2005] [warn] [client 69.157.21.164] [AxKit]
[LibXSLT] parsing stylesheet
[Fri May 13 18:08:31 2005]
Re: [ANNOUNCE :] Apache-AxKit-Provider-RDBMS
On Mar 11, 2005, at 5:17 AM, Tom Schindl wrote: Hi, sometime ago I promised in a thread that I will upload a Provider which lets you fetch content from a database not using XSP which has the draw-back that AxKit cannot cache the transform results. say that again? Yours does cache or doesn't? --simon -- Simon Woodside - Founder Semacode Corporation http://semacode.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
new version please!
Hi it's been 16 months since the last release of AxKit. Is there a new version planned? Should I be using CVS? It scares me because it might be unstable... simon -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Akit URI trouble.
On Jan 5, 2005, at 1:02 PM, John Fessenden fess wrote: I'm also running on OSX 10.3.7, I wonder if that has anything to do with this. when I get a chance I'll setup on my debian box and see if i get the same errors. I'm also running on 10.3.7, works fine for me. My AxKit.pm version is 1.62. % uname -a Darwin simons-tibook.local 7.7.0 Darwin Kernel Version 7.7.0: Sun Nov 7 16:06:51 PST 2004; root:xnu/xnu-517.9.5.obj~1/RELEASE_PPC Power Macintosh powerpc % xsltproc -V Using libxml 20506, libxslt 10033 and libexslt 722 xsltproc was compiled against libxml 20506, libxslt 10033 and libexslt 722 libxslt 10033 was compiled against libxml 20506 libexslt 722 was compiled against libxml 20506 % /usr/local/apache/bin/httpd -V Server version: Apache/1.3.29 (Darwin) Server built: Feb 14 2004 01:49:20 Server's Module Magic Number: 19990320:15 Server compiled with -D HAVE_MMAP -D USE_MMAP_SCOREBOARD -D USE_MMAP_FILES -D HAVE_FCNTL_SERIALIZED_ACCEPT -D HAVE_FLOCK_SERIALIZED_ACCEPT -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D DYNAMIC_MODULE_LIMIT=64 -D HARD_SERVER_LIMIT=256 -D HTTPD_ROOT=/usr/local/apache -D SUEXEC_BIN=/usr/local/apache/bin/suexec -D DEFAULT_PIDLOG=logs/httpd.pid -D DEFAULT_SCOREBOARD=logs/httpd.scoreboard -D DEFAULT_LOCKFILE=logs/httpd.lock -D DEFAULT_ERRORLOG=logs/error_log -D TYPES_CONFIG_FILE=conf/mime.types -D SERVER_CONFIG_FILE=conf/httpd.conf -D ACCESS_CONFIG_FILE=conf/access.conf -D RESOURCE_CONFIG_FILE=conf/srm.conf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Akit URI trouble.
John, it works for me. Here's what I have.
=== a.xml ===
?xml-stylesheet href=ab.xsl type=text/xsl?
page
titlea.xml/title
contentblah/content
/page
=== b.xml ===
?xml-stylesheet href=ab.xsl type=text/xsl?
page
titleb.xml/title
contentde dah/content
/page
=== ab.xsl ===
?xml version=1.0?
xsl:stylesheet
xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version=1.0
xsl:output
method=xml
indent=yes/
xsl:template match=/page
html
head
title
xsl:value-of select=title/
/title
/head
body
xsl:value-of select=content/
/body
/html
/xsl:template
/xsl:stylesheet
=== null.xml ===
?xml-stylesheet href=a+b.xsl type=text/xsl?
null/
=== a+b.xsl ===
?xml version=1.0?
xsl:stylesheet
xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version=1.0
xsl:output
method=xml
indent=yes/
xsl:template match=/
combined
xsl:copy-of select=document('axkit:a.xml')/
xsl:copy-of select=document('b.xml')/
/combined
/xsl:template
/xsl:stylesheet
=== OUTPUT ===
?xml version=1.0?
combined
html
head
titlea.xml/title
/head
bodyblah/body
/html
?xml-stylesheet href=ab.xsl type=text/xsl?
page
titleb.xml/title
contentde dah/content
/page
/combined
--simon
On Dec 17, 2004, at 12:30 PM, John Fessenden fess wrote:
On Dec 16, 2004, at 9:55 PM, S. Woodside wrote:
I'm thinking you've got a recursive loop here. You said you had:
xsl:template match=/
combined
xsl:copy-of select=document('axkit:a.xml')/
xsl:copy-of select=document('b.xml')/
/combined
/xsl:template
presumably this xslt is being called from a.xml? In that case,
calling document('axkit:a.xml') would be infinitely recursive and
therefore very bad.
nope. I'm calling it from null.xml, which looks like this:
?xml-stylesheet href=a+b.xsl type=text/xsl?
null/
any other ideas?
--fess
--
http://simonwoodside.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Akit URI trouble.
I'm thinking you've got a recursive loop here. You said you had:
xsl:template match=/
combined
xsl:copy-of select=document('axkit:a.xml')/
xsl:copy-of select=document('b.xml')/
/combined
/xsl:template
presumably this xslt is being called from a.xml? In that case, calling
document('axkit:a.xml') would be infinitely recursive and therefore
very bad.
simon
On Dec 13, 2004, at 1:26 PM, John Fessenden fess wrote:
On Dec 10, 2004, at 2:01 PM, S. Woodside wrote:
can we see a.xml?
thanks for responding!
here's a.xml, b.xml and ab.xsl
a.xml
--
?xml-stylesheet href=ab.xsl type=text/xsl?
page
titlea.xml/title
contentblah/content
/page
b.xml
--
?xml-stylesheet href=ab.xsl type=text/xsl?
page
titleb.xml/title
contentde dah/content
/page
ab.xsl
--
?xml version=1.0?
xsl:stylesheet
xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version=1.0
xsl:output
method=xml
indent=yes/
xsl:template match=/page
html
head
title
xsl:value-of select=title/
/title
/head
body
xsl:value-of select=content/
/body
/html
/xsl:template
/xsl:stylesheet
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Iconv RH 9 not seeing but is installed
It's a wiki put it back yourself :) simon On Dec 16, 2004, at 11:53 AM, David Nolan wrote: (Though the link to my version seems to have dissappeared from the main page of the wiki. Can someone put it back please?) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Akit URI trouble.
can we see a.xml?
simon
On Dec 6, 2004, at 12:50 AM, John Fessenden fess wrote:
continuing with my explorations in how to have a pipleine, then a
cache point, then another pipline for dynamic stuff
I'm attempting to use akit URI's.
I'm trying to use the following construct in an xsl file
xsl:template match=/
combined
xsl:copy-of select=document('axkit:a.xml')/
xsl:copy-of select=document('b.xml')/
/combined
/xsl:template
However this results in an exception that I can't grok. I've tried
various experiments but gotten no where.
Any ideas what I'm missing?
here's the error log below with the exception, starting with the log
that shows
the a.xml file was fetched.
[Sun Dec 5 21:44:28 2004] [warn] [client 127.0.0.1] [AxKit]
get_axkit_uri returning (dom): '?xml version=1.0?
htmlheadtitlea.xml/title/headbodyblah/body/html
'
[Sun Dec 5 21:44:28 2004] [warn] [client 127.0.0.1] [AxKit] Caught an
exception
[Sun Dec 5 21:44:28 2004] [error] [client 127.0.0.1] [AxKit] [Error]
axkit:a.xml:1: at
/Users/fess/check/rampplans.org/ext/lib/perl5/Apache/AxKit/Language/
LibXSLT.pm line 124.
[Sun Dec 5 21:44:28 2004] [error] [client 127.0.0.1] [AxKit] From:
/Users/fess/check/rampplans.org/ext/lib/perl5/Apache/AxKit/
Exception.pm : 9
[Sun Dec 5 21:44:28 2004] [error] [client 127.0.0.1] [AxKit]
[Backtrace] axkit:a.xml:1: at
/Users/fess/check/rampplans.org/ext/lib/perl5/Apache/AxKit/Language/
LibXSLT.pm line 12
4.
Apache::AxKit::Exception::new('Apache::AxKit::Exception::Error','-
text','axkit:a.xml:1: at
/Users/fess/check/rampplans.org/ext/lib/pe...') called at
/Users/fess/check/ram
pplans.org/ext/lib/perl5/AxKit.pm line 1016
AxKit::prep_exception('axkit:a.xml:1: at
/Users/fess/check/rampplans.org/ext/lib/pe...') called at
/Users/fess/check/rampplans.org/ext/lib/perl5/AxKit.pm line 173
AxKit::__ANON__('axkit:a.xml:1: at
/Users/fess/check/rampplans.org/ext/lib/pe...') called at
/Users/fess/check/rampplans.org/ext/lib/perl5/Apache/AxKit/Language/
LibXSLT.p
m line 124
Apache::AxKit::Language::LibXSLT::handler('Apache::AxKit::Language::
LibXSLT','AxKit::Apache=SCALAR(0x1a405d4)','Apache::AxKit::Provider::
File=HASH(0x19f198c)','Apache::AxK
it::Provider::File=HASH(0x19f1a40)',1) called at
/Users/fess/check/rampplans.org/ext/lib/perl5/AxKit.pm line 759
AxKit::process_request('AxKit::Apache=SCALAR(0x1a405d4)','Apache::
AxKit::Provider::File=HASH(0x19f198c)','ARRAY(0x19f1198)','undef')
called at /Users/fess/check/rampplans.
org/ext/lib/perl5/AxKit.pm line 474
AxKit::run_axkit_engine('AxKit::Apache=SCALAR(0x1a405d4)','Apache::
AxKit::Provider::File=HASH(0x19f198c)') called at
/Users/fess/check/rampplans.org/ext/lib/perl5/AxKit.pm
line 300
eval {...} called at
/Users/fess/check/rampplans.org/ext/lib/perl5/AxKit.pm line 291
AxKit::main_handler('AxKit::Apache=SCALAR(0x1a405d4)','Apache::AxKit::
Provider::File=HASH(0x19f198c)') called at
/Users/fess/check/rampplans.org/ext/lib/perl5/AxKit.pm lin
e 204
AxKit::fast_handler('AxKit::Apache=SCALAR(0x1a405d4)') called
at /dev/null line 0
eval {...} called at /dev/null line 0
thanks.
--fess
-
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: can you do this with document('http://...') ?
Sebastian, What do you do if the name you want in the breadcrumbs is different from the directory name? simon On Nov 23, 2004, at 5:44 PM, Sebastian Rahtz wrote: I do bread crumbs by passing the Apache $REQUEST to the XSLT and parsing it in XSLT. Seems to work OK. I don't like the idea of maintaining dir.xml files. -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new user - is AxKit right for me?
On Oct 1, 2004, at 12:57 AM, Sebastian wrote: From my own experiences, using XML data sources leads to poorer performance because of the parsing overhead, so I wouldn't suggest using them for large-scale projects. I find it odd that you would say that especially in light of the info Matt just posted about performance. In my experience with my site having been slashdotted and boingboing'ed (I had in one day 120 000 hits and 19 000 pages) the performance has been very smooth on a minimal box. This is all due to caching - when I left caching off another time the server got totally slugged (oops) due to a boingboing'ing. I never replied to Matt's thread but I want to say that when I picked AxKit it was partially due to the promise of fantastic scalability due to caching - and that's been borne out for me by experience. I also credit my success to heavy-duty use of CSS to keep the page sizes way down. simon -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new user - is AxKit right for me?
I agree. I've had a number of times when I've been volunteering for organizations building web sites, and I could clearly see that if I was building it myself, AxKit would make it easy, fast, scalable and easy (for me) to maintain. But I couldn't expect them to find people to grok XML and XSLT after I left. :-P How does AxKit performance compare to Cocoon? simon On Oct 1, 2004, at 10:58 AM, Tod Harter wrote: Personally I think the only really MAJOR question is customer acceptance. Someone is going to have to maintain your application and depending on the application there may be people (possibly 3rd parties) managing content and styling information. Those people may need to be exposed to technologies like XSLT. A common kind of thing with webapps you may get is 'Yeah, well our designers cannot deal with this XSLT stuff, they want (plug in whatever here CF, ASP, Mason, PHP, etc) templating technology instead'. -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSLT-accessed query params and testing existance
On Jul 8, 2004, at 6:53 AM, Kjetil Kjernsmo wrote: xsl:param name=foo select=''/ Is that line really necessary? Yes, but you can simplify it to xsl:param name=foo/ it will automatically default to '' (empty string) if nothing is passed in. You need it in order to define the param inside the xslt. simon -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSLT-accessed query params and testing existance
xsl:choose xsl:when test=$url_parameter != '' !-- it was set -- /xsl:when xsl:otherwise !-- it was not set -- /xsl:otherwise /xsl:choose simon On Jul 7, 2004, at 10:56 AM, Kjetil Kjernsmo wrote: But then, I need to test whether a parameter exists... In XSP that's straightforward, thanks to the many good taglibs, but I haven't found anything on checking the parameters in XSLT, is it doable? -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxNoCache...
are you sure about that? on linux x86 I use PIs for everything and have no performance problems. simon On Jun 15, 2004, at 7:06 AM, Mike Chamberlain wrote: Don't use PI's, or any of the AxAdd directives which require to snoop the xml. (ie look at the first node for node name, namespace or dtd). -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axkit survives a slashdotting
The hardware is some kind of pentium class box running debian. Nothing
very beefy.
The pipeline is more like a tree. It's all XSLT.
index.html is processed by /xsl/site.xsl
(all of the files on the site are .html but mime-mapped to XML)
site.xsl copies in a bunch of static content include files using
statements like:
xsl:copy-of select=document('/xinc/banner.xml')/
I also use an axkit: URI in site.xsl, :
xsl:copy-of
select=document('axkit:/weblog/front.xml')/page/xhtml/*/
this is why I said it's more like a tree. This creates a new axkit
pipeline, the result of which is a weblog-style output in the left
content pane.
The secondary/weblog pipeline has the following PI stylesheets in order
- /weblog/xsl/weblog.xsl
- /weblog/xsl/blog2front.xsl
front.xml is basically just a config file that calls these XSLTs with a
number value that defines how many recent weblog entries to display.
weblog.xsl gathers the weblog entries from the weblog data store. it's
just a XML file, weblog.xml. Something like this
xsl:apply-templates
select=document($weblog.source_file,.)/weblog/entry/
the results are passed along to blog2front.xsl which converts it to an
HTML format suitable for a front-page summary style of display
That's the end of the weblog secondary pipeline. The results are fed
back into site.xsl and the final output of that is HTML, sent to the
client.
Obviously when I change weblog.xml, it re-caches the whole thing.
I really like XSLT and I think by using it I avoided the worries about
needing to regenerate for every single load which you get with XSP.
I had about 125000 hits on saturday and sunday. At the peak it was
probably well over 100 hits/ second. Of those, 18000 on each day were
page hits.according to webalizer. I figure at the peak, when it was
first on /., it was probably 3 or 4 times the day's average, which was
5 pages a second. Must have been a slow day for slashdot ;-)
simon
On May 9, 2004, at 5:34 AM, Michael A Nachbaur wrote:
S.Woodside wrote:
Hi my site http://semacode.org just got slashdotted but survived just
fine. The load average is at 1.00, caching is on, it's all XSLT (no
XSP though) serving up the weblog feed on the main page and
everything. No problemo.
Congratulations! Can you give a bit more information about the
hardware and the pipeline layout? I've performed benchmark tests with
ab numerous times on my AxKit websites, but there's nothing that can
equal a Slashdotting for testing the true merit of your application's
performance.
--
Michael A. Nachbaur [EMAIL PROTECTED]
http://nachbaur.com/pgpkey.asc
--
http://simonwoodside.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: axkit survives a slashdotting
Oh yeah, one more thing. I'm really careful about keeping the number of bytes down, on the two big days I served up 900 MB each day (with the 125000 hits each day) simon On May 9, 2004, at 5:34 AM, Michael A Nachbaur wrote: S.Woodside wrote: Hi my site http://semacode.org just got slashdotted but survived just fine. The load average is at 1.00, caching is on, it's all XSLT (no XSP though) serving up the weblog feed on the main page and everything. No problemo. Congratulations! Can you give a bit more information about the hardware and the pipeline layout? I've performed benchmark tests with ab numerous times on my AxKit websites, but there's nothing that can equal a Slashdotting for testing the true merit of your application's performance. -- Michael A. Nachbaur [EMAIL PROTECTED] http://nachbaur.com/pgpkey.asc -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axkit survives a slashdotting
Hi my site http://semacode.org just got slashdotted but survived just fine. The load average is at 1.00, caching is on, it's all XSLT (no XSP though) serving up the weblog feed on the main page and everything. No problemo. simon -- http://simonwoodside.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: providing style from dynamic XSL
On Mar 22, 2004, at 8:17 AM, Tod Harter wrote: All true, but remember that AxKit caches the DOM trees of every stylesheet in memory, so 'dynanic' is more like 'whatever happens the 1st time is what you will get until you restart apache', though some provider level hacking can fix that, unless I've missed some progress in that area since the last update to AxKit I got, cause 1.62 I'm pretty sure is pretty pig-headed abou this! Interesting a) I've always been doing this with caches off I think b) wouldn't axkit notice that the file changed and recache simon -- 99% Devil, 1% Angel homepage http://www.simonwoodside.com for the developing world http://www.openict.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: providing style from dynamic XSL
On Mar 21, 2004, at 3:42 PM, Dave Roe wrote:
Hi Simon,
On Mar 19, 2004, at 8:17 PM, S. Woodside wrote:
You can generate XSL using the exsl document output function, then
run the generated XSL on a document using the regular XSL document()
function.
If you need more info I can provide it.
Yes, please.
snip
I'm talking about the creation of dynamic XSL. In other words,
code-generation, and then executing the generated code. EXSLT provides
a document function, which is supported by LibXSLT. (you don't need to
download anything from exslt.org) You activate it in your XSL with
something like this
xmlns:exsl=http://exslt.org/common;
extension-element-prefixes=exsl
in the xsl:stylesheet element. Then exsl:document ... will create
xml output into a separate document file. You also create a dummy
genxsl (or whatever) prefix,
xmlns:genxsl=foobarfoo
Then you need a namespace alias:
xsl:namespace-alias stylesheet-prefix=genxsl result-prefix=xsl/
This will convert anything that's prefixed genxsl: in your stylesheet,
into xsl: in the output. Then do something like this:
exsl:document href=gen.xsl indent=yes encoding=UTF-8
genxsl:stylesheet version=1.0
...
and insert your code there. Any xslt prefixed with genxsl will execute
when you run the generated code, anything prefixed with xsl will run
now. You can mix and match.
To run the generated code, just fire off an axkit: URI document request:
xsl:copy-of select=document('axkit:/foo/bar.xml')/
Use the usual axkit methods to specify that bar.xml will go through
gen.xsl
simon
--
99% Devil, 1% Angel
homepage http://www.simonwoodside.com
for the developing world http://www.openict.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: providing style from dynamic XSL
You can generate XSL using the exsl document output function, then run the generated XSL on a document using the regular XSL document() function. If you need more info I can provide it. simon -- 99% Devil, 1% Angel homepage http://www.simonwoodside.com for the developing world http://www.openict.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axkit on OS X panther
I installed successfully on Panther after a fresh wipe of the boot partition and reinstall of fink. I documented what I did here: http://simonwoodside.com/dev/axkit/howto.html (it's a bit different from the previous incarnation of the howto) simon -- 99% Devil, 1% Angel homepage http://www.simonwoodside.com for the developing world http://www.openict.net member of http://www.mozilla.org/projects/camino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axkit on OS X panther
Hi did anyone ever get axkit working on 10.3 (OS X panther) ? I'm trying but I get linking errors when I try to install XML::LibXML. Sorry I don't have output available right now. I'm just wondering if anyone (Arne?) got it to work and what they did. simon -- 99% Devil, 1% Angel homepage http://www.simonwoodside.com for the developing world http://www.openict.net member of http://www.mozilla.org/projects/camino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LibXSLT document() source-relative URL handling
There's a way to force document() to be source relative or style-sheet relative based on the second parameter, which you would set to either . or ... check the XSLT FAQ http://www.dpawson.co.uk/xsl/sect2/sect21.html simon -- 99% Devil, 1% Angel homepage http://www.simonwoodside.com for the developing world http://www.openict.net member of http://www.mozilla.org/projects/camino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Phat/Rich Clients, AxKit, and the Web's Future
On Tuesday, November 25, 2003, at 08:49 AM, Robin Berjon wrote: S Woodside wrote: On Monday, November 24, 2003, at 08:12 AM, Robin Berjon wrote: For the forms stuff, stealing from Cocoon and looking into that server-side implementation of XForms (that converts to HTML+script) from IBM would imho be interesting steps. For the WS part, I think that making U-shaped pipelines easier to set up and use would do most of the job (to allow others to build stuff more easily). I think we can do without support for SOAP/RPC (which most big cos are giving up on anyway) and focus on supporting document/literal SOAP, which fits our idea of a document much better IMHO. does this mean the same as roundtripping the data? Hmm, no, at least I don't think so. Which part made you think that? Did you have anything more in mind? What's a U-shaped pipeline? I was just going to explain what roundtripping the data meant but now I can't remember. simon -- 99% Devil, 1% Angel homepage http://www.simonwoodside.com for the developing world http://www.openict.net member of http://www.mozilla.org/projects/camino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Phat/Rich Clients, AxKit, and the Web's Future
On Wednesday, November 19, 2003, at 07:22 PM, Michael A Nachbaur wrote: So, anyway, to answer the question, I would like to see better support for outputting RDF in AxKit. Perhaps I had better spit the RDF out as a result of an XSL transform, but somehow that never occurred to me before. Right .. I was just going to say, what makes RDF so special that you can't use the normal XMLish tools to generate it? simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Phat/Rich Clients, AxKit, and the Web's Future
How's your cross-browser compatibility for that? simon On Thursday, November 20, 2003, at 10:43 AM, Tod Harter wrote: Interesting. I am trying a different tack. My client-side application is built by loading an initial page, which contains javascript logic which goes back to the server via XMLHttpRequest(), gets whatever data is required for the particular operation being performed (served back as raw XML by the server side), applies XSLT to it, and attaches the resulting UI to the DOM tree in whatever is designated as the content area for whatever enclosing UI element is holding this 'panel' or whatnot. XUL could certainly be incorporated in there, but basically what I have is a component and a corresponding XSLT to instantiate it. You can go back and forth to the server all day and there are no 'pages' being loaded. In fact the application becomes entirely a normal event-driven GUI, albeit with some javascript glue logic. -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTML output processing
probably you have (in XSLT) output set to HTML which converts it into a non XML format. But you have just stumbled into the nastiest hornet's nest of XHTML, which is that there's no agreed-upon MIME type for XHTML. And older browsers will, of course, choke on XHTML especially if you set one of the more correct mime types (that is, not text/html). I don't remember all the details, but it's all well put out in an article called XHTML considered harmful or seomthing like that. Personally, I do my final output from XSLT in HTML format. simon On Wednesday, November 19, 2003, at 08:40 AM, Andy Gale wrote: Hi, I've recently started using AxKit and XSP/XSLT to produce web pages. I'm trying to output XHTML 1.0 with certain formatting quirks such as no carriage returns after liblah/li elements. Using the AxTraceIntermediate directive I've managed to ascertain that something seems to converting my XHTML into HTML and reformatting it. This is causing a problem with the rendering in IE. I can find no description in any of the documentation as to why this would happen. Is there anyway to get around this? Regards, Andy -- Andy Gale Developer, intY Ltd, Bristol, UK [e: [EMAIL PROTECTED] w: www.inty.com t: +44 (0)1454 640512] intY has scanned this email for all known viruses (www.inty.com) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
updated os x install instructions
Hi I just updated my OS X install instructions (I just installed AxKit on a fresh 10.2.8) http://simonwoodside.com/dev/axkit/howto.html simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axstylename
U... no it won't ... think about it ... simon On Monday, November 10, 2003, at 07:56 AM, Tod Harter wrote: FILESMATCH (foo|bar) AxAddProcessor ... bothgetthis.xsl AxStyleName foo AxAddProcessor ... somethingforfooonly.xsl /AxStyleName AxStyleName bar AxAddProcessor ... somethingforbaronly.xsl /AxStyleName /FILESMATCH should do you just fine ;o). On Sunday 09 November 2003 11:21 pm, S Woodside wrote: That's cool, but not quite what I was thinking about. I want to be able to do something like this: AxStyleName foo|bar AxAddProcessor ... bothgetthis.xsl /AxStyleName AxStyleName foo AxAddProcessor ... somethingforfooonly.xsl /AxStyleName AxStyleName bar AxAddProcessor ... somethingforbaronly.xsl /AxStyleName That's a vertical OR bar (|) BTW (foo OR bar) simon -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AxKit::App::Gallery, AxHandleDirs and axkit:: URI
Hi there,
I'm messing around ::Gallery (thanks nik!) and I ran into a problem
with AxHandleDirs. Apparently it doesn't co-exist well with the axkit:
URI. I can be ultra specific at this point because I haven't created a
simple test case. But it looks kinda like the wrong stylesheets are
being applied when a document('axkit:') call is made.
anyone else ever seen that?
...
This got me hacking for a workaround (there isn't any clean one, I
can't use document('http://mysite.com/foo/bar.xml') for relative
requests...) and then thinking about AxHandleDirs which has given me
grief in the past. I don't like the way AxHandleDirs works. I think it
goes against the file-oriented design of AxKit and the apache config
files. There's lots of useful apache directives (like Files ...) and
AxAdd*Processor directives that can be used with files. But with
AxHandleDirs you basically are pretty limited in your options.
Not only that, but it's kind of odd because you only get the XML back
if the UA opens the directory foo/bar/ ... you don't get the XML
directory file back if you call foo/bar/index.html . I think that's
wrong -- the directory XML should replace index.html by default. Or you
could name the file with something like AxHandleDirs filename.xml And
then if you request that file, you get the auto-generated index for the
dir it resides in.
simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit::App::Gallery, AxHandleDirs and axkit:: URI
On Sunday, November 9, 2003, at 02:42 AM, S Woodside wrote: I can be ultra specific at this point s/can/can't/ simon -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axstylename
AxStyleName #default It owuld be cool if you could give it multiple name such as: AxStyleName #default|rss which would match on default or on ?style=rss as well. simon -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axstylename
On Sunday, November 9, 2003, at 11:06 PM, Kip Hampton wrote: S Woodside wrote: AxStyleName #default It owuld be cool if you could give it multiple name such as: AxStyleName #default|rss which would match on default or on ?style=rss as well. You can make a named style the default using the AxStyle directive: AxStyleName foo ... Processor definitions ... /AxStyleName AxStyleName bar ... Processor definitions ... /AxStyleName AxStyleName baz ... Processor definitions ... /AxStyleName AxStyle foo This causes the named style foo to be applied as the default, fallback style. That's cool, but not quite what I was thinking about. I want to be able to do something like this: AxStyleName foo|bar AxAddProcessor ... bothgetthis.xsl /AxStyleName AxStyleName foo AxAddProcessor ... somethingforfooonly.xsl /AxStyleName AxStyleName bar AxAddProcessor ... somethingforbaronly.xsl /AxStyleName That's a vertical OR bar (|) BTW (foo OR bar) simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit vs CGI with XSLT and XSL
James, On Wednesday, November 5, 2003, at 12:38 PM, James Lavery wrote: The current prototype manages navigation around the site and choice of stylesheet, by processing the CGI submission events (using the CGI::XMLApplication Perl module) and then using Perl code called from the CGI script. Using axkit one of the benefits you can get is a very good caching mechanism. Does AxKit support user session/login management as part of its core functionality? No. With AxKit, how does one set up the basic stylesheet-selection mechanism? For example, if a user fills data on a page produced using stylesheet A, how to take the user to stylesheet B, displaying data produced from having queried the database using parameters supplied in stylesheet A. I presume that ultimately we're into HTML forms etc., or do I presume wrong? If you mean XSLT stylesheets, then correct, HTML forms it is. AxKit doesn't supplant HTML .. it serves it ;-) (Oh yes, and are people generally using XpathScript or XSL?) Everyone uses XSLT :-D simon -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mac OS X and AxKit (further info)
Well if it's going to dynamically link at runtime against the new one, then just move aside the one on your machine (supplied by apple???) when you are building so it doens't see it.. simon On Thursday, November 6, 2003, at 07:05 PM, Arne Claassen wrote: I decided to look a little more closely what happens when AxKit builds and it's building against the DSO apache on my machine rather than the new one. AxKit's Makefile.PL uses Apache::src to find apache, which reports the wrong apache.. I can't determine how Apache::src determines the apache to use and how to change it. Any information on that? thanks, arne On Nov 1, 2003, at 11:23 AM, Arne Claassen wrote: http://axkit.org/wiki/view/AxKit/Tutorials I looked that over and decided to rebuilt my apache as statically linked. Unfortunately that just got me to the point where apache configtest complains about unresolved symbols in AxKit. Mind you, all components build, it's just that on configtest it errors out. I didn't see any config options in the tutorial that were wildly different from the way i built mine, except for the patches you did for libxml and libxslt. Since fink built those for me, i figured that bullet was dodged. Any chance that just because they built they are not usuable with AxKit? thanks, arne - 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] -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mac OS X and AxKit
On Friday, October 31, 2003, at 07:11 PM, Arne Claassen wrote: Has anyone done this successfully. Yes (but, see below) I'd like to use my TiBook for dev work offline, but my attempts have been fruitless so far. All problems seem to be dynamic linking issues. Next step i'm considering is rebuilding perl 5.8.1 from source and then rebuilding Apache again. If you can save me from that path, please let me know. If my memory serves me correctly... no wait, I have a web page for this I remember now :-) http://simonwoodside.com/dev/axkit/howto.html Er, it's a bit out of date. I don't use sablotron any more, dont' bother, it's a hassle and not worth it. Libxslt is much better. Also I think the most recent time I did it, I used perl 5.8.0. I guess next time I install I should update. If you get it to work can you tell me what you did? System info: Panther (10.3) Yeah, that's going to make things harder for you ;-) no doubt stuff has changed. I don't have panther yet myself. Has fink upgraded yet? I guess so. LibXML,LibXSLT,Expat built from source with Fink Using the OS provided Perl 5.8.1 and Apache 1.3.28 (uses DSO) i got this: IIRC with jaguar everyone said to statically compile mod_perl in and not to use DSOs. simon dyld: /usr/sbin/httpd Undefined symbols: _crc32 _deflate _deflateEnd _deflateInit2_ _gzclose _gzdopen _gzopen _gzread _gzwrite /usr/sbin/apachectl: line 171: 29992 Trace/BPT trap $HTTPD -t So i figure, it's a DSO issue and i build 1.3.27 (what i have on linux) as a static mod_perl server and now i get this: dyld: /usr/local/apache-1.3.27+mod_ssl+mod_perl/sbin/httpd Undefined symbols: /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _PERL_RUNNING expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_add_module expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_add_version_component expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_cfg_getline expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_find_linked_module expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_find_module_name expected to be defined in a dyna/Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/ AxKit.bundle undefined reference to _ap_getword_conf expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_handle_command expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_ind expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_invoke_handler expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_log_rerror expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_null_cleanup expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_palloc expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_pcalloc expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_pstrdup expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_register_cleanup expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_remove_module expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_set_flag_slot expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _ap_set_string_slot expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _perl_call_handler expected to be defined in a dynamic image /Library/Perl/5.8.1/darwin-thread-multi-2level/auto/AxKit/AxKit.bundle undefined reference to _perl_request_rec expected to be defined in a dynamic image
Re: Query String Variables
The param must be declared at the top level. Try this: ?xml version=1.0 encoding=UTF-8? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output method=html indent=yes encoding=ISO-8859-1/ xsl:param name=param/ xsl:template match=doc html head titlexsl:value-of select=title//title /head body h2param is set to: xsl:value-of select=$param//h2 xsl:apply-templates/ /body /html /xsl:template [...] simon On Wednesday, October 8, 2003, at 07:08 AM, Alex Greg wrote: Thomas Schindl wrote: Hi, you can read query variables simply using xsl:param name=my-cgi-param/ First off, thanks very much for your reply I've put AxAddPlugin Apache::AxKit::Plugin::QueryStringCache into httpd.conf and restart Apache. Next I tried creating a simple example: style.xsl: ?xml version=1.0 encoding=UTF-8? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output method=html indent=yes encoding=ISO-8859-1/ xsl:template match=doc html head titlexsl:value-of select=title//title /head body h2param is set to: xsl:param name=param //h2 xsl:apply-templates/ /body /html /xsl:template !-- templates here -- xsl:template match=para p xsl:apply-templates/ /p /xsl:template xsl:template match=link a href=/linkage/[EMAIL PROTECTED] xsl:apply-templates/ /a /xsl:template xsl:template match=title h1xsl:value-of select=.//h1 /xsl:template /xsl:stylesheet and transformed it via AxKit with a simple XML document, requesting it in my browser as: http://localhost/query_param_test/doc.xml?param=test123 Unfortunately the parameter was empty in the resulting HTML page: param is set to: Any ideas what could be wrong? Alex When you have caching turned on please ensure that you use AxAddPlugin Apache::AxKit::Plugin::QueryStringCache, because normal caching does not uses the query-string. Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PHP-generated XML and AxKit
On Tuesday, October 7, 2003, at 04:43 PM, [EMAIL PROTECTED] wrote:
Hello all,
I think this one may have come up before but I haven't found any clean
resolution despite extensive googling and some conversations with
AxKit and PHP
veterans.
I'm using PHP 4.3.0, Apache 1.3.x, and AxKit/mod_perl.
I'm curious if anyone has managed to find an elegant solution for
handling XSL
transformations on XML output from a PHP script using AxKit, rather
than
whatever libraries might be available to do this transform as part of
PHP. I'd
rather, if possible, keep my PHP code restricted to the purpose of
generating
XML (leaving XSLT out of it to be handled by Apache) and I'd also
rather not
write the XML to a file if I can avoid it.
As it stands, I have a script which outputs well-formed XML and the XSL
instruction for a .xsl stylesheet which resides on the server. If I
save that
XML as a test.xml file, AxKit happily transforms it upon a browser
request for
the test.xml. If I don't save it, Apache just throws the XML results
of my
script to the mercies of whatever transformation engine the client
browser
might have.
Any thoughts on this?
Have you tried using the document() call in XSLT? It accepts URL
parameters. If you have a web server serving up the PHP (maybe even the
same server) you could then access it using something like
document('http://localhost/foo/bar.php'). Apache should generate the
XML as thoough for a normal user agent, then you suck it into the XSLT
through the xsl:copy-of command.
simon
Nathan Simpson
--
www.simonwoodside.com :: www.openict.net :: www.semacode.org
99% Devil, 1% Angel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Generalizing AxKit::XSP::Param names
I am working on a very similar problem at the moment. I must admit I don't know much yet about javascript. But wouldn't it be possible to use javascript to collect all of the arguments together into a single URI parameter, formatted in XML something simple like this: params a1foo/a1 b1bar/b1 ... /params and then that would be returned as a single URI parameter. Then it could be parsed as XML and read off really easily, I think. At least, in XSLT, using an EXSL extension function, it would be possible to turn it into usable data to select into. It's just a theory though. I haven't even tried it yet at all. Do you think it would work? simon On Wednesday, October 1, 2003, at 03:49 PM, Vaclav Barta wrote: Hi, I have a form producing quite a few parameters (a1, b1, t1, a2, b2, t2 ... a5, b5, t5), and another page which basically just displays the values from the first page. This second page uses XSP, and my custom taglib handles each parameter triple (i.e. a1, b1, t1) by markup like eq numbers:added numbers:num1param:a1//numbers:num1 numbers:num2param:b1//numbers:num2 numbers:sumparam:t1//numbers:sum /numbers:added /eq (which is later transformed into a table row). It works, but the same markup (actually about 3 times longer than the example above) must be repeated 5 times, which is awful. Is there a way to compute the parameter names, IOW can I specify my markup just once and then call the template with 1, 2 ... 5? Bye Vasek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Generalizing AxKit::XSP::Param names
Yes indeed? What is it? =) I am very interested and hope I can use it using AxKit and pure XSLT! simon On Friday, October 3, 2003, at 03:45 AM, Jörg Walter wrote: If that example still looks lengthy, then wait for the next release of axkit, we are currently devising a system that will shorten the above example significantly. -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sidebar doctype in axkit.org
a lot of namespace URL values are non-existant URLs, it's just a unique name/identifier, not intended to actually have a dtd there. simon On Tuesday, September 23, 2003, at 05:54 PM, carlos escribano wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, This is my first post to the list, and sorry for my poor english. The file 'sidebar.xml' in the AxKit tarball follows the doctype 'sidebar' in namespace xmlns:sb=http://axkit.org/NS/sidebar-1.0;. I'd like to use it in my website, but I can't find any dtd or schema for this doctype. I don't know if there is a public release for this doctype or if it's a draft. Extracting from sidebar.xml, maybe the dtd core is: ?xml encoding=UTF-8 !ELEMENT sidebar (section+) !ELEMENT section (title, (subsection|item)+ ) !ELEMENT subsection (title, url, item+) !ATTLIST subsection expand ( yes | no ) no !ELEMENT item (title, url) !ELEMENT title (#PCDATA) !ELEMENT url (#PCDATA) Please fix me if I'm wrong. Thanks in advance, Carlos Escribano -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/cMEYVf3MWkqJvxIRAi2fAKC26LYSX7Ic1QLZr+PwaJhO8lV/7ACePouG qhsilJG0WlWM8AeD26TEIog= =mLWq -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: StyleChooser/URI phase style picking
Coupl'a comments... do you really want anyone to be able to view your raw XML??? Anyway, I think you could use vanilla apache redirect statements to do what you want, combined with the axkit handler that gives you different output based on the ? URI parameters. simon On Tuesday, September 16, 2003, at 01:01 PM, Arne Claassen wrote: I'm trying to create a behavior and tried with both with a PerlTransHandler and PerlTypeHandler without success, so i figured, I'd ask for help. Basically, xml/xslt output on my system generates html, so here's what i'm trying to do: 1) *.html gets translated to *.xml (can do that in the URI phase) 2) *.xml won't have a stylesheet, so direct access to *.xml just returns raw XML (lovely for debugging, especially with the XML modes of mozilla and IE) 3) If it comes in at *.html, check for *.xsl and attach that as stylesheet, otherwise check for default.xsl and attach that as stylesheet. This also has to happen in the URI phase since post that i don't know that it came in as *.html. That part i can't get to happen Any suggestion, or is there already a facility similar to this behavior i should instead exploit? arne -- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Caching and AxKit
On Monday, September 8, 2003, at 07:03 PM, Tod Harter wrote: One thing you can do which will let you have more flexibility in what is and isn't cached is to use XInclude or the XSLT document() function. If you pull in data from another local URL its going to have its own caching rules and often something like a dynamic sidebar or whatnot can be cached even when other content on the page isn't, and these techniques will let you do that. Tod, this doesn't make sense. If I include content using document() and the content has changed, that would invalidate any further steps in the pipeline??? simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: random  characters
On Friday, September 5, 2003, at 03:57 AM, Jörg Walter wrote: No, but a use bytes or use utf8 can be added in a backwards compatible way, so it is okay to be used, it's just how you add it which decides. (Baud did a preliminary patch I believe, that's why it was okay-ish) who's baud? simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axblog 0.2
HI folks, I just released AxBlog 0.2 of my over-the-top everything but the kitchen sink (not) weblog as seen in production on such sites as simonwoodside.com http://simonwoodside.com/dev/axkit/axblog.html - RSS output for syndication - all formatting done through multiple, reusable XSLT pipelines - output to client is in HTML 4.01 - all data is stored in a single XML file for use in multiple locations - mix and match XSLT in different orders to achieve different effects - all of the site design and layout is done using XHTML and CSS2 - modular design to fit into other AxKit sites - header, footer, etc. are factored out into the xinc directory It uses my latest, greatest axkit site design philosophy that everything should be filesystem oriented, so I appreciate any comments. simon -- simonwoodside.com -- openict.net -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit with LibXSLT on Win32
LibXSLT comes with a command line too xsltproc, does that work? Try it
on the specific file/stylesheet as well.
simon
On Tuesday, August 26, 2003, at 08:39 AM, [EMAIL PROTECTED]
wrote:
Hello,
I am trying to get AxKit running on Windows 2000 with Apache 1.3.28.
Unfortunately I can't get neither LibXSLT nor Sablotron to work on this
system. XML::Sablotron refuses to compile so I decided to use
XML::LibXSLT
The output I get in Apache's error_log is the following:
(Ther German message text Die angegebene Prozedur wurde nicht
gefunden means the specified procedure could not be found
Warning: program compiled against libxml 205 using older 204
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit] fast
handler called for /test.xml
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
Content Provider Override: Apache::AxKit::Provider::File
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
decoding from UTF-8
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit] [req]
File Provider given $r: d:/documentroot/test.xml
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
checking if we process this resource
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
media: screen, preferred style: #default
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
Cache: key = a5b1432035449f5b843a8f19821b4e90
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
getting styles and external entities from the XML
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
styles not cached - calling $provider-get_styles()
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit] using
XS get_styles (libxml2)
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
encoding to UTF-8
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
calling xs_get_styles_fh()
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
calling xs_get_styles_str()
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
parse_pi: href = test.xsl
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
parse_pi: type = text/xsl
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
xs_get_styles returned: , , dromedaries
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
Calling GetMatchingProcessors with (screen, , , , dromedaries)
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
get_styles: loading style modules
[Tue Aug 26 13:59:16 2003] [warn] [client 199.28.109.185] [AxKit]
get_styles: looking for mapping for style type: 'text/xsl'
[Tue Aug 26 14:00:02 2003] [warn] [client 199.28.109.185] [AxKit]
Caught an exception
[Tue Aug 26 14:00:02 2003] [error] [client 199.28.109.185] [AxKit]
[Error] Load of 'Apache::AxKit::Language::LibXSLT' failed with:
AxKit::load_module failed: Can't load
'd:/Perl/site/lib/auto/XML/LibXSLT/LibXSLT.dll' for module
XML::LibXSLT: load_file:Die angegebene Prozedur wurde nicht gefunden at
d:/Perl/lib/DynaLoader.pm line 206.
at d:/Perl/site/lib/Apache/AxKit/Language/LibXSLT.pm line 7
Compilation failed in require at
d:/Perl/site/lib/Apache/AxKit/Language/LibXSLT.pm line 7.
BEGIN failed--compilation aborted at
d:/Perl/site/lib/Apache/AxKit/Language/LibXSLT.pm line 7.
Compilation failed in require at (eval 11) line 1.
[Tue Aug 26 14:00:02 2003] [error] [client 199.28.109.185] [AxKit]
From: d:/Perl/site/lib/Error.pm : 148
[Tue Aug 26 14:00:02 2003] [error] [client 199.28.109.185] [AxKit]
[Backtrace] Load of 'Apache::AxKit::Language::LibXSLT' failed with:
AxKit::load_module failed: Can't load
'd:/Perl/site/lib/auto/XML/LibXSLT/LibXSLT.dll' for module
XML::LibXSLT: load_file:Die angegebene Prozedur wurde nicht gefunden at
d:/Perl/lib/DynaLoader.pm line 206.
at d:/Perl/site/lib/Apache/AxKit/Language/LibXSLT.pm line 7
Compilation failed in require at
d:/Perl/site/lib/Apache/AxKit/Language/LibXSLT.pm line 7.
BEGIN failed--compilation aborted at
d:/Perl/site/lib/Apache/AxKit/Language/LibXSLT.pm line 7.
Compilation failed in require at (eval 11) line 1.
Error::throw('Apache::AxKit::Exception::Error', '-text', 'Load of
\'Apache::AxKit::Language::LibXSLT\' failed with: AxKit:...') called at
d:/Perl/site/lib/Apache/AxKit/Provider.pm line 228
Apache::AxKit::Provider::get_styles('Apache::AxKit::Provider::File=HASH
(0x10bc640)',
'screen', '#default') called at d:/Perl/site/lib/Axkit.pm line 831
AxKit::get_styles('screen', '#default',
'Apache::AxKit::Cache=HASH(0x10548f8)',
'Apache::AxKit::Provider::File=HASH(0x10bc640)') called at
d:/Perl/site/lib/Axkit.pm line 395
AxKit::run_axkit_engine('Apache=SCALAR(0x10b7948)',
'Apache::AxKit::Provider::File=HASH(0x10bc640)') called at
d:/Perl/site/lib/Axkit.pm line 288
eval {...} called at d:/Perl/site/lib/Axkit.pm line 279
AxKit::main_handler('Apache=SCALAR(0x10b7948)',
'Apache::AxKit::Provider::File=HASH(0x10bc640)') called at
d:/Perl/site/lib/Axkit.pm line 193
Re: Chaining
What are you talking about Tod ;-) That's crazy talk. XSLT is much more fun if you actually write lots of templates. If you need to add boilerplate code it's easy enough to do something like this: xsl:template match=/ !--add html headers or whatever-- xsl:apply-templates/ !--add html footers or whatever-- /xsl:template then if you want to kill off certain nodes that you're not using it's easy enough: xsl:apply-templates match=dontwantthis/ Having the default rule I think is useful as a double-check, so that if I get extraneous text output it's a red flag that I goofed somewhere. simon On Tuesday, August 5, 2003, at 03:01 PM, Tod Harter wrote: What I meant was, you're right, but I've brainwashed myself so bad with my cookie cutter approach ;o) that I forget the rules... Really, XSLT (at least for my purposes) should just ignore anything that there isn't an explicit match for. I always put in a 'do nothing' and then just run an open apply templates loop at the top to get that behaviour, which is 99.99% of the time what you want when building web pages. I guess XSLT is showing its roots, not surprising given the terminology they use (stylesheet??? its a PROGRAM guys!). So the original post is correct in general, though in my little cozy world my way works too. Sorry, should be xsl:apply-templates/ not xsl:copy-of .../ sigh. Sorry, but this is wrong. With your experience, you surely know that copy-of copies a whole subtree, and nothing in your template continues processing, so you would bypass most other template rules. Just imagine a XML snippet abc//b/a. A match on a would work, a match on c would not, as the XSLT processor would never get that far. -- Giant Electronic Brain Internet/E-Commerce Consulting Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: iconv on OS X - workaround
On Monday, July 28, 2003, at 04:28 AM, Robin Berjon wrote:
eval {
print running xml2-config... ;
-my $libs = backtick('xml2-config --libs');
+my $libs = backtick('xml2-config --libs') . -L/sw/lib;
$config{LIBS} .= $libs if $libs;
-my $inc = backtick('xml2-config --cflags');
+my $inc = backtick('xml2-config --cflags') . -I/sw/include;
$config{INC} .= $inc if $inc;
print ok\n;
};
It's a hack I'm afraid (but hey, whatever gets AxKit to install...).
Passing the right options on the command line should have ended those
directories in $config{LIBS,INC}. Either there's a bug in the
Makefile.PL, or you've mispassed an option.
What would the correct options have looked like? I tried
--libs=-L/sw/lib, '--libs=-L/sw/lib', LIBS=/sw/lib and 'LIBS=/sw/lib' I
think.
Here's a context grep (and you can see my changes)
% grep -C LIBS Makefile.PL
print running xml2-config... ;
my $libs = backtick('xml2-config --libs') . -L/sw/lib;
$config{LIBS} .= $libs if $libs;
my $inc = backtick('xml2-config --cflags') . -I/sw/include;
$config{INC} .= $inc if $inc;
--
if (have_library('xml2')) {
$config{DEFINE} .= ' -DHAVE_LIBXML2';
$config{LIBS} .= ' -lxml2 -lz';
$xml_parser_found++;
}
--
$config{CCFLAGS} = $Config{ccflags} .
' -D_WINSOCK2API_ -D_MSWSOCK_ -D_INC_SIGNAL -D_INC_MALLOC ';
$config{LIBS} =
qq{ -L$Apache::MyConfig::Setup{APACHE_LIB} -lApacheCore } .
qq{ -L$Apache::MyConfig::Setup{MODPERL_LIB} -lmod_perl};
--
my ($src, $opt) = @_;
my $cfile = gensym();
# local $config{LIBS};
# $config{LIBS} .= $opt;
unless (mkdir(.testlink, 0777)) {
rm_fr(.testlink);
simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: What of AxKit 2.0?
Can I make a request? The ability to specify XSLT parameter values through configuration. simon On Monday, July 28, 2003, at 05:10 PM, Daisuke Maki wrote: So I know this topic has been covered before, but I'd like to ask once again the state of AxKit 2.0, and what the plans are... The reason I ask is because now that I'm more or less over with my previous project, I'd like to start fiddling with apache 2.0 and mod_perl 2.0, to prepare myself for the inevitable migration. And I would rather be working on AxKit rather than some other random project Is there any CVS repository setup anywhere? I suspect not, but in that case what do Matt and everybody else plan to do -- any roadmaps or anything like that? --d -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What of AxKit 2.0?
On Monday, July 28, 2003, at 06:47 PM, Kip Hampton wrote: Can I make a request? The ability to specify XSLT parameter values through configuration. -1 This is the sort of thing that custom Plugin classes are for (and is just as do-able with the current version as it would be in any future version). What if I don't want to write perl? XSLT is a first-order implementation language for AxKit is it not? If you're doing an axkit site in pure XSLT, parameters would be the only way to supply configuration information straight from axkit to the stylesheets. simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiki
This one seems to be the problem. I guess it might be useful to see the .htaccess files for the wiki directory and all the super-directories as well. I have the wiki running and don't remember having any config problems with it. Are you sure that the .htaccess is OK and being read? simon On Friday, July 25, 2003, at 12:41 PM, Colin Goodier wrote: [Fri Jul 25 17:34:50 2003] [warn] [client 127.0.0.1] [AxKit] [DECLINED] No styles defined for '/home/coling/perforce/web/staff/courses/wiki/view' -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: very slow transformation of Docbook-HTML
On Thursday, July 24, 2003, at 10:00 AM, Tod Harter wrote:
xsl:apply-templates select=common:node-set($mydocument)/
and do pull processing on imported chunks. That lets your library of
chunks be
a lot more generic since you now don't have to 'take it or leave it'
when you
import, you can filter in just particular parts of an external
document. :o).
umm... you don't need to use exslt to do that !
xsl:apply-templates select=document('foo')/foo/bar/ works just fine.
simon
--
www.simonwoodside.com -- 99% Devil, 1% Angel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building applications with AxKit and XSP, in a reusable extensible way...
What if you build an XSLT pipeline, and then bring in the XSP generated
content at the last stage using a xsl:copy-of
select=document('axkit:foo/bar.xsp')/ call?
simon
On Wednesday, July 23, 2003, at 06:23 AM, Adam Griffiths wrote:
Hi,
I've been using AxKit for a while now and I'd really appreciate any
ideas or
information on the following question.
XSP is great for generating dynamic XML documents and it's fast too.
It also
caches the Perl code necessary to generate the dynamic XML page so
multiple
requests only require it is parsed once. However as my application
grows and
has an increasing number of XSP pages I am finding that many share
identical
code / xsp-xml fragments, which makes maintaining them all is becoming
increasingly difficult.
I'm looking for a way to reuse XML fragments across many XSP pages,
and thus
save allot of time composing them and maintaining them (there is a
simple
example below). One way that could work would be to use XSLT before
XSP in
the AxKit pipeline so a single tag could be expanded (transformed)
into the
relevant XSP tags. However there is a major problem with that idea and
that
is that AxKit won't cache the XSP page is it is preceded by an XSL
transform, and without the cache there would be a major drop in
performance.
One thing that would solve my problem would be to be able to tell AxKit
where is should cache in the pipeline and then it would be possible to
have:
XSL
|
XSL
|
XSP - cache Perl code here
|
XSL
|
OUTPUT
Basically I'd like to take out the common factors from a group of xsp
pages,
in a reusable extensible manor. Has anyone lese come across the same
problem? Is there a way that I can achieve this, or something like it?
Your comments and ideas would be greatly appreciated.
Regards
Adam
__
Here is an example where this would prove very useful: If many XSP
pages in
an application authenticate a user before displacing the page with XSP
tags
something like this (using the imaginary authuser taglib):
authuser:check
authuser:require
authuser:groupadministrators/authuser:group
authuser:grouppowerusers/authuser:group
!-- the user must be in the administrators or powerusers groups
to
view this page --
/authuser:require
authuser:invalid
!--The logged in user does not have the required access to view
this
page --
/authuser:invalid
authuser:valid
!--A valid user is logged in, display the page --
!-- page content goes here --
/authuser:valid
autheruser:no-user
!-- no user is logged in, redirect to login page--
/autheruser:no-user
/authuser:check
To changed the required groups of users would require every page is
changed.
It could be simplified as:
adminpage
!-- page content goes here --
/adminpage
And then only the XSL transform would need to be updated to make
changes to
the authentication of multiple pages.
s_p_a_m_t_r_a_p from:[EMAIL PROTECTED]
Do not email the above address or remove these two lines
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
anti-spam: do not post this address publicly
www.simonwoodside.com -- 99% Devil, 1% Angel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: very slow transformation of Docbook-HTML
On Tuesday, July 22, 2003, at 04:41 PM, Brian Acton wrote: However, it's painfully slow at serving up an extremely trivial Docbook file (just 1 article element enclosing 1 section with 5 para takes ~20 seconds!). While this is happening, the client browser (Mozilla) is also taking up huge system resources. Caching doesn't appear to work, since subsequent requests for the same document take equally as long. Um, are you sure axkit is processing it? Mozilla includes an XSLT parser you know ... which parser are you using with AxKit ? LibXSLT? did you configure axkit to process the file? Send us your axkit config settings. A much larger Docbook file (from which the trivial test snippet was taken) is transformed to HTML reasonably quickly by Xalan. With AxKit it's interminable (literally, so far -- I've run out of patience and had to kill Mozilla every time). If Mozilla is hanging or spinning this is NOT an axkit problem. You are probably seding it untransformed XML, and then it'll try to apply the stylesheet based on the given PI FWIW, DocBook stylesheets ARE slow. That's why xsltproc has the --norman option for profiling BTW ;-) You can speed it up a LOT by commenting out all the languages you don't need it try. simon Any suggestions as to what I may have done wrong? I'm new at AxKit so it could be something really obvious, and nothing to do with AxKit at all. Regards, Brian P.S. Here are the PIs that I used: ?xml version=1.0 encoding=ISO-8859-1 standalone=no? ?xml-stylesheet href=/XML/XSL/docbook-xsl-1.61.2/html/docbook.xsl type=text/xsl? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: very slow transformation of Docbook-HTML
On Tuesday, July 22, 2003, at 11:27 PM, Brian Acton wrote: (1) Although the Dromedaries example at: http://axkit.org/wiki/view/AxKit/QuickStart worked for me, I had actually followed the AxKit installation instructions at: http://axkit.org/wiki/view/AxKit/AxKitRedHat9 SetHandler perl-script PerlHandler AxKit Please fix the mistake in the wiki Sablotron So sablotron can't even handle the docbook xslt files? That's kind of pathetic. simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: encoding problems in AxKit version 1.6.1-CVS
Well, it might apply in this case. libxml comes with some tools, see man libxml for a list at the bottom. xmllint might be able to help you debug this problem. If you can reproduce the problem in the command line, then it occurs before it gets to perl, if you can't, then it's more likely to be in the perl XML::LibXML or AxKit area. simon On Wednesday, July 16, 2003, at 01:15 PM, Marco Marongiu wrote: S Woodside wrote: What happens when you use the libxml command line tools? Erm... feeling:ignorantany suggestions?/feeling:ignorant -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit and Perl
just overwrite them? ;-) simon On Wednesday, July 16, 2003, at 08:11 PM, Peter Flynn wrote: Instead you manually download the latest libxml2 and libxslt from ftp://xmlsoft.org/ and install the *tarballs* manually. Note: don't install the RPMs. But how do I get rid of the libxml2 and libxslt RPMs that are already installed without leaving me with a broken dependency? I can of course use --force, but that's pretty unclean. -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit and Perl
You might want to consider other religions then, I find sacrificing chickens can work too. simon On Monday, July 14, 2003, at 05:20 PM, Peter Flynn wrote: And finding where @INC is defined is obviously one of those well-hidden tricks only to be revealed after much fasting and prayer :-) -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Include
Hmm... xinclude is supposed to be included in libxslt and in
XML::LibXSLT (i've never tried it). you should get the same result with
xsl:copy-of select=document('menu.xml')/ I think. (there are some
tricks about what it's relative too, see the archives or the XSLT FAQ
for info)
simon
On Monday, July 14, 2003, at 08:35 PM, Robert Ferney wrote:
I've tried to include file b.xml in an xslt stage in the application
I'm
writing for what should be some relatively static content that I want
in
it's own file out for maintainability reasons.
however... the following didn't work.
can anybody help me with a method that would work here?
thanks.
-Rob
?xml version=1.0?
xsl:stylesheet
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:xi=http://www.w3.org/2001/XInclude;
version=1.0
xsl:template match=/page
div class=menu
xi:include href=menu.xml /
/div
div class=content
xsl:apply-templates select=body/
/div
/xsl:template
/xsl:stylesheet
--
www.simonwoodside.com -- 99% Devil, 1% Angel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit and Perl
IME learning about the idiosyncracies of perl installations, @INC,
etc., etc. are essential to running axkit unfortunately. I'm not an
expert so I won't try to answer your questions, I usually go into hack
mode when I try to get something to work.
Also IME it's much safer to build your own {everything} rather than
using debian packages, RPMs, fink, etc. when it comes to using AxKit.
Has anyone ever used AxKit successfully on RH9 ? You might always want
to try checking out if there are any perl on RH9 mailing lists. have
you seen this
http://maclux-rz.uibk.ac.at/~maillists/axkit-users/msg05486.shtml
BTW you know that apache has some helpful reporting it can do about the
mod_perl installation on a webpage right?
simon
On Sunday, July 13, 2003, at 08:11 PM, Peter Flynn wrote:
Before I went on vacation I was struggling to get AxKit working
under Red Hat 9, which had perl-5.8.0-88 installed by default.
The consensus was that locale settings were causing problems.
I built a fresh Perl from source but that also failed to handle
the locales, so I changed the locales but that still didn't fix
it.
John Fessenden suggested I try a lower release of Perl, so I
installed --force 5.0.8-55 (having uninstalled all the www and
XML stuff layered on top of 88), but that seems to cause even
more problems, as when I tried to put the www and XML stuff
back, it Digest and MIME-64 both claimed they needed a Perl
= 5.6 to run with, which is fairly nonsensical for a 5.8 :-)
I'm now left with traces of at least three non-working Perls.
I can probably get rid of them, although it'll probably break
the OS not to have perl in existence for a while. Most of it
seems to live in /usr/lib/perl5 and locate can find the string
perl easily enough...but:
1. are there other hidden nooks and crannies where I need to
remove important files to be sure they won't interfere with
a later install?
2. can anyone recommend a version and release of Perl that they
know hand-on-heart *will* work with Apache, mod_perl, and
AxKit under RH9? Is it worth trying an RPM again, or should
I ditch the idea and use the source? Does anyone know how
many system utilities depend on perl 5.8.0 55?
3. 90% of Perl's problem is it fails to look in sensible places
for files. It insists on searching something called @INC
which is clearly some mind of path, but it includes directories
no-one in their right minds would put files in, and omits all
the obvious places. Someone posted the location where @INC is
defined, but I can't locate the post. Where is @INC defined
so I can change it to search properly?
I don't even know if I want to use AxKit: I want to demo it to
a class, along with Cocoon and PropelX and other XML servers,
and I have one week left in which to get it working without
breaking my system. I did once get a version of it working for
a day or two last year, so I know it *can* work.
And please can someone document on the AxKit site never ever to
try installing it on RH9 if the default Apache and Perl are
installed :-) That piece of information would have saved me at
least two weeks time.
///Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
anti-spam: do not post this address publicly
www.simonwoodside.com -- 99% Devil, 1% Angel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
odd gotcha on os x handling directories
Hi I had an odd gotcha for a while which I fixed now. In my .htaccess on debian I formerly had FilesMatch \.(html|xml)$ PerlHandler AxKit /FilesMatch but I changed it to just PerlHandler AxKit becuase I didn't need the restrictions any more. No problem. As a result I started having this problem with it on my OS X machine where I would get this error: [Sat Jul 12 19:14:52 2003] [warn] [client 127.0.0.1] [AxKit] handler called for / [Sat Jul 12 19:14:52 2003] [warn] [client 127.0.0.1] [AxKit] Content Provider Override: Apache::AxKit::Provider::File [Sat Jul 12 19:14:52 2003] [warn] [client 127.0.0.1] [AxKit] decoding from UTF-8 [Sat Jul 12 19:14:52 2003] [warn] [client 127.0.0.1] [AxKit] [req] File Provider given $r: /Library/WebServer/Apache2 [Sat Jul 12 19:14:52 2003] [warn] [client 127.0.0.1] [AxKit] checking if we process this resource [Sat Jul 12 19:14:52 2003] [warn] [client 127.0.0.1] [AxKit] '/Library/WebServer/Apache2' is a directory and my browser (camino) would redirect me to http://localhost// (and keep adding /'s) well, I don't mind adding the FilesMatch back in, but it's weird anyway. Here's httpd -V from both machines debian: % /usr/sbin/apache -V Server version: Apache/1.3.27 (Unix) Debian GNU/Linux Server built: Jun 26 2003 16:49:46 Server's Module Magic Number: 19990320:13 Server compiled with -D EAPI -D HAVE_MMAP -D HAVE_SHMGET -D USE_SHMGET_SCOREBOARD -D USE_MMAP_FILES -D HAVE_FCNTL_SERIALIZED_ACCEPT -D HAVE_SYSVSEM_SERIALIZED_ACCEPT -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D HARD_SERVER_LIMIT=4096 -D HTTPD_ROOT=/usr -D SUEXEC_BIN=/usr/lib/apache/suexec -D DEFAULT_PIDLOG=/var/run/apache.pid -D DEFAULT_SCOREBOARD=/var/run/apache.scoreboard -D DEFAULT_LOCKFILE=/var/run/apache.lock -D DEFAULT_ERRORLOG=/var/log/apache/error.log -D TYPES_CONFIG_FILE=/etc/mime.types -D SERVER_CONFIG_FILE=/etc/apache/httpd.conf -D ACCESS_CONFIG_FILE=/etc/apache/access.conf -D RESOURCE_CONFIG_FILE=/etc/apache/srm.conf % xsltproc -V Using libxml 20506, libxslt 10029 and libexslt 719 xsltproc was compiled against libxml 20506, libxslt 10029 and libexslt 719 libxslt 10029 was compiled against libxml 20506 libexslt 719 was compiled against libxml 20506 OS X: % httpd -V Server version: Apache/1.3.27 (Darwin) Server built: 07/09/03 01:22:05 Server's Module Magic Number: 19990320:13 Server compiled with -D HAVE_MMAP -D USE_MMAP_SCOREBOARD -D USE_MMAP_FILES -D HAVE_FCNTL_SERIALIZED_ACCEPT -D HAVE_FLOCK_SERIALIZED_ACCEPT -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D HARD_SERVER_LIMIT=256 -D HTTPD_ROOT=/usr/local/apache -D SUEXEC_BIN=/usr/local/apache/bin/suexec -D DEFAULT_PIDLOG=logs/httpd.pid -D DEFAULT_SCOREBOARD=logs/httpd.scoreboard -D DEFAULT_LOCKFILE=logs/httpd.lock -D DEFAULT_ERRORLOG=logs/error_log -D TYPES_CONFIG_FILE=conf/mime.types -D SERVER_CONFIG_FILE=conf/httpd.conf -D ACCESS_CONFIG_FILE=conf/access.conf -D RESOURCE_CONFIG_FILE=conf/srm.conf % xsltproc -V Using libxml 20508, libxslt 10031 and libexslt 721 xsltproc was compiled against libxml 20508, libxslt 10031 and libexslt 721 libxslt 10031 was compiled against libxml 20508 libexslt 721 was compiled against libxml 20508 both are running AxKit 1.6.1 simon -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit 1.6.1 Build Failure on FreeBSD 4.8-STABLE
I think this should be a FAQ ;-) check the archives, it's come up many times before. IIRC it's a bug in the makefile somehow, and if you comment out the check in the makefile, so it doesn't check for iconv, it will still link to it properly and work. simon On Tuesday, July 8, 2003, at 01:45 PM, Christopher H. Laco wrote: I recently went to upgrade a box that I haven't touched in a few months and I can't get AxKit to build. The os is FreeBSD 4.8-STABLE, built yesterday, and the machine already has an old install of AxKit 1.6 working. Yeah, I know, if it ain't broke; and ain't ain't a word. :-) Initially, I ran portupgrade to build and upgrade the latest version. The port in the FreeBSD ports collection is now marked as broken, so I commented that out just for giggles. That build failed with the error below. I then downloaded the 1.6.1 release from CPAN and attempted to build it and received thethe same errors. -- $ perl Makefile.PL [snip] checking for iconv() in -liconv... no checking for libiconv() in -liconv... no checking for iconv() in -lc... no AxKit needs the iconv system library to work properly. This comes by default with most Unix systems, however it may be that you do not have the development libraries installed, or possibly that you just don't have iconv available on your system. For *BSD systems, iconv is available in your distribution's ports collection. For Win32 systems, a google search will often suffice to find a Win32 library version. -- Now, libiconv 1.9.1 is installed and located in my /usr/local/lib/, and AxKit 1.6 worked fine, so I'll assume this is some change in the detection scripts. I scanned Makefile.PL and saw no reference to iconv, nor do I understand much of the makefile kool-aid. So, if someone could just point me in the right direction or to the right file, I'd like to try and fix it and send an updated ports Makefile to freebsd.org. Thanks, -=Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
turning off axkit in a subdir
Hi folks. I just finished converting my entire homepage into axkit so I am happy :-) Has anyone successfully configured axkit, to disable axkit in subdirectory that would otherwise be using it? I have applied axkit to all the files in my site in a broad swath (using FilesMatch *.html), and I want to disable axkit in a certain buried subdirectory where the files served will not be XML at all. If you've done this, would you mind sharing your .htaccess configuration with me? Thanks, simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Choosing styles for long pipelines]
I've noticed a lot of people seem to like this idea, of providing different output depending on a query parameter. What's the attraction of this method? For example, most RSS feeds, are provided in a separate file, rss.xml or index.rdf. simon Now I've started experimenting with RSS, and figure it would be nice to automatically generate a RSS output. A natural way of doing this (to me) is with a parameter on the end of the URL to specify the format. Which is exactly what Apache::AxKit::StyleChooser::QueryString is supposed to do. -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: turning off axkit in a subdir
On Sunday, July 6, 2003, at 06:01 PM, Matt Sergeant wrote: On Sunday, Jul 6, 2003, at 21:48 Europe/London, S Woodside wrote: Has anyone successfully configured axkit, to disable axkit in subdirectory that would otherwise be using it? I have applied axkit to all the files in my site in a broad swath (using FilesMatch *.html), and I want to disable axkit in a certain buried subdirectory where the files served will not be XML at all. If you've done this, would you mind sharing your .htaccess configuration with me? Thanks, SetHandler default-handler I get this: [Sun Jul 6 15:12:17 2003] [error] [client 65.93.183.218] [AxKit] [Error] xmlParse returned error: 5, Space required after the Public Identifier SystemLiteral or ' expected xmlParseExternalID: PUBLIC, no URI Opening and ending tag mismatch: BR line 27 and STRONG Opening and ending tag mismatch: BR line 26 and SMALL AttValue: or ' expected attributes construct error error parsing attribute name attributes construct error xmlParseStartTag: problem parsing attributes Couldn't find end of Start Tag IMG line 32 AttValue: or ' expected [.snip...] AttValue: or ' expected attributes construct error Specification mandate [Sun Jul 6 15:12:17 2003] [error] [client 65.93.183.218] [AxKit] From: /home/simon/local/lib/perl/5.8.0/Apache/AxKit/Exception.pm : 9 = When I load /stats/simonwoodside.com/index.html. Here's the config: %%% pwd /data/sites/simonwoodside.com/stats %%% cat .htaccess SetHandler default-handler %%% pwd /data/sites/simonwoodside.com %%% cat .htaccess PerlModule AxKit #GENERAL Redirect permanent /oldnews/rss.xml http://simonwoodside.com/weblog/rss.xml RedirectMatch permanent /(.*)\.php$ http://simonwoodside.com/$1.html ErrorDocument 404 /writings/404.html AxStackTrace Off AxGzipOutput On FilesMatch .*.xml|.*.html PerlHandler AxKit AxAddStyleMap application/x-xsp Apache::AxKit::Language::XSP AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT AxAddXSPTaglib AxKit::XSP::Util AxCacheDir /tmp/axcache.simonwoodside.com AddType text/xml .html AddType text/xml .xml AddHandler axkit .html AddHandler axkit .xml SetHandler perl-script /FilesMatch simon -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Design Question
On Friday, July 4, 2003, at 11:55 PM, John Fessenden wrote: On Fri, 4 Jul 2003, S Woodside wrote: It would be nice to be able to do http://foo.com/bar/key.pdf and get a PDF render of key.xml Why bother with outputting PDF at all? You can use a CSS media=print style sheet to get the same kind of effect for the whole website, it's a lot easier. Here's a good place to start if you're new to this: http://www.meyerweb.com/eric/articles/webrev/21.html simon -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AxKit performance problem
On Friday, July 4, 2003, at 04:55 AM, Robin Berjon wrote: Alan Edel wrote: Some additional info: - This is a dual-cpu system, and is not busy at the time of the request. - An xml file of 3,750,509 bytes will cause this problem to occur. - An xml file that's 984,519 bytes takes a LONG time to process, but does eventually complete. In this case, the request starts at 13:30:59 and finishes at 13:38:01. There appear to be three choke points: a. xs_get_styles_str() -- this step takes 15 seconds b. [LibXSLT] performing transformation -- this takes OVER 6 MINUTES (from 13:31:15 to 13:37:53) c. [LibXSLT] outputting to $r -- this takes 8 seconds What does your stylesheet do? It is terribly easy to write non-optimal stylesheets. It won't be noticeable on small files, but on larger ones it becomes terrible. I remember just tweaking an XPath a little bit and bring a processing from 4 minutes down to a few seconds. xsltproc has a nice option, --norman, that will profile your code too, it's great :-) :-) simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Design Question
It would be nice to be able to do http://foo.com/bar/key.pdf and get a PDF render of key.xml Why bother with outputting PDF at all? You can use a CSS media=print style sheet to get the same kind of effect for the whole website, it's a lot easier. simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deferring XSL transformation to the browser
I don't recall ever hearing of a browser that could do an XSLT pipeline, but I don't pay too much attention to it. simon On Friday, July 4, 2003, at 07:11 PM, Michael A Nachbaur wrote: If not, I feel an itch that I might have to go and scratch. -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axkitcachedir serves wrong pages
Whoa -- that would maybe problem I was seeing last week that I gave up on because I couldn't create a nice test case. So, now I have got this in .htaccess for my site: AxAddPlugin Apache::AxKit::Plugin::AddXSLParams::Request AxAddPlugin Apache::AxKit::Plugin::QueryStringCache PerlSetVar AxAddXSLParamGroups VerboseURI Is that good enough? Specifically I was getting unexpected behaviour when I was calling a URL with parameters through the axkit: URI in a document() call in XSLT. simon On Sunday, June 29, 2003, at 06:29 PM, Tom Schindl wrote: If you want to cache on url+parameter basis you'll have to use AxAddPlugin Apache::AxKit::Plugin::QueryStringCache. Tom Am Son, 2003-06-29 um 21.00 schrieb Fabian Sturm: Hello! I have some inconsisten behavior in AxKit. I use the AddXSLParams::Request module to deliver different webpages depending on the url http://myserver/index.xml?lang=de vs. http://myserver/index.xml?lang=en Everything works fine so far but AxKit creates a .xmlstyle_cache in every directory. I therefore added the AxCacheDir option to the httpd.conf. It worked fine as long as I used AxKit 1.6 and :AddXSLParams::Request 1.0. But with AxKit 1.6.1 and Apache-AxKit-Plugin-AddXSLParams-Request-1.01 it only creates one of the pages english or german (the first one requested) and then delivers this from the cache regardless of the parameter. I guess it is a bug? Thanks, Fabian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axkit1.6.1/libxslt1.0.30/libxml2.5.7/os x woe
I upgraded to libxml 2.5.7 now and it's the same error/message. The complete error log is at the bottom of the message. % xsltproc -V Using libxml 20507, libxslt 10030 and libexslt 720 xsltproc was compiled against libxml 20506, libxslt 10030 and libexslt 720 libxslt 10030 was compiled against libxml 20506 libexslt 720 was compiled against libxml 20506 TIA simon On Sunday, June 29, 2003, at 10:35 PM, S Woodside wrote: Hi, I have a problem where, libXSLT chokes because it cannot find /sw/etc/xml/catalog : [Sun Jun 29 22:17:33 2003] [warn] [client 127.0.0.1] [AxKit] LibXSLT match_uri: /sw/etc/xml/catalog [Sun Jun 29 22:17:33 2003] [warn] [client 127.0.0.1] [AxKit] LibXSLT open_content_uri: /sw/etc/xml/catalog [Sun Jun 29 22:17:33 2003] [warn] [client 127.0.0.1] [AxKit] Content Provider Override: Apache::AxKit::Provider::File [Sun Jun 29 22:17:33 2003] [warn] [client 127.0.0.1] [AxKit] decoding from UTF-8 [Sun Jun 29 22:17:33 2003] [warn] [client 127.0.0.1] [AxKit] [req] File Provider given $r: /Library/WebServer/Apache2/sw [Sun Jun 29 22:17:33 2003] [warn] [client 127.0.0.1] [AxKit] encoding to UTF-8 [Sun Jun 29 22:17:33 2003] [warn] [client 127.0.0.1] [AxKit] Caught an exception [Sun Jun 29 22:17:33 2003] [error] [client 127.0.0.1] [AxKit] [UnCaught] File '/Library/WebServer/Apache2/sw' does not exist or is not readable This occurs after I upgraded LibXSLT to 1.0.30, but libxml is still on 2.5.6, so perhaps that is the problem. Fink does not yet have 2.5.7, so I guess that I will try to install it manually at this point. For reference, the old line from before I upgraded was: [Thu Jun 26 23:41:51 2003] [warn] [client 127.0.0.1] [AxKit] LibXSLT match_uri: file:///sw/etc/xml/catalog (there was no subsequent open_content_uri: logged) simon [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] handler called for /index.html [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] Content Provider Override: Apache::AxKit::Provider::File [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] decoding from UTF-8 [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [req] File Provider given $r: /Library/WebServer/Apache2/index.html [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] checking if we process this resource [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] media: screen, preferred style: #default [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] Cache: key = 6591425666379adfb427ea140a5bbf04 [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] getting styles and external entities from the XML [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] styles cached [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] cache doesn't exist [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] some condition failed. recreating output [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] styles: Apache::AxKit::Language::LibXSLT(/xsl/site.xsl) [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] encoding to UTF-8 [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] Style Provider Override: Apache::AxKit::Provider::File [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [uri] File Provider looking up uri /xsl/site.xsl [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [uri] File Provider set filename to /Library/WebServer/Apache2/xsl/site.xsl [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] about to execute: Apache::AxKit::Language::LibXSLT::handler [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [LibXSLT] getting the XML [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [LibXSLT] parsing stylesheet [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [LibXSLT] checking if stylesheet is cached [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [LibXSLT] stylesheet cached [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [LibXSLT] performing transformation [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] LibXSLT match_uri: /sw/etc/xml/catalog [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] LibXSLT open_content_uri: /sw/etc/xml/catalog [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] Content Provider Override: Apache::AxKit::Provider::File [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] decoding from UTF-8 [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] [req] File Provider given $r: /Library/WebServer/Apache2/sw [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] encoding to UTF-8 [Mon Jun 30 00:21:54 2003] [warn] [client 127.0.0.1] [AxKit] Caught an exception [Mon Jun 30 00:21:54 2003] [error] [client 127.0.0.1] [AxKit] [UnCaught] File '/Library/WebServer/Apache2/sw' does not exist or is not readable [Mon Jun 30 00:21:54 2003] [error] [client
Re: AxKit with MathML
Well, if you're try to literally copy them through with xsl:copy-of .../ then perhaps you haven't got the namespace right. Make sure you are declaring the namespace with a prefix in the header, and then copy it with xsl:copy-of select=mathml:foobar/ or whatever. simon On Friday, June 20, 2003, at 08:35 PM, Streph Treadway wrote: Hi, all, I am pretty inexperienced with AxKit so please forgive what may be an extremely ignorant question. I am interested in using AxKit to serve pages that will include MathML, which is itself a form of XML. I would like to transform some elements but pass significant chunks of MathML directly to browsers without processing it. I have tried a few experiments, but the XSLT step strips out my MathML tags. Any suggestions? Yours, Streph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: navigation bar with axkit
On Tuesday, June 17, 2003, at 02:33 AM, Michael Kröll wrote: S Woodside wrote: | At the moment I tried to do it with xsl:value-of select=$request.uri/ | How do I get that to work in XSLT? I would also like to get the current | URI in XSLT and parse it. Try http://search.cpan.org/author/KHAMPTON/Apache-AxKit-Plugin- AddXSLParams-Request-1.01/Request.pm Thanks simon -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wiki report
On Monday, June 16, 2003, at 02:38 AM, Matt Sergeant wrote: On Monday, Jun 16, 2003, at 03:27 Europe/London, S Woodside wrote: for http://www.axkit.org/wiki/view/AxKit/DefaultPage between Fri Jun 13 17:59:33 2003 and 18:05:11 this address: 80.109.253.93 (ibkink03.chello.at) deleted various parts of the AxKit wiki page. I restored the previous version (Jun 7) Maybe the wiki should mail changes to an axkit mailing list? (axkit-docs probably). Yeah. Could it include a diff? simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wiki report
for http://www.axkit.org/wiki/view/AxKit/DefaultPage between Fri Jun 13 17:59:33 2003 and 18:05:11 this address: 80.109.253.93 (ibkink03.chello.at) deleted various parts of the AxKit wiki page. I restored the previous version (Jun 7) simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: navigation bar with axkit
in XSLT,
document(foo.xml, .) will work relative to the source document
document(foo.xml, document('') ) will work relative to the XSLT in
question
(I might have that backwards)
simon
On Saturday, June 14, 2003, at 08:27 AM, Fabian Sturm wrote:
Hello!
I have the problem that I want to create a navigation bar for my
webpages with xml/xslt and axkit.
The structure of my documents/directories is like this:
/
index.xml
imprint.xml
projects (folder)
publications (folder)
privat (folder)
(and these files)
navbar.xml
webpage.xsl
style_body.xsl
style_navbar.xsl
/projects/
index.xml
navbar.xml
projectA (folder)
projectB (folder)
/projects/projectA/
index.xml
navbar.xml
Depending on what website is displayed I want to show a different
navigation bar.
If it is the root index page it should look like:
Home
Imprint
Projects
Publications
Privat
And if I am displaying projects/index.xml it should look like:
Home
Imprint
Projects
-ProjectA
-ProjectB
Publications
Privat
How can I do that? the main stylesheet is from / and I think I don't
have a way to know if I came from /index.html or /Projects/index.html.
If I would I probaly could travers the path down and add each of
the navbar.xml files with document or import on the way.
Any suggestions how to do that, efficient and without having to
specify the full path for each page.
Thanks a lot, Fabian
mime-attachment
--
anti-spam: do not post this address publicly
www.simonwoodside.com -- 99% Devil, 1% Angel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: navigation bar with axkit
On Saturday, June 14, 2003, at 02:51 PM, Robin Berjon wrote:
S Woodside wrote:
in XSLT,
document(foo.xml, .) will work relative to the source document
document(foo.xml, document('') ) will work relative to the XSLT in
question
(I might have that backwards)
No, you have the right way, except that the second one is uselessly
complex and can be written as document(foo.xml) as that's the
default.
Yup, but if you feed it a node value or attribute value, it works
relative to the URI of that node. Putting in the second argument as
document('') ensures it will always treat it relative to the stylesheet
http://www.dpawson.co.uk/xsl/sect2/N2602.html#d2849e46
simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
generic source file redirection
I was thinking recently along this line. Could AxKit have a generic system to redirect accesses to a file to some other source? Such as, foo.xml, is actually an abstraction of a database, or as Brian said, ColdFusion. Could there be an AxKit API, to make these abstractions? simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with xsl:processing-instruction...
there's probably other ways to get the same effect though. (using
document() maybe with document('axkit://...'))
simon
On Monday, June 9, 2003, at 10:00 PM, Jeremy Frumkin wrote:
Hi all -
I have an XSL file which adds a processing instruction to an XML file.
I would then like AxKit to follow that processing instruction on the
new document, but AxKit does not parse the newly created file to
process the in-line instruction.
I am adding:
xsl:processing-instruction name=xsl-stylesheet
xsl:texthref=somestylesheet.xsl type=text/xsl/xsl:text
/xsl:processing-instruction
This yields an XML document with the 2nd line being:
?xml-stylesheet href=ToLNetscape.xsl type=text/xsl?
This should then cause the new XML file to be processed with the new
processing instruction, no?
-- JF
--
===
Jeremy Frumkin
Metadata Systems Librarian
University of Arizona Library
[EMAIL PROTECTED]
+1 520.621.2916
+1 520.621.9733
===
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
anti-spam: do not post this address publicly
www.simonwoodside.com -- 99% Devil, 1% Angel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: hello!
On Tuesday, May 27, 2003, at 05:19 PM, Mauro Sciaccaluga wrote: ?xml-stylesheet href=guide.xsl type=text/xsl? Before there was just: !DOCTYPE guide SYSTEM guide.dtd I have both these files: guide.dtd and guide.xsl A !DOCTYPE tag is not normal XML I don't think. It's a hold-over from SGML I think. As far as defining an XSLT transformation on the file, it's useless. DTD don't transform documents they just specify and/or validate them. There are some AxKit directives for apache that will specify a transformation, that are documented on the man page and in the docs wiki on axkit.org. However Why not just use the ?xml-stylesheet ... ? processor include? It's just as good. simon -- www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: FYI: local install of XML::LibXML and XML::LibXSLT
Whoops, wrong mail address again (OS X). A little more detail .. the problem with XML::LibXML not detecting the library was the same problem with xsubpp although it took a while to figure that out. The Makefile.PL generated a Conftest.PL type test to see if the library was available. Makefile.PL generated a Makefile with the hard-coded path in it, which is why I said it was a MakeMaker problem. changing to this XSUBPPDIR = /home/simon/local/share/perl/5.6.1/ExtUtils made the problem go away. Simon Begin forwarded message: From: Simon Woodside Date: Sun Apr 6, 2003 11:36:03 PM America/Montreal To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: FYI: local install of XML::LibXML FYI I installed XML::LibXML locally (without root) into a situation where my libxml2 was also installed locally. I was having trouble with it not detecting the installed library that I eventually resolved by commenting out the tests in Makefile.PL I had PERL5LIB=/home/simon/local/lib/perl/5.6.1:/home/simon/local/share/ perl/5.6.1 and I ran perl Makefile.PL PREFIX=/home/simon/local Then running make gave the following error: make: *** No rule to make target `/usr/share/perl/5.6.1/ExtUtils/xsubpp', needed by `LibXML.c'. Stop. This is a problem (I guess) with MakeMaker not applying the proper prefix to find xsubpp (which is installed in /home/simon/local/share/perl/5.6.1/ExtUtils/) I hacked the Makefile to manually change the path. simon -- anti-spam: do not post that address publicly www.simonwoodside.com -- 99% Devil, 1% Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [xslt] Re: more on the xslt namespace pipeline issue
I have now updated to 1.0.29 of libxslt and the testcase I posted
earlier is working now. Daniel, sorry about wasting your time.
Robin Berjon wrote:
When passing a DOM around, what I believe is the correct namespace
information will be passed around. However when you save to an
intermediate file you get this:
btest
rngform xmlns=http://simonwoodside.com/rng;;
titleRNG Form/title
/rngform
/btest
Now I am very confused about this difference between the DOM and the
serialized output. I have never used DOM.
Now I am running: Using libxml 20506, libxslt 10029 and libexslt 719
% xsltproc a_instance.xml
?xml version=1.0?
btest xmlns:simon=http://simonwoodside.com/rng;
simon:rngform
titleRNG Form/title
/simon:rngform
/btest
As we can see, thanks to namespace defaulting, we now have:
{}btest
{http://simonwoodside.com/rng}rngform
{http://simonwoodside.com/rng}}title
After reading http://www.jclark.com/xml/xmlns.htm it seems to me that
this is correct! Is there some difference between the inheritance of an
unprefixed name in input from a file as opposed to in output of a DOM?
Which is an entirely different document. Properly serialising that
would have required libxml to add xmlns='' on title, except that's
only possible starting with namespaces 1.1. Another option would have
been to add a random prefix to rngform, but that wouldn't be nice.
I can see now that adding the xmlns='' on title in the trace file gives
the same behaviour as AxKit uses internally, but
1) It is still different than the latest xsltproc's output
2) It seems to me that according to the rules of XSLT it is incorrect
(after re-reading the entire XSLT FAQ section on namespaces, I do not
see how this can be correct).
Unless I am solidly mistaken on how XSLT should treat namespace
contexts in xsl:element, the bug is yours and the AxKit processing
pipeline expresses the most logical output.
It seems clear to me that on reading input files, the elements should
inherit an unprefixed namespace in XSLT ... and this is how AxKit
behaves in the first stage of the pipeline. Why should the rules change
in the intermediate stages? I am looking at this from a black-box
perspective, it seems to me that the results of the pipeline should be
exactly the same as the results of manually pipelining it, using
xsltproc.
My head hurts from this stuff.
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
