Flow Database stuff ( The new FOM? )

ok, I am confused on what is happening to the Datbase.js file. but instead of a request for the long explanation, I will settle for a quick yes or no. I am a java newbie... so bear with me... >From the petstore: // temporary hack to avoid requiring datasource config in cocoon.xconf

cvs commit: cocoon-site/site/1.x 3rdparty.html caching.html changes.html connection-pool.html contrib.html dynamic.html esql.html faqs.html fp.html guide.html hosting.html how-it-works.html index.html infrastructure.html install.html ldap.html license.html livesites.html patches.html sql.html sqltaglib.html technologies.html todo.html wd-xsp.html xmlfragment.html xsp.html

vgritsenko2003/07/09 17:54:12 Modified:xdocsdocs-book.xml site-book.xml site/1.x 3rdparty.html caching.html changes.html connection-pool.html contrib.html dynamic.html esql.html faqs.html fp.html guide.html hosting.html

Re: cvs commit: cocoon-site/src/documentation/content/xdocs/communitymail-archives.xml

Joerg Heinicke wrote: Hello Vadim, while in CygWin Cocoon 1.x build does not work, Now it works. ;-P Vadim

cvs commit: cocoon-site/site/1.x mail-archives.html mail-lists.html

vgritsenko2003/07/09 17:48:52 Removed: site/1.x mail-archives.html mail-lists.html Log: update site (removed mail list and archive pages)

cvs commit: cocoon-1/xdocs contrib.xml docs-book.xml patches.xml site-book.xml

vgritsenko2003/07/09 17:44:26 Modified:xdocscontrib.xml docs-book.xml patches.xml site-book.xml Log: Fix bugs in *-book files and fix broken links Revision ChangesPath 1.5 +2 -1 cocoon-1/xdocs/contrib.xml Index: contrib.xml ==

Re: problem with the HTML DTD

oh shit, now I see it. Why is it with the lates checkout but not with 1.8.2? any idea. What's the difference? Christoph - Original Message - From: "Joerg Heinicke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 10, 2003 1:57 AM Subject: Re: problem with the HTML DTD >

cvs commit: cocoon-2.1/src/test/org/apache/cocoon/environment/mock MockEnvironment.java

ghoward 2003/07/09 17:36:49 Modified:src/test/org/apache/cocoon/environment/mock MockEnvironment.java Log: surely this is what was meant? Revision ChangesPath 1.5 +2 -2 cocoon-2.1/src/test/org/apache/cocoon/environment/mock/MockEnvironm

cvs commit: cocoon-2.1/src/test/org/apache/cocoon/environment/mock MockEnvironment.java

ghoward 2003/07/09 17:25:26 Modified:src/test/org/apache/cocoon/util/test MIMEUtilsTestCase.java src/test/org/apache/cocoon/generation FileGeneratorTestCase.java AbstractGeneratorTestCase.java src/test/org/apac

Re: problem with the HTML DTD

It starts with the same output, but ends with the exception below. Win 2000, either JDK 1.3.1_06 or 1.4.1_02 (java.endorsed.dirs set) and recent Cocoon 1.x CVS (1.8.3-dev). Joerg Christoph Gaffga wrote: I tried targets site, package, dist-zip, docs. I make a build clean and try it again zo mak

Re: problem with the HTML DTD

I tried targets site, package, dist-zip, docs. I make a build clean and try it again zo make sure... I got a lot output like [java] [XalanProcessor] Applying XSL sheet "sbk:/style/stylesheets/book2project.xsl" [java] [XalanProcessor] Applying XSL sheet "sbk:/style/stylesheets/directory2project.xs

Re: problem with the HTML DTD

"build site"? Joerg Christoph Gaffga wrote: I tried to build the 1.8.2 (WinXP, JDK1.2.2), and it seems to work without an exception. strange :-/ Christoph - Original Message - From: "Joerg Heinicke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 09, 2003 11:56 PM Subj

Re: problem with the HTML DTD

I tried to build the 1.8.2 (WinXP, JDK1.2.2), and it seems to work without an exception. strange :-/ Christoph - Original Message - From: "Joerg Heinicke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 09, 2003 11:56 PM Subject: Re: problem with the HTML DTD > That's

