Generate multi-level XML document using standard SQL select statement
Just tried MS SQL server 2000. I can type in browser: http://localhost/mydb?sql=select * from dept, emp where dept.deptno=emp.dept.no for xml autoroot=List then, I will get XML: List dept id='10' name='Sales' emp id='10' name='King' salary='5000'/ emp id='20' name='John' salary='200'/ /dept dept id='20' name='Account' emp id='30' name='Peter' salary='2000'/ /dept ... /List The nesting of joined result is automatic, and I found that it is very useful. so is there any similar tool that can be used to get similar result? Thanks Evan __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CachingCIncludeTransformer - no effect?
Hi Vadim, thank you for your reply. Yes, I declared it in the sitemap. Can you please tell me shortly how to switch on debug for this case? Thank you, best regards - Volker - -Original Message- From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] Sent: Freitag, 10. Mai 2002 14:55 To: [EMAIL PROTECTED] Subject: RE: CachingCIncludeTransformer - no effect? From: Volker Schneider [mailto:[EMAIL PROTECTED]] Dear colleagues, I have built a xsp-page which takes two xml-Files and builds a xsp which will be compiled by another pipeline: map:match pattern=xsp-part1 map:generate src=part1.xsp/ map:serialize type=xml/ /map:match map:match pattern=xsp-part2 map:generate src=part2.xsp/ map:serialize type=xml/ /map:match map:match pattern=xsp-main map:generate src=main.xsp/ map:transform type=cinclude/ map:serialize type=xml/ /map:match map:match pattern=xsp-result map:generate type=serverpages src=cocoon:/xsp-main/ map:serialize type=xml/ /map:match This is not very performant, so that I tried to use the CachingCIncludeTransformer instead of the CIncludeTransformer, but bad performance did not change. My other xsp sample pages run 2-3 times faster than this. One point is, that I have 4 pipelines here and with every new included part I will get a further one. I think that caching of the CInclude result will be very helpful in this case. Is it necessary to switch the CachingCIncludeTranformer to on? I looked into the source code, but I did not find anything that looks like a switch or a helpful attribute. Do you have CachingCIncludeTranformer declared in the sitemap? Does it actually work (turn on debug and look for messages from the MRUStore)? Vadim Can anybody help me? Thank you, best regards - Volker - - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cocoon Internal Server Error
Hi Sonia,
oh, I think there are some additional classes missing. You can try to find
the classes within the class files and move these files too to the lib
directory as well. Maybe it'll be successful.
Best regards
- Volker -
-Original Message-
From: Sonia Pérez [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 10. Mai 2002 17:25
To: [EMAIL PROTECTED]
Subject: Cocoon Internal Server Error
Hi,
First of all thanks Volker, I have copied those files to
{TOMCAT_HOME}/lib and
now I get another error.
OS Debian
Tomcat4
JDK1.3
The error is:
Cocoon 2 - Internal server error
*type* fatal
*message*_Language Exception_
*description*_ org.apache.cocoon.ProcessingException: Language
Exception: org.apache.cocoon.components.language.LanguageException:
Error compiling sitemap_xmap: Line 22, column 7:
Class org.apache.avalon.framework.component.Component not found in
import. Line 23, column 7:
Class org.apache.avalon.framework.configuration.Configurable not found
in import. Line 24, column 7:
Class org.apache.avalon.framework.configuration.Configuration not found
in import. Line 25, column 7:
Class org.apache.avalon.framework.configuration.ConfigurationException
not found in import. Line 26, column 7:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found in import. Line 27, column 7:
Class org.apache.avalon.framework.parameters.Parameters not found in
import. Line 29, column 7:
Class org.apache.cocoon.Constants not found in import. Line 30, column 7:
Class org.apache.cocoon.ProcessingException not found in import. Line
31, column 7:
Class org.apache.cocoon.ResourceNotFoundException not found in import.
Line 32, column 7:
Class org.apache.cocoon.ConnectionResetException not found in import.
Line 33, column 7:
Class org.apache.cocoon.acting.Action not found in import. Line 34,
column 7:
Class org.apache.cocoon.environment.Environment not found in import.
Line 35, column 7:
Class org.apache.cocoon.environment.Redirector not found in import. Line
36, column 7:
Class org.apache.cocoon.matching.Matcher not found in import. Line 37,
column 7:
Class org.apache.cocoon.matching.PreparableMatcher not found in import.
Line 38, column 7:
Class org.apache.cocoon.selection.Selector not found in import. Line 39,
column 7:
Class org.apache.cocoon.sitemap.AbstractSitemap not found in import.
Line 40, column 7:
Class org.apache.cocoon.components.pipeline.StreamPipeline not found in
import. Line 41, column 7:
Class org.apache.cocoon.components.pipeline.EventPipeline not found in
import. Line 42, column 7:
Class org.apache.cocoon.sitemap.Sitemap not found in import. Line 43,
column 7:
Class org.apache.cocoon.sitemap.NotifyingGenerator not found in import.
Line 44, column 7:
Class org.apache.cocoon.sitemap.ContentAggregator not found in import.
Line 45, column 7:
Class org.apache.cocoon.sitemap.Manager not found in import. Line 46,
column 7:
Class org.apache.cocoon.sitemap.SitemapRedirector not found in import.
Line 47, column 7:
Class org.apache.cocoon.components.language.markup.xsp.XSPRequestHelper
not found in import. Line 48, column 7:
Class org.apache.cocoon.components.language.markup.xsp.XSPResponseHelper
not found in import. Line 49, column 7:
Class org.apache.cocoon.components.notification.NotifyingBuilder not
found in import. Line 50, column 7:
Class org.apache.cocoon.components.notification.Notifying not found in
import. Line 51, column 7:
Class org.apache.cocoon.components.notification.SimpleNotifyingBean not
found in import. Line 62, column 34:
Superclass org.apache.cocoon.sitemap.AbstractSitemap of class
org.apache.cocoon.www.jndi_.localhost.cocoon.sitemap_xmap not found.
Line 428, column 8:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 429, column 14:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 438, column 32:
Class org.apache.cocoon.sitemap.Sitemap not found. Line 438, column 32:
Undefined variable or class name: Sitemap Line 443, column 8:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 444, column 14:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 450, column 32:
Class org.apache.cocoon.sitemap.Sitemap not found. Line 450, column 32:
Undefined variable or class name: Sitemap Line 454, column 8:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 455, column 14:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 461, column 32:
Class org.apache.cocoon.sitemap.Sitemap not found. Line 461, column 32:
Undefined variable or class name: Sitemap Line 466, column 8:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 467, column 14:
Class org.apache.avalon.framework.configuration.DefaultConfiguration not
found. Line 473, column 32:
Class org.apache.cocoon.sitemap.Sitemap
Re: using request parameters in sitemap
sorry - never mind - I found the answer in the equest-parameter generator:
map:match pattern=dirtest1b
map:match pattern=dir type=request-parameter
map:generate type=directory src={1} depth=2/
map:serialize type=xml/
/map:match
/map:match
now it works with stuff like:
http://localhost:8080/cocoon/testdir/dirtest1b?dir=j:/jakarta-tomcat-4.0.1/webapps/cocoon/testdir/examples
just fine, even from withing document():)
Ron
Hi,
I am trying to use the directory generator and having some difficulty. I
can't get the depth to work (I did check the archives and bug reports with no luck).
I looked at the code in DirectoryGenerator.java and it looks like it should work but
it doesn't so I gave up and tried a different tack, I
created:
map:match pattern=dirtest1a/**
map:generate type=directory src={1} depth=10/
map:serialize type=xml/
/map:match
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] HTML email (RE: [docs] Suggestions about pre/pre and/orcode/code in the docs)
Gerhard Froehlich wrote: Martin Stricker wrote: MJ Ray wrote: von Schwerdtner, Thomas (GXS, FPI) wrote: [...] Does ANYONE know of a way to shut this off or to whip Outlook into shape? Yes. Shut off Outlook. Or tell Outlook to use text only. Tools-Options, Register e-Mail Format, select text as the format. Sorry if the menu entries are wrong, I only have the German version of Outlook. Ack...shut off Outlook. I did it today and moved everything to mozilla1.0 RC1. Yes it rulez... Indeed it does rule! :-)) But I gave that advice because in some cases one is *forced* to use Outlook, like myself at work. Ack indeed... *shudder* ;-) Best regards, Martin Stricker -- Homepage: http://www.martin-stricker.de/ Webmaster-Forum: http://www.masterportal24.com/cgi-bin/YaBB.cgi Red Hat Linux 7.2 for low memory: http://www.rule-project.org/rule/ Registered Linux user #210635: http://counter.li.org/ - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
namespace prefixes declarations in output HTML (repost - sorry if you got it twice)
[Sorry if you got this mail twice - I have some problems with my SMTP
server]
I know that this subject has already been discussed but I think with no
success I'm preparing a cross-platform system for very thin clients
(PDAs for example) I'd like to strip all namespace declarations before
serialization. I have seen somewhere on the mailing archives that I
should use exclude-result-prefixes directive.
So I have (the version I'm presenting is still not optimal in case of
size - I have to use CSS stylesheets also):
1. A simple xsp file:
?xml version=1.0 encoding=UTF-8?
xsp:page language=java xmlns:xsp=http://apache.org/xsp;
xmlns:xsp-formval=http://apache.org/xsp/form-validator/2.0;
xmlns:xsp-request=http://apache.org/xsp/request/2.0;
page
titleLogin page/title
body
para
bEnter login information:/b
/para
form action=login method=POST
input type=hidden name=visited
value=true/
xsp:logic
boolean userHasSeenForm = (xsp-request:get-parameter
name=visited/ != null );
/xsp:logic
xsp-formval:descriptor
name=descriptors/login.xml
constraint-set=login-info
xsp-formval:validate
name=username
xsp:logic
if (userHasSeenForm) {
if ( xsp-formval:is-null/ ) {
div align=center
bPlease provide a valid
username/b
/div
} else if (
xsp-formval:is-toolarge/ ) {
div align=center
bUsername too long/b
/div
}
}
/xsp:logic
[...]
and so on - this is not important here
2. my stylesheet is :
?xml version=1.0 encoding=UTF-8?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
exclude-result-prefixes=xsp xsp-request xsp-formval
xsl:template match=page
html
head
title
xsl:value-of select=title/
/title
META content=0 http-equiv=expires/
META content=nocache
http-equiv=pragma/
/head
xsl:apply-templates/
/html
/xsl:template
xsl:template match=title/
xsl:template match=body
body style=font-family: Tahoma;font-size: 10pt
bgcolor=#FAEBD7
xsl:apply-templates/
/body
/xsl:template
xsl:template match=para
p align=centerxsl:apply-templates//p
/xsl:template
xsl:template match=br
br/
/xsl:template
xsl:template match=link
a href={@href}xsl:value-of select=.//a
/xsl:template
xsl:template match=@*|node() priority=-2
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
xsl:template match=text() priority=-1
xsl:value-of select=./
/xsl:template
/xsl:stylesheet
Although I have included exclude-result-prefixes=xsp xsp-request
xsp-formval still the output is:
html
head
META http-equiv=Content-Type content=text/html; charset=UTF-8
titleLogin page/title META http-equiv=expires content=0 META
http-equiv=pragma content=nocache /head
body bgcolor=#FAEBD7 style=font-family: Tahoma;font-size: 10pt
p align=center
b xmlns:xsp=http://apache.org/xsp;
xmlns:xspdoc=http://apache.org/cocoon/XSPDoc/v1;
xmlns:xsp-formval=http://apache.org/xsp/form-validator/2.0;
xmlns:xsp-request=http://apache.org/xsp/request/2.0;Enter login
information:/b
/p
form xmlns:xsp=http://apache.org/xsp;
xmlns:xspdoc=http://apache.org/cocoon/XSPDoc/v1;
xmlns:xsp-formval=http://apache.org/xsp/form-validator/2.0;
xmlns:xsp-request=http://apache.org/xsp/request/2.0; action=login
method=POST
input type=hidden name=visited value=true
so it's more than ugly (the namespace declarations have been propagated
to all tags that are not explicitly matched in the xsl stylesheet
What can I do ?
ouzo
-
Please check that your question has not already been
