You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <vg...@hns.com> on 2000/08/28 15:19:18 UTC
[C2] RE: Broken examples?
About DirectoryGenerator - simply comment out one line of code:
// protected EntityResolver resolver;
and it will work. SQL example works (partially) - for me, but XSP example -
does not.
There is some problem with namespaces. If in simple-sql2html.xsl replace
<xsl:template match="sql:ROWSET">
with
<xsl:template match="ROWSET">
and so on - everything will work.
Does anybody knows what is wrong with namespaces?
Vadim
> -----Original Message-----
> From: Tom Klaasen [mailto:Tom.Klaasen@the-ecorp.com]
> Sent: Monday, August 28, 2000 7:48 AM
> To: 'cocoon-dev@xml.apache.org'
> Subject: RE: Broken examples?
>
>
> You're right, sorry I forgot to mention this.
>
> It is C2 I'm talking about.
>
> tomK
>
> > -----Original Message-----
> > From: Giacomo Pati [mailto:pati_giacomo@yahoo.com]
> > Sent: maandag 28 augustus 2000 12:37
> > To: cocoon-dev@xml.apache.org
> > Subject: Re: Broken examples?
> >
> >
> > --- Tom Klaasen <To...@the-ecorp.com> wrote:
> > > Has anybody noticed that the SQL page example, as well as the
> > > directory
> > > listing, are broke in the CVS version?
> >
> > Are you taking about C1 or C2?
> >
> > Giacomo
> >
> > =====
> > --
> > PWR GmbH, Organisation & Entwicklung Tel: +41 (0)1 856 2202
> > Giacomo Pati, CTO/CEO Fax: +41 (0)1 856 2201
> > Hintereichenstrasse 7 Mailto:Giacomo.Pati@pwr.ch
> > CH-8166 Niederweningen Web: http://www.pwr.ch
Re: C2: Integration of new Avalon?
Posted by Berin Loritsch <bl...@infoplanning.com>.
Carsten Ziegeler wrote:
>
> Hello,
>
> are there any plans when to include a newer version of Avalon?
> I looked at the current state of Avalon and saw that some Interfaces (e.f. the Configuration interface) have changed.
> When will these changes reflected by Cocoon2 ? Do you wait until the next Avalon Distribution is released?
That remains to be seen. We have to wait for the official release.
Configuration is still a moving target within Avalon, so it may be that we
wait for the release after this Clean-Up milestone. (my suggestion)
Re: C2: Integration of new Avalon?
Posted by "Pier P. Fumagalli" <pi...@apache.org>.
donaldp@mad.scientist.com wrote:
>
> Hopefully (if all goes according to plan) there should be an
> Avalon milestone release at end of next week sometime (So in
> about 10 days). It may be best to hold off til at least then
> :P
[offtopic on the Cocoon-DEV mailing list]
Ok... If we at least could stop fighting about the *GOOD* (IMVHO!) idea
of including JNDI in the Avalon kernel, we could have a release even
earlier... :)
Pier :) :)
Re: C2: Integration of new Avalon?
Posted by do...@mad.scientist.com.
On Mon, 28 Aug 2000, Carsten Ziegeler wrote:
> are there any plans when to include a newer version of Avalon?
> I looked at the current state of Avalon and saw that some
Interfaces (e.f. the Configuration interface) have changed.
Configuration changes in Avalon was a experiment with
different approach. The approach failed and the
Configuration interface will be returning to a similar state
to what is currently in Cocoon :P.
> When will these changes reflected by Cocoon2 ? Do you wait
> until the next Avalon Distribution is released?
Hopefully (if all goes according to plan) there should be an
Avalon milestone release at end of next week sometime (So in
about 10 days). It may be best to hold off til at least then
:P
--
Cheers,
Pete
*--------------------------------------------------*
| Latrobe University, | Does the name 'Pavlov' |
| Bundoora, Australia | ring a bell ? |
*--------------------------------------------------*
C2: Integration of new Avalon?
Posted by Carsten Ziegeler <cz...@sundn.de>.
Hello,
are there any plans when to include a newer version of Avalon?
I looked at the current state of Avalon and saw that some Interfaces (e.f. the Configuration interface) have changed.
When will these changes reflected by Cocoon2 ? Do you wait until the next Avalon Distribution is released?
Regards
Carsten Ziegeler
Open Source Group sunShine - Lighting up e:Business
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto:cziegeler@sundn.de
================================================================
C2: Type in CocoonServlet.java
Posted by Carsten Ziegeler <cz...@sundn.de>.
I found a typo in org.apache.cocoon.servlet.CocoonServlet.java:
Index: CocoonServlet.java
===================================================================
RCS file: S:\S_UND_N\sunShine\cvsroot/cocoon/src/org/apache/cocoon/servlet/CocoonServlet.java,v
retrieving revision 1.7
diff -r1.7 CocoonServlet.java
59c59
< this.context.log("this.configurationFile: " + this.configurationFile);
---
> this.context.log("this.configurationFile: " + configFile);
Regards
Carsten Ziegeler
Open Source Group sunShine - Lighting up e:Business
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto:cziegeler@sundn.de
================================================================
AW: [C2] RE: Broken examples?
Posted by Carsten Ziegeler <cz...@sundn.de>.
> There is some problem with namespaces. If in simple-sql2html.xsl replace
> <xsl:template match="sql:ROWSET">
> with
> <xsl:template match="ROWSET">
> and so on - everything will work.
>
> Does anybody knows what is wrong with namespaces?
>
In my opinion it is Xerces, who generates wrong SAX-Events. We have big trouble to write transformers which use own namespaces as they always get wrong endElement-events.
I posted a note to this some days ago. For a complete answer here his an excerpt of it:
<<<SNIP>>>
Using the following simple XML-File, Xerces generates wrong endElement()-Events:
<?xml version="1.0"?>
<html xmlns:sql="http://xml.apache.org/cocoon/SQL">
<head>
</head>
<body>
<sql:execute-query>
<sql:query>
select * from user
</sql:query>
</sql:execute-query>
</body>
</html>
In version 1.1.3 of Xerves the SQLTransformer receives an endElement() event with uri="http://xml.apache.org/cocoon/SQL", name="body" and raw="body".
In this case the uri is wrong. The SQLTransformer now gets his namespace and then assumes body is the value element.
<<<END SNIP>>>
As far as I can see, Xerces 1.1.3 always generates this wrong endElement if the element in question (here: body) has the default namespace and the element before had another namespace.
Meanwhile somebody (sorry, I lost your mail) has informed the Xerces developer team, so they should be aware of it.
The current solution (= workaround) is to check the "raw"-attribute of the endElement event. If it has no prefix, then we assume that the uri-attribute must be null. We know that this is not absolutely correct, but it works for us very well. It might be that the problem with your stylesheet is implied by this Xerces-bug.
It might be that the current developer release of Xerces has fixed this bug. I had no time to check this. And the mailinglists are still down.
HTH
Regards
Carsten Ziegeler
Open Source Group sunShine - Lighting up e:Business
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto:cziegeler@sundn.de
================================================================