Re: DITA and Cocoon
I'm interested to this discussion too. Please keep it on list. Angelo -- Initial Header --- From : Ross Gardler [EMAIL PROTECTED] To : users@cocoon.apache.org Cc : Date : Sat, 15 Oct 2005 21:02:46 +0100 Subject : Re: DITA and Cocoon Bertrand Delacretaz wrote: Le 15 oct. 05, à 17:21, J.D. Williams a écrit : I use DITA and Cocoon for my own Web site as a way of exploring both. I'd be interested in discussing a possible collaboration offline... Note that it doesn't have to be off-list, discussions about DITA wouldn't be off-topic here I think - and others might be interested in your experiences. Yes, the Forrest community want to build a DITA input plugin, this is actually needed by the Derby project here in Apache. I did do some preliminary exploration with the Derby folk, who provided some useful info and links. Please keep the discussion on list so that we can bring it all together. Ross - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: RE: Unintentional Caching with Tomcat 5.5.x]
On 15.10.2005 19:07, Carsten Ziegeler wrote: The uri is used as a default for the cache key. You can include parameters and any additional information in the key if you need to. You can define your own cache key by setting a parameter on the pipeline: map:pipeline type=expires map:parameter name=cache-key value=SOMETHING/ So, you can e.g. use input modules to add the uri and the request parameters in there. Nice to know. I guess it is not documented somewhere [1], is it? Jörg http://cocoon.apache.org/2.1/userdocs/concepts/caching.html#Expiration+of+Content - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Return xml from an Action to the pipeline?
I have a pipeline that is successfully producing web pages. I would like to create a report using Jasper Reports (which is just a simple java library) and then insert that report back into one of my web pages. Jasper Reports can output to xml so this should be possible. I am open to suggestions for how to do this. If put the creation of the xml report into an Action, It seems like I should be able to return the xml and have it merge back into the pipeline. An Action returns a Map - and I can put whatever I want into that Map, so I thought about putting the xml result in there and then accessing it the pipeline. I'm how I'm not sure to get at it in the pipeline, or how to merge it into the xml that was already in the pipeline before I called the Action. So, Jasper Reports aside, my question (assuming the above method is sound) is a more general 2 part question: 1) How do I return xml from an Action and access it in the pipeline? 2) How to I merge that xml document into the one that the pipeline is processing?
[CForms] Encoding Problem with CForms
Hi, I got my application up and running nicely except one small encoding-problem which is driving me nuts. I load an Xml-Document, which contains German umlauts If I print this to the console, everything is ok I load the Dom into the form debug output widget.lookupWidget(xyz).getValue() tells me the umauts are ok. When the page is displayed in the Browser everything is ok. When the Submit button is hit, and I do the widget.getValue() stuff again, the umlaus are all crappy how can I make the umlauts be sent back in the correct form? Chris
Re: [CForms] Encoding Problem with CForms
Hi Christofer, make sure the encoding you use in your files form definition matches the form-encoding parameter of your servlet engine, specified in web.xml - I'm devoloping on linux, using utf-8 as default file encoding + form encoding and had to set the form-encoding param to utf-8 like this: /!--/ / Set form encoding. This will be the character set used to decode request/ / parameters. If not set the ISO-8859-1 encoding will be assumed./ /--/ *init-param* *param-name*form-encoding*/param-name* *param-value*UTF-8*/param-value* */init-param* HTH, Johannes Christofer Dutz schrieb: Hi, I got my application up and running nicely except one small encoding-problem which is driving me nuts. I load an Xml-Document, which contains German umlauts If I print this to the console, everything is ok … I load the Dom into the form … debug output widget.lookupWidget(“xyz”).getValue() tells me the umauts are ok. When the page is displayed in the Browser everything is ok. When the Submit button is hit, and I do the widget….getValue() stuff again, the umlaus are all crappy … how can I make the umlauts be sent back in the correct form? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Getting started (again)
You can find the blog/forum web site script package at: http://sourceforge.net/projects/shapecms/ It is an early release. I hope you can get it running. Hans - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DITA and Cocoon
Given that there is widespread interest for something like this, how would you recommend we move ahead? Collaboratively capturing requirements and use-cases for a DITA app seems like a good place to start. Lenya or Daisy might make good starting points, or perhaps it would be best to start from scratch. In terms of cocoon technology my preference is XMLDB + CFORMS. Hibernate might be appropriate too for persistence, but since DITA is XML-based why would one want to work in the object-model realm? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Return xml from an Action to the pipeline?
Lachlan Paterson wrote: I have a pipeline that is successfully producing web pages. I would like to create a report using Jasper Reports (which is just a simple java library) and then insert that report back into one of my web pages. Jasper Reports can output to xml so this should be possible. I am open to suggestions for how to do this. If put the creation of the xml report into an Action, It seems like I should be able to return the xml and have it merge back into the pipeline. An Action returns a Map - and I can put whatever I want into that Map, so I thought about putting the xml result in there and then accessing it the pipeline. I'm how I'm not sure to get at it in the pipeline, or how to merge it into the xml that was already in the pipeline before I called the Action. So, Jasper Reports aside, my question (assuming the above method is sound) is a more general 2 part question: 1) How do I return xml from an Action and access it in the pipeline? 2) How to I merge that xml document into the one that the pipeline is processing? Actions should not return XML. Why not write a generator instead? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Where to put a generator
is putting my own class/package/jar in WEB-INF a good or bad idea? i've managed to keep all my documents out of COCOON_HOME by using the mount-table.xml file. it would be nice if i keep my java sources somewhere seperate as well, as i don't want them to get entangled with the cocoon build process. -- _jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Return xml from an Action to the pipeline?
Having never created a generator, I can't comment on that, but it sounds
like a good idea. Can anyone estimate how much effort this requires?
Another way might be call the java lib from flowscript, creating a DOM.
Then pass the DOM to a JXTemplate (along with any other DOMs you want to
'merge' with). The flowscript would look as follows:
var reportDom = Way.To.Create.Dom.From.Some.Java.Lib();
var otherDom = Way.To.Load.Your.Other.Dom();
cocoon.sendPage(merge-jxpipe, {reportDom : reportDom, otherDom:
otherDom } );
The JXTemplate could be as simple as the following:
to-merge
report
#{reportDom/*}
/report
other
#{otherDom/*}
/other
/to-merge
Then you could use XSLT to do the merge.
Lachlan Paterson wrote: ...
So, Jasper Reports aside, my question (assuming the above method is
sound) is a more general 2 part question:
1) How do I return xml from an Action and access it in the pipeline?
2) How to I merge that xml document into the one that the pipeline is
processing?
Actions should not return XML. Why not write a generator instead?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Return xml from an Action to the pipeline?
Is it possible to have two generators and then merge the results?On 10/16/05, Combinational Logic [EMAIL PROTECTED]
wrote:Having never created a generator, I can't comment on that, but it sounds
like a good idea.Can anyone estimate how much effort this requires?Another way might be call the java lib from flowscript, creating a DOM.Then pass the DOM to a JXTemplate (along with any other DOMs you want to
'merge' with).The flowscript would look as follows:var reportDom = Way.To.Create.Dom.From.Some.Java.Lib();var otherDom = Way.To.Load.Your.Other.Dom();cocoon.sendPage(merge-jxpipe, {reportDom : reportDom, otherDom:
otherDom } );The JXTemplate could be as simple as the following:to-mergereport#{reportDom/*}/reportother#{otherDom/*}
/other/to-mergeThen you could use XSLT to do the merge.Lachlan Paterson wrote: ... So, Jasper Reports aside, my question (assuming the above method is sound) is a more general 2 part question:
1) How do I return xml from an Action and access it in the pipeline? 2) How to I merge that xml document into the one that the pipeline is processing?Actions should not return XML. Why not write a generator instead?
-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail:
[EMAIL PROTECTED]-To unsubscribe, e-mail:
[EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where to put a generator
Hi Jason, it would be nice if i keep my java sources somewhere seperate as well, as i don't want them to get entangled with the cocoon build process. I've been down the same road as you. Like you I wondered how to keep my code seperate from Cocoon's. There are many good reasons for attempting this but the main one is to reduce the trauma involved every time a new release of Cocoon emerges. My solution was to create an Ant task which merged bits of Cocoon with bits of my project and placed the resulting hybrid in a 'testing' directory. It works, but isn't very optimal. For example, if I edit 'my' sitemap I can't get Cocoon to auto-load it until I've run the ant task to copy the edited version into the testing directory. Well... this was obviously a common concern because at the last Cocoon get together they announced the 'Brick' example. See http://www.cocoongt.org/Slides-and-recordings.html for a PDF and download the lecture audio by Bertrand Delacretaz called Cocoon Bricks: best practices by example. As well as a lot of common sense the Brick example comes with an Ant based build system that should address both your and my needs. Regards, David Legg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Return xml from an Action to the pipeline?
I think this would be possible with
cinclude. Each generator would have its own pipeline. One of your generators
would generate cinclude tags that pull in XML from the other generator/pipeline.
From: Lachlan Paterson
[mailto:[EMAIL PROTECTED]
Sent: Sunday, October 16, 2005
3:39 PM
To: users@cocoon.apache.org
Subject: Re: Return xml from an
Action to the pipeline?
Is it possible to have
two generators and then merge the results?
On 10/16/05, Combinational
Logic [EMAIL PROTECTED]
wrote:
Having never created a
generator, I can't comment on that, but it sounds
like a good idea.Can anyone estimate how much effort this requires?
Another way might be call the java lib from flowscript, creating a DOM.
Then pass the DOM to a JXTemplate (along with any other DOMs you want to
'merge' with).The flowscript would look as follows:
var reportDom = Way.To.Create.Dom.From.Some.Java.Lib();
var otherDom = Way.To.Load.Your.Other.Dom();
cocoon.sendPage(merge-jxpipe, {reportDom : reportDom, otherDom:
otherDom } );
The JXTemplate could be as simple as the following:
to-merge
report
#{reportDom/*}
/report
other
#{otherDom/*}
/other
/to-merge
Then you could use XSLT to do the merge.
Lachlan Paterson wrote: ...
So, Jasper Reports aside, my question (assuming the above method is
sound) is a more general 2 part question:
1) How do I return xml from an Action and access it in the pipeline?
2) How to I merge that xml document into the one that the pipeline is
processing?
Actions should not return XML. Why not write a generator instead?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
'Hello World' for Cocoon component builders?
I'm exhausted! I've spent the last week wading through terse web pages and
trying everything I can think of with little to show for it.
All I want to do is create a component that gets configured with parameters
from cocoon.xconf and initialized at startup. The trouble is I seem to have
fallen into a maze of twisting passageways! I can't find any native Cocoon
component tutorial so I'm having to pick my way through obsolete Avalon,
Pico, YAAFI stuff and it's doing my head in!
In theory I love the idea of component management. In practice I'm finding
the entry price is too high.
So... can anyone point me to somewhere that explains in simple terms how to
create and add a Cocoon component?
I've tried creating a simple class which extends AbstractLogEnabled and
implements Initializable but I think I must be doing something wrong in the
cocoon.xconf file because try as I might the initialize() method is never
being called.
Here's an extract of my component class: -
public class MyComponent extends AbstractLogEnabled implements Initializable
{
...
public MyComponent() {
getLogger().debug(HELLO WORLD - Constructor has been called);
throw new Exception(This is a test within constructor);
}
...
public void initialize() throws Exception {
getLogger().debug(HELLO WORLD - initialize has been called);
throw new Exception(This is a test within initialize);
}
}
and here's what I've put in cocoon.xconf: -
component class=com.test.MyComponent logger=core.startup
parameter name=my-path value=/a/path/to/somewhere
/component
I never see either of the exceptions triggered or the strings appearing in
any log file. I am assuming that for this simple class I don't need to
define a role?
Any advice would be appreciated.
Regards,
David Legg.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: 'Hello World' for Cocoon component builders?
I haven't done this in quite a while, but I'm pretty sure you need to
add a role for your class in user.roles
-Justin
On Oct 16, 2005, at 7:15 PM, David Legg wrote:
I'm exhausted! I've spent the last week wading through terse web
pages and trying everything I can think of with little to show for it.
All I want to do is create a component that gets configured with
parameters from cocoon.xconf and initialized at startup. The
trouble is I seem to have fallen into a maze of twisting
passageways! I can't find any native Cocoon component tutorial so
I'm having to pick my way through obsolete Avalon, Pico, YAAFI
stuff and it's doing my head in!
In theory I love the idea of component management. In practice I'm
finding the entry price is too high.
So... can anyone point me to somewhere that explains in simple
terms how to create and add a Cocoon component?
I've tried creating a simple class which extends AbstractLogEnabled
and implements Initializable but I think I must be doing something
wrong in the cocoon.xconf file because try as I might the initialize
() method is never being called.
Here's an extract of my component class: -
public class MyComponent extends AbstractLogEnabled implements
Initializable {
...
public MyComponent() {
getLogger().debug(HELLO WORLD - Constructor has been called);
throw new Exception(This is a test within constructor);
}
...
public void initialize() throws Exception {
getLogger().debug(HELLO WORLD - initialize has been called);
throw new Exception(This is a test within initialize);
}
}
and here's what I've put in cocoon.xconf: -
component class=com.test.MyComponent logger=core.startup
parameter name=my-path value=/a/path/to/somewhere
/component
I never see either of the exceptions triggered or the strings
appearing in any log file. I am assuming that for this simple
class I don't need to define a role?
Any advice would be appreciated.
Regards,
David Legg.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
