Re: upgrade jakarta-bcel ?
Ben Pope escribió: On 11/04/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote: Thanks Ben. FYI, in xalan, bcel is used for xsltc. So I guess it's used in cached pipelines, and I guess the default pipeline is cached, so I guess it was tested ;) It depends, because the "default" xslt transformer is xalan and not xsltc [1]. But don't worry too much testing xsltc. IMHO, the changes in the newer bcel release allows a drop in replacement. Best Regards, Antonio Gallardo. [1] http://svn.apache.org/viewcvs.cgi/cocoon/branches/BRANCH_2_1_X/src/webapp/sitemap.xmap?rev=389028&view=markup Ben Pope -- I'm not just a number. To many, I'm known as a string...
Re: upgrade jakarta-bcel ?
Ben Pope escribió: On 10/04/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote: Ben Pope escribió: With a little digging around, 5.2RC1 has recently been released: http://article.gmane.org/gmane.comp.jakarta.bcel.devel/1052 And they're looking for testers, perhaps it is still time to upgrade? Thanks for the link. This link points to the "Torsten site" in apache. I will not consider it an official release until it shows up in the bcel main site. I guess Jorg is trying to solve maven2 dependencies hell. Using this newer release will be the same as the current one for his goal. Understood, I was pointing out that a newer release is on the horizon, that it might better prepare cocoon for 5.2 when it does arrive, as well as providing a testing ground for bcel. +1 :-) Best Regards, Antonio Gallardo.
Re: upgrade jakarta-bcel ?
On 11/04/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote: > Thanks Ben. > > FYI, in xalan, bcel is used for xsltc. So I guess it's used in cached pipelines, and I guess the default pipeline is cached, so I guess it was tested ;) Ben Pope -- I'm not just a number. To many, I'm known as a string...
Re: upgrade jakarta-bcel ?
Thanks Ben. FYI, in xalan, bcel is used for xsltc. Best Regards, Antonio Gallardo. Ben Pope escribió: In case you or anybody else is interested, I downloaded bcel-5.2rc1.zip, extracted bcel-5.2rc1.jar, ran: mvn install:install-file -DgroupId=jakarta-bcel -DartifactId=jakarta-bcel -Dversion=5.2rc1 -Dpackaging=jar -Dfile=./bcel-5.2rc1.jar Changed: core/cocoon-core/pom.xml: Index: pom.xml === --- pom.xml (revision 393100) +++ pom.xml (working copy) @@ -313,7 +313,7 @@ jakarta-bcel jakarta-bcel - 20040329 + 5.2rc1 org.springframework Rebuilt, and it compiled ok. I also ran the webapp, and nothing spurious happened, but I'm not sure where bcel is used, so I don't know if that tested it or not. Ben Pope -- I'm not just a number. To many, I'm known as a string...
Re: upgrade jakarta-bcel ?
On 10/04/06, Ben Pope <[EMAIL PROTECTED]> wrote: > On 10/04/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote: > > Ben Pope escribió: > > > > > > With a little digging around, 5.2RC1 has recently been released: > > > http://article.gmane.org/gmane.comp.jakarta.bcel.devel/1052 > > > > > > And they're looking for testers, perhaps it is still time to upgrade? > > > > > Thanks for the link. This link points to the "Torsten site" in apache. I > > will not consider it an official release until it shows up in the bcel > > main site. > > > > I guess Jorg is trying to solve maven2 dependencies hell. Using this > > newer release will be the same as the current one for his goal. > > Understood, I was pointing out that a newer release is on the horizon, > that it might better prepare cocoon for 5.2 when it does arrive, as > well as providing a testing ground for bcel. In case you or anybody else is interested, I downloaded bcel-5.2rc1.zip, extracted bcel-5.2rc1.jar, ran: mvn install:install-file -DgroupId=jakarta-bcel -DartifactId=jakarta-bcel -Dversion=5.2rc1 -Dpackaging=jar -Dfile=./bcel-5.2rc1.jar Changed: core/cocoon-core/pom.xml: Index: pom.xml === --- pom.xml (revision 393100) +++ pom.xml (working copy) @@ -313,7 +313,7 @@ jakarta-bcel jakarta-bcel - 20040329 + 5.2rc1 org.springframework Rebuilt, and it compiled ok. I also ran the webapp, and nothing spurious happened, but I'm not sure where bcel is used, so I don't know if that tested it or not. Ben Pope -- I'm not just a number. To many, I'm known as a string...
Re: upgrade jakarta-bcel ?
On 10/04/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote: > Ben Pope escribió: > > > > With a little digging around, 5.2RC1 has recently been released: > > http://article.gmane.org/gmane.comp.jakarta.bcel.devel/1052 > > > > And they're looking for testers, perhaps it is still time to upgrade? > > > Thanks for the link. This link points to the "Torsten site" in apache. I > will not consider it an official release until it shows up in the bcel > main site. > > I guess Jorg is trying to solve maven2 dependencies hell. Using this > newer release will be the same as the current one for his goal. Understood, I was pointing out that a newer release is on the horizon, that it might better prepare cocoon for 5.2 when it does arrive, as well as providing a testing ground for bcel. Ben Pope -- I'm not just a number. To many, I'm known as a string...
Re: upgrade jakarta-bcel ?
Ben Pope escribió: On 10/04/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote: Jorg Heymans escribió: Hi, At the moment we are using jakarta-bcel-20040329.jar . Is there any reason not to upgrade to a more recent 5.0 or 5.1 ? Moving to 5.0 or 5.1 means downgrade. http://jakarta.apache.org/bcel/news.html With a little digging around, 5.2RC1 has recently been released: http://article.gmane.org/gmane.comp.jakarta.bcel.devel/1052 And they're looking for testers, perhaps it is still time to upgrade? Thanks for the link. This link points to the "Torsten site" in apache. I will not consider it an official release until it shows up in the bcel main site. I guess Jorg is trying to solve maven2 dependencies hell. Using this newer release will be the same as the current one for his goal. Best Regards, Antonio Gallardo.
Re: upgrade jakarta-bcel ?
On 10/04/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote: > Jorg Heymans escribió: > > Hi, > > > > At the moment we are using jakarta-bcel-20040329.jar . Is there any > > reason not to upgrade to a more recent 5.0 or 5.1 ? > > > Moving to 5.0 or 5.1 means downgrade. > > http://jakarta.apache.org/bcel/news.html With a little digging around, 5.2RC1 has recently been released: http://article.gmane.org/gmane.comp.jakarta.bcel.devel/1052 And they're looking for testers, perhaps it is still time to upgrade? Ben Pope -- I'm not just a number. To many, I'm known as a string...
Re: Calculated fields
Simone Gianni escribió: -1 for client side. As i wrote, it brings A LOT of complexity, for formatting, double implementation of everything (algorithm must be wrote both for server side and for client side, both for us and for the user), a lot of untidy stuff needed to do it, and it's relatively useless with current great AJAX support. I think it was written in the Jira issue because at that time Ajax was still far. AFAIK, calculated fields main task is inform the user. In other way, if we don't need to inform the webapp user about the "subtotal", "taxes amount in a currency" and so on, then we don't need this feature. This is why IMHO, let's talk first about the functionality before going into implementation details. :-) Best Regards, Antonio Gallardo.
Re: upgrade jakarta-bcel ?
Jorg Heymans escribió: Hi, At the moment we are using jakarta-bcel-20040329.jar . Is there any reason not to upgrade to a more recent 5.0 or 5.1 ? Moving to 5.0 or 5.1 means downgrade. http://jakarta.apache.org/bcel/news.html Best Regards, Antonio Gallardo. If nothing else this would remove another dependency on cvs.a.o, as that's where the snapshot release is currently hosted. Regards, Jorg
Re: Calculated fields
Simone Gianni wrote: > > Sylvain Wallez wrote: >>> My calculated field prototype calls algorithm.calculate() in >>> readFromRequest(). Is there a better place? >>> >> >> There's a problem to compute the initial value, as trigger widgets may >> not be initialized (or a calculated-field's initialize() can call >> initialize() on the widgets it depends on). >> >> >From there on, you should only react to change events from trigger widgets. >> > Yep, I'm just afraid to perform calculations more than once in a > single update. Since i already have a javascript algorithm, I'm afraid > of the possible overhead. The trigger widgets currently set a > "recalculate" flag, and in readFromRequest() i actually perform this : > > - Call super.readFromRequest(). > - If super.readFromRequest() parses a typed value, then the field goes > in "user typed" mode and does not perform any calculation. > - Else checks if the recalculate flag is set. > - In that case call the algorithm. > > Obviusly this poses the following problem : "What if the > readFromRequest() is called for the calculate field before the > readFromRequest() has been called on triggers?". In that case the > following could occurr : > - The algorithm would either fail due to a null value or similar. > - The algorithm would return a non update value. > > I tried a fallback for the first situation, when the algorithm cannot > compute a value. In that case the algorithm is again called when a > trigger notifies a value changed event, but this is untidy and also > have no way to handle the second situation. That's why using event listeners is the way to go : the readFromRequest phase buffers all events and actually sends them only once all widgets have read their values from the request. This allows the form model to be globally consistent when event listeners are called. > Maybe it would be easier to install a ProcessingPhaseListener, using > it this way : > - I receive value changed notifications from triggers, and set the flag. > - In readFromRequest i only check if the user typed something or not. > - When the form notifies it has finished parsing values (and > validating them) : > ... check if the recalculate flag is set > ... in that case call the algorithm > ... clear the recalculate flag > - Also, since an algorithm may also need values from other calculated > fields > ... in getValue(), if the recalculate flag is set, call the algorithm. > ... also use a calcualting flag, to report an error if a circular > calculation is detected. > > Using the ProcessingPhaseListener is a better solution? WDYT? You need to set a flag when a trigger widget has changed, and do the actual recalculation when all events have been fired. I don't remember if there's an associated phase change event that could be used for that. There's a potential problem though if a trigger widget is itself calculated. Or calculated fields must explicitly call the calculate() methods of their trigger widgets that are calculated. >>> I'm also trying to make them editable (if editable="true" specified in >>> the definition), so that if the user wants to "fine tune" the result >>> of a calculation he can modify the calculated value. Obviously, once >>> the calculated field has been modified by the user it will behave like >>> a common field, maybe until the user erases the value bringing the >>> field back to it's calculated nature? >>> >> >> Yikes! Heavy FS smell! >> > FS? Fun Stuff? Free Style? Fiancial Service? :) Flexibility Syndrome, i.e. over-design or YAGNI (you ain't gonna need it). I don't see the use case for it. >>> I tried something to make them also client side, but I don't think >>> it's a good idea. With such a good AJAX support, client side support >>> is rarely useful. Also, it poses a lot of limitations and a lot more >>> work on it : all algorithms should be able to generate a client side >>> counterpart, triggers should be rendered as client side calls to >>> "calculateXXX" functions. There is no tidy way to do this, and some >>> algorithms would be very difficult to port client side. Also, on >>> client side there is no way of apply proper field formatting, so every >>> form using calculated fields with a format different from plain will >>> end up being a mess. >>> >>> WDYT? >>> >> >> This adds more complexity to CForms. But if people consider it useful, >> well, why not. >> > -1 for client side. As i wrote, it brings A LOT of complexity, for > formatting, double implementation of everything (algorithm must be > wrote both for server side and for client side, both for us and for > the user), a lot of untidy stuff needed to do it, and it's relatively > useless with current great AJAX support. I think it was written in the > Jira issue because at that time Ajax was still far. I wasn't speaking of the client side, but only about the increased complexity of the form definition. This adds a new widget type (not that much a problem) and more expressi
upgrade jakarta-bcel ?
Hi, At the moment we are using jakarta-bcel-20040329.jar . Is there any reason not to upgrade to a more recent 5.0 or 5.1 ? If nothing else this would remove another dependency on cvs.a.o, as that's where the snapshot release is currently hosted. Regards, Jorg
Re: Update cocoon.zones
Danny Bols wrote:
> It seems that the samples in the Ajax Block and 2 ("In place editing" and
> "Other Ajax samples") of the Ajax/Dojo in the Forms Block are broken.
Confirmed after first build of stock 2.1.9 release :
Ajax-block:
-
java.lang.ClassNotFoundException:
org.apache.cocoon.template.JXTemplateGenerator
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(NativeMethod)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206)
at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170)
at
org.apache.cocoon.components.ExtendedComponentSelector.configure(ExtendedComponentSelector.java:227)
at
org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector.configure(ComponentsSelector.java:157)
at
org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:201)
at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:289)
at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524)
at
org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:566)
at
org.apache.cocoon.components.treeprocessor.sitemap.SitemapLanguage.createComponentManager(SitemapLanguage.java:90)
Forms block - "in place editing"
-
java.io.FileNotFoundException:
/Users/jheymans/Desktop/cocoon-2.1.9/build/webapp/samples/blocks/forms/forms/inplace_edit_form.xml
(No such file or directory)
The "other ajax samples" link has the same error as the ajax block.
I guess a :( is in order here
Jorg
Re: Calculated fields
On 10.04.2006 14:38, Simone Gianni wrote: Yikes! Heavy FS smell! FS? Fun Stuff? Free Style? Fiancial Service? :) Flexibility Syndrome aka Featuritis. Jörg
Help requierd on PCL serializer
Hi John, Let me introduce myself first. Myself Sarvesh Mulay, working as a Software Engg in a MNC. We are using cocoon framework in our project and we require your help in this regard. Our requirement is that we are currently generating PDF reports (in a web based application) using cocoon, now we want that the same PDF report should be sent directly to the printer, instead of a browser. But the format should be PDF. We understand that the PDF stream (sent through java pgm) cannot be recognized by all printers, so we have to use PCL serializer for this. Please suggest whether this is correct approach and if at all we can use PCL. Also provide some docs abt PCL (searched on apache site could'nt get much info). Cyio, Sarvesh To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.
Re: Calculated fields
Sylvain Wallez wrote: My calculated field prototype calls algorithm.calculate() in readFromRequest(). Is there a better place? There's a problem to compute the initial value, as trigger widgets may not be initialized (or a calculated-field's initialize() can call initialize() on the widgets it depends on). >From there on, you should only react to change events from trigger widgets. Yep, I'm just afraid to perform calculations more than once in a single update. Since i already have a _javascript_ algorithm, I'm afraid of the possible overhead. The trigger widgets currently set a "recalculate" flag, and in readFromRequest() i actually perform this : - Call super.readFromRequest(). - If super.readFromRequest() parses a typed value, then the field goes in "user typed" mode and does not perform any calculation. - Else checks if the recalculate flag is set. - In that case call the algorithm. Obviusly this poses the following problem : "What if the readFromRequest() is called for the calculate field before the readFromRequest() has been called on triggers?". In that case the following could occurr : - The algorithm would either fail due to a null value or similar. - The algorithm would return a non update value. I tried a fallback for the first situation, when the algorithm cannot compute a value. In that case the algorithm is again called when a trigger notifies a value changed event, but this is untidy and also have no way to handle the second situation. Maybe it would be easier to install a ProcessingPhaseListener, using it this way : - I receive value changed notifications from triggers, and set the flag. - In readFromRequest i only check if the user typed something or not. - When the form notifies it has finished parsing values (and validating them) : ... check if the recalculate flag is set ... in that case call the algorithm ... clear the recalculate flag - Also, since an algorithm may also need values from other calculated fields ... in getValue(), if the recalculate flag is set, call the algorithm. ... also use a calcualting flag, to report an error if a circular calculation is detected. Using the ProcessingPhaseListener is a better solution? WDYT? I'm also trying to make them editable (if editable="true" specified in the definition), so that if the user wants to "fine tune" the result of a calculation he can modify the calculated value. Obviously, once the calculated field has been modified by the user it will behave like a common field, maybe until the user erases the value bringing the field back to it's calculated nature? Yikes! Heavy FS smell! FS? Fun Stuff? Free Style? Fiancial Service? :) I tried something to make them also client side, but I don't think it's a good idea. With such a good AJAX support, client side support is rarely useful. Also, it poses a lot of limitations and a lot more work on it : all algorithms should be able to generate a client side counterpart, triggers should be rendered as client side calls to "calculateXXX" functions. There is no tidy way to do this, and some algorithms would be very difficult to port client side. Also, on client side there is no way of apply proper field formatting, so every form using calculated fields with a format different from plain will end up being a mess. WDYT? This adds more complexity to CForms. But if people consider it useful, well, why not. -1 for client side. As i wrote, it brings A LOT of complexity, for formatting, double implementation of everything (algorithm must be wrote both for server side and for client side, both for us and for the user), a lot of untidy stuff needed to do it, and it's relatively useless with current great AJAX support. I think it was written in the Jira issue because at that time Ajax was still far. Simone -- Simone Gianni
Re: Calculated fields
Simone Gianni wrote: > Hi all, > what about calculated fields? In a cocoon form I have a repeater, in > the repeater there are some numeric fields, and i need to show the sum > of values in these fields at the bottom of the page. This can be done > with fd:value-changed and some javascript or custom classes, but > actually since they are mentioned on Jira in the roadmap ( > http://issues.apache.org/jira/browse/COCOON-941 ), I need them, and > they are a good idea, I was wandering how to implement them. > > I tried prototyping something, and basically arrived to this : > > .. inside the repeater .. > > > Items > > > > Price > > > > > Sub total > > > > >items,price > > > > outside the repeater ... > > > Total items > > >/articles/*/items > > > > > Total cost > > > > >/articles/*/subtotal > > > > CalculatedField is a subclass of Field, that gets an Algortihm. The > Algorithm is a simple interface, responsible for calculating the value > and return a list of triggers. Triggers are widgets that will trigger > the re-calculation. > > Calculated fields add value change listeners on all triggers to know > when a recalculation is needed, and also to make it update gracefully > in ajax. Using triggers you don't have to disseminate the form with > value changed listeners to trigger recalculations, and also for simple > algorithms (like the arithmetic one I implemented) triggers are the > operands on which it operates. This IMMO minimizes mistakes. > > My calculated field prototype calls algorithm.calculate() in > readFromRequest(). Is there a better place? There's a problem to compute the initial value, as trigger widgets may not be initialized (or a calculated-field's initialize() can call initialize() on the widgets it depends on). >From there on, you should only react to change events from trigger widgets. > I'm also trying to make them editable (if editable="true" specified in > the definition), so that if the user wants to "fine tune" the result > of a calculation he can modify the calculated value. Obviously, once > the calculated field has been modified by the user it will behave like > a common field, maybe until the user erases the value bringing the > field back to it's calculated nature? Yikes! Heavy FS smell! > I tried something to make them also client side, but I don't think > it's a good idea. With such a good AJAX support, client side support > is rarely useful. Also, it poses a lot of limitations and a lot more > work on it : all algorithms should be able to generate a client side > counterpart, triggers should be rendered as client side calls to > "calculateXXX" functions. There is no tidy way to do this, and some > algorithms would be very difficult to port client side. Also, on > client side there is no way of apply proper field formatting, so every > form using calculated fields with a format different from plain will > end up being a mess. > > WDYT? This adds more complexity to CForms. But if people consider it useful, well, why not. Sylvain -- Sylvain Wallez http://bluxte.net Apache Software Foundation Member
[jira] Closed: (COCOON-1764) Component handling
[ http://issues.apache.org/jira/browse/COCOON-1764?page=all ] Reinhard Poetz closed COCOON-1764: -- Resolution: Won't Fix component handling is done in a different way than it is described here. Other issues will be open to describe the remaining open tasks > Component handling > -- > > Key: COCOON-1764 > URL: http://issues.apache.org/jira/browse/COCOON-1764 > Project: Cocoon > Type: New Feature > Components: - Blocks Framework > Reporter: Reinhard Poetz > > see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113813135727508&w=2 > In the current implementation of blocks, each block has an own component > manager (the choice of which type is configurable) for managing the > components of the block. The block local CM has an InterBlockServiceManager > as parent manager and through it it can access components from component > managers in other blocks that it is *wired* to, (and not from the other > blocks of the system). Let us call this behavior wiring based CM for later > reference. > Now I'm starting to think that the above described behavior is unnecessarily > complicated and has some other problems as well. So if no one protests I'm > going to change it so that the blocks still has own component managers, but > that they register their (exposed) components in a global registry and that > the parent manager of the local component managers access components from the > global registry and not only from the connected blocks. > Consequences > > A global registry is much more similar to the situation in our "compile time" > blocks than the wiring based CM, so it should be easier to migrate, > furthermore so is a global registry used in OSGi so it will be more future > safe as well. > A global registry requires less configuration in block.xml and wiring.xml. It > is enough to declare the dependency on the interfaces of the components in > the POM. If one want to make certain that a certain block is used at run > time, a run time dependency can declared in the POM. Connections in the > block.xml is only used for declaring inter block servlet communication. > A possible disadvantage is that role names could collide in the global > registry but by using URIs or package names it should be possible to > distinguish between components from different manufacturers. > The global registry approach might give run time errors when components are > missing instead of deploy time errors. But this depends to a large extent on > what lookup strategy the components and the local CMs use. If most of the > component lookup is done from within the components using a service manager > the setup problems might be defered to runtime. But if configuration based > dependency injection is used the problems can at least in principle be > detected early. > Local vs Global CMs > --- > A question that not will matter much until we use OSGi is whether the CMs are > used from within the block or from the outside. > The current design assumes that the CM is internal to each block. The reason > for this is that with OSGi R3 it was, IIUC, the only way to be able to have > the implementation classes for the components internal to the bundle. A > global CM would have requried that all implementation packages to be exported. > With R4 there are some new possibilities, one can get a class loader from a > bundle and use that for constructing components in a global CM. OSGi R4 uses > this for the new declarative services manager. A bundle that want to use the > declarative service manager signals that by pointing out its component > declaration with a special manifest header, "Service-Component". We could > have a similar global ECM++ manager for legacy support. It is rather probable > that there will be a OSGi adapted Spring CM, following the same principles. >--- o0o --- > AFAIR, we haven't discussed what lookup strategy we wanted for components in > blocks, I implemented the wiring based strategy because it seemed more > natural for me before. The OSGi CM bridge that Sylvain implemented used OSGis > service registry as a global registry. Gianugo tried to convince me that > global registry was better at ApacheCon, but I was obviously not ready for it > then -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (COCOON-1769) Role Handling
[ http://issues.apache.org/jira/browse/COCOON-1769?page=all ] Reinhard Poetz closed COCOON-1769: -- Resolution: Won't Fix solved by using Spring > Role Handling > - > > Key: COCOON-1769 > URL: http://issues.apache.org/jira/browse/COCOON-1769 > Project: Cocoon > Type: Sub-task > Components: - Blocks Framework > Reporter: Daniel Fagerstrom > > The concept of role handling is Avalon specific, so it doesn't work that well > if we want to register e.g. our sitemap components as OSGi services or Spring > components. Maybe we could just put the role info in the container as well so > that we don't need to maintain a parallel set of rolemanagers for the > blocks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (COCOON-1770) Component Configuration
[ http://issues.apache.org/jira/browse/COCOON-1770?page=all ] Reinhard Poetz closed COCOON-1770: -- Resolution: Fixed done by declarative services > Component Configuration > --- > > Key: COCOON-1770 > URL: http://issues.apache.org/jira/browse/COCOON-1770 > Project: Cocoon > Type: Sub-task > Components: - Blocks Framework > Reporter: Daniel Fagerstrom > > There is no mechanism implemented yet for deployment parameters for > components in blocks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (COCOON-1768) JARed blocks
[ http://issues.apache.org/jira/browse/COCOON-1768?page=all ] Reinhard Poetz closed COCOON-1768: -- Resolution: Won't Fix Obsolete by the use of Equinox (also Felix has solved this recently) > JARed blocks > > > Key: COCOON-1768 > URL: http://issues.apache.org/jira/browse/COCOON-1768 > Project: Cocoon > Type: New Feature > Components: - Blocks Framework > Reporter: Reinhard Poetz > Priority: Minor > > The BlocksManager assumes that the wiring location points to unpacked blocks, > implement support for packed blocks. If we change this, the block deployer > also has to support this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Calculated fields
hepabolu wrote:
First off: great idea!
I agree with Antonio that the syntax should be more flexible than your
initial proposal. I actually had a use case that required even more
elaborate calculation:
The score is the sum of a number of fields (not part of a repeater)
only if all of the fields are set to a value. Example:
Field1, Field2, Field3: each have a range 0..3
TotalScore =
if (empty(Field1) || empty(Field2) || empty(Field3)) {
sum(Field1, Field2, Field3)
}
else {
"score undefined"
}
So two additions:
- use calculated fields for all widgets, rather than just repeaters
- allow a more flexible way of expressing the calculation, maybe a
user-defined class of Expression or Algorithm.
Yes, in my current prototype implementation you are not limited to
repeaters at all! And Algorithms are java classes, already started
writing one for javascript snippet.
I don't have the proper syntax available here, but the last two could
be done in much the same way as the syntax.
Yeah, exactly, they are configured in xconf, as for every other
component. The syntax with fd:value for me is absolutely ok, as long as
you can specify a @type or something to choose between javascript,
xreporter, premade or custom algorithm implementations.
Simone
--
Simone Gianni
Re: Calculated fields
Hi Antonio, > ... > ... > This is a very nice syntax!! However this way we are binding the system to a language. This creates a number of problems : - What language is it? We should stick on xreporter expression not to introduce a new syntax. - AFAIK the current implementation of xreporter expressions does not iterate. - How do we provide expandibility of this language? If we don't we would end up having users not being able to do what they want. Maybe a good tradeoff could be : -- Algorithms in xconf -- Definition samples // Arithmetic var x = widget.getForm() . .. .. // Javascript would be in the fd:value body, it would be a pain to put it in an attribute return result; class="my.company.forms.algorithms.MyCustomAlgorithm"> or my custom language here. There could be some problems in "extracting" triggers from a javascript or xreporter expression, if not preparsing them. So maybe a "triggers" attribute where the user have to (read: can) specify which widgets triggers recaulculation is needed for some algorithms. > I think we should first define the user interface and then go into > implementation details. I do agree!
Re: Update cocoon.zones - AJAX sample error
Bertrand Delacretaz said the following on 10-04-2006 10:13: Le 10 avr. 06 à 09:47, hepabolu a écrit : ...But the AJAX sample shows an error (see below). :-( Does this sample work in the release? On the zone, I've just taken the release, unpacked and started. Haven't checked yet. Merely followed your link to the zone and came across this error. Bye, Helma
Re: Update cocoon.zones - AJAX sample error
Le 10 avr. 06 à 09:47, hepabolu a écrit : ...But the AJAX sample shows an error (see below). :-( Does this sample work in the release? On the zone, I've just taken the release, unpacked and started. -Bertrand smime.p7s Description: S/MIME cryptographic signature
RE: Update cocoon.zones
It seems that the samples in the Ajax Block and 2 ("In place editing" and
"Other Ajax samples") of the Ajax/Dojo in the Forms Block are broken.
--
Danny
> -Original Message-
> From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]
> Sent: maandag 10 april 2006 9:05
> To: dev@cocoon.apache.org
> Subject: Re: Update cocoon.zones
>
>
> Le 8 avr. 06 à 22:17, Antonio Gallardo a écrit :
>
> > .Please update cocoon zones with the latest greatest version [1]. ;-)
>
> Done - http://cocoon.zones.apache.org/demos/release/ now runs 2.1.9
>
> -Bertrand
[EMAIL PROTECTED]: Project daisy-htmlcleaner (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 daisy-htmlcleaner has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-htmlcleaner : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-htmlcleaner-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-htmlcleaner-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #27. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-htmlcleaner (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 daisy-htmlcleaner has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-htmlcleaner : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-htmlcleaner-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-htmlcleaner-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #27. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit-commons (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 jackrabbit-commons has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit-commons : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-commons-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-commons-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #22. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit-commons (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 jackrabbit-commons has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit-commons : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-commons-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-commons-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #22. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdbi (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 jdbi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdbi : Provides convenient access to relational databases using Lis... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdbi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdbi-1.3.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdbi-1.3.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdbi/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdbi/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #21. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdbi (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 jdbi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdbi : Provides convenient access to relational databases using Lis... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdbi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdbi-1.3.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdbi-1.3.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdbi/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdbi/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #21. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project nekodtd (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 nekodtd has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - nekodtd : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/nekodtd/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [nekodtd-0.1.11.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/nekodtd-0.1.11.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/nekodtd/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/nekodtd/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project nekodtd (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 nekodtd has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - nekodtd : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/nekodtd/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [nekodtd-0.1.11.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/nekodtd-0.1.11.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/nekodtd/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/nekodtd/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-framework (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 knopflerfish-framework has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-framework : Knopflerfish Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-framework-1.3.3.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-framework-1.3.3.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-framework (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 knopflerfish-framework has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-framework : Knopflerfish Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-framework-1.3.3.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-framework-1.3.3.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
Re: Update cocoon.zones - AJAX sample error
Bertrand Delacretaz said the following on 10-04-2006 09:04: Le 8 avr. 06 à 22:17, Antonio Gallardo a écrit : .Please update cocoon zones with the latest greatest version [1]. ;-) Done - http://cocoon.zones.apache.org/demos/release/ now runs 2.1.9 Just checked: yes, it shows 2.1.9 But the AJAX sample shows an error (see below). :-( Bye, Helma -- Could not load class org.apache.cocoon.template.JXTemplateGenerator for component named 'jx' at file:/home/cdemos/demos/release/cocoon-2.1.9/build/webapp/samples/blocks/ajax/sitemap.xmap:25:83 context://samples/blocks/ajax/sitemap.xmap - 25:83 Failed to load sitemap from file:/home/cdemos/demos/release/cocoon-2.1.9/build/webapp/samples/blocks/ajax/sitemap.xmap context://samples/blocks/ajax/sitemap.xmap - 25:83 [ConfigurationException] context://samples/blocks/sitemap.xmap - 66:68 context://samples/sitemap.xmap - 201:65 context://sitemap.xmap - 947:66 Java stacktrace[show] java.lang.ClassNotFoundException: org.apache.cocoon.template.JXTemplateGenerator at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:206) at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:170) at org.apache.cocoon.components.ExtendedComponentSelector.configure(ExtendedComponentSelector.java:227) at org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector.configure(ComponentsSelector.java:157) at org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:201) at org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:289) at org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108) at org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524) at org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:566) at org.apache.cocoon.components.treeprocessor.sitemap.SitemapLanguage.createComponentManager(SitemapLanguage.java:90) at org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:389) at org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:369) at org.apache.cocoon.components.treeprocessor.TreeProcessor.buildConcreteProcessor(TreeProcessor.java:339) at org.apache.cocoon.components.treeprocessor.TreeProcessor.setupConcreteProcessor(TreeProcessor.java:304) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:250) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:117) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:234) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:176) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:252) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:117) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:234) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProc
Re: Calculated fields
First off: great idea!
Antonio Gallardo said the following on 10-04-2006 02:46:
What about replacing with something like:
this will allow also to write:
In both later cases, should be able to know that "articles"
is a container and hence it needs to include in the operation the whole
set of rows from the repeater.
I think we should first define the user interface and then go into
implementation details.
I agree with Antonio that the syntax should be more flexible than your
initial proposal. I actually had a use case that required even more
elaborate calculation:
The score is the sum of a number of fields (not part of a repeater) only
if all of the fields are set to a value. Example:
Field1, Field2, Field3: each have a range 0..3
TotalScore =
if (empty(Field1) || empty(Field2) || empty(Field3)) {
sum(Field1, Field2, Field3)
}
else {
"score undefined"
}
So two additions:
- use calculated fields for all widgets, rather than just repeaters
- allow a more flexible way of expressing the calculation, maybe a
user-defined class of Expression or Algorithm.
Some random thoughts:
- use Antonio's suggestion for simple expressions
- allow a javascript function or java class to handle the expression:
function="myjavascriptfunction"/>
or
I don't have the proper syntax available here, but the last two could be
done in much the same way as the syntax.
Bye, Helma
[EMAIL PROTECTED]: Project jing (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 jing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jing : Jing performs XML Validation using RelaxNG schemas Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jing/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jing-20030619.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jing-20030619.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jing/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jing/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #16. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jing (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 jing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jing : Jing performs XML Validation using RelaxNG schemas Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jing/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jing-20030619.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jing-20030619.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jing/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jing/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #16. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project joost (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 joost has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - joost : Streaming Transformation for XML (STX) library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/joost/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [joost-20040330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/joost-20040330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/joost/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/joost/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project joost (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 joost has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - joost : Streaming Transformation for XML (STX) library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/joost/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [joost-20040330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/joost-20040330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/joost/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/joost/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project garbage (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 garbage has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - garbage : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/garbage/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [apache-garbage-0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/apache-garbage-0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/garbage/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/garbage/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #14. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project garbage (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 garbage has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - garbage : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/garbage/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [apache-garbage-0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/apache-garbage-0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/garbage/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/garbage/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #14. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jcr (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 jcr has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jcr : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jcr/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jcr-1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jcr-1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jcr/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jcr/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jcr (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 jcr has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jcr : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jcr/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jcr-1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jcr-1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jcr/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jcr/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit (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 jackrabbit has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #12. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit (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 jackrabbit has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #12. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project itext (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 itext has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - itext : iText is a library that allows you to generate PDF files on ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-1.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/itext-1.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/itext/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/itext/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #11. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project itext (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 itext has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - itext : iText is a library that allows you to generate PDF files on ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-1.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/itext-1.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/itext/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/itext/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #11. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project cowarp (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 cowarp has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cowarp : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cowarp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cowarp-0.5-dev-20051002.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/cowarp-0.5-dev-20051002.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/cowarp/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/cowarp/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #10. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project cowarp (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 cowarp has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cowarp : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cowarp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cowarp-0.5-dev-20051002.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/cowarp-0.5-dev-20051002.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/cowarp/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/cowarp/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #10. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project deli (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 deli has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - deli : Delivery context library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-x050330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/deli-x050330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/deli/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/deli/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #9. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project deli (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 deli has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - deli : Delivery context library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-x050330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/deli-x050330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/deli/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/deli/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #9. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdtcore (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 jdtcore has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdtcore : Java Development Tools from the Eclipse IDE Project Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdtcore/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdtcore-3.1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdtcore-3.1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdtcore/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdtcore/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdtcore (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 jdtcore has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdtcore : Java Development Tools from the Eclipse IDE Project Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdtcore/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdtcore-3.1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdtcore-3.1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdtcore/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdtcore/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-util (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 daisy-util has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-util : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-util-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-util-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #7. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-util (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 daisy-util has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-util : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-util-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-util-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #7. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project xreporter-expression (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 xreporter-expression has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - xreporter-expression : An expression language interpreter. Full details are available at: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xreporter-expression-20040701.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/xreporter-expression-20040701.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #6. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project xreporter-expression (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 xreporter-expression has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - xreporter-expression : An expression language interpreter. Full details are available at: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xreporter-expression-20040701.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/xreporter-expression-20040701.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #6. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-log (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 knopflerfish-log has an issue affecting its community integration. This issue affects 62 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-faces : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A "jcr:" protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-sample : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - forrest : Apache Forrest is an XML standards-oriented documentation fr... - knopflerfish-log : Knopflerfish Log - lenya : Content Management System Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-log_all-1.0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-log_all-1.0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #5. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-log (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 knopflerfish-log has an issue affecting its community integration. This issue affects 62 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-faces : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A "jcr:" protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-sample : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - forrest : Apache Forrest is an XML standards-oriented documentation fr... - knopflerfish-log : Knopflerfish Log - lenya : Content Management System Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-log_all-1.0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-log_all-1.0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #5. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project chaperon (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 chaperon has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - chaperon : Chaperon is a project that helps to convert structured text ... - cocoon-block-chaperon : Java XML Framework - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-20040205.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/chaperon-20040205.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/chaperon/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/chaperon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #4. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project chaperon (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 chaperon has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 34 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - chaperon : Chaperon is a project that helps to convert structured text ... - cocoon-block-chaperon : Java XML Framework - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-20040205.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/chaperon-20040205.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/chaperon/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/chaperon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2810042006, vmgump.apache.org:vmgump-public:2810042006 Gump E-mail Identifier (unique within run) #4. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
Re: Update cocoon.zones
Bertrand Delacretaz escribió: Le 8 avr. 06 à 22:17, Antonio Gallardo a écrit : .Please update cocoon zones with the latest greatest version [1]. ;-) Done - http://cocoon.zones.apache.org/demos/release/ now runs 2.1.9 Great! :-) Best Regards, Antonio Gallardo. P.S: As soon as my ISP restore the connection I will check it. Currently I am losing 29% of packets. :-(
Re: Update cocoon.zones
Le 8 avr. 06 à 22:17, Antonio Gallardo a écrit : .Please update cocoon zones with the latest greatest version [1]. ;-) Done - http://cocoon.zones.apache.org/demos/release/ now runs 2.1.9 -Bertrand smime.p7s Description: S/MIME cryptographic signature
