Re: AW: weird build problem - seems to be dependent on jar name

+0200 From: Carsten Ziegeler [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] What was the original name of your jar file and which classes (packages) did it contain (any sax or dom package?) Carsten -Ursprüngliche Nachricht- Von: David Crossley [mailto:[EMAIL

RE: weird build problem - seems to be dependent on jar name

Woops, yes the catalog.jar did contain some partial SAX classes. I blindly assumed that the jar only contained the catalog classes. When i remove the sax.* and re-pack the jar, then all is fixed. Sorry and thanks to all, David Crossley

proposal: entity resolution capability

it. This capability adds phenomenal power to an already phenomenal system. cheers, David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

AW: [patch] contrib.xml - new sections CVS overview and dev procedure

Thanks Carsten, i did cvs update of our local repository and all is well. David Carsten wrote: Thanks David for your work. I applied your patch - please cross check. Carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For

how to determine runtime location of resources directory

I have one coding issue that is holding up our Cocoon development work. Help please. What is the Java code to determine the full pathname to the runtime location of the resources directory: webapps/cocoon/resources/ Surely there would be an easy way to do this, but even after tearing out my

[PROPOSAL] xdocs/faq.xml needs split into topic-based FAQs

pages that should be added as placeholders? * Building and Installing * Configuration * Starting and Runtime * Samples * Sitemap * XML Content * Contributing * Other Issues I am not offering to be FAQ manager. However, i can do the document re-structuring. regards, David Crossley

Re: [Docs] General Planning

that we can export the content in a structured way to take to a future Cocoon-based application. cheers, David Crossley Ovidiu Predescu continued: Should we try to use one of the Web FAQ tools out there? I especially like the way the PHP documentation is setup (see for example http://www.php.net

Re: [Docs] General Planning

Perhaps the DocBook subset would be appropriate. www.oasis-open.org/docbook/ follow the link to A Simplified DocBook subset. regards, David Crossley Ovidiu Predescu said: Berin Loritsch said: I propose that for new documentation we use DocBook format. You will see examples in Avalon CVS

Re: proposal: entity resolution capability

Davanum Srinivas said: David, Looking forward to your sample catalog demo, docs etc. Please let us know if you run into trouble. Once you are done, please post a zip file that contains. - Any new files with suggested directory structure. - Run cvs diff -u from the main directory and add the

Re: [GUMP] Build Failure - Cocoon2

Sam, that is resolver.jar rather than catalog.jar On Tue, 21 Aug 2001, Dims wrote: Sam, We are using catalog.jar from http://www.sun.com/xml/developers/resolver/ for resolving Entities. This is checked into xml-cocoon\lib directory. Thanks, dims --- Sam Ruby [EMAIL PROTECTED] wrote:

[patch] entity catalogs - xdocs and samples

, and diffs for docs/samples/samples.xml, xdocs/*-book.xml, and webapp/sitemap.xmap regards, David Crossley catalog-bits.tar.gz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

Re: [patch] entity catalogs - xdocs and samples

entities, an example CatalogManager.properties, and diffs for docs/samples/samples.xml, xdocs/*-book.xml, and webapp/sitemap.xmap regards, David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email

[patch] entity catalogs - xdocs/catalog.xml

:07:36 @@ -7,7 +7,7 @@ titleEntity resolution with catalogs/title subtitleResolve entities to local or other resources/subtitle !-- ??? what use is subtitle - it is not displayed -- - version0.6/version + version1.1/version typeTechnical document/type authors person name=David

[patch] entity catalogs - CatalogManager.properties

The attached patch will update the CatalogManager.properties file to provide better internal documentation. It also sets the verbosity level back to 1. I do not think that it is a good idea to have the default verbosity level at the maximum setting, as this will probably just confuse new users.

Re: [patch] entity catalogs - xdocs and samples

. What's wrong? Do you need to setup something or it'll be fixed? Regards, Konstantin Piroumian - Original Message - From: David Crossley To: [EMAIL PROTECTED] Sent: Thursday, August 30, 2001 3:41 PM Subject: Re: [patch] entity catalogs - xdocs and samples Yes Dims, all

entity catalogs - success/failure reports please

Professional, Tomcat 3.2.1 - pathname problems with interpreting directory separator --- thanks, David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

Re: entity catalogs - success/failure reports please

Oops! Sorry for previous posting. I didn't see that I had to configure anything else. Konstantin - Original Message - From: David Crossley [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 31, 2001 7:34 PM Subject: entity catalogs - success/failure reports please

[patch] xdocs/samples.xml

This patch adds a proper description of the Entity Catalogs demo and removes the temporary warning about configuring the properties file. Index: samples.xml === RCS file: /home/cvspublic/xml-cocoon2/webapp/docs/samples/samples.xml,v

[Patch] catalogs - properties and xdocs

needs - show example local configuration for Simplified DocBook and full DocBook DTDs - list of platforms with reports of successful usage regards, David Crossley Index: CatalogManager.properties === RCS file: /home/cvspublic/xml

entity catalogs support - finalisation

Does the entity resolver start correctly for everybody? At the default verbosity level, you should see resolver messages going to standard output. It would be good to finalise it so that we can add it to the C2.0 release. The only thing that i can see holding it up, is a success report from a

Re: entity catalogs support - finalisation

Giacomo wrote: Quoting David Crossley [EMAIL PROTECTED]: Does the entity resolver start correctly for everybody? At the default verbosity level, you should see resolver messages going to standard output. No! It is one of the samples I mentioned not working correctly as well

Re: entity catalogs support - finalisation

Hi Jeremy, i would guess that you have the same problem as did Konstantin. That is the expected error message when the entity resolver has no mapping for the requested entity. The entity resolver probably did not configure itself because it could not find the properties file at Cocoon startup.

Re: AW: entity catalogs support - finalisation

Hi Carsten, you should not need to set the catalogs property manually. It should be automatically set by the build process to be full pathname to webapps/cocoon/resources/entities/catalog Did you use build -Dinstall.war=$TOMCAT_HOME/webapps regards, David Date: Tue, 4 Sep 2001 17:48:49 +0200

Re: AW: entity catalogs support - finalisation

Thanks Vadim, i was just writing the same email to Jeremy. However, are you sure that build clean is needed. I just do the one-line build command that you have shown and all is well. David Vadim wrote: Jeremy, Do not combine these tasks! And, do not do install if you ever used build.sh

C2 entity catalogs - parseCatalog() to load default catalog

Hi Dims, it seems that there is too much variability in the build process. It appears that we may not be able to rely on them using the build option -Dinstall.war=$TOMCAT_HOME/webapps I am sure that there would be a way to load the default catalog via our Cocoon classes at

Re: Fwd: Re: C2 entity catalogs - parseCatalog() to load default catalog

for a start. many thanks, David Dims wrote: David, Added some code in ResolverImpl to load the default catalog programatically using the parseCatalog function that you rightly pointed out. Please take a look and see in what direction you want this to go next. Thanks, dims --- David Crossley [EMAIL

[patch] CatalogManager.properties

This patch sets a dummy path for the catalogs property. We leave it free for their local configuration use, now that the default catalog is auto-loaded. David Index: CatalogManager.properties === RCS file:

[Patch] xdocs/catalog.xml

document/type authors person name=David Crossley email=[EMAIL PROTECTED]/ @@ -16,20 +17,34 @@ body s1 title=Introduction p - @docname@ has the capability to utilise an entity resolution mechanism. This - assists with entity management and also reduces the necessity for expensive

[Patch] xdocs/jars.xml - add resolver.jar

This patch adds an entry to the Jars table for the Sun resolver.jar XML Entity and URI Resolvers. I am not sure of the answer for the table column Required by Core - so said yes. regards, David Index: jars.xml === RCS file:

links between samples and xdocs

The Entity catalogs documentation has a direct link to the catalog Cocoon sample. Likewise, there is also a link from the sample demo back to its documentation. With careful sitemap entries, i can get both links to work (and they do work in the current CVS). However, i am concerned that when the

Re: links between samples and xdocs

Konstantin Piroumian wrote: David Crossley wrote: The Entity catalogs documentation has a direct link to the catalog Cocoon sample. Likewise, there is also a link from the sample demo back to its documentation. With careful sitemap entries, i can get both links to work (and they do work

[Patch] changes.xml - entry for entity catalogs

Hi Dims, this patch adds an entry to Changes doc for the entity resolver. cheers, David Index: changes.xml === RCS file: /home/cvspublic/xml-cocoon2/changes.xml,v retrieving revision 1.30 diff -u -r1.30 changes.xml --- changes.xml

[Patch] xdocs/overview.xml - add section for Samples

The attached patch adds a section to the Overview document to say that the samples are available with the distribution and shows how to use the samples to learn behind-the-scenes. It also tweaks a couple sentences in the existing sections, to better explain. David Crossley Index: overview.xml

[Patch] xdocs/contrib.xml

The attached patch enhances the explanations of contribution methods and adds a couple more tips. David Crossley Index: contrib.xml === RCS file: /home/cvspublic/xml-cocoon2/xdocs/contrib.xml,v retrieving revision 1.6 diff -u -r1.6

entity catalogs: XercesParser.java needs mods too

Hi Dims, as far as i can tell, there is a need to effect the same modifications to XercesParser.java as you did to JaxpParser.java to set the entity catalog resolver for the parser. As you know, cocoon.xconf provides the capability to activate the XercesParser instead of the default JaxpParser.

startup exception when XercesParser instead of JaxpParser

relevant? (I am actually starting to eradicate [Bug 3595] New: - Entity catalogs - XercesParser.java needs setEntityResolver However, this happened before beginning any code modifications.) Help please. regards, David Crossley -- 2001-09-19 05:14:59 - ContextManager: Adding

Re: startup exception when XercesParser instead of JaxpParser

and let us know. Also the log file will most likely show the location from where xerces jar was picked up so check that too. Thanks, dims --- David Crossley [EMAIL PROTECTED] wrote: I followed the instructions in 2.1-dev webapp/cocoon.xconf to activate the XercesParser instead

AW: ensure uniform xdocs/*.xml

Giacomo Pati wrote: Stefano Mazzocchi wrote: Carsten Ziegeler wrote: David Crossley wrote: There are some aspects of the document set that need attention - uniform XML declarations and Document Type Declarations. When these two issues are resolved, then i will create

[Patch] Entity catalogs - XercesParser.java needs setEntityResolver

I posted this patch directly to Bugzilla last week. However, it has not yet been applied. So i will post it here too. This will fix bug 3595 Entity catalogs - XercesParser.java needs setEntityResolver - applies the same changes as recently done for JaxpParser.java to setEntityResolver David

Re: AW: [Patch] Entity catalogs - XercesParser.java needs setEntityResolver

please verify if the cocoon_20_branch is working correctly? I downloaded the Cocoon-2.0rc1a.tar.gz and the entity catalogs sample demo works as expected. cheers, David Carsten -Ursprüngliche Nachricht- Von: David Crossley [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 24. September

Re: Unhappy with CatalogManager.properties

for raising this issue. We were trying to get the basic entity resolution support in first - that is now done. So it is time to attend to some other issues like yours. I am not familiar with the ramifications of running multiple cocoon apps - cocoon-dev list will help to sort it out. David Crossley Date

Re: Catalogs don't work on XSLT stylesheets

at the XSLT level. By the time that the XML stream gets to the stylesheet, then all entities have already been resolved. I would expect that you would need to declare all necessary entities from the document type declaration of your XML instance document. regards, David Crossley Date: 1 Oct 2001 10:55

entity resolution for Documentation build - almost

I have started adding to the newdocs target of build.xml to copy the entities and system catalog to the build space. This does work and the entity resolver swings into action. However, i get a strange failure when i declare an external entity in my xdocs. The only difference that i can spot is

C2 build problem, possibly with image generation

I have just had an horrific build problem that i would like to share with you. It happens every time that i try to build docs ... other builds are OK. Notably build printer-docs is OK, and this makes me wonder if it is to do with the generation of the side-bar images. Also, i successfully ran

Re: AW: [Patch] entity catalogs: accept parameters from xconf

Carsten wrote: Thanks David for the patch! Your patch is applied to the 2.1 cvs - please crosscheck. Great. Yes that works properly. However, it should be applied to 2.0 as well. thanks, David Carsten -Ursprüngliche Nachricht- Von: David Crossley [mailto:[EMAIL PROTECTED

new Bug 4221 is nothing to do with resolver

Hello Henric, i have reviewed your logfiles that you submitted to Bugzilla. You have not interpreted your logfiles correctly - this issue has nothing to do with resolver. My interpretation of your error is that Cocoon could not find your cocoon.xconf file ... -- cocoon.log at line 139 ...

Re: [Vote]: Ovidiu Predescu as new committer

A stack of support already. I would like to express my gratitude for the excellent work of Ovidiu and colleagues. Certainly +1 from me. David Dims wrote: Hi Team, I would like to propose Ovidiu Predescu [[EMAIL PROTECTED]] as a new committer for Apache Cocoon 2. His contributions have

Re: entity resolution for Documentation build - almost

] David, I added your test case to the CVS HEAD for making testing much easier for all of us. Yes, I did follow the process and retried it today again. Using Windows2K and SUN JDK 1.2.2 it works. Carsten David Crossley wrote: Would someone on each platform please try the following

new committer having trouble with cvs commit

I still have not been able to do my first commit. Hopefully someone has struck this same situation and can help - i get more frustrated every minute. Brian has set up my account, and i am registered in the avail file. I can do ssh2 cvs.apache.org OK and have checked my permissions and UNIX

Re: new committer having trouble with cvs commit

Thanks Sam, it works now. Interestingly, the relevant line in avail has the exact same content as what Brian confirmed via email some days ago. Anyway now i can. so thanks again, David Sam Ruby wrote: David Crossley wrote: However, here is what happens when i try to commit a test change

Re: new Bug 4221 is nothing to do with resolver

that are not central to Cocoon. regards, David David Crossley wrote: Hello Henric, i have reviewed your logfiles that you submitted to Bugzilla. You have not interpreted your logfiles correctly - this issue has nothing to do with resolver. My interpretation of your error is that Cocoon could

Re: entity resolution for Documentation build - almost

, if someone with linux can have a look at it? Carstem -Ursprüngliche Nachricht- Von: David Crossley [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. Oktober 2001 10:11 An: [EMAIL PROTECTED] Betreff: Re: entity resolution for Documentation build - almost Cartsen wrote

Re: Documentation: short alternative to @docname@?

Good one Bernhard - i was just working up my own reply when yours came in. Yes, entities are an obvious choice for any such XML replacement. Ideally these are defined in the DTD. Perhaps they can instead be defined in the entity catalog - i am not yet sure. Some other notes ... *) Samples -

XML validation during build docs

Has the build docs stopped doing validation of xdocs, or do i imagine that? I recall that when the build was controlled by Ant, then it was doing full XML validation. I am sure that i often received validation errors while developing my xdocs. Now that the build is run by Cocoon then it only

entity resolution for documentation builds

Now that entity catalogs and the entity resolver are properly implemented, the next step is to apply them to the documentation build. I already have this functioning correctly in my local working copy. Also the document xdocs/catalog-test.xml is already proving that it works. However, i do not

Re: Subject: Lucene as Avalon Component?

. --David Crossley Bernhard Huber wrote: Stefano Mazzocchi wrote: Bernhard, perfect timing! I was thinking about the same thing the otherday. Bernhard Huber wrote: hi, I'm taking a look at lunce, a nice search engine. As Cocoon2 claims to be an XML publishing engine, some

Re: [C2]: Release Candidate 2

Carsten wrote: Hi Team, some days ago we decided to make the release candidate 2 on next monday (5th of november). The question is now, what has to be done until then? 1) We have many open bugs in bugzilla. These must be reviewed and then solved (or declared invalid etc). 2)

some xdocs missing from cocoon_20_branch

While fixing some of the xdocs today i noticed that the following document is missing from cocoon_20_branch. Is that a deliberate ommission? tutorial.xml How to create Web Applications --David - To unsubscribe, e-mail: [EMAIL

speedy loading of documentation

When i first discovered Cocoon about a year ago, i was amazed at the extremely poor performance of the xml.apache.org website. It seemed incongruous that Cocoon could be so amazing, yet the website was so slow. Then i realised that the site was not being served by Cocoon. So it must be the

Re: [RT] semantic searching

Yes Stefano, both of your postings came through. This might be the delivery delay glitch that we have been seeing. Did you catch the end of the thread Subject: Lucene as Avalon Component? http://marc.theaimsgroup.com/?l=xml-cocoon-devm=100433830923480w=2 Therein i raised the possibility of

Re: XML validation during build docs

OK, i have XML validation working now during build docs. It revealed some validation errors - nothing too drastic. I have mended all the broken xdocs. These are the steps that i took to get it going. Basically every XML instance document must declare its ruleset. Step 4 is a worry and we need to

Re: [C2 all] SVG FILES for documentation

On Thu, 1 Nov 2001 Klaus Bertram [EMAIL PROTECTED] wrote: Hi documentation designer I will not take on that responsibility, but i will try to add your patches to CVS :-) here you find svg files for label label_over label_select separator without using a bitmat at the background. the file

notification of cTwIG Idiots Guide updates

Hi Jeremy, thanks for your excellent start with the Idiots Guide. Now that it is in the CVS, the group can assist with its maintenance. That is the purpose of today's email. While i was experimenting with XML validation during build docs i needed to fix some XML structural errors in ctwig/ On

[Proposal] xdocs for planning notes

then the note could be archived. --David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

xdocs for planning notes

from the todo documentation to such documents. Carsten -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED]] Sent: Friday, November 09, 2001 7:48 AM To: [EMAIL PROTECTED] Subject: [Proposal] xdocs for planning notes There is various long-term planning

cocoon.xconf files need all possible parameters

the outstanding changes to the factories, today will not be rc2 day. Carsten -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED]] Sent: Monday, November 05, 2001 6:45 AM To: [EMAIL PROTECTED] Subject: documentation of components in */cocoon.xconf One of the big todo

sitemap explanations are required

It would greatly assist any Cocoon user to have some xml comments documentation inside the sitemap.xmap For example, i have been trying to figure out how the documentation/sitemap.xmap works ... i cannot yet. So would someone with more understanding please add some rudimentary explanation.

Re: Our protocols

Per-Olof Noren wrote: Berin Loritsch wrote: Carsten Ziegeler wrote: Hi, you can use all three protocols nearly everywhere in the sitemap except for redirects. Inside your components you can also use these three protocols whenever you have a SourceResolver handy. This is

[Vote]: Torsten Curdt as new committer

vote: Here is my +1 --David Crossley IndexGeo Pty Ltd --- structured document management 160 Cowper Street -- and networked directories enable Goulburn NSW 2580 - geographic information discovery Australia --- www.indexgeo.com.au --- ABN: 29 070 993 609 phone: +61 2 48 221404

Torsten Curdt as new committer

-- Date: Mon, 19 Nov 2001 23:21:13 +1100 From: David Crossley [EMAIL PROTECTED] To: [EMAIL PROTECTED] I would like to propose Torsten Curdt [EMAIL PROTECTED] as a new committer for Apache Cocoon 2. Torsten has been involved with cocoon-dev for a very long time

let us get serious about 2.0 Final Release

There are SIX DAYS TO GO until the agreed date for the final release. We also agreed that the date should not slip. In my opinion, 2.0 is not yet fit for release. So there is only one option ... hold the RT threads and get on with the job. --David -- Subject: [C2.0]

Fwd: LinkAlarm Full Check - 93 for Apache Cocoon

Here is the link to the report following the RC2 release. Congratulations, broken links are well down from last time. The report does provide some interesting summary stats (both below and at the LinkAlarm report). - 581 pages - 1000 external links (237 unique) - 34636 internal links (1157

improving Cocoon mail-archives.html doc

The Cocoon page mail-archives.html has links to various places to browse/search cocoon-users and cocoon-dev However, for many months there is 408 Request timeout for http://mail-archives.apache.org/ Does anyone know what is going on? Also real-time is missing November

Re: let us get serious about 2.0 Final Release

Giacomo Pati wrote: Quoting David Crossley [EMAIL PROTECTED]: There are SIX DAYS TO GO until the agreed date for the final release. We also agreed that the date should not slip. In my opinion, 2.0 is not yet fit for release. So there is only one option ... hold the RT threads and get

Re: let us get serious about 2.0 Final Release

Bernhard Huber wrote: About documentation in general, I would like to write something about the new views, and about the sitemap elements map:aggregate, map:part, etc as I have noticed that they are not described. I will just post the plain text, or should I write it directly in the xml? It

Re: [Patch] some generator/transformer doco

Bernhard Huber [EMAIL PROTECTED] wrote: Subject: Re: let us get serious about 2.0 Final Release some documentation about cinclude, and xinclude as it is frequenty requested. and i copied from javadoc docu about velocity generator. docs are zipped up and attached bye bernhard That is

Assistance with tidy of Ctwig docs

Jeremy Aston wrote: Cool I had said to Stefano that I would pick that up. Was going to do it in the next day or so but saved me a job! Anything else a new bod could do (new to c2 mods not coding that is)? cheers jez Actually Jeremy, there is something very important that you would be

Re: Assistance with tidy of Ctwig docs

). I will check, diff and update in the next day or so. Regards Jeremy David Crossley [EMAIL PROTECTED] wrote: Jeremy Aston wrote: Cool I had said to Stefano that I would pick that up. Was going to do it in the next day or so but saved me a job

Re: [Fwd: freshmeat project listing for Cocoon]

Carsten wrote: Just to get it right. The following is the text we agree on. I'll try my best to get it into freshmeat then By the way, shouldn't we change the README or some other documents and add this text there? This excellent precis should also be added to Cocoon xdocs

Re: [Fwd: freshmeat project listing for Cocoon]

Hi Giacomo, I notice that when you committed changes to index.xml you must have missed this posting from me yesterday. --David David Crossley wrote: Carsten wrote: Just to get it right. The following is the text we agree on. I'll try my best to get it into freshmeat then By the way

Re: Compilation problems was RE: [Fwd: freshmeat project listing for Cocoon]

Christian Haul wrote: On 23.Nov.2001 -- 01:43 PM, giacomo wrote: On Fri, 23 Nov 2001, Carsten Ziegeler wrote: From: giacomo [mailto:[EMAIL PROTECTED]] Big no. After a clean checkout of the HEAD I was able to compile but building the docs failed havily. Could someone fix

build failure (no Php) after latest changes build.xml

. PhpServlet not found. public class PhpServlet extends net.php.servlet implements Runnable { --- ... looks like a problem with the new optional-tests. Platform: Linux RedHat 7.1 and Blackdown j2sdk-1.3.1 --David Crossley

Re: Compilation problems was RE: [Fwd: freshmeat project listing for Cocoon]

Jason Foster wrote: David Crossley wrote: I did raise this issue a long time ago. Everyone said that the docs build worked for them. So i thought that it was only my problem. Now it looks like i have company. Yes Christian, i too am on Linux with Blackdown J2SDK 1.3.0 Add a stock

Re: [Patch] enhanced doc concepts/views.xml

Thanks Bernhard, i have applied your documentation patch. --David Subject: Re: let us get serious about 2.0 Final Release Date: Sun, 25 Nov 2001 21:28:25 +0100 From: Bernhard Huber [EMAIL PROTECTED] To: [EMAIL PROTECTED] hi, i enhanced the view.xml describing the new features, i hope it

Re: cvs commit: xml-cocoon2/documentation cocoon.xconf

Giacomo wrote: Sorry, I thought it solves the problem. Can you explain what my change broke. Hi Giacomo, i was just in the middle of preparing two emails - one to explain this revert (and one where i think that i have tracked down the problem). When you changed the default path in

found the cause of Bug #5060 build docs

I have isolated the cause of the Bug. It looks like it will be easy to fix :-) though it will need someone else to do it. As described in Bugzilla - here is a summary ... Everything works fine with the entity resolver when Cocoon is running as a webapp. However, when running as commandline

Re: Showstoppers for 2.0 final was RE: [tale+rant] The 2.0 syndrome and [Vote]: Final Release Date

Giacomo wrote: Gianugo Rabellino wrote: giacomo wrote: On Mon, 26 Nov 2001, Giacomo Pati wrote: Quoting Gianugo Rabellino [EMAIL PROTECTED]: Gianugo Rabellino wrote: I just did a fresh checkout. This is Linux Mandrake with Blackdown 1.3.1. I'm getting plenty of entity

Re: found the cause of Bug #5060 build docs

Carsten Ziegeler wrote: John Morrison wrote: -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 27 November 2001 8:52 am To: [EMAIL PROTECTED] Subject: found the cause of Bug #5060 build docs snip/ So it seems

Re: found the cause of Bug #5060 build docs

).getAbsolutePath(); this.attributes = new HashMap(); } would help? Carsten -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 27, 2001 2:57 PM To: [EMAIL PROTECTED] Subject: Re: found the cause of Bug #5060 build docs Carsten

Re: found the cause of Bug #5060 build docs

Gianugo Rabellino wrote: David Crossley wrote: Excellent, thanks everyone. That fixes it. I have committed the changes to CommandlineContext.java into HEAD only. Would people on all platforms, please please confirm that build docs now works for you. Then i will add the changes

Re: [PATCH] was: found the cause of Bug #5060 build docs

(); } would help? Carsten -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 27, 2001 2:57 PM To: [EMAIL PROTECTED] Subject: Re: found the cause of Bug #5060 build docs Carsten Ziegeler wrote: John

