Steinar Jonsson | 1 Dec 01:24 2003
Picon
Picon

Re: Are nested flowscripts possible?

On Friday 28 November 2003 09:32, Marc Portier wrote:
> Steinar Jonsson wrote:
> > On Thursday 27 November 2003 23:53, Marc Portier wrote:
> >>Steinar Jonsson wrote:
> >>>A flowscript does a sendPageAndWait( request ), and the
> >>>request happens to start a second flowscript.
> >>>
> >>>When that second flowscript has completed its work,
> >>>how does it get back to where the first one left off?
> >>>
> >>>I can't see how to get hold of that continuation id.
> >>>Am I just being blind, or is this a bad idea altogether?
> >>
> >>yep, it's not how you use this stuff
> >>
> >>
> >>what I think you try to do is this:
> >>
> >>uri-1 --> calls function1
> >>function1() {
> >>  // do-stuff
> >>  sendPageAndWait(nextPage-uri);
> >>}
> >>
> >>on the produced page there is NOT a link with the continuation, but
> >>rather a link to some uri-2 -->  calls function2
> >>
> >>function2() {
> >>   //do other stuff.
> >>
(Continue reading)

Geoff Howard | 1 Dec 02:01 2003

Re: cvs commit: cocoon-2.2/src/java/org/apache/cocoon/components/treeprocessor sitemap2xconf.xsl

unico <at> apache.org wrote:

> unico       2003/11/30 13:16:15
> 
>   Modified:    src/java/org/apache/cocoon/components/treeprocessor
>                         sitemap2xconf.xsl
>   Log:
>   act semantics and view registry

I've been wondering where all this stands - is there some "todo" list 
somewhere?  Is there anywhere others can jump in and help?

Geoff

David Crossley | 1 Dec 03:27 2003
Picon

Re: Doco needs landing

Stefano Mazzocchi wrote:
> David Crossley wrote:
>
> > Mmmm, i am not sure that i like this approach. "Doco" sounds
> > to me like one of the reasons that "Forrest" was started.
> 
> that's right, but forrest took a different path and now focuses
> on static generation of web sites, full blown content management
> is not at reach there anymore.

That is a rash statement from afar.

Forrest was started by some visionaries with grand plans.
After a very short while, most of those people disappeared
and only a few committers remained to assist the fledgling.

Forrest documentation still talked about the grander plans.
Brilliant though it is, Forrest had to pull its horns in,
as it was not yet delivering on that vision.

So certain dreams had to be "shelved". Not abandoned, just put on
hold until there were participants, and real use cases to meet.

There were also recent cases where some new committers started to
set up some default facilities which assumed a servlet environment
and thereby broke the static docs build. We decided that the
primary focus be static, yet enable project-specific dynamic.

--David

(Continue reading)

David Crossley | 1 Dec 05:43 2003
Picon

RE: Problem with CVS of Cocoon-Documentation & an Authoring Question

Carsten Ziegeler wrote:
> Joerg Heinicke wrote:
> > I'm okay with this solution as I'm already using Mozilla, but what about 
> > the others. Indeed there should be people out there not using Mozilla, 
> > what I can't imagine. ;-)
>
> This is not only an IE problem. Try to validate that xml doc in an XML
> editor. This will simply fail, because the xml editor can't find the
> dtd to validate against :( (Of course, if you use sunBow, this problem
> is fixed there by using catalogs :) )
> 
> So,
> 
> > Another solution that came to my mind is pointing to a web URL like 
> > http://cocoon.apache.org/dtd/document-v10.dtd. This would also make 
> > validating possible in editors that don't understand catalogues.
>
> this seems to be a good approach for me.

Would it be acceptable to infrastructure <at>  apache? It is not just
one simple DTD you are downloading, there are many included bits.

I do not agree with the approach. Cocoon has encouraged people to
use the entity resolver. We should not join their bad practice.

A better solution might be to move away from DTDs. Oh drat, some
editors only support DTDs ... foiled again.

> I'm not sure, but I think
> the forrest people have already put their dtds somewhere at
(Continue reading)

bugzilla | 1 Dec 07:09 2003
Picon

DO NOT REPLY [Bug 25098] New: - SQLTransformer fails to return number of rows updated

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25098

SQLTransformer fails to return number of rows updated

           Summary: SQLTransformer fails to return number of rows updated
           Product: Cocoon 2
           Version: 2.1.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: general components
        AssignedTo: dev <at> cocoon.apache.org
        ReportedBy: dean.cording <at> kaz-group.com

The SQLTransformer fails to return the number of rows updated as a result of an 
INSERT, UPDATE or DELETE statement. 

The SQLTransformer.Query.serializeRows method will return the number of updated 
rows as a returncode attribute but it is never called for update queries. 

The following code fragment from SQLTransform.executeQuery processes the 
results from the query: 
(Continue reading)

bugzilla | 1 Dec 07:35 2003
Picon

DO NOT REPLY [Bug 25099] New: - Cocoon Forms Roadmap

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25099

Cocoon Forms Roadmap

           Summary: Cocoon Forms Roadmap
           Product: Cocoon 2
           Version: Current CVS 2.1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: sitemap components
        AssignedTo: dev <at> cocoon.apache.org
        ReportedBy: bdelacretaz <at> codeconsult.ch

This entry is used to group together entries to keep track of the roadmap, by
making it dependent on entries which together form the roadmap.

See also:
http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFormsRoadmap
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107011761631052&w=2

(Continue reading)

bugzilla | 1 Dec 07:36 2003
Picon

DO NOT REPLY [Bug 25094] - Move Woody into CocoonForms block

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25094

Move Woody into CocoonForms block

bdelacretaz <at> codeconsult.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |25099
              nThis|                            |

Bertrand Delacretaz | 1 Dec 07:46 2003
Picon

Re: Feature request votes (was Re: CocoonForms roadmap)

Le Dimanche, 30 nov 2003, à 15:18 Europe/Zurich, Reinhard Poetz a écrit 
:

> ...yep, I had the feeling too but as we don't have any rules for 
> feature
> requests and I don't have the know-how in Bugzilla how to separate
> between patches, bugs and feature requests...

There was a discussion a while ago, the best way to differentiate seems 
to be:

-[PATCH] in the summary for patches
-Severity=Enhancement for feature requests
-The rest are bugs

>  and I also don't have the
> time to find out all those things I used Wiki which was the easierst 
> way
> for *me*. When I wrote the mail to the list I asked for help moving the
> issues to Bugilla (any Bugzilla gurus out there???) but haven't got any
> reponse on my call.
>
> so, do we have the possibility to get useful reports from Bugzilla -
> useful means: to get e.g. only feature requests for CocoonForms?

"only feature requests" = "Severity==enhancement"

CocoonForms = need to to define a Component called CocoonForms for the 
"Cocoon 2" product in bugzilla.

(Continue reading)

Bertrand Delacretaz | 1 Dec 07:48 2003
Picon

Re: Feature request votes (was Re: CocoonForms roadmap)

Le Dimanche, 30 nov 2003, à 21:08 Europe/Zurich, Litrik De Roy a écrit :
> ...2) There was a piece of text saying "0 votes used out of 6 
> allowed.". Does this mean that I can only cast 6 votes. The 
> enhancements list for Woody/CocoonForms will be much longer than 
> that...

