Stefano Mazzocchi wrote:
on 6/27/03 11:48 AM Stefano Mazzocchi wrote:
As for implementing this, I planned to look into this today.
...
In short, the flow ends up emulating a request as it came from the
outside, while it should emulate it as it came from the inside (as the
cocoon:
Jeff Turner wrote:
I'm not very familiar with the code; is there some cost in keeping the
two-pass CLI alive, in the faint hope that caching comes to its rescue
one day?
Guys,
Before you implement some approach here... Let me suggest something.
Right now sitemap implementation automatically
Upayavira wrote:
Unico,
Okay. But why do you want to create a Cocoon object as
independent from the Cocoon bean? Why can't the bean create
and configure it for you?
1) because CocoonBean is single threaded and I need to run concurrent
requests.
Fair enough.
I'm not
Jeff Turner wrote:
(moving to cocoon-dev..)
On Thu, Jun 26, 2003 at 08:43:12AM +0100, Upayavira wrote:
There are quite a lot of new features in the Cocoon CLI that Forrest
isn't using, for example the option to switch off mime-type checking,
and to only scan pages once (i.e. not using the
Steven Noels wrote:
On 26/06/2003 12:33 yachting heritage wrote:
how could we avoid to received your bloody mail?
sorry, didn't meant to moderate that one through :-|
trying to remotely unsubscribe this friendly person...
Thank you for unsubscribing him from our bloody lists!!!
:)))
[EMAIL PROTECTED] wrote:
cziegeler2003/06/23 11:18:39
Modified:src/blocks/databases/conf blob.xconf
Log:
Updating to latest excalibur datasource - no more JVM dependency :)
Move BlobSource into databases block
Revision ChangesPath
1.2 +1 -1
David Crossley wrote:
I propose Reinhard Pötz to be a Cocoon committer.
Late +1. Congratulations!
Vadim
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
It is with real pleasure that I announce that three cocoon committers
were elected members of the ASF in the last round of votation that ended
today.
Vadim, Sylvain and Carsten (in alphabetical order by their last names)
Hoping that they will
Stefano Mazzocchi wrote:
on 6/23/03 6:22 AM Steven Noels wrote:
On 23/06/2003 11:18 John Morrison wrote:
Sure! Patches always welcome :)
Technically, all Lenya people have Cocoon CVS commit karma if I read the
avail file correctly.
Hmmm, if this is the case, that even
Geoff Howard wrote:
This guy along with a bunch of others found old instructions about
xml-cocoon2
xml-cocoon2 is a symlink right now:
lrwxrwxr-x 1 pier cvsadmin 19 Feb 26 18:23 xml-cocoon2@ -
cocoon-2-historical
and did a cvs checkout of HEAD thinking he was getting 2.1m3-dev.
Can we do
[EMAIL PROTECTED] wrote:
stevenn 2003/06/19 02:02:53
Modified:src/blocks/linotype/samples flow.js
Log:
reverting to original approach
Revision ChangesPath
1.4 +6 -9 cocoon-2.1/src/blocks/linotype/samples/flow.js
Index: flow.js
Pier Fumagalli wrote:
...
So, what do you think? (Surely I need some help to put together the brat)
If it provides getKey and getValidity, than it's much better velocity
than velocity in the cocoon-land!
disclamer value=could be irrelevant
Have you seen discussions on re-implementation of XSP
Joerg Heinicke wrote:
Everything seems to be ok, though you have updated Xalan and Xerces?
Cocoon 2.0.4 comes with Xalan 2.3.1 and Xerces 2.0. This /can/ be
reason, but is not needed to be. I thought more the other way around
(using the Xalan delivered with Sun JDK 1.4).
In conclusion I don't
Joerg Heinicke wrote:
[ -1 ] Release Cocoon 2.1 /immediately/. Carsten suggested the 24th of
June as target date for a first beta release
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=105548603125507w=2),
but do we really need a beta?
Yes, we need beta.
[ +0.5 ] Release Cocoon 2.1 beta
Mato Mira, Fernando wrote:
When trying
map:match pattern=*/baz
map:redirect-to uri=bar/baz/
/map:match
foo/baz will get redirected to foo/bar/baz, not to bar/baz
It's a feature. Redirect sends redirect which is resolved by browser.
Sitemap does not process redirect URI. Thus, if you want to
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
So my question is, why don't we use this implementation, to make Cocoon
more scalable? ;-)
You can. Have you tried it yet?
I guess what Volker means is adding your new implementation from the
scratchpad to excalibur store (btw, you
Stephan Michels wrote:
...
I think I have fixed it, but can't run the tests on windows, because
I got always a
'javac: invalid flag: ... '
during the compilating of the test cases.
Can you help, and run the test, tell me if it works.
It does not fail. ;-)
Vadim
[EMAIL PROTECTED] wrote:
Hi,
additional comment about the performance.
...
It seams that we need to write our own handwritten parser for the URI
stuff. What do you think?
Any specialized parser would be faster than generic parser such as
regexp. And, regexp library is not optimized for
Upayavira wrote:
I'm looking into why the if-modified-since behaviour doesn't work from the
command line.
I've found that it puts a LinkGatherer component into the pipeline, which isn't
cacheable, thus preventing caching. I've added a LinkGathererValidity and set the
key to valid and made
[EMAIL PROTECTED] wrote:
Hi,
I changed the subject because with the old one
(org.apache.excalibur.store.impl.MRUMemoryStore) I didn't get any response
:-(
Vadim any comments?
I still had your original email in the inbox...
Volker
Hi,
org.apache.excalibur.store.impl.MRUMemoryStore should
Upayavira wrote:
It is only mentioned along with the dest-dir node in the cli.xconf.
If I removed that option in the xconf file, setDestDir would go
easily.
No; you don't need to remove the option, and you don't need to change
config file at all. Do you want me to show you how? :)
Go
[EMAIL PROTECTED] wrote:
stevenn 2003/06/06 08:10:59
Modified:src/documentation/xdocs/link livesites.xml
Log:
while I was at it: deleted some host-not-founds and indicated some reservations
...
+lilink href=http://www.bethe1.com/;The EMPLOYMENT specialist in FASHION,
Upayavira wrote:
But what about the dependencies upon them that are outside the scope
of the CLI?
If you are referring to ResolverImplTestCase.java, then it *is* in
scope of CLI.
Haven't a clue what it does.
See source:
public void initialize() throws Exception {
Upayavira wrote:
Vadim,
It is particularly the removal of the Destination interface that
breaks the interface. However, removing the setDestDir will
certainly make a cleaner interface. I'll do that.
I didn't remove it in the end, because it would have taken quite a
bit of
Upayavira wrote:
On 4 Jun 2003 at 23:22, Vadim Gritsenko wrote:
It is particularly the removal of the Destination interface that
breaks the interface. However, removing the setDestDir will certainly
make a cleaner interface. I'll do that.
Thanks. Sorry for me being slow.
Slow
Upayavira wrote:
Found another one: Constants.DEFAULT_WORK_DIR is used by
src/test/org/apache/cocoon/components/resolver/test/ResolverImplTest
Ca se.java
I've moved the lot back. Obviously the comments that I based my move
upon were wrong!
Comments are not wrong... Those constants
Geoff Howard wrote:
At 02:14 AM 6/4/2003, Konstantin wrote:
+1 for lowering the log level to WARN.
But it'd be much better to provide two (or more) typical configurations,
e.g.:
- development: log level - DEBUG, development cache settings, etc.
- testing: log level - WARN, etc.
INFO should
Upayavira wrote:
Fair enough. I've moved it back.
Found another one: Constants.DEFAULT_WORK_DIR is used by
src/test/org/apache/cocoon/components/resolver/test/ResolverImplTestCa
se.java
I've moved the lot back. Obviously the comments that I based my move upon were
wrong!
Comments
Joerg Heinicke wrote:
Though we will get again endorsed lib problem questions on the users
list, I updated the XML lib jars to their latest releases as in Cocoon
2.1. I hope nobody has something against this. At least we have a good
explanation and solution for these issues now
Sylvain Wallez wrote:
Hi all,
Short story : once again, I've hit the famous endorsed library
problem. So as usual I copied Cocoon's Xalan and Xerces to
tomcat/common/endorsed, but unfortunately this broke another
application that was running in the same Tomcat.
Damn. How to solve this ?
Upayavira wrote:
...
It is particularly the removal of the Destination interface that breaks the interface.
However, removing the setDestDir will certainly make a cleaner interface. I'll do that.
Thanks. Sorry for me being slow.
Vadim
Upayavira wrote:
Dear All,
...
The changes include:
1) Improved broken link handling
2) Replaced Destination interface with ModifiableSources
...
uri type=append src-prefix=documents/ src=index.html dest=build/dest//
uri type=replace src-prefix=documents/ src=index.html
Antonio Gallardo wrote:
Steven Noels dijo:
If people need food for discussion, here's my utterly uninformed and
out-of-the-head opinion on these patches:
13070 [PATCH] Add a new tag xsp-session:getxml to XSP
- ditto by Vadim Christian - no reply
I think the ball is not in my side. :)
Carsten Ziegeler wrote:
Torsten Knodt wrote:
On Sunday 01 June 2003 15:51, Carsten Ziegeler wrote:
CZ The safest way is to lookup/release a component every time you
CZ need it, so the fragmentextractor uses the correct approach.
CZ If you know that the component you want to use is ThreadSafe
John Merrells wrote:
On Friday, May 30, 2003, at 03:19 PM, Bertrand Delacretaz wrote:
...
The Cocoon xmldb block uses the org.xmldb API, but IIUC it is limited
to querying databases.
Create / Delete / Update / Query. All is there. See for example
XMLDBTransformer.
I don't know anything
Stefano Mazzocchi wrote:
void callAction(name,map) - invoques the action indicated by the given
name and pass the given map as model
How action returns its result?
If callAction stays... why not:
map act(name, map)
map match(name, pattern, map)
boolean select(name, pattern, map)
Session
Thorsten Mauch wrote:
HI all
I like to add some common methods. As a pure jave programmer
I hate logicsheets ;(
So is it possible to extend the the class XSPGenerator and tell
Cocoon to use this class as a base class for
the XSP ?
No. See xsp.xsl
Vadim
Christopher Oliver wrote:
Vadim Gritsenko wrote:
Christopher Oliver wrote:
FlowVelocityGenerator to replace VelocityGenerator
-1 to replacing: FlowVelocityGenerator introduces dependencies on
org.apache.commons.jxpath and org.mozilla.javascript
Sorry, org.mozilla.javascript
Christopher Oliver wrote:
Vadim Gritsenko wrote:
...
First we are creating blocks for more modular design and the next
thing is we are coupling everything back into monolith. I feel that's
not the right way to go.
We've got more than 5Mb worth of optional JARs (not counting blocks'
libs
Ferenc Kiraly wrote:
Hi!
...
In particular, I wanted to write a logicsheet, that processes a
browseable-table tag. The logicsheet template takes parameters, such as
offset, limit and query. The values for these parameters come from
the request or from the session. I was not able to pass
Stefano Mazzocchi wrote:
...
Anyway, I also fixed a number of security issues. Most notably:
1) uploaded files are saved on disk by default (and web.xml has been
changed accordingly) as a temporary storage.
2) uploaded files saved on disk are removed right at the end of the
request. This
Berin Loritsch wrote:
Hunsberger, Peter wrote:
I've got a large XSLT that dumps out a bunch of stuff for
serialization to
text. If I wrap the text with a start and end element and run it
through
the XML serializer everything runs fine. If I substitute the text
serializer I get no output. A
[EMAIL PROTECTED] wrote:
stefano 2003/04/03 06:16:32
Modified:src/java/org/apache/cocoon/components/request
RequestFactory.java
Log:
removing fixmes and adding explainations
...
try {
ClassLoader loader =
Chris Pratt wrote:
Hi this may be a dumb question, however here goes:
I was able to install onto Tomcat, but when I ry in Weblogic I get teh
following, any ideas?
See cocoon-users email archives. Upgrade your weblogic to at least 6.1sp4.
Vadim
...
Apr 3, 2003 10:12:13 AM BST Debug HTTP
Sylvain Wallez wrote:
snip/
Now from an implementation point of view, finding if a generator is
present by analyzing the sitemap is difficult, if not impossible,
since a generator can be inside a matcher/action/selector (will we go
in that path or not ?), or included in a resource also used in
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
snip/
But once again, I prefer to avoid automagic implicit behaviour of
the sitemap engine, and encourage people to migrate to writing a
map:generate in their error handling and consider implicit generator
and 'type' attributes on handle-error
Sylvain Wallez wrote:
Hi folks,
We have in the 2.1 a number of features that are considered as
deprecated, although still supported. We need a way to inform users
(the ones that write Cocoon apps) that they use such deprecated
features in a way that allows them to be found easily, and not
Stefano Mazzocchi wrote:
snip/
What do you think?
Have you thought about XSPT (XSP for Transformations): XSP-like
transformers on top of STX transformation language syntax?
Vadim
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
...
So I'm thinking about a global logger dedicated to deprecation
messages. This would allow to write all messages going to that
logger to e.g. a deprecated.log file.
...
Nice suggestion; but can't we just use WARN
Sylvain Wallez wrote:
However, allowing a generator in map:handle-errors is incompatible
with the current syntax.
The idea was to allow it and make it *optional*. I.e., if no generator
specified - use noifier, if user specified some generator - use it
instead of default. As you see, syntax
Tony Collen wrote:
Saw this on XML.com how long until we get an stxtransformer? :)
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=104566478723403w=2
Vadim
Joerg Heinicke wrote:
Hello Cocooners,
I updated my local copy of Cocoon 2.1 with the current Fop release
0.20.5rc2.
There is lib/local folder for the local libs. Local is not (should not
be) checked against jars.xml.
I updated the entry in jars.xml, but a CVS update always brings back
Joerg Heinicke wrote:
Vadim Gritsenko wrote:
Joerg Heinicke wrote:
...
There is lib/local folder for the local libs. Local is not (should
not be) checked against jars.xml.
But this would not solve my problem, would it?
I updated the entry in jars.xml, but a CVS update always brings back
ivelin wrote:
...
So, Stefano, since you have your PMC chairman hat on, tell me if we can
create an incubator project.
I will gladly commit the new code to it.
If not, what other options do you suggest.
What about creating an (experimental) branch for xmlform?
Vadim
-=Ivelin=-
From http://dev2dev.bea.com/articles/Dietzen__Goland.jsp:
...BEA and its partners have submitted a reference implementation of the
XML Script technology now being standardized in ECMA to Mozilla's Rhino
project. XML Script is a new technology that makes XML a native data
type of
Geoff Howard wrote:
At 09:50 AM 3/26/2003, you wrote:
Geoff Howard wrote:
Unfortunately, when validate-jars was put back in, an override
mechanism
wasn't added so you're stuck manually editing the build file for now.
I'll be submitting a patch to first of all add the override
mechanism so
[EMAIL PROTECTED] wrote:
crafterm2003/03/26 07:37:09
Modified:src/java/org/apache/cocoon/components/language/markup/xsp/java
xsp.xsl
Log:
* Removed nonexistant import (causes xsp compilation error when using
the eclipse java compiler).
Revision Changes
Marcus Crafter wrote:
Hi Vadim,
Does the attached patch fix it ?
No. You forgot type cast :)
this.manager.release((Component)this.captureParser);
I don't have a test case for the logic sheet.
Take simple.xsp, replace fragment-variable with dom-variable:
capture:dom-variable name=page_part
Jeremy Quinn wrote:
Hi All
I am converting a legacy Cocoon 2.0 site to Cocoon 2.1.
Since when it became legacy? :)
I have documents with the following DOCTYPE declaration:
!DOCTYPE doc SYSTEM urn:kiss:doc
offtopic
Correct me if I'm wrong, but from
Stefano Mazzocchi wrote:
Am I the only one who heard complains about cocoon being very cool but
too hard to 'tune down' to simpler needs?
I'm asking because I'm starting to wonder if this is the case.
puzzled/
It's still 116 mails to go... But no, you are not alone.
Vadim
+1
Vadim
+1
Vadim
Stefano Mazzocchi wrote:
is error-handling inherited?
Only when map:mount / is inside pipeline containing error handler;
then this handler is inherited, so to speak. Anything else is a bug.
AFAIK, 2.0 compiled sitemap is 99.9% bug-less (and 0.1% takes views
must start from the last label
Christopher Oliver wrote:
snip/
Anyway, I was trying to get both of these to be equal in functionality
with Velocity and the JPath Xsp logic sheet.
snip/
This is equivalent to the functionality Ovidiu included in the jpath
Xsp logic sheet.
And this is the functionality that JexlTransformer and
Steven Noels wrote:
On 21/03/2003 13:57 Geoff Howard wrote:
Also, is cocoon-reload still enabled by default? seems a wget in a
loop with ?cocoon-reload=true could put a site in a world of hurt...
(by the way, last time I checked Jetty/Cocoon cvs is barfing on that..)
... and from the
Geoff Howard wrote:
By the way, I think there are bigger security problems in cocoon...
snip/
Also, is cocoon-reload still enabled by default? seems a wget in a
loop with ?cocoon-reload=true could put a site in a world of hurt...
(by the way, last time I checked Jetty/Cocoon cvs is barfing
Stefano Mazzocchi wrote:
It seems that we are converging toward a stable gump setup. This is
very nice and very useful to help us solidify our contracts and make
it visible for other projects underneath our food chain to watch us.
Currently, 6 blocks fail. I'm listing the problems
snip/
the
Stephan Michels wrote:
On 21 Mar 2003 [EMAIL PROTECTED] wrote:
...
/home/rubys/jakarta/cocoon-2.1/src/blocks/slide/java/org/apache/cocoon/components/repository/impl/ContextFileDescriptorsStore.java:61: package slidestore.file does not exist
[javac] import
Santiago Gala wrote:
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
It seems that we are converging toward a stable gump setup. This is
very nice and very useful to help us solidify our contracts and make
it visible for other projects underneath our food chain to watch us.
Currently, 6
Tony Collen wrote:
On Fri, 21 Mar 2003, Geoff Howard wrote:
Is it? With in-memory upload you can get to OutOfMemory exceptions and
potentially corrupt cocoon instance. With file uploads, you can create
100Mb file systems which you can fill up but you won't disturb
functionality of the server.
David Crossley wrote:
Hi Vadim, many thanks to you for fixing the build test.
anteater ain't fixed yet: don't know how to make it work for *nix and
win with same command
Vadim
Marcus Crafter wrote:
snip/
For systems where a subsitemap represents a new application,
behaviour would be configured to be as it currently is.
Why not: for systems where a subsitemap represents a new app, dont
declare anything in the parent sitemap you don't want to expose to
Geoff Howard wrote:
Is it just me or is flow not working? I see there is still a redirect
issue outstanding, and the errors I'm getting may be related to redirect.
I don't have it installed here, but IIRC the preferences sample throws
something like null is not an object when trying to log in
Jeff Turner wrote:
Hi,
Generator, Reader and Transformer all inherit from
SitemapModelComponent, which declares the setup() method:
public interface SitemapModelComponent extends Component {
/**
* Set the codeSourceResolver/code, objectModel
* codeMap/code, the source and sitemap
Stefano Mazzocchi wrote:
Leo Sutic wrote:
From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Very likely
char[] or byte[].
It could be at a very low level, such as Readers and InputStreams.
Could also be this:
http://developer.java.sun.com/developer/bugParade/bugs/4724129.html
Bug Id
Stefano Mazzocchi wrote:
Paul Duffin wrote:
A problem that I ran into was that Serializers do not have access to
the environment (Request / Response). This means that it is very hard
to write sophisticated Serializers.
For example? (I think FOP and batik are both pretty sofisticated
Stefano Mazzocchi wrote:
Vadim Gritsenko wrote:
It's already not easy to separate! I can think of how to resolve
issue 1 (dedicated FlowObjectModelHelper: ugly, but works)
yuck!
So, what do we do? Carsten, may I have your blessing for adding helper
methods to ObjectModelHelper? I can even
Can somebody knowledgable comment on the following method? Local
variable scope is not used...
private Script compileScript(Context cx, Scriptable scope,
Source src) throws Exception {
InputStream is = src.getInputStream();
Reader reader = new
I'm combining two emails into one...
Christopher Oliver wrote:
What defines an application in Cocoon.
Some (not necessarily root) sitemap and all of its subsitemaps can be
seen as one application. Sub-sitemaps can be seen as sub-applications...
For example, does each get a separate class
Stefano Mazzocchi wrote:
Vadim Gritsenko wrote:
Pier Fumagalli wrote:
On 17/3/03 20:15, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
snip/
What about adding a 'content encoding' attribute to the 'pipeline'
instead?
'transfer encoding' attribute would make sense, but content encoding
Stefano Mazzocchi wrote:
David Crossley wrote:
I went to try to resurrect the Lucene search sample today.
However, i cannot find it anywhere in CVS. Was it deliberately
removed or this is an accidental victim of the refactoring?
Damn, you're right. Probably an accidental victim of the
Jeff Turner wrote:
(note: [rt]'s are little [RT]s ;)
...
So, can I check this in, deprecate ResourceExistsAction, and we all
live happily ever after?
Check in resource-exists selector: +1.
Deprecate resource-exists action: +0.
What about resource-exists matcher? ;-)
PS: RT: 1st rule of
Pier Fumagalli wrote:
How does AbstractTextSerializer sets the content type header in the HTTP
response? The getMimeType method inherited from AbstractSerializer always
returns null...
See AbstractProcessingPipeline.java, and see also related to this bug
Steven Noels wrote:
On 18/03/2003 15:12 Vadim Gritsenko wrote:
PS: RT: 1st rule of sitemap component equivalency: Every action could
be renamed to/rewritten as a matcher
Hehe.
2nd rule: any selection of Matchers can be combined into a Selector :-D
Bzzzt!!! Funny but wrong :)
Matchers have
Butler, Mark wrote:
Hi team,
I've been receiving a lot of interest in using DELI with Cocoon 2.04
recently. I've updated the version in the 2.04 cvs repository so that DELI
works correctly and to use the latest version of DELI.
Good.
Question: Are there any plans for further updates to
Christopher Oliver wrote:
Vadim Gritsenko wrote:
Christopher Oliver wrote:
That's not the case. All are equally crippled ;) For example, when
using Xsp, the idea is that the only logic sheet you will ever use
is the jpath logic sheet. This does not give you direct access to
session, request
leo leonid wrote:
On Sonntag, März 16, 2003, at 05:32 Uhr, Christopher Oliver wrote:
leo leonid wrote:
On Freitag, März 14, 2003, at 07:45 Uhr, Christopher Oliver wrote:
the views are pretty much brain-dead: Velocity generating xhtml
directly. It would be neat if we could better show off
Ugo Cei wrote:
o.a.c.components.parser.Parser is deprecated, and if you don't include
the deprecated block in the build, you won't get the class, as expected.
Unfortunately, the XSP logicsheet
(src/java/org/apache/cocoon/components/language/markup/xsp/java/xsp.xsl)
still has an import
Hi there,
I see that there is a problem with ContinuationsManagerImpl class. Also
it may seem that this is proper Avalon component, it's not. It is used
directly from two places:
* WebContinuation.java
* JSCocoon.java
And first one AFAIU is publicly accessible object. Which means that one
Pier Fumagalli wrote:
snip/
But there is a problem... Proxies and caches...
AFAIK (took a look at spec too ;):
If, for example, in my corporation there are two guys, one using Windows in
jp and one using Linux in en_US, if the first guy requests
http://www.vnunet.com/;, I'll deliver the page
Pier Fumagalli wrote:
On 17/3/03 0:16, Vadim Gritsenko [EMAIL PROTECTED] wrote:
snip/
It (?xml? instruction) done via
format.put(OutputKeys.ENCODING,encoding.getValue()) in abstract
serializer itself.
That gets the value out of the serializer configuration itself... So, per
se, we cannot
Pier Fumagalli wrote:
On 17/3/03 20:15, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
snip/
What about adding a 'content encoding' attribute to the 'pipeline' instead?
'transfer encoding' attribute would make sense, but content encoding...
Currently pipeline does not alter content, does
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
So we need two more values in the object model Map : one for the
value dictionary, and one for the continuation.
How does it sound ?
I love it, but, as Carsten correctly pointed out, this will make it
harder to separate
Stefano Mazzocchi wrote:
Cocoon is heavily internationalized but we fail to do one thing:
signal the proper encoding to the user-agent thru HTTP headers, which
is the most reliable way of doing it.
the current *hack* is to use meta tags in the HTML stream,
Ew!
these are interpreted by the
Stefano Mazzocchi wrote:
Ovidiu did a great job showing how the flow could be well integrated
into complex publishing pipelines with the samples we have today, but
I think this is scaring away people that have to simply understand how
things work.
Also, those samples are now dependent on the
Stefano Mazzocchi wrote:
snip/
And, any of these are totally independent from the
internationalization. Internationalization affects language used to
produce output, but not how the text in this language is encoded
(UTF8, UTF16, ISO-1859-1, what-have-you).
true. but you can't have chinese
Christopher Oliver wrote:
I didn't find anything in Eclipse bugzilla. The reports on cocoon-dev
about this seem to all be coming from MacOS X.
It works ok under Win, so it should be platform related issue.
Vadim
I glanced at the code and I don't see an obvious problem (look at
Pier Fumagalli wrote:
snip/
So, in my opinion, the best way to tackle the charset-encoding problem is
to have the org.apache.cocoon.serialization.AbstractTextSerializer to
receive an OutputStream from its implementation of the
SitemapOutputComponent interface, but to expose to its solid
Christopher Oliver wrote:
Sylvain Wallez wrote:
snip/
So we need two more values in the object model Map : one for the
value dictionary, and one for the continuation.
How does it sound ?
That would work.
Excellent! I've grepped sources, seen those awful
((Environment)resolver) type
Pier Fumagalli wrote:
On 17/3/03 2:06, Vadim Gritsenko [EMAIL PROTECTED] wrote:
Practical proposal:
* Add flow-continuation to the objectModel, and getter method to the
ObjectModelHelper, as a replacement for kont environment attribute.
Read only properties of the script (global
1 - 100 of 1099 matches
Mail list logo