Re: found the cause of Bug #5060 build docs

David Crossley wrote: Gianugo Rabellino wrote: David Crossley wrote: Excellent, thanks everyone. That fixes it. I have committed the changes to CommandlineContext.java into HEAD only. Would people on all platforms, please please confirm that build docs now works for you

why many messages: Could not find component

of feedback that Cocoon is broken or they will blame those messages for their own problems. --David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

status of sitemap DTD

. However, prior to this recent DTD there was no such ruleset in CVS. Does anybody know of the existence of any other info about the structure of a sitemap. I suppose that in the code is one place. --David Crossley - Date: Thu, 8 Nov 2001 19:25:46 +1100 Subject: towards

Re: found the cause of Bug #5060 build docs

John Morrison wrote: Well done guys - just one question: does it still work as a unexpanded war file? ie, if you produce a war (apologies if this has been tested), drop it into tomcat with the do not unpack setting, is it ok? J. As explained elsewhere in this thread, we need to see it

Re: Can we go final now?

Carsten wrote: Hi Team, it seems bug 5060 is fixed, right? So we have no outstanding blockers (I hope). So, if this is the case, we should go final. I would like to have a code freeze then starting today and make the distribution tomorrow morning, so tomorrow would be the final day.

Re: [showstopper!] broken URL contract!

Carsten, I see that our documentation is out of sync between head and 2.0 branches. The new blurb for What is it on index.xml is already in 2.1 but not in 2.0 Anyway, please put Steven's suggestion towards the end of the What is it section - we just worked to get rid of the apologising type

Re: [Announcement] Apache Cocoon 2.0 Release

Carsten Ziegeler wrote: David Crossley wrote: Great work everyone. Celebration time! I notice that this announcement only went to cocoon-dev and cocoon-users, whereas the RC2 announcement also went to [EMAIL PROTECTED] and [EMAIL PROTECTED] I sent a first mail to dev and users

build failure HEAD: DatabaseSelectAction.java

I have been getting a build failure for HEAD for the last couple of days. Build is OK for cocoon_20_branch - but then 2.0 does not contain acting/DatabaseSelectAction.java I see from CVSview that recent commits were done to some classes in cocoon/acting/ --- [crossley@igacer

Re: build failure HEAD: DatabaseSelectAction.java

/AbstractComplementaryConfigurableAction.java Does that still need to be applied to HEAD as well? --David - David Crossley wrote: I have been getting a build failure for HEAD for the last couple of days. Build is OK for cocoon_20_branch - but then 2.0 does

  1   2   3   4   5   >