Re: C2.0.4: Strange XSLT behaviour in logicsheet when matching text() nodes (resent)

Sylvain Wallez wrote: Ricardo Rocha wrote: So is probably a venerable fossil today. That said, "if it ain't broken..." Ah yes, I remember that, now. Gosh, the ancient times of Cocoon 1.x... Thanks for refreshing our memory, Ricardo. In fact, I was refering to the first Cocoon *2* XSP implementa

[VOTE] Release Excalibur Phase III RC 4 (with Fortress)

I think Fortress is finally Good Enough (TM) There are some issues to be sure, but they can be worked out with a Fortress 1.1 on a short release cycle. Everyone place your votes for a release on Friday (6/6). +1 from me. PS On a sick humor note, it's a pity that we aren't in 2006 yet, then the r

Re: The end of the infamous endorsed libs problem : ParanoidCocoonServletnow really paranoid

Sylvain Wallez wrote: Hi all, Short story : once again, I've hit the famous endorsed library problem. So as usual I copied Cocoon's Xalan and Xerces to tomcat/common/endorsed, but unfortunately this broke another application that was running in the same Tomcat. Damn. How to solve this ? Insta

DO NOT REPLY [Bug 20298] - [PATCH] ExtendedXLinkPipe support for multiple XLinks per element

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Unresolved bugs with patches

On Tuesday 03 June 2003 11:33, Steven Noels wrote: SN> 20185 [PATCH] TidySerializer SN> -> ongoing discussion: I'm -0 as well due to implementation choices SN> (don't expect others to come & clean up your work) Don't know if you really ment me for the last part. But to be sure: I don't think TidyS

RE: TidySerializer

Torsten Knodt wrote: > On Tuesday 03 June 2003 09:38, Bruno Dumon wrote: > >> TK> We have a current problem, that cocoon is not useable in many >> cases, TK> because it's nearly impossible to create valid (x)html. >> And again I'm wondering why? Of the tree reasons given earlier: >> AC> 1) As a fi

Re: C2.0.4: Strange XSLT behaviour in logicsheet when matching text() nodes (resent)

Ricardo Rocha wrote: Sylvain Wallez wrote: IIRC (but don't ask me why), the XSP engine wraps every text node from the XSP file into elements. In the original implementation text nodes were preprocessed and escaped as string constants in accordance to the rules of the target programming lang

Re: TidySerializer

On Tuesday 03 June 2003 09:38, Bruno Dumon wrote: BD> TK> We have a current problem, that cocoon is not useable in many cases, BD> TK> because it's nearly impossible to create valid (x)html. BD> And again I'm wondering why? Of the tree reasons given earlier: BD> AC> 1) As a fix for the "the namesp

The end of the infamous endorsed libs problem : ParanoidCocoonServletnow really paranoid

Hi all, Short story : once again, I've hit the famous endorsed library problem. So as usual I copied Cocoon's Xalan and Xerces to tomcat/common/endorsed, but unfortunately this broke another application that was running in the same Tomcat. Damn. How to solve this ? Install another Tomcat ? Yea

cvs commit: cocoon-2.1 status.xml

sylvain 2003/06/03 06:28:26 Modified:.status.xml Log: ParanoidCocoonServlet is now really paranoid Revision ChangesPath 1.50 +5 -0 cocoon-2.1/status.xml Index: status.xml === RCS fi

cvs commit: cocoon-2.1/src/java/org/apache/cocoon/servlet BootstrapServlet.java CocoonServlet.java ParanoidClassLoader.java ParanoidCocoonServlet.java

sylvain 2003/06/03 06:25:43 Modified:src/java/org/apache/cocoon/servlet BootstrapServlet.java CocoonServlet.java ParanoidClassLoader.java ParanoidCocoonServlet.java Log: ParanoidCocoonServlet is now really paranoid Revision Change

Re: C2.0.4: Strange XSLT behaviour in logicsheet when matching text() nodes (resent)