This max number of votes is configurable per product in the bugzilla 
"products" page (http://nagoya.apache.org/bugzilla/editproducts.cgi) 
but currently we don't have access to this page, see my other mail.

-Bertrand

Nicola Ken Barozzi | 1 Dec 08:26 2003
Picon

Re: Doco needs landing (Was: cvs commit: cocoon-2.1 features.xml)

Stefano Mazzocchi wrote:

> On 28 Nov 2003, at 03:46, David Crossley wrote:
...
>> Mmmm, i am not sure that i like this approach. "Doco" sounds
>> to me like one of the reasons that "Forrest" was started.
> 
> that's right, but forrest took a different path and now focuses on 
> static generation of web sites, full blown content management is not at 
> reach there anymore.

Although we have currently decided to focus on the final generation step 
(not only CLI, but still the last presentation step), of course it does 
not mean that Doco could not be a part of Forrest.

I mean *could* not *should*.

ATM Doco is so virtual that I cannot say anything about it.

>> What is worrying is that this one-person thing (though i trust
>> Stefano to know what to do) will have no community to land in
>> and Apache will spawn yet another new project.

Well, Doco ahould be a glue that it to put together different projects 
in a coherent vision. We have Slide (backend), Lenya (CMS), Forrest 
(presentation).

Look at the Forrest community now. Do you think we are ready and willing 
to lead such a design? Speaking for me, not now, I still have lots of 
work to do on what Forrest does now.
(Continue reading)


Gmane