Is there a bug in the latest source resolver? I'm ready to fix it if
someone can come up with a test case which does not require to get
Cocoon running.
Carsten
Carsten Ziegeler:
Jorg Heymans wrote:
nope, its mine. I didn't test the new release thorough enough
before upgrading. So
[moving over a discussion from [EMAIL PROTECTED] to [EMAIL PROTECTED]
Bruno Dumon wrote:
Which also makes me think of it: the Cocoon zone is still running Daisy
1.5. I could do the upgrade, but I'm not sure on the impact this might
have. The maven plugin should be easy to upgrade, but I think
I'm currently working on the our build system and it might happen that it is
temporarily broken. I'll let you know when it is stable again.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
Hi Thorsten,
Well I think the suggestion-list content must be served by a different
thread. Here is my scenario in a little more detail:
I created a patch to make suggestion-lists support on-value-changed
events and they seem to work nicely. When debuging the FormInstance
class I can see how
Online report :
http://vmbuild.apache.org/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/291/buildId/141373
Build statistics:
State: Failed
Previous State: Ok
Started at: Thu, 10 May 2007 02:04:58 -0700
Finished at: Thu, 10 May 2007 02:07:34 -0700
Total time: 2m
NekoHTMLTransformer needs to set the default-encoding of the current system to
work properly with UTF-8
---
Key: COCOON-2063
URL:
[
https://issues.apache.org/jira/browse/COCOON-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated COCOON-2063:
--
Attachment: nekohtmltransformer-encoding.patch
Affects cocoon-html-impl.
[
https://issues.apache.org/jira/browse/COCOON-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494682
]
Alexander Klimetschek commented on COCOON-2063:
---
I forgot to mention that if someone wants to
Grzegorz Kossakowski said the following on 9/5/07 22:09:
Take a look at the snippet above, it's long trail of useless information
- noise. I know that you are as lazy as I'm but there is solution for
Thunderbird users:
https://addons.mozilla.org/pl/thunderbird/addon/612
I hope you will like
Reinhard Poetz said the following on 10/5/07 09:33:
[moving over a discussion from [EMAIL PROTECTED] to [EMAIL PROTECTED]
Bruno Dumon wrote:
Which also makes me think of it: the Cocoon zone is still running Daisy
1.5. I could do the upgrade, but I'm not sure on the impact this might
have. The
hepabolu napisał(a):
Grzegorz Kossakowski said the following on 9/5/07 22:09:
I hope you will like it. :-)
And for those not fluent in Polish:
https://addons.mozilla.org/en-US/thunderbird/addon/612
:-)
Oups, I thought that language is not encoded in URL and bases on browser
settings.
I
hepabolu napisał(a):
Reinhard Poetz said the following on 10/5/07 09:33:
[moving over a discussion from [EMAIL PROTECTED] to [EMAIL PROTECTED]
Bruno Dumon wrote:
Which also makes me think of it: the Cocoon zone is still running Daisy
1.5. I could do the upgrade, but I'm not sure on the impact
Hi,
I have added a how-to for getting the encoding right in a Cocoon
webapplication using CForms, Ajax and Dojo. It assumes that everything
should be UTF-8. The most important new information is setting dojo to do
Ajax calls in UTF-8. Took me a long time to understand all that and putting
Alexander Klimetschek pisze:
Hi,
I have added a how-to for getting the encoding right in a Cocoon
webapplication using CForms, Ajax and Dojo. It assumes that everything
should be UTF-8. The most important new information is setting dojo to
do Ajax calls in UTF-8. Took me a long time to
Hi Reinhard,
although it's a full webapplication and not a live site, it would be cool to
have Mindquarry (http://www.mindquarry.com - The OpenSource Collaborative
Software) listed as using Cocoon 2.2-dev on
http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g1/g1/706.html.
A site
hepabolu wrote:
Reinhard Poetz said the following on 10/5/07 09:33:
[moving over a discussion from [EMAIL PROTECTED] to [EMAIL PROTECTED]
Bruno Dumon wrote:
Which also makes me think of it: the Cocoon zone is still running Daisy
1.5. I could do the upgrade, but I'm not sure on the impact this
Daniel Fagerstrom pisze:
Grzegorz Kossakowski skrev:
Looking at the AbstractProcessingPipeline the getMimeType method of the
serializer is called from the setMimeTypeForSerializer method that in
turn is called in the beginning of the processXMLPipeline method
*before* the
Reinhard Poetz said the following on 10/5/07 14:51:
Daisy 2.0.X changes the name of the document in the url (1.html -
1-NS.html with NS = a namespacecode), which means you have to redo the
publishing all over again because the link to the Daisy page breaks
after the upgrade.
I don't see a
hepabolu wrote:
I don't see a reason why we need the namespace in our published URLs
at all. The Daisy plugin could cut them off.
Sure, and I'm all for cutting it off, but in Daisy the namespace is
there so backlink from the published page should go to the namespaced
version.
Now:
Daisy:
Grzegorz Kossakowski schrieb:
I only wonder why you did put docs in wiki instead of Daisy? I believe
that all the tips should be part of our documentation. Is my assumption
wrong anyhow?
I cannot edit daisy and find the Wiki easier anyway. Well, copying it over
should be easy, if I get write
Alexander Klimetschek pisze:
Grzegorz Kossakowski schrieb:
I only wonder why you did put docs in wiki instead of Daisy? I believe
that all the tips should be part of our documentation. Is my
assumption wrong anyhow?
I cannot edit daisy and find the Wiki easier anyway. Well, copying it
over
Grzegorz Kossakowski wrote:
Alexander Klimetschek pisze:
Grzegorz Kossakowski schrieb:
I only wonder why you did put docs in wiki instead of Daisy? I
believe that all the tips should be part of our documentation. Is my
assumption wrong anyhow?
I cannot edit daisy and find the Wiki easier
Alexander Klimetschek pisze:
Hi Reinhard,
although it's a full webapplication and not a live site, it would be
cool to have Mindquarry (http://www.mindquarry.com - The OpenSource
Collaborative Software) listed as using Cocoon 2.2-dev on
Reinhard Poetz wrote:
I'm currently working on the our build system and it might happen that
it is temporarily broken. I'll let you know when it is stable again.
done.
I created a profile daisy that contains everything which is necessary to
create our site. This has the advantage that
Alexander Klimetschek wrote:
Hi Reinhard,
although it's a full webapplication and not a live site, it would be
cool to have Mindquarry (http://www.mindquarry.com - The OpenSource
Collaborative Software) listed as using Cocoon 2.2-dev on
Reinhard Poetz wrote:
hepabolu wrote:
I don't see a reason why we need the namespace in our published URLs
at all. The Daisy plugin could cut them off.
Sure, and I'm all for cutting it off, but in Daisy the namespace is
there so backlink from the published page should go to the namespaced
Username jackivers
Want to updated the professional services listing.
Thanks - Jack
Reinhard Poetz schrieb:
Alex, what's your Daisy username?
alexander.klimetschek
--
Alexander Klimetschek
http://www.mindquarry.com
Grzegorz Kossakowski schrieb:
What about?:
Mindquarry.org - the site running instance of a
href=http://www.mindquarry.com;Mindquarry's/a OpenSource
Collaborative Software suite.
Mindquarry.org - the site running an instance of a
href=http://www.mindquarry.com;Mindquarry's/a OpenSource
On 10 May 2007, at 21:14, Alexander Klimetschek wrote:
Reinhard Poetz schrieb:
Alex, what's your Daisy username?
alexander.klimetschek
I gave you editor and commit access on Daisy.
/Steven
--
Steven Noelshttp://outerthought.org/
Outerthought
On 10 May 2007, at 21:02, [EMAIL PROTECTED] wrote:
Username jackivers
Want to updated the professional services listing.
Done.
/Steven
--
Steven Noelshttp://outerthought.org/
Outerthought Open Source Java XML
stevenn at
Grzegorz Kossakowski wrote:
Given that mime type (and other http header informations) are calculated
during setup phase of service's pipeline setup phase it's guaranteed
that this information can be properly determined without providing any
content (in service call, it's POSTed one). Thus,
Daniel Fagerstrom wrote:
Looking at the AbstractProcessingPipeline the getMimeType method of the
serializer is called from the setMimeTypeForSerializer method that in
turn is called in the beginning of the processXMLPipeline method
*before* the generator.generate() method that lead to the
Peter Hunsberger wrote:
Apparently somewhere between the 2.1.6 and 2.1.8 release the ability
to use the cocoon: protocol from an XSL stylesheet run via flow and
processPipelineTo has been broken or intentionally removed. Anyone
know why or if a release after 2.1.8 brings it back?
I bet it
34 matches
Mail list logo