Sylvain Wallez wrote: IIRC (but don't ask me why), the XSP engine wraps every text node from the XSP file into elements. In the original implementation text nodes were preprocessed and escaped as string constants in accordance to the rules of the target programming language. This took place prior

DO NOT REPLY [Bug 20446] New: - using get-string for an oracle output parameter

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [CLI] Breaking CocoonBean Interface

Vadim, ... > >> dest="build/dest/"/> > src="index.html" > >dest="build/dest/docs.html"/> > >>dest="zip://*.zip/page.html"/> > > It took me some time to understand meaning of "append", "replace", > "insert". Can we choose some other names for this, and/or combine > append and replace

DO NOT REPLY [Bug 20445] New: - i18n transformer does not recognize 2.0 namespace

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: C2.0.4: Strange XSLT behaviour in logicsheet when matching text() nodes (resent)

Thanks Sylvain, that worked. I see that this observation makes sense, considering that the core-logicsheet is processed first. Cheers /A > -Original Message- > From: Sylvain Wallez [mailto:[EMAIL PROTECTED] > Sent: Tuesday 03 June 2003 14:32 > To: [EMAIL PROTECTED] > Subject: Re: C2.0.4:

DO NOT REPLY [Bug 20443] - util:include-expr does not work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Unresolved bugs with patches

Antonio Gallardo wrote: Steven Noels dijo: If people need food for discussion, here's my utterly uninformed and out-of-the-head opinion on these patches: 13070 [PATCH] Add a new tag to XSP -> ditto by Vadim & Christian -> no reply I think the ball is not in my side. :) Christian committ

Re: C2.0.4: Strange XSLT behaviour in logicsheet when matching text() nodes (resent)

Geissel, Adrian wrote: Silly mail client! Hi all, I building an XSP Java logicsheet, and use the following constructs: this.contentHandler.startElement( "", "", "", xspAttr);

C2.0.4: Strange XSLT behaviour in logicsheet when matching text() nodes (resent)

Silly mail client! > Hi all, > > I building an XSP Java logicsheet, and use the following constructs: > > > > > this.contentHandler.startElement( > "", > "", > "", > xsp

Re: [CLI] Breaking CocoonBean Interface

Upayavira wrote: Dear All, ... The changes include: 1) Improved broken link handling 2) Replaced Destination interface with ModifiableSources ... It took me some time to understand meaning of "append", "replace", "insert". Can we choose some other names for this, and/or combine

Strange XSLT behaviour in logicsheet when matching text() nodes

Hi all, I building an XSP Java logicsheet, and use the following constructs: this.contentHandler.startElement( "", "", "", xspAttr); xspAttr.clear();

RE: Cocoon developers on the east coast of the US

Hi I've done some cocoon. If you have an interesting project for remote development, I'd consider. my home page is at members.cox.net/akuketayev I also know other cocoon folks in DC metro area. Argyn > -Original Message- > From: Michael Wechner [mailto:[EMAIL PROTECTED] > Sent: Monday,

Re: Unresolved bugs with patches

Steven Noels dijo: > If people need food for discussion, here's my utterly uninformed and > out-of-the-head opinion on these patches: > > 13070 [PATCH] Add a new tag to XSP > > -> ditto by Vadim & Christian -> no reply I think the ball is not in my side. :) Christian committed this patch, but Va

Re: AntBuildGenerator (was: Unresolved bugs with patches)

Le Mardi, 3 juin 2003, à 12:05 Europe/Zurich, Carsten Ziegeler a écrit : ...On the other hand we could apply such contributions simply in the scratchpad. Makes sense, in this way they won't be forgotten but it is clear that they're not part of the Cocoon core. -Bertrand

RE: AntBuildGenerator (was: Unresolved bugs with patches)

Bertrand Delacretaz wrote: > > Le Mardi, 3 juin 2003, à 11:33 Europe/Zurich, Steven Noels a écrit : > > > ...20138 [PATCH] AntBuildGenerator > > > > -> Bertrand? (I'm -0 on adding such hacks onto Cocoon, but anyhow)... > > Dunno about hacks - an AntBuildGenerator block certainly triggers some > FS

DO NOT REPLY [Bug 20271] - General background task manager leveraging Avalon

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: bug handling guideline (Re: Unresolved bugs with patches)

On 3/06/2003 11:10 Andreas Kuckartz wrote: I'm not against such a guideline and it might help in this case. So +1. But even with such a guideline, you can't force committers to do the work listed in the guideline. Correct, but it helps to guide them :-) The best way to provide guidance is by le

DO NOT REPLY [Bug 17063] - [PATCH] XSP Request docs, demo out of sync with logicsheet

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

AntBuildGenerator (was: Unresolved bugs with patches)

Le Mardi, 3 juin 2003, à 11:33 Europe/Zurich, Steven Noels a écrit : ...20138 [PATCH] AntBuildGenerator -> Bertrand? (I'm -0 on adding such hacks onto Cocoon, but anyhow)... Dunno about hacks - an AntBuildGenerator block certainly triggers some FS alarms here, but doesn't cause much harm as it c

DO NOT REPLY [Bug 15005] - [PATCH] Extension to sendmail.xsp: lists for sendmail:cc

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 13070] - [PATCH] Add a new tag to XSP

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 12993] - [PATCH] New version of CastorTransformer (includes marshalling)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Unresolved bugs with patches

On 3/06/2003 8:57 Carsten Ziegeler wrote: My point is, sending every three days an email to the list, saying "there are too many open patches/bugs" doesn't really help or motivate. Exactly. When I read these mails, I always end up with this vision of people trying to 'corporatize' open source pro

RE: TidySerializer

AC> > Bruno? BD> You expect me to give my blessing or so? I don't really care that much BD> about it all. Arguments 2 and 3 are reasonable, and certainly BD> have their uses. You dropped the question (and I had my doubts too), so I tried to sum up the pro's and asked for your opinion. Blessing s

Re: bug handling guideline (Re: Unresolved bugs with patches)

> I'm not against such a guideline and it might help in this case. So +1. > > But even with such a guideline, you can't force committers to do the > work listed in the guideline. Correct, but it helps to guide them :-) I will try to find a suitable text which can be adapted. Andreas

