Re: Fwd: Re: JDK 1.3, Forrest and Cocoon Upgrade
Antonio Gallardo wrote: Do you think we need a new vote again? :-) 2.2 is under develoment (alpha!) and should not be used in production. IMO we are free to use 1.4 for now. When we reach a consolidated state of Cocoon core 2.2 we can try to compile with 1.3 and see what is needed to enable the support again. If possible, we should do it, if not, then not. This is my interpretation of the results. So no vote is needed. -- Reinhard
Re: JXTG: invoke macro by name from expression
Antonio Gallardo wrote: On Mie, 8 de Diciembre de 2004, 15:17, Conal Tuohy dijo: Leszek Gawron wrote: Though I would suggest jx:call-macro name=fooBar/ which would make it clear that the attribute is the NAME of the macro to be invoked, rather than the macro itself. +1 here. But please keep in mind we need still support the old ways. We need to deprecate and later remove the old support. That is the way to keep contracts working with current users. :-D I didn't even think about removing something. -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
Bertrand Delacretaz wrote: Le 9 déc. 04, à 01:03, Leszek Gawron a écrit : ... +?xml version=1.0 encoding=UTF-8? ... This is BOM (byte ordering mark). It is being written by some of xml editors to the beginning of the multibyte encoded (i.e. utf-8) xml file. The file I commited is a valid xml. Check in any xml editor/browser... BOM has no meaning for UTF-8, see http://www.unicode.org/unicode/faq/utf_bom.html#BOM It is certainly better *not* to use it, to avoid any confusion. On unixish OSes, many tools check the first four bytes of a file and expect them to be ?xm -Bertrand OK. No problem. By the way: it is a little bit different on win32. Some tools detect utf encoding by checking for BOM. If there is none - ANSI encoding is assumed. -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: JDK 1.3, Forrest and Cocoon Upgrade
Il giorno 09/dic/04, alle 09:04, Reinhard Poetz ha scritto: 2.2 is under develoment (alpha!) and should not be used in production. IMO we are free to use 1.4 for now. When we reach a consolidated state of Cocoon core 2.2 we can try to compile with 1.3 and see what is needed to enable the support again. If possible, we should do it, if not, then not. This is my interpretation of the results. So no vote is needed. +1 ;-) Ugo -- Ugo Cei - http://beblogging.com/ smime.p7s Description: S/MIME cryptographic signature
Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
On Jue, 9 de Diciembre de 2004, 2:21, Leszek Gawron dijo: By the way: it is a little bit different on win32. Some tools detect utf encoding by checking for BOM. If there is none - ANSI encoding is assumed. then switch to Linux! ;-) Best Regards, Antonio Gallardo
Re: JXTG: invoke macro by name from expression
Leszek Gawron wrote:
snip/
That's good. If noone objects I will start tomorrow and hopefully commit
tomorrow.
I have not had time to evalute your proposal in detail, but from a first
look it seem good, so please go ahead.
The syntax you proposed for invocation:
jx:invoke macro=superPrettyPrintedTable
headerTemplate=addressHeaderTemplate
elements=${addresses}
rowTemplate=addressRowTemplate/
has the problem that headerTemplate and so on only are defined in the
macro definition. Which means that you can't use a schema for checking
the template. I would suggest that you use the ordinary verobose
jx:parameter name=foo value=bar/
syntax instead. So that it can work together with common XML tools, if
people want to use such.
And in another mail:
It does not seem that much coding is needed. I could also strip all inner
classes from JXTG at the same time as the first step for JXTG refactoring.
I'm working on refactoring JXTG, and will commit as soon as I have
something commitable. I would suggest that you focus on implementing the
invoke stuff, if its ok with you, so that we avoid doing the same work
twice.
You should also be aware of that refactoring is somewhat more
complicated than just stripping out the inner classes, as they have all
sort of interdependencies based on using global variable in the main
class and using public variables from each other :/
/Daniel
Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
Le 9 déc. 04, à 09:21, Leszek Gawron a écrit : ...By the way: it is a little bit different on win32. Some tools detect utf encoding by checking for BOM. If there is none - ANSI encoding is assumed... AFAIU this is ok for 16-bit based encodings, not for UTF-8. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: JXTG: invoke macro by name from expression
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
snip/
That's good. If noone objects I will start tomorrow and hopefully
commit tomorrow.
I have not had time to evalute your proposal in detail, but from a first
look it seem good, so please go ahead.
The syntax you proposed for invocation:
jx:invoke macro=superPrettyPrintedTable
headerTemplate=addressHeaderTemplate
elements=${addresses}
rowTemplate=addressRowTemplate/
has the problem that headerTemplate and so on only are defined in the
macro definition. Which means that you can't use a schema for checking
the template. I would suggest that you use the ordinary verobose
jx:parameter name=foo value=bar/
syntax instead. So that it can work together with common XML tools, if
people want to use such.
That would be good but looks like a bigger change while current macro
call is done via
macroName param1=value param2=value/
so I would reuse the current logic. If you do not mind I'll commit my
approach first and look for the way to achieve your syntax.
And in another mail:
It does not seem that much coding is needed. I could also strip all inner
classes from JXTG at the same time as the first step for JXTG
refactoring.
I'm working on refactoring JXTG, and will commit as soon as I have
something commitable. I would suggest that you focus on implementing the
invoke stuff, if its ok with you, so that we avoid doing the same work
twice.
You should also be aware of that refactoring is somewhat more
complicated than just stripping out the inner classes, as they have all
sort of interdependencies based on using global variable in the main
class and using public variables from each other :/
I was able to strip 48 classes (almost all inner) removing all public
variables and introducing getters. This was almost an identity
transformation using eclipse so for 99% I haven't broken anything.
If you already have something I should not commit - maybe I would send
you the source via email so you could use it if you wanted?
--
Leszek Gawron [EMAIL PROTECTED]
Project ManagerMobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
Bertrand Delacretaz wrote: Le 9 déc. 04, à 09:21, Leszek Gawron a écrit : ...By the way: it is a little bit different on win32. Some tools detect utf encoding by checking for BOM. If there is none - ANSI encoding is assumed... AFAIU this is ok for 16-bit based encodings, not for UTF-8. -Bertrand http://www.xencraft.com/resources/unicodebom.html quote Even though UTF-8 does not need a BOM to indicate endianness, Microsoft Notepad began prepending a BOM to its UTF-8 text files. Actually, it is a conversion of U+FEFF to an encoding as UTF-8 serialized bytes: EF BB BF (or in 4GL: CHR(15711167)). There is some value in the BOM being used as a file signature, indicating the plain text file is encoded as Unicode UTF-8, as opposed to some other code page. That particular 3-byte sequence is unlikely to represent data in any other code page, given the text is supposed to be human readable in some language. However, there is some small possibility that it represents some string in some code page... Because Microsoft did it, and there is so much Notepad data out there, the UTF-8 BOM became a de facto standard and then a de jure standard. (Although the BOM is optional.) /quote M$ again. -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
On Jue, 9 de Diciembre de 2004, 2:49, Leszek Gawron dijo: Bertrand Delacretaz wrote: Le 9 déc. 04, à 09:21, Leszek Gawron a écrit : ...By the way: it is a little bit different on win32. Some tools detect utf encoding by checking for BOM. If there is none - ANSI encoding is assumed... AFAIU this is ok for 16-bit based encodings, not for UTF-8. -Bertrand http://www.xencraft.com/resources/unicodebom.html quote Even though UTF-8 does not need a BOM to indicate endianness, Microsoft Notepad began prepending a BOM to its UTF-8 text files. Actually, it is a conversion of U+FEFF to an encoding as UTF-8 serialized bytes: EF BB BF (or in 4GL: CHR(15711167)). There is some value in the BOM being used as a file signature, indicating the plain text file is encoded as Unicode UTF-8, as opposed to some other code page. That particular 3-byte sequence is unlikely to represent data in any other code page, given the text is supposed to be human readable in some language. However, there is some small possibility that it represents some string in some code page... Because Microsoft did it, and there is so much Notepad data out there, the UTF-8 BOM became a de facto standard and then a de jure standard. (Although the BOM is optional.) /quote M$ again. This is the standard: http://www.zvon.org/tmRFC/RFC3023/Output/chapter8.html#sub1 :-D Best Regards, Antonio Gallardo.
Re: JXTG: invoke macro by name from expression
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
snip/
That's good. If noone objects I will start tomorrow and hopefully
commit tomorrow.
I have not had time to evalute your proposal in detail, but from a
first look it seem good, so please go ahead.
The syntax you proposed for invocation:
jx:invoke macro=superPrettyPrintedTable
headerTemplate=addressHeaderTemplate
elements=${addresses}
rowTemplate=addressRowTemplate/
has the problem that headerTemplate and so on only are defined in
the macro definition. Which means that you can't use a schema for
checking the template. I would suggest that you use the ordinary verobose
jx:parameter name=foo value=bar/
syntax instead. So that it can work together with common XML tools, if
people want to use such.
That would be good but looks like a bigger change while current macro
call is done via
macroName param1=value param2=value/
so I would reuse the current logic. If you do not mind I'll commit my
approach first and look for the way to achieve your syntax.
And in another mail:
It does not seem that much coding is needed. I could also strip all
inner
classes from JXTG at the same time as the first step for JXTG
refactoring.
I'm working on refactoring JXTG, and will commit as soon as I have
something commitable. I would suggest that you focus on implementing
the invoke stuff, if its ok with you, so that we avoid doing the same
work twice.
You should also be aware of that refactoring is somewhat more
complicated than just stripping out the inner classes, as they have
all sort of interdependencies based on using global variable in the
main class and using public variables from each other :/
I was able to strip 48 classes (almost all inner) removing all public
variables and introducing getters. This was almost an identity
transformation using eclipse so for 99% I haven't broken anything.
If you already have something I should not commit - maybe I would send
you the source via email so you could use it if you wanted?
http://www.apache.org/~lgawron/jxtg-20041209.zip
Wasn't that hard with eclipse. Still took 4 hours so I'd appreciate if
you looked at it :)
--
Leszek Gawron [EMAIL PROTECTED]
Project ManagerMobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: JXTG: invoke macro by name from expression
On Jue, 9 de Diciembre de 2004, 3:01, Leszek Gawron dijo: If you already have something I should not commit - maybe I would send you the source via email so you could use it if you wanted? http://www.apache.org/~lgawron/jxtg-20041209.zip Wasn't that hard with eclipse. Still took 4 hours so I'd appreciate if you looked at it :) I think you can commit the changes, if it is working. This way all of us can review it. WDYT? Best Regards, Antonio Gallardo.
Re: JXTG: invoke macro by name from expression
Antonio Gallardo wrote: On Jue, 9 de Diciembre de 2004, 3:01, Leszek Gawron dijo: If you already have something I should not commit - maybe I would send you the source via email so you could use it if you wanted? http://www.apache.org/~lgawron/jxtg-20041209.zip Wasn't that hard with eclipse. Still took 4 hours so I'd appreciate if you looked at it :) I think you can commit the changes, if it is working. This way all of us can review it. WDYT? The problem is that it will make all Daniel's changes uncommitable as my changes are massive. Daniel - how many changes have you done already? -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
Le 9 déc. 04, à 09:49, Leszek Gawron a écrit : ... Because Microsoft did it, and there is so much Notepad data out there, the UTF-8 BOM became a de facto standard and then a de jure standard. (Although the BOM is optional.).. hmm...not sure if notepad is the kind of reference that we want to use here ;-) Anyway, I think most or all our XML files are UTF-8 with no BOM, so it's probably not a good idea to change. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: svn commit: r111262 - in cocoon/branches/BRANCH_2_1_X/src: java/org/apache/cocoon/components/flow webapp/WEB-INF
Bertrand Delacretaz wrote: Le 9 déc. 04, à 09:49, Leszek Gawron a écrit : ... Because Microsoft did it, and there is so much Notepad data out there, the UTF-8 BOM became a de facto standard and then a de jure standard. (Although the BOM is optional.).. hmm...not sure if notepad is the kind of reference that we want to use here ;-) Anyway, I think most or all our XML files are UTF-8 with no BOM, so it's probably not a good idea to change. It is not only the problem of notepad. At least 2 tools I use (UltraEdit and Araxis Merge) follow the same logic. -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Cocoon-2.1.X Tests Failure 12/09/04
Automated Cocoon Unit tests failed! Full log file if this unit test run is available here: http://nagoya.apache.org/~vadim/cocoon-test-log-20041209.log Last messages from the log file: == [foreach] reader-mime-type.xml:39: Starting http://localhost:1///samples/test/reader-mime-type/test20.html [foreach] reader-mime-type.xml:41: Running test [Header: Content-type = text/html ... done (0ms) [foreach] reader-mime-type.xml:39: Finished http://localhost:1///samples/test/reader-mime-type/test20.html (89ms) [foreach] reader-mime-type.xml:44: Starting http://localhost:1///samples/test/reader-mime-type/test20.html [foreach] reader-mime-type.xml:46: Running test [Header: Content-type = text/html ... done (0ms) [foreach] reader-mime-type.xml:44: Finished http://localhost:1///samples/test/reader-mime-type/test20.html (28ms) [foreach] reader-mime-type.xml:50: Starting http://localhost:1///samples/test/reader-mime-type/test30.html [foreach] reader-mime-type.xml:52: Running test [Header: Content-type = text/html ... done (0ms) [foreach] reader-mime-type.xml:50: Finished http://localhost:1///samples/test/reader-mime-type/test30.html (454ms) [foreach] reader-mime-type.xml:55: Starting http://localhost:1///samples/test/reader-mime-type/test30.html [foreach] reader-mime-type.xml:57: Running test [Header: Content-type = text/html ... done (1ms) [foreach] reader-mime-type.xml:55: Finished http://localhost:1///samples/test/reader-mime-type/test30.html (84ms) [foreach] reader-mime-type.xml:61: Starting http://localhost:1///samples/test/reader-mime-type/test40.html [foreach] reader-mime-type.xml:63: Running test [Header: Content-type = text/html ... done (0ms) [foreach] reader-mime-type.xml:61: Finished http://localhost:1///samples/test/reader-mime-type/test40.html (33ms) [foreach] reader-mime-type.xml:66: Starting http://localhost:1///samples/test/reader-mime-type/test40.html [foreach] reader-mime-type.xml:68: Running test [Header: Content-type = text/html ... done (0ms) [foreach] reader-mime-type.xml:66: Finished http://localhost:1///samples/test/reader-mime-type/test40.html (28ms) [foreach] reader-mime-type.xml:72: Starting http://localhost:1///samples/test/reader-mime-type/test50.html [foreach] reader-mime-type.xml:74: Running test [Header: Content-type = text/html[1;31m Failure: file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/cocoon-2.1.7-dev/test/anteater/reader-mime-type.xml:74: message doesn't match because header 'content-type' is not present[m [foreach] ... done (7ms) [foreach] reader-mime-type.xml:72: Finished http://localhost:1///samples/test/reader-mime-type/test50.html (45ms) BUILD FAILED file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/cocoon-2.1.7-dev/test/anteater/reader-mime-type.xml:72: Task at file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/cocoon-2.1.7-dev/test/anteater/reader-mime-type.xml:72: failed Total time: 26 seconds Last messages from the server console: == [EMAIL PROTECTED]: Startup sequence initiated from main() method [EMAIL PROTECTED]: Loaded properties from [/disk/raid0/home/vadim/svn/cocoon-2.1.X/server.properties] [EMAIL PROTECTED]: Initiating startup sequence... [EMAIL PROTECTED]: Server socket opened successfully in 4 ms. [EMAIL PROTECTED]: Database [index=0, id=0, db=file:/disk/raid0/home/vadim/svn/cocoon-2.1.X/build/webapp/WEB-INF/db/cocoondb, alias=] opened sucessfully in 2097 ms. [EMAIL PROTECTED]: Startup sequence completed in 2139 ms. [EMAIL PROTECTED]: 2004-12-09 01:30:06.889 HSQLDB server 1.7.3 is online [EMAIL PROTECTED]: To close normally, connect and execute SHUTDOWN SQL [EMAIL PROTECTED]: From command line, use [Ctrl]+[C] to abort abruptly - The database 'db' root directory has been set to /disk/raid0/home/vadim/svn/cocoon-2.1.X/build/webapp/WEB-INF/db. Keep in mind that if a war upgrade will take place the database will be lost. - Database points to /disk/raid0/home/vadim/svn/cocoon-2.1.X/build/webapp/WEB-INF/db - [main] '/db/system/SysSymbols' Set object system_SysConfig - [main] '/db/system/SysConfig' Set document database.xml - [main] '/db/system/SysSymbols' Set object meta_Metas - [main] '/db/system/SysSymbols' Set object meta_Metas_system_SysConfig - Database 'db' successfully opened - Xindice server successfully started parameter = @PARAMETER@ replaceme = replaceme-abc parameter = @PARAMETER@ replaceme = replaceme-123 - VM shutting down with the disk store for cocoon-ehcache-1 still active. The disk store is persistent. Calling dispose... - Database 'db' successfully closed - Scheduler Cocoon_$_Thu_Dec_09_01:29:53_PST_2004 paused. - Scheduler Cocoon_$_Thu_Dec_09_01:29:53_PST_2004 shutting down. - Scheduler Cocoon_$_Thu_Dec_09_01:29:53_PST_2004 paused
WebServiceProxyGenerator does not do redirects correctly
The commons HttpClient library does not automatically do redirects (see http://jakarta.apache.org/commons/httpclient/redirects.html). So, when the WebServiceProxyGenerator receives a redirect response, which has no body, it chokes on it. In my case I was trying to proxy a JSPWiki instance - the POST requests, which generate a 302 response, caused this error. It seems that the redirects have to be handled by the WebServiceProxyGenerator class. -- Ramon Casha ramon.casha (at) linux.org.mt Malta Linux User Group
[RFC] JXTG Refactoring (was: JXTG: invoke macro by name from expression)
Leszek and I have started refactoring JXTG, by breaking it up in its subclasses. Later we will work on creating more detailed interfaces between the different parts and all the other stuff that has been discussed on the list. Now the question is: where should this work take place? For the refactoring aspect its better to work on JXTG in core (BTW what is the correct terminology, before we refered to code not being in a block as core but now ECM++ is placed in a directory named core). But considering that we are going to add stuff, and make it a framework for further template experiments, it makes more sense to place it in a block. Also our long time plan is to remove as much as possible from core, AFAIU. So what I propose is that we do the refactoring in the template block. And that we call the refactored JXTG something else to avoid collisions with the original one, e.g. JXTemplateGenerator2 or o.a.c.template.generator.JXTemplateGenerator. While doing this I suggest that we freeze development of the original JXTG, except for bug fixes. And after a while when the refactored version start to become stable, concerning functionality and contracts, we can discuss replacing the original JXTG with the refactored and improved one. Is this a good plan or do you have other suggestions? /Daniel Some comments to Leszek's mail below. Leszek Gawron wrote: Antonio Gallardo wrote: On Jue, 9 de Diciembre de 2004, 3:01, Leszek Gawron dijo: If you already have something I should not commit - maybe I would send you the source via email so you could use it if you wanted? http://www.apache.org/~lgawron/jxtg-20041209.zip Wasn't that hard with eclipse. Still took 4 hours so I'd appreciate if you looked at it :) I think you can commit the changes, if it is working. This way all of us can review it. WDYT? The problem is that it will make all Daniel's changes uncommitable as my changes are massive. Daniel - how many changes have you done already? Quite a lot of them, but mainly in other areas then the ones you have worked in. And I'm quite busy with other things the next few days so I think it is better that you commit your stuff than that I block the process. I would prefer to divede all the classes in some different directories like environment for the code that connects to the cocoon object, expression for epression related functionality, tag for executable tags, script for parsing, execution, basic xml event classes and interface for executable tags. But there is no hurry with that we can do such things later, you can commit it as is. I set up some basic testing stuff that I can commit as soon as you have commited your stuff. I think creating a testing set for JXTG is an important part of our futire work. I can see that I should start to use modern tools like Eclipse, I'm still using Emacs for everything and it is not ideal for large refactorings. OTH I don't create my own code with the same coding style as in JXTG, so most of the time I don't have such a clear need for automated refactoring help. /Daniel
[GUMP@brutus]: Project cocoon-block-xsp (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-xsp *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-xsp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xsp-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-xsp/gump_work/build_cocoon_cocoon-block-xsp.html Work Name: build_cocoon_cocoon-block-xsp (Type: Build) Work ended in a state of : Success Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=xsp gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-session-fw (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-session-fw *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-session-fw/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [session-fw-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-session-fw/gump_work/build_cocoon_cocoon-block-session-fw.html Work Name: build_cocoon_cocoon-block-session-fw (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=session-fw gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-batik (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-batik *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-batik/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [batik-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-batik/gump_work/build_cocoon_cocoon-block-batik.html Work Name: build_cocoon_cocoon-block-batik (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=batik gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-chaperon (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-chaperon *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-chaperon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [chaperon-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-chaperon/gump_work/build_cocoon_cocoon-block-chaperon.html Work Name: build_cocoon_cocoon-block-chaperon (Type: Build) Work ended in a state of : Success Elapsed: 10 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=chaperon gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-databases (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-databases *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-databases/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [databases-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-databases/gump_work/build_cocoon_cocoon-block-databases.html Work Name: build_cocoon_cocoon-block-databases (Type: Build) Work ended in a state of : Success Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=databases gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-hsqldb (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-hsqldb *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-hsqldb/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [hsqldb-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-hsqldb/gump_work/build_cocoon_cocoon-block-hsqldb.html Work Name: build_cocoon_cocoon-block-hsqldb (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=hsqldb gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-taglib (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-taglib *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-taglib/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [taglib-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-taglib/gump_work/build_cocoon_cocoon-block-taglib.html Work Name: build_cocoon_cocoon-block-taglib (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=taglib gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-html (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-html *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-html/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [html-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-html/gump_work/build_cocoon_cocoon-block-html.html Work Name: build_cocoon_cocoon-block-html (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=html gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-itext (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-itext *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-itext/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [itext-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-itext/gump_work/build_cocoon_cocoon-block-itext.html Work Name: build_cocoon_cocoon-block-itext (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=itext gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-jfor (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-jfor *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jfor/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jfor-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jfor/gump_work/build_cocoon_cocoon-block-jfor.html Work Name: build_cocoon_cocoon-block-jfor (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=jfor gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-linkrewriter (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-linkrewriter *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-linkrewriter/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [linkrewriter-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-linkrewriter/gump_work/build_cocoon_cocoon-block-linkrewriter.html Work Name: build_cocoon_cocoon-block-linkrewriter (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=linkrewriter gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-velocity (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-velocity *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-velocity/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [velocity-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-velocity/gump_work/build_cocoon_cocoon-block-velocity.html Work Name: build_cocoon_cocoon-block-velocity (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=velocity gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-midi (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-midi *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-midi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [midi-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-midi/gump_work/build_cocoon_cocoon-block-midi.html Work Name: build_cocoon_cocoon-block-midi (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=midi gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-paranoid (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-paranoid *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-paranoid/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [paranoid-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-paranoid/gump_work/build_cocoon_cocoon-block-paranoid.html Work Name: build_cocoon_cocoon-block-paranoid (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=paranoid gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-poi (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-poi *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-poi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [poi-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-poi/gump_work/build_cocoon_cocoon-block-poi.html Work Name: build_cocoon_cocoon-block-poi (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=poi gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-profiler (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-profiler *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-profiler/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [profiler-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-profiler/gump_work/build_cocoon_cocoon-block-profiler.html Work Name: build_cocoon_cocoon-block-profiler (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=profiler gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
Re: JXTG: invoke macro by name from expression
Leszek Gawron wrote: Daniel Fagerstrom wrote: snip/ syntax instead. So that it can work together with common XML tools, if people want to use such. That would be good but looks like a bigger change while current macro call is done via macroName param1=value param2=value/ so I would reuse the current logic. If you do not mind I'll commit my approach first and look for the way to achieve your syntax. I don't mind, do it as you find suitable. /Daniel
[GUMP@brutus]: Project cocoon-block-python (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-python *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-python/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [python-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-python/gump_work/build_cocoon_cocoon-block-python.html Work Name: build_cocoon_cocoon-block-python (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=python gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-serializers (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-serializers *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-serializers/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [serializers-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-serializers/gump_work/build_cocoon_cocoon-block-serializers.html Work Name: build_cocoon_cocoon-block-serializers (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=serializers gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-template (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-template has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-template : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [template-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/gump_work/build_cocoon_cocoon-block-template.html Work Name: build_cocoon_cocoon-block-template (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=template gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-web3 (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-web3 *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-web3/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [web3-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-web3/gump_work/build_cocoon_cocoon-block-web3.html Work Name: build_cocoon_cocoon-block-web3 (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=web3 gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-woody (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-woody *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-woody/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [woody-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-woody/gump_work/build_cocoon_cocoon-block-woody.html Work Name: build_cocoon_cocoon-block-woody (Type: Build) Work ended in a state of : Success Elapsed: 15 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=woody gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-forms (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-forms *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-forms/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [forms-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-forms/gump_work/build_cocoon_cocoon-block-forms.html Work Name: build_cocoon_cocoon-block-forms (Type: Build) Work ended in a state of : Success Elapsed: 18 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=forms gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-authentication-fw (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-authentication-fw *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-authentication-fw/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [authentication-fw-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-authentication-fw/gump_work/build_cocoon_cocoon-block-authentication-fw.html Work Name: build_cocoon_cocoon-block-authentication-fw (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=authentication-fw gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-bsf (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-bsf *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-bsf/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [bsf-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-bsf/gump_work/build_cocoon_cocoon-block-bsf.html Work Name: build_cocoon_cocoon-block-bsf (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=bsf gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-deli (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-deli *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-deli/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [deli-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-deli/gump_work/build_cocoon_cocoon-block-deli.html Work Name: build_cocoon_cocoon-block-deli (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=deli gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-jms (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-jms *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jms/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jms-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jms/gump_work/build_cocoon_cocoon-block-jms.html Work Name: build_cocoon_cocoon-block-jms (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=jms gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-portal (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-portal *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-portal/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [portal-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-portal/gump_work/build_cocoon_cocoon-block-portal.html Work Name: build_cocoon_cocoon-block-portal (Type: Build) Work ended in a state of : Success Elapsed: 11 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=portal gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-linotype (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-linotype *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-linotype/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [linotype-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-linotype/gump_work/build_cocoon_cocoon-block-linotype.html Work Name: build_cocoon_cocoon-block-linotype (Type: Build) Work ended in a state of : Success Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=linotype gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-naming (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-naming *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-naming/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [naming-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-naming/gump_work/build_cocoon_cocoon-block-naming.html Work Name: build_cocoon_cocoon-block-naming (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=naming gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-portal-fw (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-portal-fw *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-portal-fw/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [portal-fw-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-portal-fw/gump_work/build_cocoon_cocoon-block-portal-fw.html Work Name: build_cocoon_cocoon-block-portal-fw (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=portal-fw gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-qdox (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-qdox *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-qdox/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [qdox-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-qdox/gump_work/build_cocoon_cocoon-block-qdox.html Work Name: build_cocoon_cocoon-block-qdox (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=qdox gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-stx (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-stx *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-stx/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [stx-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-stx/gump_work/build_cocoon_cocoon-block-stx.html Work Name: build_cocoon_cocoon-block-stx (Type: Build) Work ended in a state of : Success Elapsed: 3 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=stx gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
Re: [RFC] JXTG Refactoring
Daniel Fagerstrom wrote: Leszek and I have started refactoring JXTG, by breaking it up in its subclasses. Later we will work on creating more detailed interfaces between the different parts and all the other stuff that has been discussed on the list. Now the question is: where should this work take place? For the refactoring aspect its better to work on JXTG in core (BTW what is the correct terminology, before we refered to code not being in a block as core but now ECM++ is placed in a directory named core). But considering that we are going to add stuff, and make it a framework for further template experiments, it makes more sense to place it in a block. Also our long time plan is to remove as much as possible from core, AFAIU. So what I propose is that we do the refactoring in the template block. And that we call the refactored JXTG something else to avoid collisions with the original one, e.g. JXTemplateGenerator2 or o.a.c.template.generator.JXTemplateGenerator. o.a.c.template.generator.JXTemplateGenerator in template block it is. I will commit it as is and commit small steps further. Quite a lot of them, but mainly in other areas then the ones you have worked in. And I'm quite busy with other things the next few days so I think it is better that you commit your stuff than that I block the process. I would prefer to divede all the classes in some different directories like environment for the code that connects to the cocoon object, expression for epression related functionality, tag for executable tags, script for parsing, execution, basic xml event classes and interface for executable tags. But there is no hurry with that we can do such things later, you can commit it as is. You are totally right. Right now it was just the simplest thing to do. It's still a little bit messy and will require lots of additional refactoring. I set up some basic testing stuff that I can commit as soon as you have commited your stuff. I think creating a testing set for JXTG is an important part of our futire work. Expect a commit soon. -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
[GUMP@brutus]: Project cocoon-block-xmldb (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-xmldb *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-xmldb/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xmldb-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-xmldb/gump_work/build_cocoon_cocoon-block-xmldb.html Work Name: build_cocoon_cocoon-block-xmldb (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=xmldb gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-asciiart (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-asciiart *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-asciiart/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [asciiart-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-asciiart/gump_work/build_cocoon_cocoon-block-asciiart.html Work Name: build_cocoon_cocoon-block-asciiart (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=asciiart gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-cron (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-cron has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-cron : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-cron/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cron-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-cron/gump_work/build_cocoon_cocoon-block-cron.html Work Name: build_cocoon_cocoon-block-cron (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=cron gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-faces (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-faces *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-faces/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [faces-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-faces/gump_work/build_cocoon_cocoon-block-faces.html Work Name: build_cocoon_cocoon-block-faces (Type: Build) Work ended in a state of : Success Elapsed: 9 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=faces gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-lucene (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-lucene *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-lucene/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [lucene-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-lucene/gump_work/build_cocoon_cocoon-block-lucene.html Work Name: build_cocoon_cocoon-block-lucene (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=lucene gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-petstore (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-petstore *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-petstore/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [petstore-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-petstore/gump_work/build_cocoon_cocoon-block-petstore.html Work Name: build_cocoon_cocoon-block-petstore (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=petstore gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-querybean (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-querybean *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-querybean/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [querybean-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-querybean/gump_work/build_cocoon_cocoon-block-querybean.html Work Name: build_cocoon_cocoon-block-querybean (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=querybean gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-axis (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-axis *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-axis/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [axis-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-axis/gump_work/build_cocoon_cocoon-block-axis.html Work Name: build_cocoon_cocoon-block-axis (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=axis gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-fop (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-fop *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-fop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-fop/gump_work/build_cocoon_cocoon-block-fop.html Work Name: build_cocoon_cocoon-block-fop (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=fop gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-proxy (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-proxy *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-proxy/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [proxy-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-proxy/gump_work/build_cocoon_cocoon-block-proxy.html Work Name: build_cocoon_cocoon-block-proxy (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=proxy gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-tour (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-tour *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-tour/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [tour-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-tour/gump_work/build_cocoon_cocoon-block-tour.html Work Name: build_cocoon_cocoon-block-tour (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=tour gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-apples (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-apples *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-apples/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [apples-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-apples/gump_work/build_cocoon_cocoon-block-apples.html Work Name: build_cocoon_cocoon-block-apples (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=apples gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-jsp (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-jsp *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jsp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jsp-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jsp/gump_work/build_cocoon_cocoon-block-jsp.html Work Name: build_cocoon_cocoon-block-jsp (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=jsp gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-eventcache (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-eventcache *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-eventcache/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [eventcache-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-eventcache/gump_work/build_cocoon_cocoon-block-eventcache.html Work Name: build_cocoon_cocoon-block-eventcache (Type: Build) Work ended in a state of : Success Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=eventcache gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-repository (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-repository *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-repository/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [repository-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-repository/gump_work/build_cocoon_cocoon-block-repository.html Work Name: build_cocoon_cocoon-block-repository (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=repository gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-webdav (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-webdav *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-webdav/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [webdav-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-webdav/gump_work/build_cocoon_cocoon-block-webdav.html Work Name: build_cocoon_cocoon-block-webdav (Type: Build) Work ended in a state of : Success Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=webdav gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-slide (in module cocoon) success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-slide *no longer* has an issue. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-slide/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [slide-block.jar] identifier set to project name -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-slide/gump_work/build_cocoon_cocoon-block-slide.html Work Name: build_cocoon_cocoon-block-slide (Type: Build) Work ended in a state of : Success Elapsed: 6 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=slide gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
DO NOT REPLY [Bug 31718] - [Patch] Image Operation Reader
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31718. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31718 [EMAIL PROTECTED] changed: What|Removed |Added Summary|Image Operation Reader |[Patch] Image Operation ||Reader -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: [RFC] JXTG Refactoring
Daniel Fagerstrom wrote: Leszek and I have started refactoring JXTG, by breaking it up in its subclasses. Later we will work on creating more detailed interfaces between the different parts and all the other stuff that has been discussed on the list. Now the question is: where should this work take place? For the refactoring aspect its better to work on JXTG in core (BTW what is the correct terminology, before we refered to code not being in a block as core but now ECM++ is placed in a directory named core). But considering that we are going to add stuff, and make it a framework for further template experiments, it makes more sense to place it in a block. Also our long time plan is to remove as much as possible from core, AFAIU. So what I propose is that we do the refactoring in the template block. And that we call the refactored JXTG something else to avoid collisions with the original one, e.g. JXTemplateGenerator2 or o.a.c.template.generator.JXTemplateGenerator. I have commited an initial JXTemplateGenerator to o.a.c.template.jxtg.JXTemplateGenerator and moved Jonas' templating proposal to o.a.c.template.v2 package. Please review. -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
DO NOT REPLY [Bug 32541] - [Patch] HTTPIncludeTransformer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32541. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32541 --- Additional Comments From [EMAIL PROTECTED] 2004-12-09 14:36 --- Differences are not about including XML response once or doing it multiple times, it's about features. Anyway, you can't do asynchronous HTTP calls (the results wouldn't be in the outgoing document, or in the right order), and they can't be nested, so it makes no sense sending multiple request. I looked at the Proxy Generators... HttpProxyGenerator provides some of the functionalities of the HTTP[Request/Include]Transformer, but not all. For example, it can't send SOAP call; it's why WebServiceProxyGenerator was created. But then, another problem comes in mind; both proxies don't allow the user to manually set request header, or authentication information. It could be a real problem when you want to access some secure servers or when the server filters request on the User-Agent header. The transformer I submitted does all these things in one component, that's the beauty! But I agree with you on merging generators and transformer altogether into one component. It would be far more elegant instead of having multiple generators/transformers when one would be enough. And both transformer and a generator could use that component. I'm willing to investigate this way and maintaining the component (if I am allowed, of course). I suggest renaming HTTPIncludeTransformer to HTTPRequestTransformer and we could put it in the 2.2 branch, in a block or in the scratchpad area and let the users use both HttpProxyGenerator or HTTPRequestTransformer for now. I think both have their place. WDYT? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is.
Re: [RFC] JXTG Refactoring
Leszek Gawron wrote: snip/ I have commited an initial JXTemplateGenerator to o.a.c.template.jxtg.JXTemplateGenerator and moved Jonas' templating proposal to o.a.c.template.v2 package. Please review. Nice! Don't have time to review in any detail right now. I added some basic test cases. Two of them that tries to test that the cocoon object is accesible from expressions are faulty, I didn't get them to work even with the original JXTG, any idea about what goes wrong? --- o0o --- For further refactoring I think that we should try to factor out the execute method as you certainly have seen it is quite intermingled with other stuff. IMO it should be static (or better moved to an own class), and depend of three arguments: execute(XMLConsumer consumer, ExecutionContext context, ...) where ExecutionContext is a new class containing the jexl and jxpath contexts, ServiceManager (and SourceResolver but that is accesible from ServiceManager), Variables, cache and definitions. There was some discussion about context in http://marc.theaimsgroup.com/?t=11017341082r=1w=2. In a next step the cache object should be factored out from the ExecutionContext and replaced by some kind of script manager, so that we can have the code that compiles and caches the scripts at one place. Then execute takes a number of events as arguments, I would like to abstact the coupling between execution and event implementation, but how it should be done requires more thinking. Each tag has code in three places: its start tag that contains data, in the parser for setting it up and inexecute for executing it. That is rather confusing, so we shoud put all the three parts in one class. How this can be done has been discussed in the above thread among other places. Hiding the jxpath and jexl specifc code beyond one interface would also be nice. WDYT? /Daniel
Re: [RFC] JXTG Refactoring
Daniel Fagerstrom wrote: Leszek Gawron wrote: snip/ I have commited an initial JXTemplateGenerator to o.a.c.template.jxtg.JXTemplateGenerator and moved Jonas' templating proposal to o.a.c.template.v2 package. Please review. Nice! I am totally busy right now. I'll try to look into your test cases in the evening as well as make some comments about further steps. -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: [RFC] JXTG Refactoring
Daniel Fagerstrom wrote: snip/ For further refactoring I think that we should ... Even more important is of course to add lots of test cases, so that we ensure high quality. For those who have corrected more or less subtle bugs in JXTG, consider adding a test case for it so that we can avoid regression. Also, the refactored JXTG is supposed to be kept back compatible at all time, so the really adventuerous can consider switching from the original to the new JXTG in his/her sitemaps so that we can detect and correct regression as fast as possible (if you not are the kind of person that has a cron script that compile and install the latest Linux kernel from CVS each night in your production servers, you might want to avoid using the new JXTG for production yet, though ;) ). /Daniel
Re: how to list all sitemap components
I'd just use eclipse to find every class that implements the right interface(s). Would that work? Geoff On Thu, 09 Dec 2004 10:46:36 +1100, David Crossley [EMAIL PROTECTED] wrote: I am trying to create a list of all sitemap components in the Cocoon core and blocks. So far i have tried to use 'find and grep' by looking for well-known filenames, e.g. *Transformer.java and also searching in well-known directories, e.g. /transformation/ However, that misses some components and gets too much extra stuff. Using the package name inside the *.java also misses some components. Is there a way to uniquely identify the sitemap components by grepping the *.java e.g. perhaps a unique method name? --David
Re: how to list all sitemap components
Geoff Howard wrote: I'd just use eclipse to find every class that implements the right interface(s). Would that work? Or, what we need is a tool that lists all the interfaces that a class implements. Hmm. Javadoc. For the CastorTransformer, you get a line saying: *All Implemented Interfaces:* Component http://avalon.apache.org/framework/api/org/apache/avalon/framework/component/Component.html, Configurable http://avalon.apache.org/framework/api/org/apache/avalon/framework/configuration/Configurable.html, ContentHandler http://java.sun.com/j2ee/sdk_1.3/techdocs/api/org/xml/sax/ContentHandler.html, LexicalHandler http://java.sun.com/j2ee/sdk_1.3/techdocs/api/org/xml/sax/ext/LexicalHandler.html, LogEnabled http://avalon.apache.org/framework/api/org/apache/avalon/framework/logger/LogEnabled.html, Poolable http://excalibur.apache.org/apidocs/org/apache/avalon/excalibur/pool/Poolable.html, Recyclable http://excalibur.apache.org/apidocs/org/apache/avalon/excalibur/pool/Recyclable.html, SitemapModelComponent http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/sitemap/SitemapModelComponent.html, Transformer http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/transformation/Transformer.html, XMLConsumer http://excalibur.apache.org/apidocs/org/apache/excalibur/xml/sax/XMLConsumer.html, XMLConsumer http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/xml/XMLConsumer.html, XMLPipe http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/xml/XMLPipe.html, XMLProducer http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/xml/XMLProducer.html The word Transformer is in there, as is SitemapModelComponent, each of which tell you what you want to know. Am I correct? Regards, Upayavira Geoff On Thu, 09 Dec 2004 10:46:36 +1100, David Crossley [EMAIL PROTECTED] wrote: I am trying to create a list of all sitemap components in the Cocoon core and blocks. So far i have tried to use 'find and grep' by looking for well-known filenames, e.g. *Transformer.java and also searching in well-known directories, e.g. /transformation/ However, that misses some components and gets too much extra stuff. Using the package name inside the *.java also misses some components. Is there a way to uniquely identify the sitemap components by grepping the *.java e.g. perhaps a unique method name? --David
Re: svn commit: r111375 - in cocoon/trunk/src/blocks/template: java/org/apache/cocoon/template/generation java/org/apache/cocoon/template/jxtg java/org/apache/cocoon/template/jxtg/environment java/org/apache/cocoon/template/jxtg/expression java/org/apache/cocoon/template/jxtg/script java/org/apache/cocoon/template/jxtg/script/event java/org/apache/cocoon/template/script java/org/apache/cocoon/template/tag java/org/apache/cocoon/template/v2 java/org/apache/cocoon/template/v2/generation java/org/apache/cocoon/template/v2/script java/org/apache/cocoon/template/v2/tag java/org/apache/cocoon/template/v2/tag/samples test/org/apache/cocoon/template/generation test/org/apache/cocoon/template/script
[EMAIL PROTECTED] wrote: Author: lgawron Added: cocoon/trunk/src/blocks/template/java/org/apache/cocoon/template/jxtg/JXTemplateGenerator.java Url: http://svn.apache.org/viewcvs/cocoon/trunk/src/blocks/template/java/org/apache/cocoon/template/jxtg/JXTemplateGenerator.java?view=autorev=111375 == --- (empty file) +++ cocoon/trunk/src/blocks/template/java/org/apache/cocoon/template/jxtg/JXTemplateGenerator.java Thu Dec 9 04:38:49 2004 @@ -0,0 +1,1230 @@ +/* + * Copyright 1999-2004 The Apache Software Foundation. + * + * Licensed under the Apache License, Version 2.0 (the License); + * you may not use this file except in compliance with the License. Please do: svn propset svn:eol-style native *.java svn propset svn:keywords Id *.java Vadim
Re: how to list all sitemap components
Le 9 déc. 04, à 00:46, David Crossley a écrit : I am trying to create a list of all sitemap components in the Cocoon core and blocks... Doesn't qdox list the interfaces that a class implements? If it's the case, it should be possible to create a pipeline (using the qdox block) or use the qdox ant task to generate the list, by finding all classes which implement the Generator interface. Is there a way to uniquely identify the sitemap components by grepping the *.java e.g. perhaps a unique method name? Probably not, as the method could be implemented in a base class and as such not be visible in the derived class's source code. I'd go the qdox route, assuming it finds the inherited interfaces. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: how to list all sitemap components
Bertrand Delacretaz wrote: Le 9 déc. 04, à 00:46, David Crossley a écrit : I am trying to create a list of all sitemap components in the Cocoon core and blocks... Doesn't qdox list the interfaces that a class implements? If it's the case, it should be possible to create a pipeline (using the qdox block) or use the qdox ant task to generate the list, by finding all classes which implement the Generator interface. Is there a way to uniquely identify the sitemap components by grepping the *.java e.g. perhaps a unique method name? Probably not, as the method could be implemented in a base class and as such not be visible in the derived class's source code. I'd go the qdox route, assuming it finds the inherited interfaces. -Bertrand cd build/cocoon-2.1.7-dev/javadocs/ grep -rl SitemapModelComponent * That's pretty easy, isn't it? Regards, Upayavira
Re: XML Serializers [was: XMLSerializer replaces tabs with #9; ]
Dear All I just migrated our projects to 2.1.6 and found that they were severely affected by this new behaviour as all our generated XHTML has escaped tabs, quotes etc. Thus I'd (I think we all do) appreciate clarity on what the correct (and expected) behaviour of the serialisation is. In the meantime (since I wouldn't want to miss all the new, nice changes in 2.1.6) I found an almost workaround (have tried only with the XHTML serialiser) which requires only minor changes to the XSLs: map:serializer mime-type=text/html name=xhtml src=org.apache.cocoon.components.serializers.XHTMLSerializer doctype-public-//W3C//DTD XHTML 1.0 Transitional//EN/doctype-public doctype-systemhttp://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd/doctype-system encodingUTF-8/encoding /map:serializer The only caveat is that in javascripts quotes are still escaped, which can be taken care of however by enclosing them with xsl:comment. I hope I'm not too much off-topic Regards G.
Re: how to list all sitemap components
Le 9 déc. 04, à 16:56, Upayavira a écrit : ...cd build/cocoon-2.1.7-dev/javadocs/ grep -rl SitemapModelComponent * Good one! Here's the pretty listing then: for i in $(grep -rl SitemapModelComponent * | grep org/apache) do echo $i | sed 's/\//\./g' | sed 's/\.html$//' done There's still a bit of junk left (package-frame etc) but it's a good start. -Bertrand smime.p7s Description: S/MIME cryptographic signature
[GUMP@brutus]: Project cocoon-block-template (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-template has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-template : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [template-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/gump_work/build_cocoon_cocoon-block-template.html Work Name: build_cocoon_cocoon-block-template (Type: Build) Work ended in a state of : Failed Elapsed: 19 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=template gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[GUMP@brutus]: Project cocoon-block-cron (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-cron has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-cron : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-cron/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cron-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-cron/gump_work/build_cocoon_cocoon-block-cron.html Work Name: build_cocoon_cocoon-block-cron (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=09122004 -Dblock-name=cron gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
Lame question...
I have some quite-large tables that i use for lookups (categories, mostly, and prices). They fit pretty nicely in a DOM in memory, no problem, and they almost never change. Now, I want to access those from XSLT as a variable. Normally, I would aggregate the source, and pass it in the input to the processor, and then do the lookup when I need to. Big waste of time, though, because normally (in Java) I'd parse the XML into a DOM (once) and pass it to the XSLT as a parameter (kind of like using the document function). Is there something like that in Cocoon (allow to pass a full DOM as a parameter to the XSLT processor) or shall I start coding? Pier smime.p7s Description: S/MIME cryptographic signature
Re: Lame question...
Pier Fumagalli wrote: I have some quite-large tables that i use for lookups (categories, mostly, and prices). They fit pretty nicely in a DOM in memory, no problem, and they almost never change. Now, I want to access those from XSLT as a variable. Normally, I would aggregate the source, and pass it in the input to the processor, and then do the lookup when I need to. Big waste of time, though, because normally (in Java) I'd parse the XML into a DOM (once) and pass it to the XSLT as a parameter (kind of like using the document function). Is there something like that in Cocoon (allow to pass a full DOM as a parameter to the XSLT processor) or shall I start coding? Probably that's what you want: http://issues.apache.org/bugzilla/show_bug.cgi?id=9916 And no, it's not here yet. One workaround I see is to write extension which would somehow get to the DOM and return it to xslt processor... Vadim
Re: how to list all sitemap components
Geoff Howard wrote: I'd just use eclipse to find every class that implements the right interface(s). Would that work? Thanks Geoff. However, command-line tools only because i need to script it. Sorry, i forgot to specify that. --David
Re: Lame question...
I could be way off, but... Have you tried including the data in the stylesheet itself and using document() to self-reference? .micah Pier Fumagalli wrote: I have some quite-large tables that i use for lookups (categories, mostly, and prices). They fit pretty nicely in a DOM in memory, no problem, and they almost never change. Now, I want to access those from XSLT as a variable.
Cinclude bug 32491
Hello, my application heavily relies on stream that I use through cinclude post. I saw there was a problem when I test the 2.1.6, as reported in bug 32491. I saw the explanation about the bug but I didn't understand anything... Just a question. When I have a chance to see this bug solved ? Thanks a lot for the fabulous work on cocoon, -- Jean-Christophe Kermagoret [EMAIL PROTECTED]
Re: Lame question...
Pier Fumagalli wrote: I have some quite-large tables that i use for lookups (categories, mostly, and prices). They fit pretty nicely in a DOM in memory, no problem, and they almost never change. Now, I want to access those from XSLT as a variable. Normally, I would aggregate the source, and pass it in the input to the processor, and then do the lookup when I need to. Big waste of time, though, because normally (in Java) I'd parse the XML into a DOM (once) and pass it to the XSLT as a parameter (kind of like using the document function). Is there something like that in Cocoon (allow to pass a full DOM as a parameter to the XSLT processor) or shall I start coding? Pier Something you could do that would be usefull for accessing XML databases with DOM interface also (Xindice e.g. IIRC), would be to extend o.a.excalibur.xml.xslt.XSLTProcessorImpl, so that it become DOM aware. What needs to be changed is the resolve(String href, String base) method (that is used for handling document(), xsl:include and xsl:import). Now it takes a href, finds a Source and transforms it to a javax.xml.transform.stream.StreamSource. Instead one can start by checking if the Source implements javax.xml.transform.dom.DOMSource, (or DOMizable if we would like to make it analogous to XMLizable), if it does it is just returned from resolve directly. A similar extension is needed for the transform method so that it also becomes DOMSource aware. Then you just creates a source like e.g. XModuleSource that implements DOMSource and finds and return your DOM from somewhere. AFAIK neither Saxon or Xalan is as efficient with a DOMSource as with their internal specalized XML tree representation. But it should be much more efficient than to serialize your DOM and build the internal representation. /Daniel
DO NOT REPLY [Bug 32620] New: - Tiny typo in AbstractTextSerializer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32620. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32620 Summary: Tiny typo in AbstractTextSerializer Product: Cocoon 2 Version: Current SVN 2.1 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Small typo in the comment around line 364 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 32620] - Tiny typo in AbstractTextSerializer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32620. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32620 --- Additional Comments From [EMAIL PROTECTED] 2004-12-10 00:44 --- Created an attachment (id=13716) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=13716action=view) small typo fix Here's the fix -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 32620] - [PATCH] Tiny typo in AbstractTextSerializer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32620. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32620 [EMAIL PROTECTED] changed: What|Removed |Added Summary|Tiny typo in|[PATCH] Tiny typo in |AbstractTextSerializer |AbstractTextSerializer -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 32620] - [PATCH] Tiny typo in AbstractTextSerializer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32620. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32620 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #13716|0 |1 is obsolete|| --- Additional Comments From [EMAIL PROTECTED] 2004-12-10 00:48 --- Created an attachment (id=13717) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=13717action=view) small typo fix w/o debugging changes -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: Lame question...
Vadim Gritsenko said: Pier Fumagalli wrote: Is there something like that in Cocoon (allow to pass a full DOM as a parameter to the XSLT processor) or shall I start coding? Probably that's what you want: http://issues.apache.org/bugzilla/show_bug.cgi?id=9916 And no, it's not here yet. One workaround I see is to write extension which would somehow get to the DOM and return it to xslt processor... It would seem to be fairly trivial to modify TraxTransformer to accept as parameters the names of input modules it should call along with the desired attribute. These could then be invoked in getLogicSheetParameters and added to the parameter map. Ralph
Re: how to list all sitemap components
Bertrand Delacretaz wrote: Upayavira a écrit : ...cd build/cocoon-2.1.7-dev/javadocs/ grep -rl SitemapModelComponent * Good one! Here's the pretty listing then: for i in $(grep -rl SitemapModelComponent * | grep org/apache) do echo $i | sed 's/\//\./g' | sed 's/\.html$//' done There's still a bit of junk left (package-frame etc) but it's a good start. Thanks, that will be suitable. Fiddling with the SitemapTask.java i can also getting a listing. So i will be able to work out a solution. Thanks. --David
A novel way of finding Cocoon-driven sites on the web
(at least those which have problems ;-) http://www.google.ch/search? q=%22internal%20server%20error%22%20org.apache.cocoon -Bertrand smime.p7s Description: S/MIME cryptographic signature
