I can see a lot of uses for this
Hi All
Is there some demand for a JMX interface for Cocoon?
This could be very usefull in a J2EE environment, as it was in my last project.
I built these functions below as a cocoon block which I could spend to the community.
- ClearCacheMBean (the
I've hit this - it only happens when compiling the stylesheet though. Concurrent
requests right at
startup do not do wel...I had no workaround...but that would be a GOOD THING to have
fixed...
Hi Cocooners,
Are their any other Cocoon users having Threading Issues with xsltc?
Its seems that
Bart Guijt wrote:
Hi there,
As a result of gaining some hands-on Cocoon experience, I created a JavadocSource
and
-SourceFactory which largely complies to what you are discussing here.
...
Yes! Yes! Wow!
Obviously a donation is most welcome, we need this to implement our User
Has anyone built a genreator for XLS files? I looked around the source tree and didn't
see
anything.
THanks!
--
The heights of genius are only measurable by the depths of stupidity.
-
To unsubscribe, e-mail: [EMAIL
There isa serializer there - but no generator from what I can see
it's in the blocks area
xml-cocoon2/src/blocks/poi
Andy Lewis wrote:
Has anyone built a genreator for XLS files? I looked around the source tree and
didn't see
anything.
THanks
understoodthanks...
That's what I thought you meant by generator, not very familiar with cocoon
vernacular ;)
sorry!
Andy Lewis wrote:
There isa serializer there - but no generator from what I can see
it's in the blocks area
xml-cocoon2/src/blocks/poi
Andy Lewis wrote
I have a need to, under specific circumstances, do a RequestDispatcher.forward out of
Cocoon. I've
not found any support for this in Cocoon. Alternatives won't work since I need to do
this while
preserving request attributes. I would expect to be able to code this as an Action
without extreme
If I actually get it working, I would certinaly contribute it. Yeah, ugly, but
probalby no really
CLEAN way to achieve it.
At any rate, many thanks for the guidance - I'll go with a reader. I suspected that
using the
wrong componenet would cause me grief
Vadim Gritsenko wrote:
Andy Lewis
what about I/O terms?
sendPageBlocking
sendPageNonBlocking
or something akin to these?
Sylvain Wallez wrote:
Michael Melhem wrote:
On Wed, Dec 04, 2002 at 02:19:33PM +0100, Sylvain Wallez wrote:
Marcus Crafter wrote:
Hi Troops!
Hope all is well.
I've just checked in
With the caveat that I read the list, but have not worked with many of the features I
read about,
wouldn't it be posible to create a set of Input Modules to do validation? I recall a
discussion
about having input modules be able to wrap other input modules, so you should simply
be able to
Thier product has been around since 1998...so they have been around too...still
unfortunate though.
I just don't get it. Don't these guys do any kind of research before naming their
product?
Cocoon XSP's have been around for quite some time now.
If I would have been these guys I would
To satisfy my own curiosity, I actualy asked them about it, and got this response. I
should point
out that in retrospect my inital email to them was, well, slightly more abrasive than
it ought to
jave been, for which I did follow-up with an apology. At any rate, here was the reply
I got:
If
I could see uses for it - very similar to what you suggest. However I was instead
looking into
achiving the same thing with the Request Generator, the Fragment Extractor and internal
pipelines...
A long long time ago Carsten Ziegeler wrote:
Nearly all generators could be rewritten as sources,
How about code snipptets as well?
There was a brief thread the other day that struck me as a perfect candidate - the
correct way
to get the parser component
Diana Shannon wrote:
... It would be
wonderful to have a library of sitemap/pipeline snippets, to give users
ideas how to
I've tried a complete wipe of the directory and re-checkout from CVS and still have no
luck.
My environment is Mandrake 8.1 and Sun JDK 1.3.1_03
I'm getting:
Apache Cocoon Build System
--
Buildfile: build.xml
init:
Thanks...got it...I think.
I'll be interested to hear how the research comes out
Andy Lewis wrote:
If I have a custom transformer or generator that I wanted to deploy as a part of
Coccon block,
can I using that interface? And is it an Avalon component or not? Are there
adidtional
snip /
So, I picture Cocoon being (or containing) two different containers:
- an avalon component container (could be Fortress or Merlin)
- a cocoon block container (could be based on Phoenix or we make our
own)
In that case, the way you write, use and deploy 'avalon components' in
I've watched this thred for quite a while. Some people don't like XML, some people
don't like
Javascript. It was mentioned on here earlier, and I think it bears repeating:
What is the definition of the problem?
I know, everyone has a general sense of it. But before picking a language, perhaps
How about ICE?
I've got a Cocoon-friendly ICE 1.1 effort underway. If I get it working.(amidst
the myriad of
other things going on)
Besides ICE 2.0 is beingrefactored for SOAP integration...so it would be a shame to
miss out on
that
Following is an initial draft of a new component I
Just a suggestion here on item 2 - take it for what it is worth.
The recommended way to improve performance is with something like SQUID - a proxy
cache. THat is
the approahc I take, and by all accounts it works well. Unfortunately, out of the
box Cocoon
doesn't have that, so it appears
I'm fine with SQUID...my was relating to a way to improive perceived performance of
the base
distribution
From: Andy Lewis [mailto:[EMAIL PROTECTED]]
Just a suggestion here on item 2 - take it for what it is worth.
The recommended way to improve performance is with something
like
I really like the philosophy behind what Berin is proposing here. You do
need to understand the lifecycle you are working in for component usage,
but how is that new
From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
From: Leo Sutic [mailto:[EMAIL PROTECTED]]
Berin,
I am 75% for
I've always maintained that the key difference between an object and a
component is granularity. Both can be reusable, but a component generally
represents a (reusable) encapsulation of a conceptually larger chunk of
logic/data than a typical object.
From: Leo Sutic [mailto:[EMAIL PROTECTED]]
snip/
If you to change Transformer interface to return only
XMLSource/ContentHandler, all the logic and state Transformer has moves
into this XMLSource.
Thus, XMLSource becomes heavy and Transformer light. Obviously,
Transformer becomes ThreadSafe (which is good) and XMLSource must be
snip/
Yes, if they share same ... how you call it? ... scope: both are
ThreadSafe or Poolable (by nature). Here, one (Transformer) will be
ThreadSafe (or even not a component (it's too lightweight for it)), and
other (XMLSource) - Poolable.
Thus, you can not keep an instance of XMLSource
I'm not a committer here - but I think this is a excellent way to handle
it...
Matthew Langham wrote:
I discussed this with Sylvain and we both were not sure of the Apache
side of things. Perhaps someone can comment on what is allowed in
the sense of tolerated. Thanks.
Ok, a few comments
so do the lawyers you use to render it unenforcable. With the current
state of IP law, only the lawyers win.
On Wednesday 29 May 2002 02:58 am, you wrote:
RedHat\'s patent applications
...
How can you fight this kind of evil, when an \inventor\ simply
combines two trivial techniques
27 matches
Mail list logo