RE: bug handling guideline (Re: Unresolved bugs with patches)

Andreas Kuckartz wrote: > > > But what about a bug handling guideline? > > Is there something similar for the Apache community in general? > > This is what I think is needed - and can be a result of this thread. > I'm not against such a guideline and it might help in this case. So +1. But even

Re: Caching in cocoon, especially CIncludeTransformer

Carsten Ziegeler wrote: Sylvain Wallez wrote: I don't know if this should be an independent component, or one that extends the SourceResolver. Ah ok, by independent component I meant a component that extends perhaps the SourceResolver component from Avalon, but can still be looked up usi

bug handling guideline (Re: Unresolved bugs with patches)

> We have at the moment 4 blockers: > http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=Blocker&product=Cocoon+2&order=Bug+Number > > 1. Vadim, 2002-09-21: "Blocking 2.1 release" > 2. Berin, 2002-07-11 (bug reporter) > 3. 2002-11-07, u

DO NOT REPLY [Bug 20443] New: - util:include-expr does not work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Unresolved bugs with patches

I think this is plain simple - as long as noone of the committers has time for it and has fun in doing so, nothing will happen. This is open source development and this means, things are not done because someone "forces" you to do them. Work is done because someone has fun in doing so. I don't want

RE: Caching in cocoon, especially CIncludeTransformer

Sylvain Wallez wrote: > > I don't know if this should be an independent component, or one that > extends the SourceResolver. Ah ok, by independent component I meant a component that extends perhaps the SourceResolver component from Avalon, but can still be looked up using a component manager. So

cvs commit: cocoon-2.0 changes.xml

bruno 2003/06/03 00:53:31 Modified:.changes.xml Log: mention fixing of bug 14327 Revision ChangesPath 1.17 +6 -1 cocoon-2.0/changes.xml Index: changes.xml === RCS file: /home/cvs/

cvs commit: cocoon-2.1 status.xml

