Bruno Dumon wrote:
OTOH, having the docs
split up between a lot of little maven-sites might lessen the overview.
Because of the nature of Daisy this shouldn't become a problem:
- we can have one navigation document which is a collection of all
block navigation docs
- we have Daisy books
* Reinhard Poetz:
> For those of you, who think that blocks will never get finished - here a
> short list on our achievments so far:
>
> - splitting up of the monolytic Cocoon core has started by Daniel's
>refactorings
> - we use Spring as component framework and finally got rid of ECM, Ava
Bruno Dumon wrote:
On Mon, 2006-03-06 at 18:39 +0100, Reinhard Poetz wrote:
hepabolu wrote:
Finally, adding the proposed plugin can always be added later without
loosing the effort of the current setup.
ok, that's right. Anyway, I can't do it myself now but if somebody is
interested, I ca
On Tue, 2006-03-07 at 09:06 +0100, Reinhard Poetz wrote:
> Bruno Dumon wrote:
>
> > OTOH, having the docs
> > split up between a lot of little maven-sites might lessen the overview.
>
> Because of the nature of Daisy this shouldn't become a problem:
>
> - we can have one navigation document wh
[ http://issues.apache.org/jira/browse/COCOON-1793?page=all ]
Ugo Cei reassigned COCOON-1793:
---
Assign To: Ugo Cei
> [PATCH] Enum selection list with apache enum support and null-text
> --
>
>
[
http://issues.apache.org/jira/browse/COCOON-1793?page=comments#action_12369188
]
Ugo Cei commented on COCOON-1793:
-
Looks like you forgot to add the PreferredContact class to your patch (forgot
to svn add, maybe?).
> [PATCH] Enum selection list with apa
[ http://issues.apache.org/jira/browse/COCOON-1793?page=all ]
Simone Gianni updated COCOON-1793:
--
Attachment: enumselectionlist-samples2.diff
Yeah, right, forgot svn add :) this is the patch for it.
> [PATCH] Enum selection list with apache enum suppor
[ http://issues.apache.org/jira/browse/COCOON-1793?page=all ]
Ugo Cei closed COCOON-1793:
---
Fix Version: 2.1.9-dev (current SVN)
Resolution: Fixed
Applied. Please cross-check.
> [PATCH] Enum selection list with apache enum support and null-text
> ---
[ http://issues.apache.org/jira/browse/COCOON-1707?page=all ]
Jean-Baptiste Quenot updated COCOON-1707:
-
Attachment: 20060307-cocoon-ldaptr
Proposed patch
> Allow configuration of initial context in LDAPTransfor
[ http://issues.apache.org/jira/browse/COCOON-1707?page=all ]
Jean-Baptiste Quenot updated COCOON-1707:
-
Attachment: (was: 20060307-cocoon-ldaptr)
> Allow configuration of initial context in LDAPTransfor
[ http://issues.apache.org/jira/browse/COCOON-1707?page=all ]
Jean-Baptiste Quenot updated COCOON-1707:
-
Attachment: 20060307-cocoon-ldaptr
Updated patch
> Allow configuration of initial context in LDAPTransfor
[PATCH] Propagation of namespaces to a repeaters child bindings and
implementation of a move-node binding
-
Key: COCOON-1794
URL: http://issues.apache.org/jira/browse/COCOON-1
Jean-Baptiste Quenot wrote:
* Reinhard Poetz:
- [cocoon-deployer-webapp-sample] is a very simple example. Here we need
something more useful. We have to identify blocks that we want
to show. I suggest
# cforms + samples
# ctemplate + samples
# auth + samples
# session-fw + samples
* Reinhard Poetz:
> Jean-Baptiste Quenot wrote:
> > * Reinhard Poetz:
>
> >> Except cforms all these blocks are not shared between 2.1 and changing
> >> cforms shouldn't be a big problem as the cforms directories are
> >> references from 2.1 on a very detailed level. Right?
> >Can you elaborate
[
http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369260
]
Max Pfingsthorn commented on COCOON-1794:
-
This is an interesting topic. However, retrospectively moving the rows around
doesn't seem to be the best way to solve thi
Jean-Baptiste Quenot wrote:
In cocoon-deploy.xml you can define which _concrete_ blocks that
*you* in the role of the deployer want to use to satisfy a
requirement.
So if we write an Eclipse plugin to configure deployment, we will
have to edit both cocoon-deploy.xml and pom.xml?
I updated SVN and tried to run the block deployment samples
(cocoon-deployer-webapp-sample or cocoon-deployer-plugin-demo) and get the
following stacktrace:
25336 [BoundedThreadPool0-1] WARN org.mortbay.log - /p1/test
org.apache.avalon.framework.configuration.ConfigurationException: Could not l
Hello everybody,
to get Apache FOP 0.91 beta working with Cocoon, a new Serializer is
necessary (the FOP API changed considerably). I wrote a very simple but
working Serializer and hope that helps a little for future releases of
Cocoon. The Serializer doesn't accept any configuration except 'mime-
Please add it to our issue tracker Jira at
https://issues.apache.org/jira/browse/COCOON for organizational and
especially legal reasons.
Thanks.
Jörg
On 07.03.2006 19:52, Alexander Lochschmied wrote:
Hello everybody,
to get Apache FOP 0.91 beta working with Cocoon, a new Serializer is
neces
[
http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369295
]
Suzan Foster commented on COCOON-1794:
--
I don't think the InsertNodeJXPathBinding is the correct place to implement
positioning. Positioning doesn't imply insertion as
Reinhard Poetz wrote:
> I updated SVN and tried to run the block deployment samples
> (cocoon-deployer-webapp-sample or cocoon-deployer-plugin-demo) and get the
> following stacktrace:
>
>
> Any ideas?
>
Yupp :) This is due to a change I did last week; the change is not
finished as I wanted to
21 matches
Mail list logo
