Re: DO NOT REPLY [Bug 24767] - [PATCH] Hello World Example for M$ Word 2003 XML Format

Hi! Thanks Tony, for applying the patch. Can you confirm that there's some garbage when viewing the file page2wordml.xsl in viewcvs with mozilla? http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/webapp/samples/hello-world/style/xsl/page2wordml.xsl?rev=1.1&content-type=text/vnd.viewcvs-markup IE

Re: DO NOT REPLY [Bug 24767] - [PATCH] Hello World Example for M$ Word 2003 XML Format

Andreas Hochsteger wrote: Hi! Thanks Tony, for applying the patch. Can you confirm that there's some garbage when viewing the file page2wordml.xsl in viewcvs with mozilla? http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/webapp/samples/hello-world/style/xsl/page2wordml.xsl?rev=1.1&content-type=

Re: DOM Protocol, Was: Revised ResourceLoadAction posted...

Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: If I extend it to handle request / session / application context, which seem like a good idea, what syntax would be reasonable? dom:/[request,session,context]/attribute-name/xpath or maybe one should be a little bit more specific: dom:/[request-

Re: XSP "official" position

* Vadim Gritsenko <[EMAIL PROTECTED]> [2003-11-18 03:03]: > Gianugo Rabellino wrote: > > >Interesting comments here at ApacheCon. Some users are still convinced > >that we're pushing XSP as the prominent way to build interactive stuff > >and web applications. Actually on the site there is no par

Re: cvs commit: cocoon-2.1/src/blocks/linotype/misc powered-by-cocoon.psd powered by cocoon.psd

[EMAIL PROTECTED] wrote: crossley2003/11/17 17:52:09 Added: src/blocks/linotype/misc powered-by-cocoon.psd Removed: src/blocks/linotype/misc powered by cocoon.psd Log: Replace silly Win filename with something sensible. Could not find any reference to this image in the app.

Re: whitespace cleanup and efficiency drive

Vadim Gritsenko wrote: > David Crossley wrote: > >Joerg Heinicke wrote: > > > >>The result of this thread: let's care only about white spaces. > > > >So now we need a policy. Here is my proposal: > > > >For all text files > >- Replace all tabs with spaces. > >- No trailing whitespace. > >- No M$-D

Re: XSP "official" position

David Rogers wrote: Regarding the comment on needing English skills...I can help out there. I fancy my self a bit of a tech writer. I have "fixed" just a bit of snuff in the wiki but don't want to write anything there that is incorrect. I bet there are a few others that could help as well. I am f

Re: DOM Protocol, Was: Revised ResourceLoadAction posted...

Sylvain Wallez wrote: Vadim Gritsenko wrote: My initial though was to have following syntax: dom:[request|session|context]:# Xpath, and '#' symbol is obviously optional, and '#' was chosen for consistency with existing xmldb: protocol. Just some thoughts: - why "dom" only? We should also

Separating build system sources from Cocoon sources

Hello, folks, when trying to integrate gump2blocks.properties.xsl I came across some mixtures in our sources, which I would like to solve. Partly we mixed the sources of our build system with the Cocoon sources. In particular src/targets/*-build.xml and src/resources/dev/**. Those things are no

Re: XSP "official" position

Alain Javier Guarnieri del Gesu wrote: * Vadim Gritsenko <[EMAIL PROTECTED]> [2003-11-18 03:03]: Gianugo Rabellino wrote: Interesting comments here at ApacheCon. Some users are still convinced that we're pushing XSP as the prominent way to build interactive stuff and web applications. A

session in authentication context

Hi, I thought the dev list might be a better place for an insight to this problem : I'm using the authentication framework to get and modify authentication data from a user. I use the sitemap structure shown in the last paragraph of this page : http://cocoon.apache.org/2.1/deve

Re: XSP "official" position

On Mon, Nov 17, 2003 at 09:01:57PM -0600, Antonio Gallardo wrote: > I really no wonder why peope still think XSP is the great Gig in the > Cocoon town, because if you google around you will feel this is the way > Cocoon goes. To be honest I don't google about this for a long time but > still early

Re: XSP "official" position

On Mon, Nov 17, 2003 at 09:16:23PM -0600, Tony Collen wrote: > Vadim Gritsenko wrote: > > > > > > >XSP if not perfect, but we still need some kind of "official" > >templating. What's the alternatives here? > > > >... and it's not that convinient to assemble DOM (or something) in flow > >and th

Re: DOM Protocol, Was: Revised ResourceLoadAction posted...

[EMAIL PROTECTED] wrote: Vadim Gritsenko wrote: My initial though was to have following syntax: dom:[request|session|context]:# Xpath, and '#' symbol is obviously optional, and '#' was chosen for consistency with existing xmldb: protocol. I like the "#" part, but all the ":" looks st

Re: XSP "official" position

Tony Collen wrote: Vadim Gritsenko wrote: XSP if not perfect, but we still need some kind of "official" templating. What's the alternatives here? ... and it's not that convinient to assemble DOM (or something) in flow and then pass it to the templates... ;-) Even the JXTemplateGenerator? I

Re: Separating build system sources from Cocoon sources

Joerg Heinicke wrote: Hello, folks, when trying to integrate gump2blocks.properties.xsl I came across some mixtures in our sources, which I would like to solve. Partly we mixed the sources of our build system with the Cocoon sources. In particular src/targets/*-build.xml and src/resources/dev/

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

[EMAIL PROTECTED] wrote: tony2003/11/17 23:30:23 Modified:src/webapp/samples/hello-world/style/xsl page2wordml.xsl Log: saving file as UTF-8 Revision ChangesPath 1.2 +43 -46cocoon-2.1/src/webapp/samples/hello-world/style/xsl/page2wordml.xsl Index: page2wordml.

Re: session in authentication context

julien bloit wrote: Hi, I thought the dev list might be a better place for an insight to this problem : May be, but dev list is much less tolerable to html mail. Please fix your client to send plain text only. Vadim

Re: XSP "official" position

Gianugo Rabellino wrote: Interesting comments here at ApacheCon. Some users are still convinced that we're pushing XSP as the prominent way to build interactive stuff and web applications. Actually on the site there is no particular endorsement of XSP, but there not either a word of warning ab

Re: XSP "official" position

Gianugo Rabellino wrote: Interesting comments here at ApacheCon. Some users are still convinced that we're pushing XSP as the prominent way to build interactive stuff and web applications. Actually on the site there is no particular endorsement of XSP, but there not either a word of warning abou

Re: cvs commit: cocoon-site/src/documentation/content/xdocs/community committer.xml book.xml

[EMAIL PROTECTED] wrote: Here is one way to find files that have DOS line-endings: find . -type f | xargs grep -l '^M' (to add the ^M use "Ctrl-v Ctrl-m" at the command-line). Here is one way to find files that have any hidden control characters:

Re: XSP "official" position

Torsten Curdt wrote: Gianugo Rabellino wrote: Interesting comments here at ApacheCon. Some users are still convinced that we're pushing XSP as the prominent way to build interactive stuff and web applications. Actually on the site there is no particular endorsement of XSP, but there not either

Re: XSP "official" position

If you wanna compare you need to compare Flow vs. Actions and XSP vs. Transformers (or other server pages / templating approaches). The discussion really takes a strange way when comparing these both concepts. ...not any stranger than comparing Flow vs. XSP ;) IMO it's obvious: the mixture of

Re: DOM Protocol, Was: Revised ResourceLoadAction posted...

Vadim Gritsenko wrote: Sylvain Wallez wrote: Vadim Gritsenko wrote: My initial though was to have following syntax: dom:[request|session|context]:# Xpath, and '#' symbol is obviously optional, and '#' was chosen for consistency with existing xmldb: protocol. Just some thoughts: - why "dom"

Re: cvs commit: cocoon-2.1 blocks.properties

Geoff Howard wrote: Joerg Heinicke wrote: [EMAIL PROTECTED] wrote: cziegeler2003/11/13 02:18:28 Modified:.blocks.properties Log: Exclude JMS for the release; otherwise Cocoon doesn't compile with 1.3 :( We have to find a better solution for the next version *All* bloc

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

[EMAIL PROTECTED] wrote: jeremy 2003/11/18 05:16:34 Modified:src/blocks/woody/samples/resources woody-field-styling.xsl Log: My sincere appologies, I committed the wrong project Undoing my changes (I HOPE!!!) Revision ChangesPath 1.15 +0 -5 cocoon-2.1/src

Re: XSP "official" position

Torsten Curdt wrote: If you wanna compare you need to compare Flow vs. Actions and XSP vs. Transformers (or other server pages / templating approaches). The discussion really takes a strange way when comparing these both concepts. ...not any stranger than comparing Flow vs. XSP ;) Flow vs. XS

Re: DOM Protocol, Was: Revised ResourceLoadAction posted...

Daniel Fagerstrom wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: Vadim Gritsenko wrote: My initial though was to have following syntax: dom:[request|session|context]:# Xpath, and '#' symbol is obviously optional, and '#' was chosen for consistency with existing xmldb: protocol. Jus

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: jeremy 2003/11/18 05:16:34 Modified:src/blocks/woody/samples/resources woody-field-styling.xsl Log: My sincere appologies, I committed the wrong project Undoing my changes (I HOPE!!!) Revision ChangesPath 1.15 +

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

Sylvain Wallez wrote: Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: jeremy 2003/11/18 05:16:34 Modified:src/blocks/woody/samples/resources woody-field-styling.xsl Log: My sincere appologies, I committed the wrong project Undoing my changes (I HOPE!!!) Revision Chan

Re: DOM Protocol, Was: Revised ResourceLoadAction posted...

Daniel Fagerstrom wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: Vadim Gritsenko wrote: My initial though was to have following syntax: dom:[request|session|context]:# Xpath, and '#' symbol is obviously optional, and '#' was chosen for consistency with existing xmldb: protocol. Jus

Re: XSP "official" position

Joerg Heinicke wrote: Torsten Curdt wrote: XSP leaves room for heavy abuse! I guess that's the major problems. ...plus that debugging is a pain :) Exactly, we must do it impossible to abuse it :-) Going towards an XML only template language would also allow to have an interpreter instead of c

Re: Separating build system sources from Cocoon sources

Joerg Heinicke wrote: Hello, folks, when trying to integrate gump2blocks.properties.xsl I came across some mixtures in our sources, which I would like to solve. Partly we mixed the sources of our build system with the Cocoon sources. In particular src/targets/*-build.xml and src/resources/dev/*

Re: XSP "official" position

Leszek Gawron wrote: Jakarta commons has something called DBUtils (http://jakarta.apache.org/commons/dbutils/index.html) - I do not know the functionality but I suppose if this was wrapped with Scriptable I think it would be very useful. Mmmmh... Populating a JS object directly from a ResultS

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: tony2003/11/17 23:30:23 Modified:src/webapp/samples/hello-world/style/xsl page2wordml.xsl Log: saving file as UTF-8 Revision ChangesPath 1.2 +43 -46 cocoon-2.1/src/webapp/samples/hello-world/style/xsl/page2wordml.x

Re: Separating build system sources from Cocoon sources

Joerg Heinicke wrote: Joerg Heinicke wrote: Hello, folks, when trying to integrate gump2blocks.properties.xsl I came across some mixtures in our sources, which I would like to solve. Partly we mixed the sources of our build system with the Cocoon sources. In particular src/targets/*-build.xml

OJB block clean up

In the block there is a WEB-INF directory including compiled classes. IMO that's not ok and from what I see I think it can be removed, but some possible useful files could be missing afterwards: OJB.properties, repository.xml and repository.dtd. The rest is already in the java directory AFAICS.

rich clients and macromedia flex

Hi, While the XUL people have been complaining about MS not adopting their way and going with XAML (Longhorn), Macromedia has something that could obsolete them both. It uses flash (v7) to deliver a Flex server generated SWF. checkout Flex and MXML: http://www.macromedia.com/devnet/flex best,

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

Tony Collen wrote: Vadim Gritsenko wrote: [EMAIL PROTECTED] wrote: tony2003/11/17 23:30:23 Modified:src/webapp/samples/hello-world/style/xsl page2wordml.xsl Log: saving file as UTF-8 Revision ChangesPath 1.2 +43 -46 cocoon-2.1/src/webapp/samples/hello-world/sty

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

Vadim Gritsenko wrote: According to cvs [1], both version of files are, actually, binary. First one [2] I cant even try to decipher, and the second one [3] seems almost like XML file, but with binary prefix - which makes it not an XML but some proprietary binary file. Your option is to delete t

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

On 18.11.2003 17:35, Tony Collen wrote: Where I get confused is the encoding. I have the following options: Default ANSI DOS Unicode Unicode (big-endian) UTF-8 Which of these is the proper one? As long as you do not specify one in the XML declaration it should be UTF-8. Joerg

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

Joerg Heinicke wrote: As long as you do not specify one in the XML declaration it should be UTF-8. Fixed, plz check Everyday is a learning day :) Joerg Tony

Re: OJB block clean up

Joerg Heinicke dijo: > In the block there is a WEB-INF directory including compiled classes. > IMO that's not ok and from what I see I think it can be removed, but > some possible useful files could be missing afterwards: OJB.properties, > repository.xml and repository.dtd. The rest is already in t

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

Unfortunately it's still broken as 1.2. Look at the first three characters. http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/webapp/samples/hello-world/style/xsl/page2wordml.xsl?rev=1.4&content-type=text/vnd.viewcvs-markup Joerg

Re: OJB block clean up

On 18.11.2003 17:49, Antonio Gallardo wrote: Joerg Heinicke dijo: In the block there is a WEB-INF directory including compiled classes. IMO that's not ok and from what I see I think it can be removed, but some possible useful files could be missing afterwards: OJB.properties, repository.xml and r

Re: cvs commit: cocoon-2.1/src/webapp/samples/hello-world/style/xsl page2wordml.xsl

Joerg Heinicke wrote: Unfortunately it's still broken as 1.2. Look at the first three characters. *bashes head onto desk* Opening the file in Eclipse, I see one "weird" character before the xml declaration, which I can delete. Ok, let me play with this and see what combination works *conti

Re: OJB block clean up

Joerg Heinicke dijo: Hi Joerg: >> Thanks for asking Joerg. The .class are there because they are already >> "JDO enhanced". This is a special step after compiling in JDO. > > Yes, I read about it. But these class files are used nowhere? How will > they get to build/webapp/samples/**? Before it wa

RE: [Website] Project homepage

Dion Gillard wrote: > James Strachan wrote: > > > Lenya, which has a URI, http://cocoon.apache.org/lenya/, > > > outside of the incubator domain. > > Hmmm, how come Lenya got a URI? Can we have one too? I guess so if > > Lenya already has? > As an outsider, this is very confusing. Lenya 'is not an

Re: cvs commit: cocoon-2.1 blocks.properties

On 18.11.2003 15:28, Geoff Howard wrote: cziegeler2003/11/13 02:18:28 Modified:.blocks.properties Log: Exclude JMS for the release; otherwise Cocoon doesn't compile with 1.3 :( We have to find a better solution for the next version *All* blocks must be able to be included

Re: XSP "official" position

I've never liked the idea of putting controller logic in XSP pages, however, new users of Cocoon that come from server-page backgrounds will probably want to do this because that is what they're used to. I think this is a really bad thing because if you approach things this way, you really mis

RE: session in authentication context

Hi, yes, mergexml is currently not supported by the authentication context. This is mainly because noone needed it until now (which doesn't mean that it doesn't make sense, of course). So, if you need this feature, you have to implement it and we can apply the patch :) PS: Please post plain mails

RE: filename for cocoon-latest.* on mirror.cgi

David Crossley wrote: > > Carsten Ziegeler wrote: > > I just added the current version information to the mirror page, > > so when you go to that page, you see to which version "latest" > > relates. > > > > Thanks for the hint. > > That is a bit better, but Andrew hints at other issues. When the

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

Vadim Gritsenko wrote: Sylvain Wallez wrote: Vadim Gritsenko wrote: ... You can try this for wi:help:
var hWin = new PopupWindow('h');
hWin

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

On 18 Nov 2003, at 21:22, Vadim Gritsenko wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: Vadim Gritsenko wrote: ... You can try this for wi:help:
var hWin = new PopupWindow('h

Re: XSP "official" position

Antonio Gallardo wrote: This is why I am working 10-30 hours every day. Wow. I sometimes would like to be able to work 24+ hours a day: can you share your secret with us? ;-) -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source Java & XMLAn

Re: XSP "official" position

Steven Noels dijo: > Antonio Gallardo wrote: > >> This is why I am working 10-30 hours every day. > > Wow. I sometimes would like to be able to work 24+ hours a day: can you > share your secret with us? ;-) Easy don't sleep in all this time and work this time. I wrote intentionally this values, be

Re: cvs commit: cocoon-2.1/tools/jetty/lib jetty-4.2.14.jar jetty-4.2.9.jar

Antonio, I think that this has been my mistake, I uploaded a wron version for jetty, I have just test it, and It did not work with jdk 1.3. Please get the new version that uploaded on forrest right now.. Cheers Cheche Antonio Gallardo wrote: Ugo Cei dijo: [EMAIL PROTECTED] wrote: Update jet

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

Vadim Gritsenko wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: Looks super-cool. Wanna commit it? Ok, I'm working on it... Found some issues with IE with the above code... Will try some workaround(s)... N!! I spent a large part of the afternoon and all this evening on th

woody as popup windows, and when CSS "position: absolute" is not absolute...

Done. are now shown as popup windows. I faced a very strange behaviour for help popups within tabs and wanted to let you know about what I learned from it. When we write "position: absolute" in a CSS, the absolute position is actually... relative!!! The explanation is in §4 of http://www.w3.o

Re: woody as popup windows, and when CSS "position: absolute"is not absolute...

Sylvain Wallez dijo: > Done. are now shown as popup windows. Congrats! :-D Best Regards, Antonio Gallardo

DynamicSelectionListTestCase

Could someone more into woody please check the DynamicSelectionListTestCase ...it causes a NPE Thanks -- Torsten BTW: is there a way excuting just a specific testcase?

Re: cvs commit: cocoon-2.1/tools/jetty/lib jetty-4.2.14.jar jetty-4.2.9.jar

Juan Jose Pablos dijo: > Antonio, > I think that this has been my mistake, I uploaded a wron version for > jetty, I have just test it, and It did not work with jdk 1.3. > > Please get the new version that uploaded on forrest right now.. Thanks! I will do it right now. Best Regards, Antonio Galla

Re: cvs commit: cocoon-2.1/tools/jetty/lib jetty-4.2.14.jar jetty-4.2.9.jar

Antonio Gallardo dijo: > Juan Jose Pablos dijo: >> Antonio, >> I think that this has been my mistake, I uploaded a wron version for >> jetty, I have just test it, and It did not work with jdk 1.3. >> >> Please get the new version that uploaded on forrest right now.. > > Thanks! I will do it right n

Re: woody as popup windows, and when CSS "position: absolute"is not absolute...

Sylvain Wallez dijo: > Done. are now shown as popup windows. Simply GREAT! I just compiled and saw it. It is even better than my old help since we can even add links inside the help. Many thanks again Sylvain for this stuff. I think this is a very + for Woody and Cocoon in the new arena: webapp

[RT] SAX stream buffering

Hi, folks! The numbers of the XMLByteStreamCompilerInterpreterTestCase and the SaxBufferTestCase gave me some RT -- If you have a look at the testcases it's quite obvious that the SaxBuffer is *much* faster than the XMLByteStream classes. As a thumb rule -just to get the dimensions- we could say:

Re: DO NOT REPLY [Bug 24759] - [WOODY] - widget rendering error inside repeater on first request

This is just my guess, of course I can be wrong. It seems to be a complex bug, because it works fine when you have not woody repeaters at all. I saw how all the pointers to widgets are good configured and then when the "new Created woody transformer" that would process the saxBuffer receives the fi

Re: DO NOT REPLY [Bug 24759] - [WOODY] - widget rendering error inside repeater on first request

Torsten Curdt dijo: >> This is just my guess, of course I can be wrong. It seems to be a >> complex >> bug, because it works fine when you have not woody repeaters at all. >> >> I saw how all the pointers to widgets are good configured and then when >> the "new Created woody transformer" that would

[OT] - About MS published schemas

Hi: I found this interesting article about the recent MS published schemas. And I like to share it with the rest of the community: http://www.theregister.co.uk/content/4/34045.html Best Regards, Antonio Gallardo

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

Sylvain Wallez wrote: Vadim Gritsenko wrote: Vadim Gritsenko wrote: Sylvain Wallez wrote: Looks super-cool. Wanna commit it? Ok, I'm working on it... Found some issues with IE with the above code... Will try some workaround(s)... N!! I spent a large part of the afternoon

Re: cvs commit: cocoon-2.1/src/blocks/woody/samples/resources woody-field-styling.xsl

Vadim Gritsenko wrote: Sylvain Wallez wrote: N!! I spent a large part of the afternoon and all this evening on these issues and just solved them! I was just doing the final polishing before committing. Please wait a few minutes. It's so complicated! I'd not be able to do it

Re: [OT] - About MS published schemas

Saw this too. Seems like once some standard transforms are built, they should get included with cocoon. I'd like to see something go from a result-set to the Excel template (due to be published in Dec '03). Still, you'd have to know that the Office 2003 suite is going to be installed at all of

Re: [OT] - About MS published schemas

David Kavanagh dijo: > Saw this too. Seems like once some standard transforms are built, they > should get included with cocoon. I'd like to see something go from a > result-set to the Excel template (due to be published in Dec '03). > Still, you'd have to know that the Office 2003 suite is going t

Re: [OT] - About MS published schemas

Alas, windows-only tools (office, vpn clients) are the only things keeping me from running Linux on my laptop.. :-/ If it werent' for those paying customers... :-) David Antonio Gallardo wrote: David Kavanagh dijo: Saw this too. Seems like once some standard transforms are built,

Re: rich clients and macromedia flex

Le Mardi, 18 nov 2003, à 17:27 Europe/Zurich, Robert Koberg a écrit : ...checkout Flex and MXML: http://www.macromedia.com/devnet/flex Thanks Robert, this is very interesting. I'm currently using Flash, remote-controlled from java code, for an interactive exhibition display project and the combin