bruno 2003/06/03 00:50:34 Modified:.status.xml Log: mention fixing of bug 14327 Revision ChangesPath 1.49 +5 -0 cocoon-2.1/status.xml Index: status.xml === RCS file: /home/cvs/coc

DO NOT REPLY [Bug 15843] - EmptyStackException in EnvironmentStack

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: TidySerializer

On Mon, 2003-06-02 at 17:57, Torsten Knodt wrote: > > When TidySerializer would be in cocoon, more people would try it. And perhaps > there will be someone who cleans it up and adds SAX and DOM support. That's right. > Also > perhaps someone integrates it into xalan. > And for the namespace p

Re: Caching in cocoon, especially CIncludeTransformer

Carsten Ziegeler wrote: Sylvain Wallez wrote: I don't like all those static methods that hardcode more and more logic, and even less when they lookup some components... Why aren't these methods part of a CocoonResolver component that would extend Excalibur's SourceResolver with some XML-rela

RE: Unresolved bugs with patches

Antonio Gallardo wrote: > > > Le Mardi, 3 juin 2003, à 08:06 Europe/Zurich, Carsten Ziegeler a écrit : > >> ...I think this is plain simple - as long as noone of the committers > >> has time for it and has fun in doing so, nothing will happen > Hi: > > but we also must think in users that use h

cvs commit: cocoon-2.1/src/deprecated/java/org/apache/cocoon/components/source/impl AvalonToCocoonSourceInvocationHandler.java

cziegeler2003/06/03 00:29:19 Modified:.status.xml src/java/org/apache/cocoon/environment AbstractEnvironment.java Added: src/deprecated/java/org/apache/cocoon/components/source/impl AvalonToCocoonSourceInvocat

DO NOT REPLY [Bug 11533] - [PATCH] Replacement for AvalonToCocoonSource

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 11962] - DigesterTransformer donation

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 11962] - DigesterTransformer donation

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 11533] - [PATCH] Replacement for AvalonToCocoonSource

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 11533] - [PATCH] Replacement for AvalonToCocoonSource

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 12158] - some improvements to Main.java

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 16018] - Incomplete transfer of page to users using squid.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Unresolved bugs with patches

> Le Mardi, 3 juin 2003, à 08:06 Europe/Zurich, Carsten Ziegeler a écrit : >> ...I think this is plain simple - as long as noone of the committers >> has time for it and has fun in doing so, nothing will happen Hi: but we also must think in users that use his time to fill a bugzilla report. Th

RE: Unresolved bugs with patches

Bertrand Delacretaz wrote: > > Le Mardi, 3 juin 2003, à 08:06 Europe/Zurich, Carsten Ziegeler a écrit : > > ...I think this is plain simple - as long as noone of the committers > > has > > time for it and has fun in doing so, nothing will happen > > Yes, but I think Joerg has a point too: more

Re: Unresolved bugs with patches

Le Mardi, 3 juin 2003, à 08:06 Europe/Zurich, Carsten Ziegeler a écrit : ...I think this is plain simple - as long as noone of the committers has time for it and has fun in doing so, nothing will happen Yes, but I think Joerg has a point too: more comments on bugzilla could help people under

RE: Caching in cocoon, especially CIncludeTransformer

Sylvain Wallez wrote: > > I don't like all those static methods that hardcode more and more logic, > and even less when they lookup some components... > > Why aren't these methods part of a CocoonResolver component that would > extend Excalibur's SourceResolver with some XML-related features ?

RE: Unresolved bugs with patches

Joerg Heinicke wrote: > > But it's obvious we have a more or less bad bug handling. Most of the > bugs are not even ASSIGNED, so nobody can really see if it's only a bug > report of a user or a confirmed bug. Why don't we accept or reject a bug > within a month at the latest. > And the patches?

Re: Cocoon developers on the east coast of the US

Hi Michael. I've been involved with cocoon for some time now. I'm in Central Jersey and I'm involved in the creation of cocoon application for my company. A demo is available at my web site. Let me know what type of exciting projects you are embarking on. Thanks -Yatin Michael Wechner wrote: Hel

