RE: Identifier used in FragmentExtractorTransformer

So what is your solution? I can't find it in the mail archive... > -Oorspronkelijk bericht- > Van: Joerg Heinicke [mailto:[EMAIL PROTECTED] > Verzonden: vrijdag 21 oktober 2005 23:14 > Aan: dev@cocoon.apache.org > Onderwerp: Re: Identifier used in FragmentExtractorTransformer > > On 21.10

Re: [RT] Rules for adding blocks and functionality?

Le 23 oct. 05, à 21:48, Andrew Savory a écrit : ...On 23 Oct 2005, at 19:20, Daniel Fagerstrom wrote: Just because of its importance, you agree that it is important don't you ;) we should follow our usual and well proven development patterns which involves community involvement. FWIW, Syl

Re: [RT] Rules for adding blocks and functionality?

Le 24 oct. 05, à 06:50, Niclas Hedhman a écrit : I would like to propose; 1. Make Apache Cocoon 3.0 into the slim down, no frills, no blocks, no nothing, thing that has been discussed recently... Agreed, and even start this with 2.2, IIUC as soon as mavenizaion is finished, blocks c

Re: [RT] Rules for adding blocks and functionality?

On Monday 24 October 2005 02:20, Daniel Fagerstrom wrote: > * We really need to get rid of obsolete stuff. Must really every single > block go to 2.2? Are there some oneman shows that better could be > returned to their creator and driven on source forge or Cocoon-dev? Agree, but to accommodate pe

Re: [JIRA] Migration Status

On 24 Oct 2005, at 00:10, Pier Fumagalli wrote: On 24 Oct 2005, at 00:07, Jeff Turner wrote: On Sun, Oct 23, 2005 at 11:19:06PM +0100, Pier Fumagalli wrote: Still mangling with a few unexpected things: it seems that the status migration was wrong for the following issues: Unable to determin

[jira] Updated: (COCOON-1660) can't use singleton classes in Continuable