Re: problem with the HTML DTD (was: cvs commit: cocoon-site/src/documentation/content/xdocs/community mail-archives.xml)

oh, seems I workt to long, it's not a comment, it's an entity. Is it valid? (little bit off-topic). Christoph - Original Message - From: "Christoph Gaffga" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, July 09, 2003 11:48 PM Subject: Re: problem with th

DO NOT REPLY [Bug 20381] - XSLTC: top-level xsl:variable with document() breaks

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: problem with the HTML DTD

That's correct, it's a SGML file I guess. But how to get Cocoon 1.x build working :) Joerg Christoph Gaffga wrote: hi, My editor also thinks that the DTD-file is invalid: Line 31, col 3: This file is not well-formed: ">" expected. W3C sould change the file, it's not a valid xml-1.0 file, see ht

Re: problem with the HTML DTD (was: cvs commit: cocoon-site/src/documentation/content/xdocs/community mail-archives.xml)

hi, My editor also thinks that the DTD-file is invalid: Line 31, col 3: This file is not well-formed: ">" expected. W3C sould change the file, it's not a valid xml-1.0 file, see http://www.w3.org/TR/REC-xml#sec-comments Christoph - Original Message - From: "Joerg Heinicke" <> To: <[E

Re: Javdoc typo in org.apache.cocoon.transformation.XMLDBTransformer- 2.1m3

Thanks, fixed. Joerg Morgan Roderick wrote: Hi gang I may have found a Javadoc typo in org.apache.cocoon.transformation.XMLDBTransformer In the 2.1m3 release the apidoc for XMLDBTransformer reads: Definition: org.apache.xindice.client.xmldb.DatabaseImpl xmldb:xindice:///db/

Re: [Vote] Cocoon Advanced Control Flow

