Sylvain Wallez wrote:
Done: the selection list builders are now pluggable components. And I
also wrote the FlowJXPathSelectionList just to test if this worked
properly...
In the back of my mind I'm a little sad because you took away from me
the possibility of making a first, substantial commit
Hi:
I forgot the binding file. Here is the binding definition file:
wb:context
xmlns:wb=http://apache.org/cocoon/woody/binding/1.0;
path=/areasList
wb:repeater id=transaction parent-path=.
row-path=. unique-row-id=are_id unique-path=@are_id
wb:on-bind
wb:value
Another question :)
Currently with ECM we have to implement the Component interface
even if we only use Serviceable (because of the internal
handling with the proxies etc.)
Do we still need this with Fortress? I guess: no.
Carsten
-Original Message-
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
Sent: donderdag 23 oktober 2003 10:29
To: [EMAIL PROTECTED]
Another question :)
Currently with ECM we have to implement the Component
interface even if we only use Serviceable (because of the
internal
As this interface was moved to excalibur sourceresolve, I'd like to
remove it, off course moving all dependencies to the excalibur one. Any
objections?
-- Unico
Perhaps moving it into the deprecated section, first.
We can then remove it for 2.2.
Carsten
-Original Message-
From: Unico Hommes [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 11:13 AM
To: [EMAIL PROTECTED]
Subject: ModifiableTraversableSource
As this interface
OK, I'll do that.
Carsten Ziegeler wrote:
Perhaps moving it into the deprecated section, first.
We can then remove it for 2.2.
Carsten
-Original Message-
From: Unico Hommes [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 11:13 AM
To: [EMAIL PROTECTED]
Antonio Gallardo dijo:
Hi:
Can be wd:repeater the only widget inside a wd:form?
I tought it can be used as a grid table. Example:
Suppuse you have a simple table with 2 fields: are_id and are_name:
Here is the woody definition file:
wd:form
Hmm, I may have spoken too soon.
I am looking into moving
o.a.cocoon.component.source.(Modifiable)TraversableSource into
deprecated area. In order to accomplish this I need to migrate
SlideSource towards that as well.
Now some things are quite different between these interfaces. To give
you an
I've been looking at the authentication block, in order to integrate it
with RoleFilterTransformer using a Filter to support use of
request.isUserInRole().
However after going through it over and over, my opinion is that it is
WAY too overcomplicated, and to add insult to injury, doesn't even
Unico Hommes [EMAIL PROTECTED] wrote:
Hmm, I may have spoken too soon.
I am looking into moving
o.a.cocoon.component.source.(Modifiable)TraversableSource into
deprecated area. In order to accomplish this I need to migrate
SlideSource towards that as well.
And SourceDescriptionGenerator as
Carsten Ziegeler wrote:
Geoff Howard wrote:
[EMAIL PROTECTED] wrote:
ghoward 2003/10/22 18:45:34
Modified:src/webapp/samples/sources sitemap.xmap samples.xml
src/webapp/WEB-INF cocoon.xconf
Added: src/webapp/samples/sources/content upload.xml
If there are any examples of this newer method then ill happily update
the PartSource i've implemented.
Paul
-Original Message-
From: Geoff Howard [mailto:[EMAIL PROTECTED]
Sent: 23 October 2003 12:24
To: [EMAIL PROTECTED]
Subject: Re: cvs commit: cocoon-2.1/src/webapp/WEB-INF
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=24052.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=24052.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
There was a related thread on Avalon dev a few weeks ago that may
interest you:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg08037.html
It also mentions this project on sourceforge:
http://sourceforge.net/projects/aaa4avalon/
Although it's a phoenix block it may be interesting to look at.
Hi:
I am trying to save the bean back from the woody form.
I am getting this error:
org.apache.commons.jxpath.JXPathException: Exception trying to remove
xpath .; Cannot modify property: test.forms.AreasList.areasList; No write
method
What is means? What kind of method is expected to be there?
Just found:
http://sangam.sourceforge.net/
An Eclipse plugin for XP style pair programming. No idea how good it is.
It requires a server (open source Kizna Syncshare
http://www.kizna.org), which I'm not in a position to install. Anyone
into trying it out?
Regards, Upayavira
Geoff Howard
Guido Casper wrote:
Unico Hommes [EMAIL PROTECTED] wrote:
Guido Casper wrote:
I would like to make the following changes to the 2.1 repo
and will
go ahead if noone objects (as soon I find some time):
-Creating a repository block and moving there all source
interfaces
not
Upayavira wrote:
Just found:
http://sangam.sourceforge.net/
An Eclipse plugin for XP style pair programming. No idea how good it is.
It requires a server (open source Kizna Syncshare
http://www.kizna.org), which I'm not in a position to install. Anyone
into trying it out?
Been there, done
Carsten Ziegeler wrote:
I saw the changes from Recyclable to Resettable in 2.2.
What does this mean for existing components? Is Recyclable
still supported?
If that class is loaded, yes. If the Recyclable class is not
available, then the Classloader will not allow the existing
component to load.
Berin Loritsch wrote:
Carsten Ziegeler wrote:
I saw the changes from Recyclable to Resettable in 2.2.
What does this mean for existing components? Is Recyclable
still supported?
If that class is loaded, yes. If the Recyclable class is not
available, then the Classloader will not
Berin Loritsch wrote:
Carsten Ziegeler wrote:
Another question :)
Currently with ECM we have to implement the Component interface
even if we only use Serviceable (because of the internal
handling with the proxies etc.)
Do we still need this with Fortress? I guess: no.
No,
Carsten Ziegeler wrote:
Berin Loritsch wrote:
Carsten Ziegeler wrote:
I saw the changes from Recyclable to Resettable in 2.2.
What does this mean for existing components? Is Recyclable
still supported?
If that class is loaded, yes. If the Recyclable class is not
available, then the
Carsten Ziegeler wrote:
Berin Loritsch wrote:
Carsten Ziegeler wrote:
Another question :)
Currently with ECM we have to implement the Component interface
even if we only use Serviceable (because of the internal
handling with the proxies etc.)
Do we still need this with Fortress? I guess: no.
Berin Loritsch wrote:
So, we can remove it from everywhere (in 2.2). Should we do it?
There is no reason I can think of that would require it...
Sometime in the future, Component will be really deprecated and then we have
to remove it in order to get rid off the nice warnings. Perhaps, we
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=23949.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Joerg Heinicke wrote:
http://www.securiteam.com/securitynews/6W00L0U8KC.html
Hey, someone wanted to test the Cocoon community :-)
Joerg
Hm, I think we should consider releasing 2.1.3 as a security update.
Thoughts?
Tony Collen wrote:
Hm, I think we should consider releasing 2.1.3 as a security update.
Thoughts?
Not just for that but for incorporating all the fixes that were done at
the GT and more.
But, can we please make sure that the test suite runs, this time?
Otherwise, +1 from me.
Ugo
--
Ugo Cei
Hi all,
I have some concerns and would like to share with you. Sorry if these has already been discussed or sounds non-sense. Anyway, I will be glad to hear your voices (I am not in the dev list, so please in case you post a reply send me a copy too).
1- I know that Cocoon provides different
On Tue, 21 Oct 2003, Sylvain Wallez wrote:
snipped/
Ok, I understand. I encountered a somehow similar problem and came to
the conclusion that what we need is actually to have wd:selection-list
a pluggable component.
We could then have wd:selection-list
Tony Collen dijo:
Joerg Heinicke wrote:
http://www.securiteam.com/securitynews/6W00L0U8KC.html
Hey, someone wanted to test the Cocoon community :-)
Joerg
Hm, I think we should consider releasing 2.1.3 as a security update.
Thoughts?
+1 A new release right now!
Antonio Gallardo
Tony Collen wrote:
Joerg Heinicke wrote:
http://www.securiteam.com/securitynews/6W00L0U8KC.html
Hey, someone wanted to test the Cocoon community :-)
Joerg
Hm, I think we should consider releasing 2.1.3 as a security update.
+1 I thought Carsten had already proposed a date because of the
First of all, sorry for the massive cross-post, but I think it is going
to be a great opportunity for all the communities involved to show off
their potentials with the apache infrastructure.
The proposal is about the creation of a content management system for
apache projects, codenamed Doco
Hi Stefano,
I think the overall concept for this project is pretty cool and very
well thought out.
The one part that stands out to me as a weak link is the reply vs.
reply to all mechanism. It seems prone to human errors and to things
like vacation messages. How would conflicts be handled
Giacomo Pati wrote:
Why not just have the @src of the selection-list check the protocol
used to distinguish the type?
That's a possibility I evaluated, but keep in mind that you need to
specify also the name of the properties used to retrieve the key and
value from each object in the collection.
hi:
I am testing woody. In this sample:
http://localhost:/samples/woody/form2bean.flow
Try this:
1.Press Add contact
2.Press Submit query
3.Press (on the top of your browser) Back
4.Press Submit query
Can you see the repeated Herman row?
Please explain.
Best Regards,
Antonio Gallardo
Nice one... I put a summary of it all in Bugzilla.
/LS
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]
Unico Hommes [EMAIL PROTECTED] wrote:
-Adding a setSourceProperty() method to the
SourceInspector interface
Already have it on my local copy. :-)
Cool! So I leave this to you :-)
Actually I think it's better to define a subinterface named
SourceDescriptor that defines these methods. This
Hello,
in my opnion it would be nice to have a method like getParameterMap() from
Servlet programming which returns all request parameters as name value pairs
in a hash map. This method should reside in interface
org.cocoon.apache.environment.Request oder http.HttpRequest.
Do you agree with
Stephan Coboos wrote:
in my opnion it would be nice to have a method like getParameterMap() from
Servlet programming which returns all request parameters as name value pairs
in a hash map. This method should reside in interface
org.cocoon.apache.environment.Request oder http.HttpRequest.
- Original Message -
From: Ugo Cei [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 9:11 PM
Subject: Re: [suggestion] Method getParameterMap in Request?
Stephan Coboos wrote:
in my opnion it would be nice to have a method like getParameterMap()
from
Servlet
On Tue, 21 Oct 2003, Sylvain Wallez wrote:
Hi team,
I'd like to add the use of leniency to JXPath expressions in
JXTemplateGenerator: currently, if a path does not exist, a nice
exception is thrown. This may be good in some circumstances (avoids
endless hair pulling sessions to finally
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=21536.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=21536.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=21536.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=21536.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
47 matches
Mail list logo
