Re: svn commit: r179405 - in /cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/event: EventManager.java Publisher.java Receiver.java Register.java aspect/EventAspectContext.java impl/DefaultEventManager.java
Ralph Goers wrote: Do you have any details of where you want to go with this? Is it safe to assume you want to deprecate Subscriber? Yepp - the whole event manager/subscriber/publisher/register thing is imho way too complex. So I merged publisher and register into the event manager and simplified the subscriber (which is now called receiver). During the various projects we've done with the portal, it turned out that most of the work is adding your own events and create some subscribers for the events. And I think the current solution requires too much coding. For example the new Receiver interface passes not only the event but also the PortalService to the receiver, so the receiver has access to the whole portal without requiring to implement any lifecycle methods. I have no concrete ideas yet, but I want to simplify the receiver in a way that you don't have to implement the interface anymore (Don't know how yet :) ). And I'm interested in enabling scriptable event receivers - for example write your receiver in flow script. But these are just some rough ideas. While sort of on the same topic, I would like to move in the direction of not exposing event ids in URLs, at least as far as possible. I started this with a couple of events but I haven't done all the ones that could be. Yeah, this is a very annoying topic. If you have any suggestions we should talk about them. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Logkit jvadocs
Niclas Hedhman wrote: IMHO, the long-term(!) strategy should be to use the JDK Logging as the API, and innovative people will figure out how to redirect that to Log4J or something else. Yes, my thoughts go in the same direction: why not use the JDK logging? It's available and doesn't require any additional jar. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Logkit jvadocs
Vadim Gritsenko wrote: ATM, I'd say do what you want as long as: * Cocoon 2.1 stays as it is. * Cocoon 2.2 can be run with LogKit. I.e., I'm ok if you switch default to Log4J and remove logkit.jar, as long as I can put it back and change the default back to LogKit. Yes, it will be possible to configure LogKit in 2.2 then, with one difference: the bootstrap logging (or whatever you call) - the logging before the logging system is initialized will not be done using LogKit. But this should be transparent as well (I think). Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [SUMMARY] Caching DynamicSelectionList
Antonio Gallardo wrote: On Mar, 31 de Mayo de 2005, 16:26, Joerg Heinicke dijo: Vadim's comments made me think again about the caching of selection lists. And I don't think having a shorter cache period than a form processing (as part of one request) makes no sense as it leads to inconsistent forms when a selection list is reused. Please explain. More this. Are you telling a cache life shorter than a request, makes or not makes sense? Sorry, for the above question. Too much negation on the sentence got me confused. Having this you *can* use time-based caching as you just need to check the cache validity on first access to the source during the form processing. During the form processing you always use the same (buffered) selection list. Now I can think of optimizations of the above when you only use a selection list (or the source it is based on to be exact) once in a form: there is no need for buffering. Yep. I told that in one of my first mails. It can also be stated as: caching matter only inside a repeater. Can this be determined? Yep. If (the selection-list widget has not a repeater as ancestor) OR ((the selection list widget if has a repeater as ancestor) AND (the repeater has less than 2 rows) Now the other validity scopes. I do not have a real idea how to configure it. @cache=request|form|session|static? (Is current static bound to form instance or even longer? If it is the first it will be the same like what I had in mind with form). 1. per request (I have this already implemented on my HD, including the lastest comments about how to implement it). 2. Per form, What I understand here is to cache all the selection-list and use the cache until the form is finished. 3.per session. Valid while the user is logged in. Refreshed on each new login. 4.static. As it is implemented now. About 2 and 3. I believe there are some usecases for them. What I am not sure is if the time effort vs. gain is important enough to add more complexity. Maybe, yes, but I will be glad to see them first. And check if this is OK. IMO the complexity is in setting up the cache mechanism. Adding new scopes (i.e. cache durations) is then mostly a matter of finding the right place to store the cached data. Time based caching can be easily done on the pipeline as we know or using the cached: pseudo protocol, but then you still either have no buffered selection list sax events or you need an object holding the buffer with the necessary lifetime. Currently, I only create the buffer if there is the corresponding flag. I don't think it can create problems for time based cache. BTW, I don't committed, because I want to know the final keywords for @cache. We can start with static and request, and add other values later. Are we going to deprecate @dynamic? Yes. Use of @dynamic should be logged as deprecated. Also, the default behavior should be changed to either cache=none or cache=request, whereas today it's similar to cache=static. Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: Google Summer of Code - projects and mentors wanted
Bertrand Delacretaz wrote:
Cocoonistas,
You might have noticed yesterday's announcement at
http://code.google.com/ about the Summer of Code initiative,
http://code.google.com/summerofcode.html
We should have more detailed info for the ASF communities in the next
few days (we're still ironing out the details about project sandboxes,
CLAs etc.), but as the initiative is public already, project
propositions are welcome at
http://wiki.apache.org/general/SummerOfCode2005.
Each project needs to have at least one mentor (who must be a committer
AFAIK, but various models might be possible) to happen, so that students
are not lost in the dark.
I have entered a project at
http://wiki.apache.org/general/SummerOfCode2005#cocoon-refdoc, and I'm
looking for at least one co-mentor, as I'll be partially offline in July
and August. If someone's available for this, please let me know.
Are we allowed to offer another project? I would like to propose
http://issues.apache.org/bugzilla/show_bug.cgi?id=33324
(http://wiki.apache.org/cocoon/FlowscriptAndSessionReplication).
I volunteer as mentor and as Betrand I'm looking for a co-mentor as I will be
offline for two or three weeks.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
Re: Google Summer of Code - projects and mentors wanted
Le 2 juin 05, à 11:56, Reinhard Poetz a écrit : ...Are we allowed to offer another project? I would like to propose http://issues.apache.org/bugzilla/show_bug.cgi?id=33324 (http://wiki.apache.org/cocoon/FlowscriptAndSessionReplication)... Sure, there's no problem in having several Cocoon-related projects! -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Google Summer of Code - projects and mentors wanted
Bertrand Delacretaz wrote:
Le 2 juin 05, à 11:56, Reinhard Poetz a écrit :
...Are we allowed to offer another project? I would like to propose
http://issues.apache.org/bugzilla/show_bug.cgi?id=33324
(http://wiki.apache.org/cocoon/FlowscriptAndSessionReplication)...
Sure, there's no problem in having several Cocoon-related projects!
Fine! Any volonteers for the role of the second mentor?
---
One question to the role of the mentor: AFAIU it's about guiding him but I won't
be able to answer all questions in detail - if I could I would have done it
myself ;-)
Am I right here?
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: Google Summer of Code - projects and mentors wanted
Le 2 juin 05, à 12:22, Reinhard Poetz a écrit : ...One question to the role of the mentor: AFAIU it's about guiding him but I won't be able to answer all questions in detail - if I could I would have done it myself ;-).. That's how I understand it: the mentor is the contact person, can help about where to find the answers but does not necessarily know them. See also http://code.google.com/mentfaq.html under What is the role of a mentoring organization?. IMO all this will be the mentor's responsibility for the mentored projects. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Google Summer of Code - projects and mentors wanted
Reinhard Poetz wrote: Bertrand Delacretaz wrote: Le 2 juin 05, à 11:56, Reinhard Poetz a écrit : ...Are we allowed to offer another project? I would like to propose http://issues.apache.org/bugzilla/show_bug.cgi?id=33324 (http://wiki.apache.org/cocoon/FlowscriptAndSessionReplication)... Sure, there's no problem in having several Cocoon-related projects! Fine! Any volonteers for the role of the second mentor? --- One question to the role of the mentor: AFAIU it's about guiding him but I won't be able to answer all questions in detail - if I could I would have done it myself ;-) Am I right here? The way I see it is that the design discussion should occur through the normal develpoment channels, so the idea is they do some background work and come back to the community with a proposal or RT, once the design is complete they have to implement it. Again, problems are solved through the normal community channels. Ross
Re: Google Summer of Code - projects and mentors wanted
Ross Gardler wrote:
Reinhard Poetz wrote:
Bertrand Delacretaz wrote:
Le 2 juin 05, à 11:56, Reinhard Poetz a écrit :
...Are we allowed to offer another project? I would like to propose
http://issues.apache.org/bugzilla/show_bug.cgi?id=33324
(http://wiki.apache.org/cocoon/FlowscriptAndSessionReplication)...
Sure, there's no problem in having several Cocoon-related projects!
Fine! Any volonteers for the role of the second mentor?
---
One question to the role of the mentor: AFAIU it's about guiding him
but I won't be able to answer all questions in detail - if I could I
would have done it myself ;-)
Am I right here?
The way I see it is that the design discussion should occur through the
normal develpoment channels, so the idea is they do some background work
and come back to the community with a proposal or RT, once the design is
complete they have to implement it. Again, problems are solved through
the normal community channels.
Bertrand and Ross, thanks for your answers. Find the project description at
http://wiki.apache.org/general/SummerOfCode2005#cocoon-flowscript-serialization.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: Google Summer of Code - projects and mentors wanted
Reinhard Poetz wrote:
http://wiki.apache.org/general/SummerOfCode2005#cocoon-refdoc
http://wiki.apache.org/general/SummerOfCode2005#cocoon-flowscript-serialization.
Do we have something else on our wishlists (some fancy cforms features, etc.)?
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
RE: Google Summer of Code - projects and mentors wanted
Do we have something else on our wishlists (some fancy cforms features, etc.)? An effort to substancially reduce the number of open issues in bugzilla? Bye, Helma
Re: Google Summer of Code - projects and mentors wanted
Reinhard Poetz wrote: Reinhard Poetz wrote: http://wiki.apache.org/general/SummerOfCode2005#cocoon-refdoc http://wiki.apache.org/general/SummerOfCode2005#cocoon-flowscript-serialization. Do we have something else on our wishlists (some fancy cforms features, etc.)? I posted the answer under wrong subthread: 1. we still have not touched the subject of attribute driven template language. it would nicely suit as a project that could be finished till the end of summer. 2. cforms reusable widget repository... -- Leszek Gawron [EMAIL PROTECTED] IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Google Summer of Code - projects and mentors wanted
Linden H van der (MI) wrote:
Do we have something else on our wishlists (some fancy cforms
features, etc.)?
An effort to substancially reduce the number of open issues in bugzilla?
I have thought about something similar too but it is difficult to set it up as
single project with a clearly defined project goal.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: Google Summer of Code - projects and mentors wanted
Linden H van der (MI) wrote: Do we have something else on our wishlists (some fancy cforms features, etc.)? An effort to substancially reduce the number of open issues in bugzilla? we still have not touched the subject of attribute driven template language. it would nicely suit as a project that could be finished till the end of summer. -- Leszek Gawron [EMAIL PROTECTED] IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Google Summer of Code - projects and mentors wanted
Leszek Gawron wrote:
1. we still have not touched the subject of attribute driven template
language. it would nicely suit as a project that could be finished till
the end of summer.
2. cforms reusable widget repository...
yes, I like both ideas! Who wants to mentor the projects? Tim, Leszek?
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: Google Summer of Code - projects and mentors wanted
Reinhard Poetz wrote: Reinhard Poetz wrote: http://wiki.apache.org/general/SummerOfCode2005#cocoon-refdoc http://wiki.apache.org/general/SummerOfCode2005#cocoon-flowscript-serialization. Do we have something else on our wishlists (some fancy cforms features, etc.)? Web service integration. It is a common user requirement and we have a number of implementations with various properties and also some variants within Cocoon. But we have nothing coherent yet. Also the Axis 2.0 architecture seem quite interesting. I'm interested enough to do some mentoring in the area but not enough to implement anything in the near future. /Daniel
Re: Google Summer of Code - projects and mentors wanted
Reinhard Poetz wrote: Leszek Gawron wrote: 1. we still have not touched the subject of attribute driven template language. it would nicely suit as a project that could be finished till the end of summer. 2. cforms reusable widget repository... yes, I like both ideas! Who wants to mentor the projects? Tim, Leszek? I can at least be a co-mentor for the attribute driven templates. /Daniel
Re: Google Summer of Code - projects and mentors wanted
Le 2 juin 05, à 13:51, Reinhard Poetz a écrit : ...Do we have something else on our wishlists (some fancy cforms features, etc.)? People with ideas are welcome to write them up at http://wiki.apache.org/general/SummerOfCode2005, even if no mentor is available yet. In that case, putting dev@cocoon.apache.org as the contact address and a note like we're still looking for a mentor would be ok. If some of us are thinking of mentoring one project but not more, it might help in doing a dynamic allocation of mentors to projects which actually happen. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Google Summer of Code - projects and mentors wanted
Reinhard Poetz wrote: Leszek Gawron wrote: 1. we still have not touched the subject of attribute driven template language. it would nicely suit as a project that could be finished till the end of summer. 2. cforms reusable widget repository... yes, I like both ideas! Who wants to mentor the projects? Tim, Leszek? I propose that me and Daniel (as he already agreed in other post) co-mentor template project and Tim does the cforms (if he wants to of course). I would surely love to contribute in both areas. -- Leszek Gawron [EMAIL PROTECTED] IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: Google Summer of Code - projects and mentors wanted
Linden H van der (MI) wrote: Do we have something else on our wishlists (some fancy cforms features, etc.)? An effort to substancially reduce the number of open issues in bugzilla? Unfortunately, the bugs in bugzilla are likely to require a level of knowledge of Cocoon that we are unlikely to meet in any of our students, which is a shame :-( We really need to think of interesting projects that they are likely to be attracted to, and that form clearly defined and measurable projects. Regards, Upayavira
Re: Google Summer of Code - projects and mentors wanted
Linden H van der (MI) wrote: An effort to substancially reduce the number of open issues in bugzilla? IMO this would be more something for a FirstFriday if these are still happening. Jorg
RE: Re: Google Summer of Code - reinstate FirstFridays?
Linden H van der (MI) wrote: An effort to substancially reduce the number of open issues in bugzilla? IMO this would be more something for a FirstFriday if these are still happening. Sounds good to me too. Why was the idea dropped in the first place? I haven't joined them but got the impression that it were fun times for the committers. Bye, Helma
Re: Google Summer of Code - projects and mentors wanted
Leszek Gawron wrote: Reinhard Poetz wrote: Leszek Gawron wrote: 1. we still have not touched the subject of attribute driven template language. it would nicely suit as a project that could be finished till the end of summer. 2. cforms reusable widget repository... yes, I like both ideas! Who wants to mentor the projects? Tim, Leszek? I propose that me and Daniel (as he already agreed in other post) co-mentor template project and Tim does the cforms (if he wants to of course). I would surely love to contribute in both areas. Wrote a proposal for ATL: http://wiki.apache.org/general/SummerOfCode2005#cocoon-atl Leszek, add your email and update the description if you want to change or add anything. /Daniel
Re: Google Summer of Code - reinstate FirstFridays?
Le 2 juin 05, à 15:11, Linden H van der ((MI)) a écrit : ...Sounds good to me too. Why was the idea dropped in the first place? I haven't joined them but got the impression that it were fun times for the committers... I don't think it was formally dropped, but it died for lack of active participants. And yes it was fun! -Bertrand smime.p7s Description: S/MIME cryptographic signature
reinstate (themed) FirstFridays?
Linden H van der (MI) wrote: IMO this would be more something for a FirstFriday if these are still happening. Sounds good to me too. Why was the idea dropped in the first place? I haven't joined them but got the impression that it were fun times for the committers. +1 I don't think the idea was officially dropped, just went to sleep quietly AFAICT. How about coming up with one or more specific (but not restrictive) themes for each First Friday? It could get people more motivated and helps to keep the gathering more focussed. The primary goal of FF (to gather and chat about all things cocoon) stays ofcourse. If Firstfriday takes off again we should really consider my proposal [1]. Any infra@ aware people around that can help us out here ? WDYT? Jorg [1] http://article.gmane.org/gmane.text.xml.cocoon.devel/50579
Re: Google Summer of Code - projects and mentors wanted
Sylvain Wallez wrote: Ralph Goers wrote: Reinhard Poetz wrote: Do we have something else on our wishlists (some fancy cforms features, etc.)? What about some ajax stylings for cforms? Some I'd love to have are: - cocoon suggests ajax styling for cforms fields providing autocompletion of inputs, - reorderable repeaters [1] 1. Convert all poolable gnerators, and transformers to be thread safe. +1 2. Modify the build process to use maven. ... or rewrite the ant builds to use the library task and without generating the blocks build file with XSLT. Don't want to rain on the party, but this is *summer* of code, meaning 2 months of work[2]. Expecting students to implement difficult things (e.g. continuations serialization) or cleaning up the bugzilla, even all this is badly needed, seem too complicated to me for a student discovering our code base. So subjects that have a chance to be successful in terms of candidates and result are those that don't need to much in-depth knowledge of the core and have a clear functionnal scope. Agreed. However, before creating proposals it would also be nice to know that there is buy-in from the committers that a proposal should be made. I wouldn't want to propose something that other committers would object to. Sylvain [1] http://tool-man.org/examples/edit-in-place.html#listExamples [2] http://code.google.com/summfaq.html Ralph
Re: Google Summer of Code - projects and mentors wanted
On Jue, 2 de Junio de 2005, 16:50, Sylvain Wallez dijo: Ralph Goers wrote: Reinhard Poetz wrote: Do we have something else on our wishlists (some fancy cforms features, etc.)? What about some ajax stylings for cforms? Some I'd love to have are: - cocoon suggests ajax styling for cforms fields providing autocompletion of inputs, - reorderable repeaters [1] What about the XUL interface for cforms? I will like to add this project. First I want to know what you think about this 2 months task? http://issues.apache.org/bugzilla/show_bug.cgi?id=25295 Best Regards, Antonio Gallardo
dynamic datasource connection
Hi, I need to connect to an ms access database, but the database is constantly changing. Is there a way to dynamically connect to the database using cocoon? I noticed that you have to tell cocoon.xconf beforehand what database to connect to, is there a way to pass in the database url? thanks cc _ Don't just Search. Find! http://search.sympatico.msn.ca/default.aspx The new MSN Search! Check it out!