Christopher Oliver wrote: Sylvain Wallez wrote: That is perfectly ok. Also, would "cocoon.parameters" make sense for also ? IMO yes, as otherwise there's no means to pass e.g. parts of the URI (matcher wildcards) to the continued script. What do you think ? Sylvain It's already there (as i

cvs commit: cocoon-2.1/src/blocks/xmldb/java/org/apache/cocoon/transformation XMLDBTransformer.java

joerg 2003/07/09 14:36:53 Modified:src/blocks/xmldb/java/org/apache/cocoon/transformation XMLDBTransformer.java Log: Javadoc fixed (Morgan Roderick) imports cleaned up Revision ChangesPath 1.3 +16 -17 cocoon-2.1/src/blocks/xmldb/java/

Re: cvs commit: cocoon-site/src/documentation/content/xdocs/communitymail-archives.xml

Hello Vadim, while in CygWin Cocoon 1.x build does not work, it works at least at Windows command line. But this old Xerces version seems to have a problem with the HTML DTD and I don't know where to switch validation off. I never used Cocoon 1.x, so I don't have any experience with it. Joerg

cvs commit: cocoon-1/xdocs site-book.xml

joerg 2003/07/09 13:51:25 Modified:xdocssite-book.xml Log: set mail-list/-archive links to c.a.o/community/* (here too?) Revision ChangesPath 1.33 +2 -2 cocoon-1/xdocs/site-book.xml Index: site-book.xml =

Re: Fixing module confusion (was Re: All scratchpad code migratedto FOM)

Ok, thanks - will do. I'll make a README.txt and send it with the request. Geoff Vadim Gritsenko wrote: Geoff Howard wrote: We discussed this reoccuring problem recently and there was a sort of consensus (http://marc.theaimsgroup.com/?t=10562336112&r=1&w=2) to remove the link which curren

Re: cvs commit: cocoon-site/src/documentation/content/xdocs/communitymail-archives.xml

2.1 already points to c.a.o/community. 2.0 fixed and committed at cocoon-site 1.x fixed, but could not commit at cocoon-site, because build does not work: $ sh ./build.sh site Cocoon Build System --- Building with classpath lib/ant_1_3.jar:lib/batik-libs.jar:lib/bsf.jar:lib/bsfeng

cvs commit: cocoon-1/xdocs mail-archives.xml mail-lists.xml

joerg 2003/07/09 12:15:09 Removed: xdocsmail-archives.xml mail-lists.xml Log: set mail-list/-archive links to c.a.o/community/*

cvs commit: cocoon-1/xdocs docs-book.xml

joerg 2003/07/09 12:14:40 Modified:xdocsdocs-book.xml Log: set mail-list/-archive links to c.a.o/community/* Revision ChangesPath 1.30 +2 -2 cocoon-1/xdocs/docs-book.xml Index: docs-book.xml ==

Re: Fixing module confusion (was Re: All scratchpad code migratedto FOM)

Geoff Howard wrote: We discussed this reoccuring problem recently and there was a sort of consensus (http://marc.theaimsgroup.com/?t=10562336112&r=1&w=2) to remove the link which currently exists from xml-cocoon2 to the "historical" cocoon module and in its place create a real module at xm

Fixing module confusion (was Re: All scratchpad code migrated toFOM)

We discussed this reoccuring problem recently and there was a sort of consensus (http://marc.theaimsgroup.com/?t=10562336112&r=1&w=2) to remove the link which currently exists from xml-cocoon2 to the "historical" cocoon module and in its place create a real module at xml-cocoon2 which conta

Re: cvs commit: cocoon-site/src/documentation/content/xdocs/communitymail-archives.xml

Joerg Heinicke wrote: Ok, if you do the update again :) Just ping me when you are done Vadim

Re: cvs commit: cocoon-site/src/documentation/content/xdocs/communitymail-archives.xml

Ok, if you do the update again :) The modules should no longer have their own mail-lists/-archives pages. But I'll have a closer look. Joerg Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: joerg 2003/07/09 10:50:11 Modified:src/documentation/content/xdocs/community mail-archives.xm

Re: cvs commit: cocoon-site/src/documentation/content/xdocs/communitymail-archives.xml

[EMAIL PROTECTED] wrote: joerg 2003/07/09 10:50:11 Modified:src/documentation/content/xdocs/community mail-archives.xml Log: fixed mail archive links Can you check these links in 2.0/ and 2.1/ and 1.x/ sites too? Vadim

cvs commit: cocoon-site/site/community mail-archives.html

joerg 2003/07/09 11:10:16 Modified:site/community mail-archives.html Log: fixed mail archive links Revision ChangesPath 1.2 +43 -37cocoon-site/site/community/mail-archives.html Index: mail-archives.html ==

RE: All scratchpad code migrated to FOM

> I just compiled a clean checkout with jdk1.4.1_01 on windows 2000 > without problems including the scratchpad. What error did you encounter? > If it was with FlowVelocityGenerator, then you need to update from the > latest cvs. I was compiling code originally checked out of HEAD when cocoon's

cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/sax XMLByteStreamInterpreter.java

cziegeler2003/07/09 10:59:44 Modified:src/java/org/apache/cocoon/components/sax XMLByteStreamInterpreter.java Log: Resetting string list on each invocation Revision ChangesPath 1.3 +2 -1 cocoon-2.1/src/java/org/apache/cocoon/components/

cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/sax XMLByteStreamCompiler.java

cziegeler2003/07/09 10:53:03 Modified:src/java/org/apache/cocoon/components/sax XMLByteStreamCompiler.java Log: Return null if no events have arrived Revision ChangesPath 1.2 +4 -1 cocoon-2.1/src/java/org/apache/cocoon/components/sax/XM

cvs commit: cocoon-site/src/documentation/content/xdocs/community mail-archives.xml

joerg 2003/07/09 10:50:11 Modified:src/documentation/content/xdocs/community mail-archives.xml Log: fixed mail archive links Revision ChangesPath 1.3 +20 -25 cocoon-site/src/documentation/content/xdocs/community/mail-archives.xml Index: mail-archives.xml

Re: [Vote] Cocoon Advanced Control Flow

Sylvain Wallez wrote: Christopher Oliver wrote: Just to clarify: what I added was the "cocoon.parameters" property that contains a map of the parameters passed from the sitemap. The parameters are also passed positionally to the function as before. So if you want to access a named parameter y

Re: [Vote] Cocoon Advanced Control Flow

Christopher Oliver wrote: Just to clarify: what I added was the "cocoon.parameters" property that contains a map of the parameters passed from the sitemap. The parameters are also passed positionally to the function as before. So if you want to access a named parameter you can do this:

Re: [Vote] Cocoon Advanced Control Flow

Christopher Oliver wrote: Sylvain Wallez wrote: Reinhard Pötz wrote: +1 on everything but [B] : [B] Functions provided by scripts can be called within the sitemap using: [2] There are no special restrictions where you can put it within (e.g. put it

RE: Alternatives to XMLForm: what's the state of art?

From: Christopher Oliver > Reinhard Pötz wrote: > > >From: Christopher Oliver > > > > > > > >>JXForms supports the latest W3C XForms syntax (although not every > >>construct). JXForms doesn't use XMLFormTransformer. Instead > >>it provides > >>its own generator (JXFormsGenerator) and tra

Re: All scratchpad code migrated to FOM

I just compiled a clean checkout with jdk1.4.1_01 on windows 2000 without problems including the scratchpad. What error did you encounter? If it was with FlowVelocityGenerator, then you need to update from the latest cvs. Chris Jacob L E Blain Christen wrote: I just modified the remainder of

Re: [Vote] Cocoon Advanced Control Flow

Just to clarify: what I added was the "cocoon.parameters" property that contains a map of the parameters passed from the sitemap. The parameters are also passed positionally to the function as before. So if you want to access a named parameter you can do this: ... function myFlow() {

Re: Alternatives to XMLForm: what's the state of art?

Reinhard Pötz wrote: From: Christopher Oliver JXForms supports the latest W3C XForms syntax (although not every construct). JXForms doesn't use XMLFormTransformer. Instead it provides its own generator (JXFormsGenerator) and transformer (JXFormsTransformer). It uses the same Form object a

Re: [Vote] Cocoon Advanced Control Flow

Sylvain Wallez wrote: Reinhard Pötz wrote: +1 on everything but [B] : [B] Functions provided by scripts can be called within the sitemap using: [2] There are no special restrictions where you can put it within (e.g. put it within action elements) As

Re: [Vote] Cocoon Advanced Control Flow

Reinhard Pötz wrote: +1 on everything but [B] : [B] Functions provided by scripts can be called within the sitemap using: [2] There are no special restrictions where you can put it within (e.g. put it within action elements) As pointed out recentl

RE: [Vote] Cocoon Advanced Control Flow

> -Original Message- > From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 09, 2003 6:26 PM > To: [EMAIL PROTECTED] > Subject: Re: [Vote] Cocoon Advanced Control Flow > > > > Thank you for voting/reading so far (13 items ;-)! > > +1 on everything - I cannot loo

RE: Alternatives to XMLForm: what's the state of art?

From: Christopher Oliver > JXForms supports the latest W3C XForms syntax (although not every > construct). JXForms doesn't use XMLFormTransformer. Instead > it provides > its own generator (JXFormsGenerator) and transformer > (JXFormsTransformer). It uses the same Form object and validation

Re: [Vote] Cocoon Advanced Control Flow

Thank you for voting/reading so far (13 items ;-)! +1 on everything - I cannot look at all the details now but I trust you guys ;-) -Bertrand

RE: [Vote] Cocoon Advanced Control Flow

From: Steven Noels > On 9/07/2003 14:37 Reinhard Pötz wrote: > > > [3] I'm aware of Sylvain's and Marc's proposal on changing > > the scope of available controllers. I contacted Sylvain off-list > > and the said that they want to come up with a concrete > > implementation > > of th

RE: All scratchpad code migrated to FOM

> I just modified the remainder of the scratchpad code including PetStore > and JXForms to use the FOM. I also implemented the FOM WebContinuation. > However, in order not to break anyone immediately who may be using them, > I haven't yet modified the JXTemplateGenerator and FlowVelocityGenerato

Re: [Vote] Cocoon Advanced Control Flow

+1. Chris Reinhard Pötz wrote: From: Vadim Gritsenko Reinhard Pötz wrote: Thank you for voting/reading so far (13 items ;-)! Reinhard, This doco nicely summarizes what we have so far in the flow. And, because it is already present, and was already dicussed/voted some time a

RE: [Vote] Cocoon Advanced Control Flow

From: Marc Portier > > just dotting the i's and crossing the t's > (don't want to be nagging) > > Reinhard Pötz wrote: > > > > > [D] All flow interpreters[3] are Avalon components and declared > > in the cocoon.xonf: > > > >logger="[yourLogger]"> > > ... > >

cvs commit: cocoon-2.1/tools/src blocks-build.xsl

bruno 2003/07/09 08:36:27 Modified:tools/src blocks-build.xsl Log: Dropped compiler parameter from test javac because that is not supported when fork=true Revision ChangesPath 1.29 +1 -2 cocoon-2.1/tools/src/blocks-build.xsl Index: blocks-build.xsl ==

cvs commit: cocoon-2.1/tools/src blocks-build.xsl

bruno 2003/07/09 08:26:40 Modified:tools/src blocks-build.xsl Log: Use all javac parameters when building block test classes Revision ChangesPath 1.28 +7 -1 cocoon-2.1/tools/src/blocks-build.xsl Index: blocks-build.xsl ==

Javdoc typo in org.apache.cocoon.transformation.XMLDBTransformer - 2.1m3

Hi gang I may have found a Javadoc typo in org.apache.cocoon.transformation.XMLDBTransformer In the 2.1m3 release the apidoc for XMLDBTransformer reads: Definition: org.apache.xindice.client.xmldb.DatabaseImpl xmldb:xindice:///db/collection And it should probably read

Re: Alternatives to XMLForm: what's the state of art?

JXForms supports the latest W3C XForms syntax (although not every construct). JXForms doesn't use XMLFormTransformer. Instead it provides its own generator (JXFormsGenerator) and transformer (JXFormsTransformer). It uses the same Form object and validation framework as XMLForm. However, it does

RE: Alternatives to XMLForm: what's the state of art?

That's OK. I re-post my question in other way: With JXForms, do you use the same transformer as XMLForm (XMLFormTransformer)? If yes, has this transformer been updated last two months (for example to matches the latest W3C XForms draft)? If not, is the tag syntax matches the latest W3C XForms dr

cvs commit: cocoon-site/site/community mail-lists.html

stevenn 2003/07/09 07:13:41 Modified:site/community mail-lists.html Log: clarified moderation strategy Revision ChangesPath 1.2 +25 -12cocoon-site/site/community/mail-lists.html Index: mail-lists.html ==

cvs commit: cocoon-site/src/documentation/content/xdocs/community mail-lists.xml

stevenn 2003/07/09 07:13:06 Modified:src/documentation/content/xdocs/community mail-lists.xml Log: clarified moderation strategy Revision ChangesPath 1.3 +21 -8 cocoon-site/src/documentation/content/xdocs/community/mail-lists.xml Index: mail-lists.xml ==

Re: [Vote] Cocoon Advanced Control Flow

On 9/07/2003 14:37 Reinhard Pötz wrote: [3] I'm aware of Sylvain's and Marc's proposal on changing the scope of available controllers. I contacted Sylvain off-list and the said that they want to come up with a concrete implementation of their proposal in the future and this should *not

Re: [Vote] Cocoon Advanced Control Flow

just dotting the i's and crossing the t's (don't want to be nagging) Reinhard Pötz wrote: [D] All flow interpreters[3] are Avalon components and declared in the cocoon.xonf: ... our proposal was about having also non-interpreter implementations of

Re: Alternatives to XMLForm: what's the state of art?

On 9/07/2003 15:32 [EMAIL PROTECTED] wrote: My question is: have you done this and incorporated this features from xmlform.org into the JXForm? I don't know whether Ivelin or anyone else had backported any of the xmlform.org changes into Cocoon CVS, be it in XMLForm or JXForms. I don't even know w

RE: Alternatives to XMLForm: what's the state of art?

Reinhard, There was a difference between Cocoon XMLForm and xmlform.org when I posted this question: What is the current status of Cocoon XMLForm? (see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105341585732055&w=2). It appeared that there was some differences between the two (see the Ive

Re: [Vote] Cocoon Advanced Control Flow

Reinhard Pötz wrote: From: Vadim Gritsenko Reinhard Pötz wrote: Thank you for voting/reading so far (13 items ;-)! Reinhard, This doco nicely summarizes what we have so far in the flow. And, because it is already present, and was already dicussed/voted some time ago, what here

RE: [Vote] Cocoon Advanced Control Flow

From: Vadim Gritsenko > > Reinhard Pötz wrote: > > > >Thank you for voting/reading so far (13 items ;-)! > > > > Reinhard, > > This doco nicely summarizes what we have so far in the flow. And, > because it is already present, and was already dicussed/voted > some time > ago, what here we

Re: [Vote] Cocoon Advanced Control Flow

Reinhard Pötz wrote: Thank you for voting/reading so far (13 items ;-)! Reinhard, This doco nicely summarizes what we have so far in the flow. And, because it is already present, and was already dicussed/voted some time ago, what here we are voting for? :) Vadim

RE: [Vote] Cocoon Advanced Control Flow

From: Reinhard Pötz > +--+ > | Cocoon Advanced Control Flow (in general) | > +--+ +1 for A to G > +-

RE: Alternatives to XMLForm: what's the state of art?

From: Sylvain Thevoz > Hello Reinhard, > > What are the advantages if I choose JXForms (Cocoon Control > Flow) instead of XMLForms (Action)? "Only" another type of controller. IMO it is more advanced than the XMLForm actions you have to write otherwise, easier to implement and maintain. >

[Vote] Cocoon Advanced Control Flow

Digging into the archives I found Stefanos "RTs from linkmaps to flowmaps" from 2001-03-05.[1] He wrote "Take a piece of paper, avoid thinking you are writing an application for the web, so avoid taking into consideration technical constraints (like the request/response paradigm, intrinsic stat

DO NOT REPLY [Bug 21397] - [PATCH] - Woody Extension

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: Alternatives to XMLForm: what's the state of art?

Hello Reinhard, What are the advantages if I choose JXForms (Cocoon Control Flow) instead of XMLForms (Action)? >We will do the changes (integration of JXForms into the XMLForms block) >the next days. About the form, do the changes include the match of the latest XForms Candidate Release? T

cvs commit: cocoon-2.1/src/blocks/woody/samples/messages WoodyMessages.xml

bruno 2003/07/09 05:17:21 Modified:src/blocks/woody/conf woody.xconf src/blocks/woody/samples/forms form1.xml form1_template.xml form1_template.xsp src/blocks/woody/samples/messages WoodyMessages.xml Added: src/blocks/woody

RE: Alternatives to XMLForm: what's the state of art?

From: Sylvain.Thevoz > Some questions from a user that has sometimes difficulties to > follow the discussion on the dev list: > > What are the different alternatives to XMLForm and what is > the current status of each? XMLForms will be released with Cocoon 2.1 (http://marc.theaimsgroup.com/?l

Alternatives to XMLForm: what's the state of art?

Hello everybody, Some questions from a user that has sometimes difficulties to follow the discussion on the dev list: What are the different alternatives to XMLForm and what is the current status of each? What is the best alternative at the moment (and in the future) for users like me that are

RE: [vote] extend FOM_Request with remoteUser

+1 I think we don't have to vote on this particular issue. I'm preparing the vote on the complete flow implementation and will post it within the next few hours. Reinhard > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Giacomo Pati > Sent: Tuesday

cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/treeprocessor/sitemap PipelineNode.java

cziegeler2003/07/09 00:42:23 Modified:src/java/org/apache/cocoon/servlet ParanoidCocoonServlet.java CocoonServlet.java .status.xml src/scratchpad/src/org/apache/cocoon/generation GarbageGenerator.java

cvs commit: cocoon-2.1/src/java/org/apache/cocoon/components/flow/javascript/fom FOM_Cocoon.java

giacomo 2003/07/09 00:27:25 Modified:src/java/org/apache/cocoon/components/flow/javascript/fom FOM_Cocoon.java Log: added getRemoteUser property/method Revision ChangesPath 1.2 +6 -1 cocoon-2.1/src/java/org/apache/cocoon/components/flow