[ http://issues.apache.org/jira/browse/COCOON-1660?page=all ] Pier Fumagalli updated COCOON-1660: --- > can't use singleton classes in Continuable > -- > > Key: COCOON-1660 > URL: http://issues.apache.

[jira] Updated: (COCOON-1657) a crash in the name() function of the xslt, when using SQL transformer

[ http://issues.apache.org/jira/browse/COCOON-1657?page=all ] Pier Fumagalli updated COCOON-1657: --- > a crash in the name() function of the xslt, when using SQL transformer > -- > >

[jira] Updated: (COCOON-1659) xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict

[ http://issues.apache.org/jira/browse/COCOON-1659?page=all ] Pier Fumagalli updated COCOON-1659: --- > xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict >

[jira] Updated: (COCOON-1661) FormsTransformer causes NPE

[ http://issues.apache.org/jira/browse/COCOON-1661?page=all ] Pier Fumagalli updated COCOON-1661: --- > FormsTransformer causes NPE > --- > > Key: COCOON-1661 > URL: http://issues.apache.org/jira/browse/COCOON-1661 >

[jira] Updated: (COCOON-1658) XSLTC doesn't work with nodeset functions

[ http://issues.apache.org/jira/browse/COCOON-1658?page=all ] Pier Fumagalli updated COCOON-1658: --- > XSLTC doesn't work with nodeset functions > - > > Key: COCOON-1658 > URL: http://issues.apache.or

[jira] Updated: (COCOON-1663) o.a.c.transformation.EncodeURLTransformer doesn't work

[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ] Pier Fumagalli updated COCOON-1663: --- > o.a.c.transformation.EncodeURLTransformer doesn't work > -- > > Key: COCOON-1663 > UR

[jira] Updated: (COCOON-1662) XML serializer puts DOCTYPE after initial XML comments

[ http://issues.apache.org/jira/browse/COCOON-1662?page=all ] Pier Fumagalli updated COCOON-1662: --- > XML serializer puts DOCTYPE after initial XML comments > -- > > Key: COCOON-1662 > UR

[jira] Updated: (COCOON-1667) [html block] HTMLGenerator doesn't copy POST parameters

[ http://issues.apache.org/jira/browse/COCOON-1667?page=all ] Pier Fumagalli updated COCOON-1667: --- > [html block] HTMLGenerator doesn't copy POST parameters > --- > > Key: COCOON-1667 >

[jira] Updated: (COCOON-1666) [PATCH] Fix for validation-error tag in FormsTemplateTransformer

[ http://issues.apache.org/jira/browse/COCOON-1666?page=all ] Pier Fumagalli updated COCOON-1666: --- > [PATCH] Fix for validation-error tag in FormsTemplateTransformer > > > Key: COCOO

[jira] Updated: (COCOON-1664) jsp functionality broken in cocoon 2.1.7-dev, Tomcat 5.5.7, jdk1.5.0_01

[ http://issues.apache.org/jira/browse/COCOON-1664?page=all ] Pier Fumagalli updated COCOON-1664: --- > jsp functionality broken in cocoon 2.1.7-dev, Tomcat 5.5.7, jdk1.5.0_01 > --- > >

[jira] Updated: (COCOON-1665) Database / avalon problems

[ http://issues.apache.org/jira/browse/COCOON-1665?page=all ] Pier Fumagalli updated COCOON-1665: --- > Database / avalon problems > -- > > Key: COCOON-1665 > URL: http://issues.apache.org/jira/browse/COCOON-1665 >

[jira] Updated: (COCOON-1668) [PATCH] NullPointerException in MultiValueField

[ http://issues.apache.org/jira/browse/COCOON-1668?page=all ] Pier Fumagalli updated COCOON-1668: --- > [PATCH] NullPointerException in MultiValueField > --- > > Key: COCOON-1668 > URL: http://issu

[jira] Moved: (COCOON-1668) [PATCH] NullPointerException in MultiValueField

[ http://issues.apache.org/jira/browse/COCOON-1668?page=all ] Pier Fumagalli moved CTEMP-1571 to COCOON-1668: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1668 (was: CTEMP-1571) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1667) [html block] HTMLGenerator doesn't copy POST parameters

[ http://issues.apache.org/jira/browse/COCOON-1667?page=all ] Pier Fumagalli moved CTEMP-1564 to COCOON-1667: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1667 (was: CTEMP-1564) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1666) [PATCH] Fix for validation-error tag in FormsTemplateTransformer

[ http://issues.apache.org/jira/browse/COCOON-1666?page=all ] Pier Fumagalli moved CTEMP-1558 to COCOON-1666: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1666 (was: CTEMP-1558) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1665) Database / avalon problems

[ http://issues.apache.org/jira/browse/COCOON-1665?page=all ] Pier Fumagalli moved CTEMP-1520 to COCOON-1665: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1665 (was: CTEMP-1520) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1664) jsp functionality broken in cocoon 2.1.7-dev, Tomcat 5.5.7, jdk1.5.0_01

[ http://issues.apache.org/jira/browse/COCOON-1664?page=all ] Pier Fumagalli moved CTEMP-1457 to COCOON-1664: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1664 (was: CTEMP-1457) Workflow: Cocoon Workflow (was: jira) C

[jira] Updated: (COCOON-1663) o.a.c.transformation.EncodeURLTransformer doesn't work

[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ] Pier Fumagalli updated COCOON-1663: --- Bugzilla Id: (was: 33662) Description: Not sure that EncodeURLTransformer is for xml/xslt with no xsp's in the mix, but it certainly doesn't seem

[jira] Moved: (COCOON-1663) o.a.c.transformation.EncodeURLTransformer doesn't work

[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ] Pier Fumagalli moved CTEMP-1451 to COCOON-1663: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1663 (was: CTEMP-1451) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1662) XML serializer puts DOCTYPE after initial XML comments

[ http://issues.apache.org/jira/browse/COCOON-1662?page=all ] Pier Fumagalli moved CTEMP-1242 to COCOON-1662: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1662 (was: CTEMP-1242) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1660) can't use singleton classes in Continuable

[ http://issues.apache.org/jira/browse/COCOON-1660?page=all ] Pier Fumagalli moved CTEMP-1183 to COCOON-1660: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1660 (was: CTEMP-1183) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1661) FormsTransformer causes NPE

[ http://issues.apache.org/jira/browse/COCOON-1661?page=all ] Pier Fumagalli moved CTEMP-1194 to COCOON-1661: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1661 (was: CTEMP-1194) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1659) xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict

[ http://issues.apache.org/jira/browse/COCOON-1659?page=all ] Pier Fumagalli moved CTEMP-1175 to COCOON-1659: --- Project: Cocoon (was: Cocoon 2) Key: COCOON-1659 (was: CTEMP-1175) Workflow: Cocoon Workflow (was: jira) C

[jira] Moved: (COCOON-1658) XSLTC doesn't work with nodeset functions

[ http://issues.apache.org/jira/browse/COCOON-1658?page=all ] Pier Fumagalli moved CTEMP-831 to COCOON-1658: -- Project: Cocoon (was: Cocoon 2) Key: COCOON-1658 (was: CTEMP-831) Workflow: Cocoon Workflow (was: jira) Comp

[jira] Moved: (COCOON-1657) a crash in the name() function of the xslt, when using SQL transformer

[ http://issues.apache.org/jira/browse/COCOON-1657?page=all ] Pier Fumagalli moved CTEMP-740 to COCOON-1657: -- Project: Cocoon (was: Cocoon 2) Key: COCOON-1657 (was: CTEMP-740) Workflow: Cocoon Workflow (was: jira)

Re: [JIRA] Migration Status

On 24 Oct 2005, at 00:07, Jeff Turner wrote: On Sun, Oct 23, 2005 at 11:19:06PM +0100, Pier Fumagalli wrote: Still mangling with a few unexpected things: it seems that the status migration was wrong for the following issues: Unable to determine the current status for issue 'COCOON-1571'. Unabl

Re: [JIRA] Migration Status

On Sun, Oct 23, 2005 at 11:19:06PM +0100, Pier Fumagalli wrote: > Still mangling with a few unexpected things: it seems that the status > migration was wrong for the following issues: > > Unable to determine the current status for issue 'COCOON-1571'. > Unable to determine the current status for

Re: [RT] Rules for adding blocks and functionality?

On 23.10.2005 23:45, Ralph Goers wrote: We are chosen as committers as induviduals and not as representants for our companies. From a community stand point I would say that it is time to deprecate the SQLTransformer. As a representative for my company I would rather say: no way, we have tons o

[jira] Deleted: (COCOON-1451) o.a.c.transformation.EncodeURLTransformer doesn't work

[ http://issues.apache.org/jira/browse/COCOON-1451?page=all ] Pier Fumagalli deleted COCOON-1451: --- > o.a.c.transformation.EncodeURLTransformer doesn't work > -- > > Key: COCOON-1451 >

[jira] Deleted: (COCOON-1457) jsp functionality broken in cocoon 2.1.7-dev, Tomcat 5.5.7, jdk1.5.0_01

[ http://issues.apache.org/jira/browse/COCOON-1457?page=all ] Pier Fumagalli deleted COCOON-1457: --- > jsp functionality broken in cocoon 2.1.7-dev, Tomcat 5.5.7, jdk1.5.0_01 > --- > >

[jira] Deleted: (COCOON-1183) can't use singleton classes in Continuable

[ http://issues.apache.org/jira/browse/COCOON-1183?page=all ] Pier Fumagalli deleted COCOON-1183: --- > can't use singleton classes in Continuable > -- > > Key: COCOON-1183 > URL: http://issues.ap

[jira] Deleted: (COCOON-740) a crash in the name() function of the xslt, when using SQL transformer

[ http://issues.apache.org/jira/browse/COCOON-740?page=all ] Pier Fumagalli deleted COCOON-740: -- > a crash in the name() function of the xslt, when using SQL transformer > -- > >

[jira] Deleted: (COCOON-831) XSLTC doesn't work with nodeset functions

[ http://issues.apache.org/jira/browse/COCOON-831?page=all ] Pier Fumagalli deleted COCOON-831: -- > XSLTC doesn't work with nodeset functions > - > > Key: COCOON-831 > URL: http://issues.apache.o

[jira] Deleted: (COCOON-1175) xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict

[ http://issues.apache.org/jira/browse/COCOON-1175?page=all ] Pier Fumagalli deleted COCOON-1175: --- > xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict > ---

[jira] Deleted: (COCOON-1194) FormsTransformer causes NPE

[ http://issues.apache.org/jira/browse/COCOON-1194?page=all ] Pier Fumagalli deleted COCOON-1194: --- > FormsTransformer causes NPE > --- > > Key: COCOON-1194 > URL: http://issues.apache.org/jira/browse/COCOON-11

[jira] Deleted: (COCOON-1242) XML serializer puts DOCTYPE after initial XML comments

[ http://issues.apache.org/jira/browse/COCOON-1242?page=all ] Pier Fumagalli deleted COCOON-1242: --- > XML serializer puts DOCTYPE after initial XML comments > -- > > Key: COCOON-1242 >

[jira] Deleted: (COCOON-1520) Database / avalon problems

[ http://issues.apache.org/jira/browse/COCOON-1520?page=all ] Pier Fumagalli deleted COCOON-1520: --- > Database / avalon problems > -- > > Key: COCOON-1520 > URL: http://issues.apache.org/jira/browse/COCOON-1520

[jira] Deleted: (COCOON-1558) [PATCH] Fix for validation-error tag in FormsTemplateTransformer

[ http://issues.apache.org/jira/browse/COCOON-1558?page=all ] Pier Fumagalli deleted COCOON-1558: --- > [PATCH] Fix for validation-error tag in FormsTemplateTransformer > > > Key:

[jira] Deleted: (COCOON-1564) [html block] HTMLGenerator doesn't copy POST parameters

[ http://issues.apache.org/jira/browse/COCOON-1564?page=all ] Pier Fumagalli deleted COCOON-1564: --- > [html block] HTMLGenerator doesn't copy POST parameters > --- > > Key: COCOON-1564 >

[jira] Deleted: (COCOON-1571) [PATCH] NullPointerException in MultiValueField

[ http://issues.apache.org/jira/browse/COCOON-1571?page=all ] Pier Fumagalli deleted COCOON-1571: --- > [PATCH] NullPointerException in MultiValueField > --- > > Key: COCOON-1571 > URL: http:/

DO NOT REPLY [Bug 35986] - [PATCH] NullPointerException in MultiValueField

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35811] - [html block] HTMLGenerator doesn't copy POST parameters

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35673] - [PATCH] Fix for validation-error tag in FormsTemplateTransformer

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 35144] - Database / avalon problems

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 33762] - jsp functionality broken in cocoon 2.1.7-dev, Tomcat 5.5.7, jdk1.5.0_01

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 33662] - o.a.c.transformation.EncodeURLTransformer doesn't 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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 30824] - XML serializer puts DOCTYPE after initial XML comments

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29547] - can't use singleton classes in Continuable

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 29401] - xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23615] - XSLTC doesn't work with nodeset functions

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://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 21177] - a crash in the name() function of the xslt, when using SQL transformer

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://issues.apache.org/bugzilla/show_bu

[JIRA] Migration Status

Still mangling with a few unexpected things: it seems that the status migration was wrong for the following issues: Unable to determine the current status for issue 'COCOON-1571'. Unable to determine the current status for issue 'COCOON-1564'. Unable to determine the current status for issue 'C

Re: [RT] Rules for adding blocks and functionality?

Sylvain Wallez wrote: Let me just explain how this works: - I added two classes to CForms (about 3 weeks ago), namely ContainerAsMap and RepeaterAsList. These classes are a Map and a List implementations (live wrappers) on top of a container widget and a repeater respectively. - I added jdbi.

Re: [RT] Rules for adding blocks and functionality?

Daniel Fagerstrom wrote: First, let me say I don't completely disagree with deprecating some blocks or components, although it may appear that way from my comments below. But this is not a simple issue. We are chosen as committers as induviduals and not as representants for our companies. F

Re: [RT] Rules for adding blocks and functionality?

Daniel Fagerstrom wrote: was: Super-easy SQL/Form integration for simple CRUD applications Sylvain Wallez wrote: Daniel Fagerstrom wrote: Sylvain, It seem to be great stuff, and something that we really need. But being somewhat formalistic I'm a bit doubtfull about the timing. Ok, you com

Re: [RT] Rules for adding blocks and functionality?

Andrew Savory wrote: On 23 Oct 2005, at 19:20, Daniel Fagerstrom wrote: ... * We really need to get rid of obsolete stuff. Must really every single block go to 2.2? Are there some oneman shows that better could be returned to their creator and driven on source forge or Cocoon-dev? Hmm

Re: forms documentation updates

Bruno Dumon wrote: Hi, you might have seen the notification mails on the docs list for updates to the forms documentation, but is probably easier if I explain what I've done: Great job Bruno! I started filling some blanks, starting with Ajax and will continue next week also! Sylvain

Re: [M10N] separating samples from blocks

Ralph Goers wrote: >> >> > There are easy ways to deal with that. Again, I am speaking from a > Maven 1 perspective since that is what I am very familiar with. My > understanding is that Maven 2 can do what Maven 1 can and more. > One way is to have each block have a pom which just does a multi

Bug report for Cocoon 2 [2005/10/23]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

M10N daisy page

Hi all, I've started a daisy page on the current status and a bit more background info http://cocoon.zones.apache.org/daisy/documentation/756.html We should probably find a proper location for this, so feel free to move it around. Jorg

Re: Super-easy SQL/Form integration for simple CRUD applications

Sylvain Wallez wrote: > I would also appreciate a crash course on how to add new dependencies in > trunk. For the maven part, refer to http://cocoon.zones.apache.org/daisy/documentation/756.html Would you like to try it out with the new jdbi ? :-P Regards Jorg

Re: [RT] Rules for adding blocks and functionality?

Upayavira wrote: Basically, we relegate blocks not by removing or reducing them, but my lifting others. We will have a background of many blocks, many one man shows, half maintained ones, etc. However, we will also have lists saying "these are the cool ones, the ones that really work and are r

Re: [RT] Rules for adding blocks and functionality?

Ralph Goers wrote: > > > Andrew Savory wrote: > >> >>> * We really need to get rid of obsolete stuff. Must really every >>> single block go to 2.2? Are there some oneman shows that better >>> could be returned to their creator and driven on source forge or >>> Cocoon-dev? >> >> >> >> Hmm. I'm

Re: [RT] Rules for adding blocks and functionality?

Andrew Savory wrote: * We really need to get rid of obsolete stuff. Must really every single block go to 2.2? Are there some oneman shows that better could be returned to their creator and driven on source forge or Cocoon-dev? Hmm. I'm not convinced of this. The problem is that we ca

Re: [M10N] separating samples from blocks

Jorg Heymans wrote: Ralph Goers wrote: /src /blocks /cforms /api pom.xml /impl pom/xml /samples pom.xml /test pom.xml

* ATTENTION * Bugzilla Closed for new Entries

Everyone, as of right now, BugZilla is closed for entries while I'm migrating the content to Jira. Please refrain for using BugZilla and/or Jira for bugs until the import is finished. Thank you for understanding. Pier smime.p7s Description: S/MIME cryptographic signature

[jira] Deleted: (COCOON-2) Test issue

[ http://issues.apache.org/jira/browse/COCOON-2?page=all ] Pier Fumagalli deleted COCOON-2: > Test issue > -- > > Key: COCOON-2 > URL: http://issues.apache.org/jira/browse/COCOON-2 > Project: Cocoon > Type: Bug >

Re: [M10N] separating samples from blocks

Daniel Fagerstrom wrote: Joerg Heinicke wrote: ... Ralph made a proposal [1] where exactly one block (= directory) per block (= block in the narrower sense) exists, but with many modules (in the maven sense) in them: /src /blocks /cforms /api

Re: [RT] Rules for adding blocks and functionality?

Hi, On 23 Oct 2005, at 19:20, Daniel Fagerstrom wrote: Just because of its importance, you agree that it is important don't you ;) we should follow our usual and well proven development patterns which involves community involvement. FWIW, Sylvain showed quite a few people an example of thi

[jira] Closed: (COCOON-2) Test issue

[ http://issues.apache.org/jira/browse/COCOON-2?page=all ] Pier Fumagalli closed COCOON-2: --- Resolution: Fixed I'm closing this issue for good... > Test issue > -- > > Key: COCOON-2 > URL: http://issues.apache.org/jira/browse

[jira] Commented: (COCOON-2) Test issue

[ http://issues.apache.org/jira/browse/COCOON-2?page=comments#action_12332920 ] Pier Fumagalli commented on COCOON-2: - Work is progressiong. > Test issue > -- > > Key: COCOON-2 > URL: http://issues.apache.org/jira/browse/COCOON

[jira] Updated: (COCOON-2) Test issue

[ http://issues.apache.org/jira/browse/COCOON-2?page=all ] Pier Fumagalli updated COCOON-2: Making a workflow change indicating that feedback was received. > Test issue > -- > > Key: COCOON-2 > URL: http://issues.apache.org/jira/br

[jira] Commented: (COCOON-2) Test issue

[ http://issues.apache.org/jira/browse/COCOON-2?page=comments#action_12332918 ] Pier Fumagalli commented on COCOON-2: - This is the feedback... > Test issue > -- > > Key: COCOON-2 > URL: http://issues.apache.org/jira/browse/COCO

[jira] Updated: (COCOON-2) Test issue

[ http://issues.apache.org/jira/browse/COCOON-2?page=all ] Pier Fumagalli updated COCOON-2: We're now requiring feedback, and the issue should be placed on hold. > Test issue > -- > > Key: COCOON-2 > URL: http://issues.apache.org/j

[jira] Commented: (COCOON-2) Test issue

[ http://issues.apache.org/jira/browse/COCOON-2?page=comments#action_12332916 ] Pier Fumagalli commented on COCOON-2: - This is a comment without status workflow change. > Test issue > -- > > Key: COCOON-2 > URL: http://issues.a

[jira] Created: (COCOON-2) Test issue

Test issue -- Key: COCOON-2 URL: http://issues.apache.org/jira/browse/COCOON-2 Project: Cocoon Type: Bug Reporter: Pier Fumagalli Assigned to: Cocoon Developers Team This is a test issue. -- This message is automatically generated by JIRA. - If you

Re: [JIRA] Updated workflows

On 23 Oct 2005, at 19:36, Pier Fumagalli wrote: On 23 Oct 2005, at 18:56, Pier Fumagalli wrote: Ok, progress on Jira. As requested, I added the workflow statuses that marks an issue as "on hold" (when waiting for feedback) and "continued" meaning that feedback was received and work should

[jira] Deleted: (COCOON-1) This is a test issue

[ http://issues.apache.org/jira/browse/COCOON-1?page=all ] Pier Fumagalli deleted COCOON-1: > This is a test issue > > > Key: COCOON-1 > URL: http://issues.apache.org/jira/browse/COCOON-1 > Project: Cocoon >

[jira] Reopened: (COCOON-1) This is a test issue

[ http://issues.apache.org/jira/browse/COCOON-1?page=all ] Pier Fumagalli reopened COCOON-1: - The issue is being reopened. > This is a test issue > > > Key: COCOON-1 > URL: http://issues.apache.org/jira/browse/COC

[jira] Created: (COCOON-1) This is a test issue

This is a test issue Key: COCOON-1 URL: http://issues.apache.org/jira/browse/COCOON-1 Project: Cocoon Type: Bug Reporter: Pier Fumagalli Assigned to: Cocoon Developers Team This is a test issue to verify that Jira is correctly configured.

Re: [M10N] When to ditch Ant and switch to Maven

Daniel Fagerstrom wrote: > > * M2 stable enough (2.0 is out so this should be fullfilled) > * Reasonably fast (don't need to be as fast as Ant, but not several > times slower) > * Easy configuration of what blocks to compile (like blocks.properties > and maybe even dependency aware) > * M2 bundl

Re: [JIRA] Updated workflows

On 23 Oct 2005, at 18:56, Pier Fumagalli wrote: Ok, progress on Jira. As requested, I added the workflow statuses that marks an issue as "on hold" (when waiting for feedback) and "continued" meaning that feedback was received and work should continue. I'm waiting for the changes to propag

Re: [M10N] separating samples from blocks

Daniel Fagerstrom wrote: > Some of our blocks have become rather large and would probably better be > split into smaller blocks. The portal is one example. With the separate > Ajax block CForms have in one sense allready been splitted, it might be > a good idea to split it further. For the core w

Re: [M10N] separating samples from blocks

Ralph Goers wrote: >>> /src >>> /blocks >>> /cforms >>> /api >>> pom.xml >>> /impl >>> pom/xml >>> /samples >>> pom.xml >>> /test >>>

[RT] Rules for adding blocks and functionality?

was: Super-easy SQL/Form integration for simple CRUD applications Sylvain Wallez wrote: Daniel Fagerstrom wrote: Sylvain, It seem to be great stuff, and something that we really need. But being somewhat formalistic I'm a bit doubtfull about the timing. Ok, you committed it before the freez

Re: [M10N] When to ditch Ant and switch to Maven

Daniel Fagerstrom wrote: * M2 stable enough (2.0 is out so this should be fullfilled) * Reasonably fast (don't need to be as fast as Ant, but not several times slower) For me, this isn't an issue. * Easy configuration of what blocks to compile (like blocks.properties and maybe even depende

[JIRA] Updated workflows

Ok, progress on Jira. As requested, I added the workflow statuses that marks an issue as "on hold" (when waiting for feedback) and "continued" meaning that feedback was received and work should continue. I'm waiting for the changes to propagate through the system now... Pier smime.p7s

Re: [M10N] separating samples from blocks

Joerg Heinicke wrote: On 23.10.2005 13:40, Upayavira wrote: Sorry, I'm afraid I don't understand what you are saying! No problem, let me try a second time: Ralph made a proposal [1] where exactly one block (= directory) per block (= block in the narrower sense) exists, but with many mod

Re: [M10N] separating samples from blocks

Jorg Heymans wrote: Ralph Goers wrote: I don't like this structure much. I prefer /src /blocks /cforms /api pom.xml /impl pom/xml /samples pom.xml

Re: [RT] Is Cocoon Obsolete?

Peter, thanks so much for this, great plug for me to start. Peter Hunsberger wrote: On 9/30/05, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: There was a moment where I could have been one of the first people to respond to this thread, you just happened to ask this question when I was watching

forms documentation updates

Hi, you might have seen the notification mails on the docs list for updates to the forms documentation, but is probably easier if I explain what I've done: * the introductionary sample has been updated to reflect the current state of affairs (jx instead of forms transformer, no use of form.model

Re: Super-easy SQL/Form integration for simple CRUD applications

Daniel Fagerstrom wrote: Sylvain, It seem to be great stuff, and something that we really need. But being somewhat formalistic I'm a bit doubtfull about the timing. Ok, you committed it before the freeze, but not in good enough time to make much community involvment possible before the releas

Re: svn commit: r326930 - in /cocoon/blocks/forms/trunk: java/org/apache/cocoon/forms/event/ java/org/apache/cocoon/forms/formmodel/ java/org/apache/cocoon/forms/resources/ samples/forms/

On 23.10.2005 10:52, Sylvain Wallez wrote: The only case where form behaviour will be different will be for fields that have change listeners but no submit-on-change="true" in the template. These forms will not be broken, but will roundtrip too much to the server. It depends on how you defin

Re: Super-easy SQL/Form integration for simple CRUD applications

Sylvain, It seem to be great stuff, and something that we really need. But being somewhat formalistic I'm a bit doubtfull about the timing. Ok, you committed it before the freeze, but not in good enough time to make much community involvment possible before the release. /Daniel Sylvain Wall

Re: [M10N] separating samples from blocks

Joerg Heinicke wrote: ... Ralph made a proposal [1] where exactly one block (= directory) per block (= block in the narrower sense) exists, but with many modules (in the maven sense) in them: /src /blocks /cforms /api pom.xml

  1   2   >