XMLFormTransformer: unknown element [item]
Hi, I get following error in error.log on demo xmlForm: ERROR (2003-06-30) 11:27.58:188 [xmlform.sitemap.transformer] (/cocoon/samples/xmlform/wizard) Thread-14/XMLFormTransformer: unknown element [item] ERROR (2003-06-30) 11:27.58:188 [xmlform.sitemap.transformer] (/cocoon/samples/xmlform/wizard) Thread-14/XMLFormTransformer: unknown element [item] ... ERROR (2003-06-30) 11:28.02:501 [xmlform.sitemap.transformer] (/cocoon/samples/xmlform/wizard) Thread-14/XMLFormTransformer: pass through element [group] ERROR (2003-06-30) 11:28.02:548 [xmlform.sitemap.transformer] (/cocoon/samples/xmlform/wizard) Thread-14/XMLFormTransformer: pass through element [group] ... Regards, Hill Cocoon 2.1m2, Tomcat 4.1, Java 1.4 __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: svgz to jpeg ?
I think you'll have to write your own GZipGenerator or possibly a GZipSource? You are right that the gzipped svg document is not a ZIP archive (it doesn't include a table of contents or anything - it's just a single BLOB). On the bright side, gzip is trivial to use in Java, so writing your own shouldn't be hard. CHeers Con -Original Message- From: rob [mailto:[EMAIL PROTECTED] Sent: Monday, 30 June 2003 09:35 To: [EMAIL PROTECTED] Subject: Re: svgz to jpeg ? On 28 Jun 2003 at 14:51, Upayavira wrote: Ah. So your file on disc is compressed svg. Okay, so you need to uncompress it into XML and pass that into the SVG2JPG serializer. There's two ways to do that, either with a zip generator (I think there's an example of one in the Langham Ziegler Cocoon book), or using the Jar protocol (see http://wiki.cocoondev.org/Wiki.jsp?page=JarProtocolExample). Both should extract your zipped SVG ready for converting to JPG. Thanks again for you reply. I've tried using the jar protocol, but it does not accept the 'svgz' file as a valid zip archive. I guess this is because there is no physical file to extract i.e jar:http//localhost/xyz.svg!??? Even Winzip will not open it. I haven't tried the zip generator yet because I haven't found any documentation, and someone has borrowed my Cocoon book !! Regards, Rob. - 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: xsp-request:get-parameter into xsl:variable problem
On 29.Jun.2003 -- 09:50 PM, C Bram Dit Saint Amand wrote:
This is an extract from request_attributes.xsl, a logicsheet which is
called by some_page.xsp
xsl:template match=request-attributes:get/webaction
xsl:variable name=webaction-valuexsp-request:get-parameter
name=webaction//xsl:variable
xsl:if test=contains($webaction-value, 'add_to_favourites_session')
and contains('add_to_favourites_session', $webaction-value)
$webaction-value most likely contains some XSP or Java code at the
time the logicsheet is applied -- which is when the XSP is translated
to Java servlet sourcecode *not* which every request!
So you may not use XSL to check for run time values in a
logicsheet. You need to use Java instead.
esql:connection
esql:poolperso-mysql/esql:pool
esql:execute-query
esql:queryINSERT INTO FavouritesBasketSession(SessionID,
URL) VALUES('xsp-session:get-id/', 'xsp-request:get-attribute
name=relative-url/');/esql:query
/esql:execute-query
/esql:connection
/xsl:if /xsl:template
When I access some_page.xsp?webaction=add_to_favourites_session, the
template is executed: the xsl:variable is created, but what is inside
the xsl:if *isn't* executed, which suggests that there is a problem with
the xsl:variable. For information, displaying the variable's content
with xsl:copy-of works (it correctly displays
'add_to_favourites_session'), but with xsl:value-of it doesn't display
anything.
Indeed, since it effectively copies the XSP / Java code used to read
the request attribute. It does not, however, copy the _value_ of that
attribute.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Link Hosting: RimuHosting
Hi. I'd appreciate a listing on your hosting page (http://cocoon.apache.org/2.1/link/hosting.html). Thanks! Regards, Peter http://rimuhosting.com a href=""RimuHosting - Java Hosting Specialists/a - They will install the latest Cocoon version by request
Re: XSP+SVG in cocoon-2.0.4
Gautam
Look at:
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=105550804911211w=2
The use of SVG is well described in a set of sample code.
Derek
[EMAIL PROTECTED] 30/06/2003 01:59:30
hi there,
I want to display an SVG image along side the web page content on
the users browser(user has Adobe SVG Viewer3.0 installed ) by putting
the SVG document within my XSP page.
As long as my pipeline displays the svg as png raster image
using the SVG2PNG serializer,it works fine.But the associated image
properties such as Zoom-In or Zoom-out are lost. For the user to keep
using these properties through IE,i want to pass the raw SVG content to
the users browser which then will handle the responsibility of
displaying the SVG .
My xsp documents looks something like this:
?xml version=1.0?
xsp:page language=java xmlns:xsp=http://apache.org/xsp;
document
header
titleTest SVG Page/title
/header
body
s1 title=SVG Image
pYou can use the mouse right click event to Zoom-In
or Zoom-Out
/p
p
img src=batikFX.svg/
/p
/s1
/body
/document
/xsp:page
Currently my sitemap pipeline looks like this:
map:match pattern=*.svg
map:generate src=resources/svg/{1}.svg/
map:serialize type=svg2png/
/map:match
What is the bext possible way to go about these? Can anyone help me
out on these?
regards,
Gautam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Mailscanner thanks transtec Computers for their support.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[summary] reading xml from pipeline into a flow script
Jonathan's suggestion worked, so I thought I'd summarize the solution
back to the list as a demo javascript flow script.
function demo() {
print getXML(http://localhost:8080/cocoon/mypipeline.xml;);
}
function getXML(urlStr) {
//
// return output of a pipeline as an xml string (and/or dom)
// [NB. watch out for my app-specific parse settings below!]
//
var factory =
Packages.javax.xml.parsers.DocumentBuilderFactory.newInstance();
factory.setValidating(false);
// Prevent expansion of entity references
factory.setExpandEntityReferences(false);
// Configure it to ignore comments
factory.setIgnoringComments(true);
var document;
var isvalid = true;
try {
document = factory.newDocumentBuilder().parse(urlStr);
} catch (e) {
isvalid = false;
print(xml parse error: + e + \n);
}
var xmlStr;
if (isvalid) {
// Convert document to string
var format = new Packages.org.apache.xml.serialize.OutputFormat(document);
var strOut = new Packages.java.io.StringWriter();
var XMLSerial = new
Packages.org.apache.xml.serialize.XMLSerializer(strOut,format);
XMLSerial.serialize(document.getDocumentElement());
xmlStr = strOut.toString();
}
return xmlStr;
}
Jonathan Spaeth wrote:
One simple way of accomplishing this is to simply, define pipeline to
generate, transform, and serialize the xml. Then, in the flowscript,
simply use the jaxp dom api to load the generated xml:
flow() {
var document =
Packages.javax.xml.parsers.DocumentBuilderFactory.newInstance().newDocumentBuilder().build(http://uri-to-xml-file);
...
document.getDocumentElement();
// it is now a dom
}
-Original Message-
From: Simon Price [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 28, 2003 3:25 PM
To: [EMAIL PROTECTED]
Subject: reading xml from pipeline into a flow script
From within a flow script, I would like to read (or pass in) xml
generated by a series of pipeline xslt transformations.
Please could someone give me a pointer on how to do this?
Cheers
Simon
---
Simon Price
Institute for Learning and Research Technology
University of Bristol
8-10 Berkeley Square
Bristol BS8 1HH
United Kingdom
Direct: +44 (0)7071 226 720
Office: +44 (0)117 928 7193
Fax: +44 (0)117 928 7112
[EMAIL PROTECTED]
http://www.ilrt.bristol.ac.uk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
---
Simon Price
Institute for Learning and Research Technology
University of Bristol
8-10 Berkeley Square
Bristol BS8 1HH
United Kingdom
Direct: +44 (0)7071 226 720
Office: +44 (0)117 928 7193
Fax: +44 (0)117 928 7112
[EMAIL PROTECTED]
http://www.ilrt.bristol.ac.uk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: reading xml from pipeline into a flow script
you can use this snippet:
function getString(src) {
try {
var is = cocoon.environment.resolveURI(src).getInputStream();
return
Packages.org.apache.cocoon.components.language.markup.xsp.XSPUtil.getContent
s(is);
}
catch(ex) {
print(ex: + ex);
}
return null;
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: reading xml from pipeline into a flow script
This will work but not with the upcoming Flow Object Model. You won't
have access to the environment any more. If you are interested in the
FOM you find a reference here:
http://wiki.cocoondev.org/Wiki.jsp?page=FOM (be aware that this is a
working document and may change!!!)
So currently the easiest way is
{
...
var uri = cocoon://blablabla;
var resolver = cocoon.componentManager.lookup(
Packages.org.apache.cocoon.environment.SourceResolver.ROLE );
var srce = resolver.resolveURI( uri );
cocoon.componentManager.release( resolver );
var dom =
Packages.org.apache.cocoon.components.source.SourceUtil.toDOM( srce );
...
}
which will probably change with FOM to
{
...
var uri = cocoon://blablabla;
var resolver = cocoon.getComponent(
Packages.org.apache.cocoon.environment.SourceResolver.ROLE );
var srce = resolver.resolveURI( uri );
// release of the component (not defined yet
var dom =
Packages.org.apache.cocoon.components.source.SourceUtil.toDOM( srce );
...
}
Hope this helps!
Reinhard
-Original Message-
From: Frank Taffelt [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 9:34 AM
To: [EMAIL PROTECTED]
Subject: Re: reading xml from pipeline into a flow script
you can use this snippet:
function getString(src) {
try {
var is =
cocoon.environment.resolveURI(src).getInputStream();
return
Packages.org.apache.cocoon.components.language.markup.xsp.XSPU
til.getContent
s(is);
}
catch(ex) {
print(ex: + ex);
}
return null;
}
-
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]
problems with a real mobile phone
Hi.. I'm trying to access my cocoon application on my computer with a real mobile device (a panasonic GD67 GPRS) but I'm always getting 'unsupported content type'. With emulators it all worked properly but now I'm getting this problem on a real mobile. I'm using custom generators to create XML and then I'm using xsl to convert the xml into WML. I'm managing to connect to the application with my mobile but it seems that the problem is that no proper WML is given out. Maybe I have to arrange something in the serializer of the sitemap for wml? I would appreciate any hints and help.. I'm using Jdk 1.4.1 , Tomcat 4.1.18, Cocoon 2.0.4 (The mobile's user agent string is: Panasonic-GAD67/1.0 UP.Browser/5.0.3.5 (GUI)) --- Donate to YMCA's Help The Homeless Campaign at http://shop.di-ve.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: problems with a real mobile phone
ho, if you haven't setup a serializer for wml (specifying the doctype, etc.), then you should do so. that would look something like: ... map:serializer logger=sitemap.serializer.wml mime-type=text/vnd.wap.wml name=wml src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//WAPFORUM//DTD WML 1.1//EN/doctype-public doctype-systemhttp://www.wapforum.org/DTD/wml_1.1.xml/doctype-system encodingISO-8859-1/encoding /map:serializer ... -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von [EMAIL PROTECTED] Gesendet: Montag, 30. Juni 2003 13:09 An: [EMAIL PROTECTED] Betreff: problems with a real mobile phone Hi.. I'm trying to access my cocoon application on my computer with a real mobile device (a panasonic GD67 GPRS) but I'm always getting 'unsupported content type'. With emulators it all worked properly but now I'm getting this problem on a real mobile. I'm using custom generators to create XML and then I'm using xsl to convert the xml into WML. I'm managing to connect to the application with my mobile but it seems that the problem is that no proper WML is given out. Maybe I have to arrange something in the serializer of the sitemap for wml? I would appreciate any hints and help.. I'm using Jdk 1.4.1 , Tomcat 4.1.18, Cocoon 2.0.4 (The mobile's user agent string is: Panasonic-GAD67/1.0 UP.Browser/5.0.3.5 (GUI)) -- - Donate to YMCA's Help The Homeless Campaign at http://shop.di-ve.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]
Using Saxon transformer together with Xalan and XSLTC
Hi, I try to use Saxon 7.6 together with Xalan There is the following warning in the logs when I try to place saxon.jar to WEB-INF/lib: Date: Mon Jun 30 14:01:53 EEST 2003 (1056970913164) Thread: PoolThread-4 Message #: 1 Level: WARN NDC: Category: sitemap.serializer.xhtml Message:Cannot know if transformer needs namespaces attributes - assuming NO. Location: org.apache.avalon.framework.logger.LogKitLogger.warn(LogKitLogger.java:159) Thrown: org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName of each element at net.sf.saxon.event.ContentEmitter.getNameCode(ContentEmitter.java:170) at net.sf.saxon.event.ContentEmitter.startElement(ContentEmitter.java:128) at org.apache.cocoon.serialization.AbstractTextSerializer.needsNamespacesAsAttributes(AbstractTextSerializer.java:341) at org.apache.cocoon.serialization.AbstractTextSerializer.configure(AbstractTextSerializer.java:268) at org.apache.cocoon.serialization.XMLSerializer.configure(XMLSerializer.java:76) ... The result is the HTML and XHTML serializers work properly only after Saxon transformer. They work incorrectly after XSLT and Xalan transformers (f.e. the attribute href isn't generated, although as far as I've found the xml-s after all transformers are the same). My emviroment is Win2000, jdk1.4.1_02, Jetty4.2.9, Cocoon2.1m3-dev -- Best regards, Peter mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Saxon transformer together with Xalan and XSLTC
Hi, PV I try to use Saxon 7.6 together with Xalan PV There is the following warning in the logs when I try to place PV saxon.jar to WEB-INF/lib: PV Date: Mon Jun 30 14:01:53 EEST 2003 (1056970913164) PV Thread: PoolThread-4 PV Message #: 1 PV Level: WARN PV NDC: PV Category: sitemap.serializer.xhtml PV Message:Cannot know if transformer needs namespaces attributes - assuming NO. PV Location: org.apache.avalon.framework.logger.LogKitLogger.warn(LogKitLogger.java:159) PV Thrown: PV org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName of each element PV at net.sf.saxon.event.ContentEmitter.getNameCode(ContentEmitter.java:170) PV at net.sf.saxon.event.ContentEmitter.startElement(ContentEmitter.java:128) PV at org.apache.cocoon.serialization.AbstractTextSerializer.needsNamespacesAsAttributes(AbstractTextSerializer.java:341) PV at org.apache.cocoon.serialization.AbstractTextSerializer.configure(AbstractTextSerializer.java:268) PV at org.apache.cocoon.serialization.XMLSerializer.configure(XMLSerializer.java:76) PV ... PV The result is the HTML and XHTML serializers work properly only after PV Saxon transformer. They work incorrectly after XSLT and Xalan PV transformers (f.e. the attribute href isn't generated, although as PV far as I've found the xml-s after all transformers are the same). My apologies, but the same is the input xml. The output xml-s are different: for Saxon - ?xml version=1.0 encoding=UTF-8? html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en head titleSamples/title meta http-equiv=Content-Type content=text/xhtml; charset=UTF-8/ link href=/styles/main.css type=text/css rel=stylesheet/ /head body h1List/h1 p xmlns= class=block2 Sample 1 - a href=examples/linotype/view/a /p p xmlns= class=block2 Sample 2 - a href=examples/charts/view/a /p /body /html for Xalan - ?xml version=1.0 encoding=UTF-8? html xmlns=http://www.w3.org/1999/xhtml; head xmlns=http://www.w3.org/1999/xhtml; title xmlns=http://www.w3.org/1999/xhtml;Samples/title meta xmlns=http://www.w3.org/1999/xhtml/ link xmlns=http://www.w3.org/1999/xhtml/ /head body xmlns=http://www.w3.org/1999/xhtml; h1 xmlns=http://www.w3.org/1999/xhtml;List/h1 p xmlns=http://www.w3.org/1999/xhtml; xmlns= Sample 1 - a xmlns=http://www.w3.org/1999/xhtml; xmlns=view/a /p p xmlns=http://www.w3.org/1999/xhtml; xmlns= xmlns= Sample 2 - a xmlns=http://www.w3.org/1999/xhtml; xmlns= xmlns=view/a /p /body /html So there is duplicating xmlns attributes in XML generated by Xalan. PV My emviroment is Win2000, jdk1.4.1_02, Jetty4.2.9, Cocoon2.1m3-dev -- Best regards, Petermailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: about Xindice
On Sun, 29 Jun 2003 22:00:20 +0200 Josema Alonso [EMAIL PROTECTED] wrote: Hi, Yury. It could be due to a number of reasons. It could depend on JDK version you're using, if you're using DOM or SAX, the XPath expression you're using, if you're validating data or not...or even a bug...you have provided very little info. Anyway, I suggest you should try at [EMAIL PROTECTED] which is more suitable for this kind of questions. And maybe you could try to search its archives (http://marc.theaimsgroup.com/?l=xindice-users). I remember questions like these surfaced recently. Best. Thanks for your reply. I use JDK v1.3, Xindice database deployed on tomcat 4.1.18 I would like to learn about the maximum productivity of xindice and ways to tune it (may be in tomcat side). And can I defend the xindice from being overloaded by high traffic (for example, if web-robots scan my site). -- Best regards, Yury Mikhienko. IT engineer, ZAO Mobicom-Kavkaz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XMLFORM and Cirilic encoding
Hello, I have a problem with Cirilic encoding when working with xmlforms. Everything is ok exept when I submit a cirilic text in a textbox: I write: Ãàëÿ and on the server it appears like: °» In select or labels the text appears as cirilic. But in textboxes and textareas - not. Any idea? Thanks Galia Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!
Re: XMLFORM and Cirilic encoding
Hello Galia, Try to set the form encoding. It is in the web.xml file: init-param param-nameform-encoding/param-name param-valueutf-8/param-value /init-param Simply incomment it for cocoon 2.1. GA Hello, GA I have a problem with Cirilic encoding when working with xmlforms. Everything is ok exept when I submit a cirilic text in a textbox: GA I write: GA and on the server it appears like: #208;#208;?#208;?#209;#143; GA In select or labels the text appears as cirilic. But in textboxes and textareas - not. GA Any idea? GA Thanks GA Galia GA - GA Do you Yahoo!? GA SBC Yahoo! DSL - Now only $29.95 per month! -- Best regards, Petermailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLFORM and Cirilic encoding
Thank you Peter! It works perfect! :-)Peter Velychko [EMAIL PROTECTED] wrote: Hello Galia,Try to set the form encoding. It is in the "web.xml" file:form-encodingutf-8Simply incomment it for cocoon 2.1.GA Hello,GA I have a problem with Cirilic encoding when working with xmlforms. Everything is ok exept when I submit a cirilic text in a textbox:GA I write: ÃàëÿGA and on the server it appears like: #208;#208;°#208;»#209;#143;GA In select or labels the text appears as cirilic. But in textboxes and textareas - not.GA Any idea?GA ThanksGA GaliaGA -GA Do you Yahoo!?GA SBC Yahoo! DSL - Now only $29.95 per month!-- Best regards,Peter mailto:[EMAIL PROTECTED]-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!
Re: reading xml from pipeline into a flow script
Thanks. I was glad of any solution at midnight on saturday, but I'll
watch to see how the fom evolves as you advise. Thanks.
Simon
Reinhard Pötz wrote:
This will work but not with the upcoming Flow Object Model. You won't
have access to the environment any more. If you are interested in the
FOM you find a reference here:
http://wiki.cocoondev.org/Wiki.jsp?page=FOM (be aware that this is a
working document and may change!!!)
So currently the easiest way is
{
...
var uri = cocoon://blablabla;
var resolver = cocoon.componentManager.lookup(
Packages.org.apache.cocoon.environment.SourceResolver.ROLE );
var srce = resolver.resolveURI( uri );
cocoon.componentManager.release( resolver );
var dom =
Packages.org.apache.cocoon.components.source.SourceUtil.toDOM( srce );
...
}
which will probably change with FOM to
{
...
var uri = cocoon://blablabla;
var resolver = cocoon.getComponent(
Packages.org.apache.cocoon.environment.SourceResolver.ROLE );
var srce = resolver.resolveURI( uri );
// release of the component (not defined yet
var dom =
Packages.org.apache.cocoon.components.source.SourceUtil.toDOM( srce );
...
}
Hope this helps!
Reinhard
-Original Message-
From: Frank Taffelt [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 9:34 AM
To: [EMAIL PROTECTED]
Subject: Re: reading xml from pipeline into a flow script
you can use this snippet:
function getString(src) {
try {
var is =
cocoon.environment.resolveURI(src).getInputStream();
return
Packages.org.apache.cocoon.components.language.markup.xsp.XSPU
til.getContent
s(is);
}
catch(ex) {
print(ex: + ex);
}
return null;
}
-
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]
--
---
Simon Price
Institute for Learning and Research Technology
University of Bristol
8-10 Berkeley Square
Bristol BS8 1HH
United Kingdom
Direct: +44 (0)7071 226 720
Office: +44 (0)117 928 7193
Fax: +44 (0)117 928 7112
[EMAIL PROTECTED]
http://www.ilrt.bristol.ac.uk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP+SVG in cocoon-2.0.4
hi Derek
Thanks a lot for your help...and to the one who put those scripts
It was a real help to me!!
regards
Gautam
[EMAIL PROTECTED] 06/30/03 02:41AM
Gautam
Look at:
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=105550804911211w=2
The use of SVG is well described in a set of sample code.
Derek
[EMAIL PROTECTED] 30/06/2003 01:59:30
hi there,
I want to display an SVG image along side the web page content on
the users browser(user has Adobe SVG Viewer3.0 installed ) by putting
the SVG document within my XSP page.
As long as my pipeline displays the svg as png raster image
using the SVG2PNG serializer,it works fine.But the associated image
properties such as Zoom-In or Zoom-out are lost. For the user to keep
using these properties through IE,i want to pass the raw SVG content
to
the users browser which then will handle the responsibility of
displaying the SVG .
My xsp documents looks something like this:
?xml version=1.0?
xsp:page language=java xmlns:xsp=http://apache.org/xsp;
document
header
titleTest SVG Page/title
/header
body
s1 title=SVG Image
pYou can use the mouse right click event to Zoom-In
or Zoom-Out
/p
p
img src=batikFX.svg/
/p
/s1
/body
/document
/xsp:page
Currently my sitemap pipeline looks like this:
map:match pattern=*.svg
map:generate src=resources/svg/{1}.svg/
map:serialize type=svg2png/
/map:match
What is the bext possible way to go about these? Can anyone help me
out on these?
regards,
Gautam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Mailscanner thanks transtec Computers for their support.
-
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]
Refactoring Flow/XMLForms example
I'm continuing to play with Flow and in particular, XMLForms:
Today I decided to refactor the flow-driven feedback wizard in the
samples:
http://localhost:8080/cocoon/samples/xmlform/flow
In particular, I wanted to get rid of the inlined validation function
definitions in the calls to Xform.sendview ().
So I went into feedbackWizard.js and defined a userinfo object with a
member, bean, and the two validation functions defined as methods.
However when I restarted Cocoon, it looks like XForm.sendView is not
getting the validation function passed to it, as when I enter data
that would trigger the validator, it's ignored, and only the Schematron
validation's applied.
I know that passing a function as data in JavaScript's a little
non-obvious.
Here's my revisions to feedbackWizard.js
// XML Form Feedback Wizard Application
cocoon.load(resource://org/apache/cocoon/components/flow/javascript/
xmlForm.js);
/**
* Constructor for UserInfo object
*/
function UserInfo ()
{
this.bean = null;
}
/**
* Validate UserIdentity
* @param xform XForm object
*/
function UserInfo_validateUserIdentity (xform)
{
var bean = xform.getModel();
print(I can also do validation in JavaScript);
print(age = +xform.getValue(number(/age)));
print(role = +bean.role);
if (bean.age 40) {
xform.addViolation(/age, Hey, you're too old);
}
}
UserInfo.prototype.validateUserIdentity = function (xform)
{
UserInfo_validateUserIdentity (xform);
}
/**
* Validate Deployment
* @param xform XForm object
*/
function UserInfo_validateDeployment (xform)
{
var bean = xform.getModel();
print(I can also do validation in JavaScript);
if (bean.publish) {
xform.addViolation(/publish, Sorry, I won't let you publish);
}
}
UserInfo.prototype.validateDeployment = function (xform)
{
UserInfo_validateDeployment (xform);
}
function feedbackWizard(xform) {
var userinfo = new UserInfo ();
userinfo.bean = {
firstName: Donald,
lastName: Duck,
email: [EMAIL PROTECTED],
age: 5,
number: 1,
liveUrl: http://;,
publish: true,
hidden: true,
count: 1,
notes: your notes here,
favorite: [http://xml.apache/org/cocoon;,
http://jakarta.apache.org;,
http://www.google.com;,
http://www.slashdot.com;,
http://www.yahoo.com;],
hobby: [swim, movies, ski, gym, soccer],
allHobbies: [
{
key: swim,
value: Swimming
},
{
key: gym,
value: Body Building
},
{
key: ski,
value: Skiing
},
{
key: run,
value: Running
},
{
key: football,
value: Football
},
{
key: read,
value: Reading
},
{
key: write,
value: Writing
},
{
key: soccer:,
value: Soccer
},
{
key: blog,
value: Blogging
}],
role: [Hacker, Executive],
system: {
os: Unix,
processor: p4,
ram: 512,
servletEngine: Tomcat,
javaVersion: 1.3,
}
}
xform.setModel(userinfo.bean);
xform.sendView(userIdentity,
userIdentity.xml,
userinfo.validateUserIdentity (xform));
// move this into a method of UserInfo
/*function(xform) { */
/*var bean = xform.getModel(); */
/* print(I can also do validation in JavaScript); */
/* print(age = +xform.getValue(number(/age))); */
/* print(role = +bean.role); */
/*if (bean.age 40) { */
/* xform.addViolation(/age, Hey, you're too old); */
/* } */
/* }); */
print(handling user identity);
xform.sendView(deployment,
deployment.xml,
userinfo.validateDeployment (xform));
// move this into a method of UserInfo
/*function(xform) { */
/* var bean = xform.getModel(); */
/* print(I can also do validation in JavaScript); */
/*if (bean.publish) { */
/*xform.addViolation(/publish, Sorry, I won't let you
publish); */
/* } */
/* }); */
print(handling deployment);
xform.sendView(system, system.xml);
print(handling system);
xform.sendView(confirm, confirm.xml);
print(handling confirm);
xform.finish(end.xml);
print(done);
}
-- whump
-
To unsubscribe, e-mail: [EMAIL
Woody textareas?
Are textareas implemented in Woody yet? I cannot find anything in the (oh so sparse) documentation. Furthermore, has anyone used Woody extensively yet? (I know, I know, it's alpha at this point but I need some serious forms handling.) Should I be considering Xforms instead? Who got some experience getting their hands bloodied with forms in Cocoon? I'm ever anxious to find out. Thanks in advance, Luke. winmail.dat- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Woody textareas?
On 30/06/2003 18:58 Luke Penca wrote: Are textareas implemented in Woody yet? I cannot find anything in the (oh so sparse) documentation. Have you checked with http://wiki.cocoondev.org/Wiki.jsp?page=Woody ? It's not fully up to date, but that tracking CVS commit messages might help you already. Furthermore, has anyone used Woody extensively yet? (I know, I know, it's alpha at this point but I need some serious forms handling.) Should I be considering Xforms instead? Who got some experience getting their hands bloodied with forms in Cocoon? I'm ever anxious to find out. I jotted down already some of the background of Woody's genesis over here: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=105491414614553w=2 So its feature list is in active expansion, and it has been created to be extensively used and actively supported. HTH, /Steven -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Woody textareas?
Cocoon's form handling is (imho) it's weakest area at present although it is rapidly improving with the interplay between flow and xmlform. Unless your app is simple, I'd recommend not wasting time on the simple form validator and db actions. Pure xmlforms where you end up writing java code for each form is elegant but time consuming. I've not looked in detail at woody. However, I'd strongly recommend that you take a look at the petstore sample. This uses javascript as the interface to the persistence layer part of your model and (to my taste) a really easy to understand but flexible logic layer in a separate javascript file. The sample has switchable view layers that can be velocity/xslt/jxpath/jsomethingelse. The velocity vesion is very clean and easy to read (but there again, I used to be an assembler programmer!). Use is made of xmlform - with validation done in either schematron and/or javascript. Cheers Simon Luke Penca wrote: Are textareas implemented in Woody yet? I cannot find anything in the (oh so sparse) documentation. Furthermore, has anyone used Woody extensively yet? (I know, I know, it's alpha at this point but I need some serious forms handling.) Should I be considering Xforms instead? Who got some experience getting their hands bloodied with forms in Cocoon? I'm ever anxious to find out. Thanks in advance, Luke. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Simon Price Institute for Learning and Research Technology University of Bristol 8-10 Berkeley Square Bristol BS8 1HH United Kingdom Direct: +44 (0)7071 226 720 Office: +44 (0)117 928 7193 Fax: +44 (0)117 928 7112 [EMAIL PROTECTED] http://www.ilrt.bristol.ac.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Contribution: MultiPartPostAction FilePartGenerator
Hello all, As per the Cocoon contribution guidelines, I've made some Cocoon extensions source code available for download at: http://www.tempeststrings.com/cocoon/index.html. There are two files that meet the guidelines for contribution to the Cocoon code base: org.apache.cocoon.acting.MultiPartPostAction.java org.apache.cocoon.generation.FilePartGenerator.java Together, these will allow Cocoon to accept a multi part post containing an uploaded file and kickoff a pipeline by parsing the file's contents for generation. I've used this source to configure a Cocoon installation as a real-time data conversion service. Using the service, a user can upload a file in XML format, and immediately receive a response containing the same data in any format supported by Cocoon Serializers. A sample sitemap.xconf is included in the header comments of MultiPartPostAction. My hope is that these contributions will make their way into the Coccon code base. Please let me know if I can assist in any way. Please note that the other files (not the two described above) found in this distribution rely on GPL code and can not be released under the Apache license. Thanks, -Eric Simmerman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Saxon transformer together with Xalan and XSLTC
Peter Velychko wrote: So there is duplicating xmlns attributes in XML generated by Xalan. Could it be that the AElfred parser from the saxon jar kicks in? IT is known to report namespace attributes differently than Xerces which may cause hickups in some Xalan versions (unfortunately, this is a dark corner in the SAX spec). Try to remove the services entry from the saxon jar and see whether the problem persists. it this fails, see whether you can import the XML parser functionality from the servlet container rather than the webapp lib. OTOH, it could be the XML parser imported from the servlet container which causes problems. Try to use the Xerces component instead of the SAXParser component to exclude this possiblity. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Woody textareas?
-Original Message- From: Simon Price [mailto:[EMAIL PROTECTED] Sent: Montag, 30. Juni 2003 20:04 ... Cocoon's form handling is (imho) it's weakest area at present although it is rapidly improving with the interplay between flow and xmlform. ... Simon Luke Penca wrote: Are textareas implemented in Woody yet? I cannot find anything in the (oh so sparse) documentation. Furthermore, has anyone used Woody extensively yet? (I know, I know, it's alpha at this point but I need some serious forms handling.) Should I be considering Xforms instead? Who got some experience getting their hands bloodied with forms in Cocoon? I'm ever anxious to find out. ... Luke. I've just started prototyping with Woody and I think it is a diamond in the raw. Finally a form handling package that does not require you to write a bean class or Cocoon action for every little form! Coming to the original question: There is no special textarea widget but you can emulate it easily by a field widget with styling: wt:widget id=question xhtml:textarea rows=5 cols=30 wrap=physical/ /wt:widget which is then transformed into HTML as: xsl:template match=wi:field[wi:styling/xhtml:textarea] xhtml:textarea name=[EMAIL PROTECTED] xsl:apply-templates select=wi:styling/xhtml:textarea/@*/ xsl:choose xsl:when test=wi:value != '' xsl:value-of select=wi:value/ /xsl:when xsl:otherwise xsl:value-of select='#160;'/ /xsl:otherwise /xsl:choose /xhtml:textarea /xsl:template HTH, ALfred. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The senders company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the senders company. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Link Livesites: http://www.ctg.albany.edu
We had it already on the list last week, here is the official announcement. I have added the link in the CVS. Joerg Original Message Subject: RE: Contact Us Form Date: Mon, 30 Jun 2003 09:41:18 -0400 From: Jim Costello [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Yes, We would be glad to be listed on your powered by Cocoon page. Our base url is http://www.ctg.albany.edu. The entire site is done in Cocoon 2, using standard XML/XSL with a docbook schema for our XML documents. The site currently has close to 4000 pages produced by approximately 300 xml/xsl files. We expect to be producing about 10,000 pages by the end of the year with no increase in the number of xml/xsl files. The main content of our site are the reports, guides and studies that our Center produces. We needed a sensible way to manage these documents, control the source file and produce a variety of formats HTML, PDFs, multiple locations on the site. XML and Cocoon has been the answer. The site has only been live for about 1 month, but we've already seen a doubling of our traffic and it's much easier to maintain and find our information on the site now. It's all Cocoon and XML/XSL; no database involvement. We also have a white paper on the site at http://www.ctg.albany.edu/publications/reports/xml that explains our rationale and approach to using xml and cocoon. One other component of the site at http://www2.ctg.albany.edu/egovfirststop/ uses Cocoon 1 and mySQL database to power an information repository application. We will be upgrading this application to Cocoon 2. Jim Costello Web Application Developer Center for Technology in Govenment www.ctg.albany.edu [EMAIL PROTECTED] (518) 442-3812 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
where is the sitemap dtd?
Can anybody point me to a location where I can download the Document Type Definition (DTD) for the cocoon sitemap. I don't know, maybe I am just blind, but I could't find it anywhere. Regards, Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Refactoring Flow/XMLForms example
Further experiment and was able to answer my question:
On Monday, June 30, 2003, at 09:54 AM, [EMAIL PROTECTED] wrote:
I'm continuing to play with Flow and in particular, XMLForms:
Today I decided to refactor the flow-driven feedback wizard in the
samples:
http://localhost:8080/cocoon/samples/xmlform/flow
In particular, I wanted to get rid of the inlined validation function
definitions in the calls to Xform.sendview ().
The solution is that while you still have to call the function wrapper
in the arguments, you can define your functions elsewhere thus:
function UserInfo_validateUserIdentity (xform)
{
var bean = xform.getModel();
print(I can also do validation in JavaScript);
print(age = +xform.getValue(number(/age)));
print(role = +bean.role);
if (bean.age 40) {
xform.addViolation(/age, Hey, you're too old);
}
}
UserInfo.prototype.validateUserIdentity = function (xform)
{
UserInfo_validateUserIdentity (xform);
}
...
xform.sendView(userIdentity,
userIdentity.xml,
function (xform) { userinfo.validateUserIdentity
(xform); });
and now the refactored example works as before.
-- whump
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: problems with a real mobile phone
Thanks for your help...I was setting up the serializer wrongly for the wml..was using the wrong encoding..your snippet worked perfectly.. Regards Pierre ho, if you haven't setup a serializer for wml (specifying the doctype, etc.), then you should do so. that would look something like: ... map:serializer logger=sitemap.serializer.wml mime-type=text/vnd.wap.wml name=wml src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//WAPFORUM//DTD WML 1.1//EN/doctype-public doctype-systemhttp://www.wapforum.org/DTD/wml_1.1.xml/doctype-system encodingISO-8859-1/encoding /map:serializer ... -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von [EMAIL PROTECTED] Gesendet: Montag, 30. Juni 2003 13:09 An: [EMAIL PROTECTED] Betreff: problems with a real mobile phone Hi.. I'm trying to access my cocoon application on my computer with a real mobile device (a panasonic GD67 GPRS) but I'm always getting 'unsupported content type'. With emulators it all worked properly but now I'm getting this problem on a real mobile. I'm using custom generators to create XML and then I'm using xsl to convert the xml into WML. I'm managing to connect to the application with my mobile but it seems that the problem is that no proper WML is given out. Maybe I have to arrange something in the serializer of the sitemap for wml? I would appreciate any hints and help.. I'm using Jdk 1.4.1 , Tomcat 4.1.18, Cocoon 2.0.4 (The mobile's user agent string is: Panasonic-GAD67/1.0 UP.Browser/5.0.3.5 (GUI)) -- - Donate to YMCA's Help The Homeless Campaign at http://shop.di-ve.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] --- Donate to YMCA's Help The Homeless Campaign at http://shop.di-ve.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
including a static XML file in the return from my sql call?
I'm trying to import a static XML file into the
results of my SQL call.
Here's my sitemap.xmap block:
map:match pattern=ameddReportByBDE/*.pdf
map:generate type=request/
map:transform type=xslt src=render-logic.xsl
map:parameter name=label value={1}/
/map:transform
map:transform type=xinclude/
map:transform type=xslt src=render-logic.xsl/
map:transform type=xinclude/
map:transform type=xslt src=render-logic5.xsl
map:parameter name=label value={1}/
/map:transform
map:transform type=sql
map:parameter name=dburl
value=jdbc:mysql://localhost/amedd?user=adminamp;password=alpha
/
/map:transform
map:transform type=xinclude/
!--
map:transform src=ameddReportByBDE.xsl/
map:serialize type=fo2pdf/
--
map:serialize type=xml/
/map:match
and inside render-logic5.xsl, I've got :
xsl:template match=mops:report-sql
mops:report-xinclude-headlines
xi:include
xsl:attribute name=hrefreports/xsl:value-of
select=$label//headlines.xml#xpointer(/headlines)/xsl:attribute
/xi:include
/mops:report-xinclude-headlines
/xsl:template
but my final XML only includes the included xml, and
not the results from the sql query.
Help?
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Contribution: MultiPartPostAction FilePartGenerator
Thank you for this work and your interest in contributing. I hope this is the first of many. Here are my thoughts after a quick look: The MultiPartPostAction seems unnecessary. What do you gain by placing a copy of the uploaded file which is already in the ObjectModel under the Request object directly in the ObjectModel? The FilePartGenerator OTOH seems useful (I don't think the existing StreamGenerator will do this). As noted above, the action is not needed in the equation - you can just get the FilePart right out of the Request in the Generator. Then, I don't see the reason behind the overloaded getInputSource() - the FilePart is designed to allow polymorphism there - just cast the Request.get() to FilePart and call FilePart.getInputStream() on it. If you find I'm correct, could you look at refactoring this and submitting a patch to Bugzilla? I'd be more than willing to help with anything that doesn't make sense to you. As far as I can see, none of the HSSF stuff is useful without the GnumericWriter which is GPL. The last I heard someone was working directly in the poi project on a Gnumeric generator from Excel that could then go straight in cvs. Unless that is now not a project that will ever happen for some reason, I'd be against introducing even the hooks for a GPL version that would just get replaced later. If you want to keep this available for others to contribute and benefit, I'd recommend approaching cocoondev which can by its nature accomodate GPL. By the way, I don't think you can legally use the cocoon package name on the GPL source file - better pick another package name. Still, I am just one voice - does anyone else have opinions one way or the other? Thanks again, Geoff Howard -Original Message- From: Simmerman, Eric [mailto:[EMAIL PROTECTED] Sent: Monday, June 30, 2003 1:50 PM To: [EMAIL PROTECTED] Subject: Contribution: MultiPartPostAction FilePartGenerator Hello all, As per the Cocoon contribution guidelines, I've made some Cocoon extensions source code available for download at: http://www.tempeststrings.com/cocoon/index.html. There are two files that meet the guidelines for contribution to the Cocoon code base: org.apache.cocoon.acting.MultiPartPostAction.java org.apache.cocoon.generation.FilePartGenerator.java Together, these will allow Cocoon to accept a multi part post containing an uploaded file and kickoff a pipeline by parsing the file's contents for generation. I've used this source to configure a Cocoon installation as a real-time data conversion service. Using the service, a user can upload a file in XML format, and immediately receive a response containing the same data in any format supported by Cocoon Serializers. A sample sitemap.xconf is included in the header comments of MultiPartPostAction. My hope is that these contributions will make their way into the Coccon code base. Please let me know if I can assist in any way. Please note that the other files (not the two described above) found in this distribution rely on GPL code and can not be released under the Apache license. Thanks, -Eric Simmerman - 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: Contribution: MultiPartPostAction FilePartGenerator
Eric, Please use Bugzilla (http://nagoya.apache.org) to provide your enhancements otherwise I fear that they will be overlooked. Additionally I cc'ed cocoon-dev. Without looking at your sources and examples: What does your generator provide what http://cocoon.apache.org/2.1/userdocs/generators/stream-generator.html can't do for you? Cheers, Reinhard -Original Message- From: Simmerman, Eric [mailto:[EMAIL PROTECTED] Sent: Monday, June 30, 2003 7:50 PM To: [EMAIL PROTECTED] Subject: Contribution: MultiPartPostAction FilePartGenerator Hello all, As per the Cocoon contribution guidelines, I've made some Cocoon extensions source code available for download at: http://www.tempeststrings.com/cocoon/in dex.html. There are two files that meet the guidelines for contribution to the Cocoon code base: org.apache.cocoon.acting.MultiPartPostAction.java org.apache.cocoon.generation.FilePartGenerator.java Together, these will allow Cocoon to accept a multi part post containing an uploaded file and kickoff a pipeline by parsing the file's contents for generation. I've used this source to configure a Cocoon installation as a real-time data conversion service. Using the service, a user can upload a file in XML format, and immediately receive a response containing the same data in any format supported by Cocoon Serializers. A sample sitemap.xconf is included in the header comments of MultiPartPostAction. My hope is that these contributions will make their way into the Coccon code base. Please let me know if I can assist in any way. Please note that the other files (not the two described above) found in this distribution rely on GPL code and can not be released under the Apache license. Thanks, -Eric Simmerman - 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]