Re: Application

attachment did not come thru. sorry, kcook >>> <[EMAIL PROTECTED]> 06/02/03 05:11PM >>> Please see the attached file.

Cocoon developers on the east coast of the US

Hello all I am looking for Cocoon developers on the east coast of the US (preferably Boston/Cambridge and NYC). If you are interested to work on an exciting project (which probably everyone would say , please contact me off the list. Thanks Michael

Re: Unresolved bugs with patches

I fail to see how ownership by a person would help in applying patches more consistently. Having a 'sponsoring committer' might help to get patches applied. Then again, I think you are looking at the symptom, not the cause. The fact no sponsoring committers exist for certain patches might tell

Re: dbxml

Steven, On Monday, June 2, 2003, at 11:27 AM, Steven Noels wrote: Looking at your enquiries, I believe we should be better informed about what exactly you want us to add to Cocoon CVS. I've been asked be a few dbxml users about integration with Cocoon. I've never actually used it myself, so I'm

Re: Unresolved bugs with patches

> The fact no sponsoring committers exist for certain > patches might tell more about the patch than the willingness of the > committers. That certainly is true for some of the patches. In my opinion it does make makes sense if committers enter a comment if they visit a patch and decide not to use

DO NOT REPLY [Bug 14144] - [Patch] add CompressionFilter declaration to web.xml

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Unresolved bugs with patches

On 2/06/2003 20:46 Andreas Kuckartz wrote: Here is a list of the 31 unresolved bugs for which patches have been created. Only one bug is "owned" by a person. The others are owned by the developers list. I fail to see how ownership by a person would help in applying patches more consistently. Havi

Unresolved bugs with patches

Here is a list of the 31 unresolved bugs for which patches have been created. Only one bug is "owned" by a person. The others are owned by the developers list. Andreas --- 6879 [PATCH] Cache improvement using ESI invalidation protocol 9728 [PATCH] CocoonServlet getClassPath() enhancements Tomcat4

Re: dbxml

On 2/06/2003 18:57 John Merrells wrote: Good. Who has the final word on this though? Is it the Cocoon PMC? Or is there an Apache PMC...? We (the Cocoon PMC) make sure to properly check copyright and licensing issues before committing anything to our code base. Looking at your enquiries, I believ

Re: dbxml

On Friday, May 30, 2003, at 06:07 PM, Vadim Gritsenko wrote: It's called XML:DB API, by http://xmldb.org/ Ah, OK. Yes I know about XML:DB. I looked at it but it wasn't suitable for dbxml. You could easily implement XML:DB on top of the dbxml API. Huh? As I read this (http://sleepycat.com/download

Re: TidySerializer

On Monday 02 June 2003 17:38, Bruno Dumon wrote: BD> What I wanted to avoid though is that problems with the normal HTML BD> serializer (like the namespace or textarea problem) would be hidden by BD> jtidy, and that users would be pointed to the tidyserializer as the BD> solution for these problems

Re: TidySerializer

On Monday 02 June 2003 17:05, Arjé Cahn wrote: AC> When should one use the TidySerializer? AC> --- AC> 1) As a fix for the "the namespace problem" AC> 2) When human-readable HTML output is needed AC> 3) To validate the output to a dtd It doesn't really validate

DO NOT REPLY [Bug 15302] - XSPUtil.relativeFilename() throws NPE

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 15302] - XSPUtil.relativeFilename() throws NPE

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: TidySerializer

On Mon, 2003-06-02 at 17:05, Arjé Cahn wrote: > I'm using the TidyUI standalone from the Tidy sourceforge community > (http://tidy.sourceforge.net/), which is very good, but the JTidy port has been > abandoned - how awfull! > > But "the namespace problem" - that was one of my reasons, too. > >

RE: TidySerializer

I'm using the TidyUI standalone from the Tidy sourceforge community (http://tidy.sourceforge.net/), which is very good, but the JTidy port has been abandoned - how awfull! But "the namespace problem" - that was one of my reasons, too. When should one use the TidySerializer?