RE: Does ValidatingTransformer support DTD validation
Hi David, yes it is and i tested it yesterday without any luck by the way. I am going to test some of my existing use cases with #cocoon3 in the next few days. I think it will be much easier for me to walk through the code as it is much leaner and meaner. Robby -Oorspronkelijk bericht- Van: David Crossley [mailto:cross...@apache.org] Verzonden: vr 1-7-2011 2:53 Aan: dev@cocoon.apache.org Onderwerp: Re: Does ValidatingTransformer support DTD validation Robby Pelssers wrote: > Hi David, > > One thing I still need to investigate was Jeroen's reply: > > Hi Robby, > > have you checked this page [1]? I'm not sure if this is the same > component, but is might lead you further. > > [1] http://wiki.apache.org/cocoon/ValidationTransformer > > Jeroen > > > I checked that (probably somewhat deprecated) documentation but i noticed > something that could be usefull: > > src='validation/xhtml1-transitional.dtd'> > > > > If i find some time this week I will check if setting that 'active' parameter > to true does any good unless you beat me to it ;-) This is a different component to the Transformer that is in Cocoon SVN. -David <>
Re: Improved C3 infrastructure
On 06/30/2011 05:31 PM, Francesco Chicchiriccò wrote: On 30/06/2011 17:25, Simone Tripodi wrote: Hi all guys, we now have new terrific toys available for C3 :) * Sonar - https://analysis.apache.org/dashboard/index/org.apache.cocoon.root:cocoon-root * Nexus - https://repository.apache.org/content/repositories/snapshots/org/apache/cocoon/ * Jenkins - https://builds.apache.org/job/Cocoon-trunk/ See http://www.apache.org/dev/publishing-maven-artifacts.html for more infos how to configure your settings.xml to deploy on Nexus (the Jenkins job should do it for us). I already uploaded the beta-1-snapshot just to test it. Parent POM already updated, have fun!!! Great job, Simone, well done! +1! -- Reinhard Pötz Founder & Managing Director, Indoqa and Deepsearch http://www.indoqa.com/people/reinhard-poetz.html Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinh...@apache.org Furthermore, I think Oracle has to honor the JSPA agreement. http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
Re: Does ValidatingTransformer support DTD validation
Robby Pelssers wrote: > Hi David, > > One thing I still need to investigate was Jeroen's reply: > > Hi Robby, > > have you checked this page [1]? I'm not sure if this is the same > component, but is might lead you further. > > [1] http://wiki.apache.org/cocoon/ValidationTransformer > > Jeroen > > > I checked that (probably somewhat deprecated) documentation but i noticed > something that could be usefull: > > src='validation/xhtml1-transitional.dtd'> > > > > If i find some time this week I will check if setting that 'active' parameter > to true does any good unless you beat me to it ;-) This is a different component to the Transformer that is in Cocoon SVN. -David
AUTO: Gabriel Gruber/Workflow is out of office. (returning 18.07.2011)
I am out of the office until 18.07.2011. Ich bin bis zum 30.6.2011 auf Urlaub und ab 18.7.2011 wieder für Sie erreichbar. Bei technischen Fragen zum System Webdesk wenden Sie sich bitte vertrauensvoll an Hrn. Wurm oder Hrn. Stastny. Bei Fragen zu laufenden Projekten wenden Sie sich bitte an Hrn. Gutzelnig! mit freundlichen Grüssen Gabriel Gruber Note: This is an automated response to your message "Improved C3 infrastructure" sent on 30.06.2011 17:25:30. This is the only notification you will receive while this person is away.
[C3] Cocoon3 beta-1-SNAPSHOTs available
Hi all guys, just to let you know that Cocoon3 beta-1-SNAPSHOTs artifacts are available on ASF snapshot repository, to start playing with them you just need to add the ASF snapshot repository[1] in your pom.xml. Enjoy and have fun, feedbacks are always appreciated!!! Have a nice day, Simo [1] https://repository.apache.org/content/groups/snapshots/ http://people.apache.org/~simonetripodi/ http://www.99soft.org/
Re: Improved C3 infrastructure
On 30 June 2011 17:25, Simone Tripodi wrote: > Hi all guys, > we now have new terrific toys available for C3 :) > > * Sonar - > https://analysis.apache.org/dashboard/index/org.apache.cocoon.root:cocoon-root > * Nexus - > https://repository.apache.org/content/repositories/snapshots/org/apache/cocoon/ > * Jenkins - https://builds.apache.org/job/Cocoon-trunk/ > > See http://www.apache.org/dev/publishing-maven-artifacts.html for more > infos how to configure your settings.xml to deploy on Nexus (the > Jenkins job should do it for us). I already uploaded the > beta-1-snapshot just to test it. > > Parent POM already updated, have fun!!! > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > Well done! Trying to raise the quality percentages and lower the issues of Sonar can be addictive :) Jasha Joachimsthal Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466 US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll free) www.onehippo.com
Re: Improved C3 infrastructure
On 30/06/2011 17:25, Simone Tripodi wrote: Hi all guys, we now have new terrific toys available for C3 :) * Sonar - https://analysis.apache.org/dashboard/index/org.apache.cocoon.root:cocoon-root * Nexus - https://repository.apache.org/content/repositories/snapshots/org/apache/cocoon/ * Jenkins - https://builds.apache.org/job/Cocoon-trunk/ See http://www.apache.org/dev/publishing-maven-artifacts.html for more infos how to configure your settings.xml to deploy on Nexus (the Jenkins job should do it for us). I already uploaded the beta-1-snapshot just to test it. Parent POM already updated, have fun!!! Great job, Simone, well done! -- Francesco Chicchiriccò Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/
Improved C3 infrastructure
Hi all guys, we now have new terrific toys available for C3 :) * Sonar - https://analysis.apache.org/dashboard/index/org.apache.cocoon.root:cocoon-root * Nexus - https://repository.apache.org/content/repositories/snapshots/org/apache/cocoon/ * Jenkins - https://builds.apache.org/job/Cocoon-trunk/ See http://www.apache.org/dev/publishing-maven-artifacts.html for more infos how to configure your settings.xml to deploy on Nexus (the Jenkins job should do it for us). I already uploaded the beta-1-snapshot just to test it. Parent POM already updated, have fun!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/
Re: [C3] New blog post about Cocoon / Wicket integration
nice one, congrats! hope it will be just the first of a serie!!! :) all the best, Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ 2011/6/30 Francesco Chicchiriccò : > Hi all, > I've written a blog post [1] about the Cocoon / Wicket integration, making a > little more complex example out of the cocoon-sample-wicket-webapp. > > Please let me know what do you think. > > Cheers. > > [1] > http://chicchiricco.blogspot.com/2011/06/build-rich-xml-enabled-applications.html > > -- > Francesco Chicchiriccò > > Apache Cocoon Committer and PMC Member > http://people.apache.org/~ilgrosso/ > >
[C3] New blog post about Cocoon / Wicket integration
Hi all, I've written a blog post [1] about the Cocoon / Wicket integration, making a little more complex example out of the cocoon-sample-wicket-webapp. Please let me know what do you think. Cheers. [1] http://chicchiricco.blogspot.com/2011/06/build-rich-xml-enabled-applications.html -- Francesco Chicchiriccò Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/
RE: Does ValidatingTransformer support DTD validation
I think i finally understand what is causing the difference.
If you use the cocoon:/ protocol in your generator the Source is a
SitemapSource (and instance of XMLizable) and it will be handled differently
then if your generator would be pointing to a file.
public static void parse(SAXParser parser, Source source,
ContentHandler handler) throws SAXException, IOException, ProcessingException {
if (source instanceof XMLizable) {
toSAX((XMLizable) source, handler); //!!! for use-case
} else {
try {
parser.parse(getInputSource(source), handler); //!!! for
use-case
} catch (SourceException e) {
throw SourceUtil.handle(e);
}
}
}
Can someone shed some light on how-to resolve my need to actually parse the
source coming from calling another cocoon pipeline. This is specifically
needed for DITA (and being able to use the DITA toolkit).
Kind regards,
Robby Pelssers
-Oorspronkelijk bericht-
Van: Robby Pelssers [mailto:robby.pelss...@ciber.com]
Verzonden: do 30-6-2011 11:57
Aan: dev@cocoon.apache.org
Onderwerp: RE: Does ValidatingTransformer support DTD validation
Hi David,
One thing I still need to investigate was Jeroen's reply:
Hi Robby,
have you checked this page [1]? I'm not sure if this is the same
component, but is might lead you further.
[1] http://wiki.apache.org/cocoon/ValidationTransformer
Jeroen
I checked that (probably somewhat deprecated) documentation but i noticed
something that could be usefull:
If i find some time this week I will check if setting that 'active' parameter
to true does any good unless you beat me to it ;-)
Robby
-Oorspronkelijk bericht-
Van: David Crossley [mailto:cross...@apache.org]
Verzonden: do 30-6-2011 8:46
Aan: dev@cocoon.apache.org
Onderwerp: Re: Does ValidatingTransformer support DTD validation
David Crossley wrote:
> Robby Pelssers wrote:
> >
> > i am trying to use the validating transformer with a DTD but can't get it
> > to work.
>
> IIRC when i set this up for Apache Forrest a while back,
> then i could not get DTD validation working either.
> So we converted the DTD to RELAX NG using Trang.
>
> Some of the notes and links here might help:
> http://forrest.apache.org/howto-dev.html#debug-validation
> https://issues.apache.org/jira/browse/FOR-1172
>
> (I have been trying to investigate this for ages.
> Sorry, not much time, so i hope this much helps.)
>
> No matter what i do to configure the transformer, there are only
> three default grammar for SchemaParser instantiated
> (DEBUG messages in core.log). Two for "RELAX NG" and one for
> XML Schema, and none for DTD.
>
> Been twiddling sitemap.xmap (and forrest.xmap) and cocoon.xconf files.
>
> Trying to specify a grammar for the particular use in the
> sitemap match, then requesting the validation report gives
> "Unsupported grammar language".
>
> Not specifying a grammar, then requesting the validation report gives
> "The markup in the document preceding the root element must be well-formed"
>
> The logs show that the DTD has been resolved by the
> catalog entity resolver.
>
> There is a message for "Detecting grammar" for the DTD,
> but no resolution message for "detected for schema" like
> there is for RNG validation.
>
> Then we get the error message for "markup" as above,
> a SAXParseException.
> This line of the DTD is the first " So it is not parsing it as a DTD.
>
> Note that Forrest still uses Cocoon-2.1 but IIRC then this Validation
> block is the same.
>
> Need to look at the Cocoon Samples. Perhaps there is a reason
> that Pier did provide a DTD sample in the beginning.
Typo: did *not* provide a DTD sample
> Another thought: I wonder if this is because our "xml-parser"
> is configured in cocoon.xconf to have validate=false.
>
> -David
>
> > I already took a look at the source and found this block of code in
> > http://svn.apache.org/repos/asf/cocoon/trunk/blocks/cocoon-validation/cocoon-validation-impl/src/main/java/org/apache/cocoon/components/validation/jaxp/JaxpSchemaParser.java
> >
> > I tried
> >
> >
> > > value="http://www.w3.org/TR/REC-xml"/>
> >
> > which does not work.
> >
> > -
> > /* Detect languages or use the supplied ones */
> > Configuration languages[] =
> > conf.getChild("grammars").getChildren("grammar");
> > Set grammars = new HashSet();
> > if (languages.length > 0) {
> >
> > /* If the configuration specified (formally) a list of grammars
> > use it */
> > for (int x = 0; x < languages.length; x++) {
> > String language = languages[x].getValue();
> > if (fact.isSchemaLanguageSupported(language)) {
> > grammar
RE: Does ValidatingTransformer support DTD validation
Hi David,
One thing I still need to investigate was Jeroen's reply:
Hi Robby,
have you checked this page [1]? I'm not sure if this is the same
component, but is might lead you further.
[1] http://wiki.apache.org/cocoon/ValidationTransformer
Jeroen
I checked that (probably somewhat deprecated) documentation but i noticed
something that could be usefull:
If i find some time this week I will check if setting that 'active' parameter
to true does any good unless you beat me to it ;-)
Robby
-Oorspronkelijk bericht-
Van: David Crossley [mailto:cross...@apache.org]
Verzonden: do 30-6-2011 8:46
Aan: dev@cocoon.apache.org
Onderwerp: Re: Does ValidatingTransformer support DTD validation
David Crossley wrote:
> Robby Pelssers wrote:
> >
> > i am trying to use the validating transformer with a DTD but can't get it
> > to work.
>
> IIRC when i set this up for Apache Forrest a while back,
> then i could not get DTD validation working either.
> So we converted the DTD to RELAX NG using Trang.
>
> Some of the notes and links here might help:
> http://forrest.apache.org/howto-dev.html#debug-validation
> https://issues.apache.org/jira/browse/FOR-1172
>
> (I have been trying to investigate this for ages.
> Sorry, not much time, so i hope this much helps.)
>
> No matter what i do to configure the transformer, there are only
> three default grammar for SchemaParser instantiated
> (DEBUG messages in core.log). Two for "RELAX NG" and one for
> XML Schema, and none for DTD.
>
> Been twiddling sitemap.xmap (and forrest.xmap) and cocoon.xconf files.
>
> Trying to specify a grammar for the particular use in the
> sitemap match, then requesting the validation report gives
> "Unsupported grammar language".
>
> Not specifying a grammar, then requesting the validation report gives
> "The markup in the document preceding the root element must be well-formed"
>
> The logs show that the DTD has been resolved by the
> catalog entity resolver.
>
> There is a message for "Detecting grammar" for the DTD,
> but no resolution message for "detected for schema" like
> there is for RNG validation.
>
> Then we get the error message for "markup" as above,
> a SAXParseException.
> This line of the DTD is the first " So it is not parsing it as a DTD.
>
> Note that Forrest still uses Cocoon-2.1 but IIRC then this Validation
> block is the same.
>
> Need to look at the Cocoon Samples. Perhaps there is a reason
> that Pier did provide a DTD sample in the beginning.
Typo: did *not* provide a DTD sample
> Another thought: I wonder if this is because our "xml-parser"
> is configured in cocoon.xconf to have validate=false.
>
> -David
>
> > I already took a look at the source and found this block of code in
> > http://svn.apache.org/repos/asf/cocoon/trunk/blocks/cocoon-validation/cocoon-validation-impl/src/main/java/org/apache/cocoon/components/validation/jaxp/JaxpSchemaParser.java
> >
> > I tried
> >
> >
> > > value="http://www.w3.org/TR/REC-xml"/>
> >
> > which does not work.
> >
> > -
> > /* Detect languages or use the supplied ones */
> > Configuration languages[] =
> > conf.getChild("grammars").getChildren("grammar");
> > Set grammars = new HashSet();
> > if (languages.length > 0) {
> >
> > /* If the configuration specified (formally) a list of grammars
> > use it */
> > for (int x = 0; x < languages.length; x++) {
> > String language = languages[x].getValue();
> > if (fact.isSchemaLanguageSupported(language)) {
> > grammars.add(language);
> > continue;
> > }
> > /* If the configured language is not supported throw an
> > exception */
> > String message = "JAXP SchemaFactory \"" + this.className +
> > "\" " +
> > "does not support configured grammar " +
> > language;
> > throw new ConfigurationException(message, languages[x]);
> > }
> > } else {
> >
> > /* Attempt to detect the languages directly using the JAXP
> > factory */
> > if
> > (fact.isSchemaLanguageSupported(Validator.GRAMMAR_XML_SCHEMA)) {
> > grammars.add(Validator.GRAMMAR_XML_SCHEMA);
> > }
> > if (fact.isSchemaLanguageSupported(Validator.GRAMMAR_RELAX_NG))
> > {
> > grammars.add(Validator.GRAMMAR_RELAX_NG);
> > }
> > if (fact.isSchemaLanguageSupported(Validator.GRAMMAR_XML_DTD)) {
> > grammars.add(Validator.GRAMMAR_XML_DTD); //this equals
> > "http://www.w3.org/TR/REC-xml";
> > }
> > }
> >
> >
> > Is there a way to configure support for DTD validation as well? XML schema
> > validation seems to work out-of-
