Carsten Ziegeler wrote:
David Crossley wrote:
Carsten Ziegeler wrote:
I just fixed some bugs in the catalog resolving code; as far
as I can tell everything is working fine. If you experience
problems, just let me know.
Most bits seem to be working again, e.g. main Cocoon
Torsten Curdt wrote:
Carsten Ziegeler wrote:
We discussed this topic several times, so I think we can
come to a conclusion now.
Currently, we have JDK 1.2 as a minimal requirement for 2.1,
but afaik the avalon framework requires JDK 1.3 anyway and
the poll started recently showed, that most are
David Crossley wrote:
Now, there is something wrong with this approach. We can easily
change (which should be the 'correct' solution) that a path
starting with / is treated as an absolute path. So
if you want to load from the context directory, you have
to specify WEB-INF/.. instead of
Carsten Ziegeler wrote, On 14/03/2003 8.23:
Upayavira wrote_
Do we have hard dependencies on servlet ? AFAIK we have some for those
components that can't live without it (e.g. JSPGenerator), but are
there others ?
Try running the CLI without a reference to servlet-XXX.jar. It
fails whilst
Carsten Ziegeler wrote:
snip/
Ok, done (I hope) - I changed the implementation and the cocoon.xconf.
How can we test it to ensure that it works correctly?
The main way is via the samples/catalog/
(top Samples page = Catalog Entity Resolver)
Try the first sample to ensure that default config
Carsten Ziegeler wrote:
The flow stuff is an optional component, which means I can use it
or not. Cocoon started as a web publishing framework and as flow is
not directly a core component for web publishing but for web
applications, I really would like to see flow as an own block
that I can either
Stefano Mazzocchi wrote, On 14/03/2003 10.31:
...
First of all, there is a major architectural difference between moving
the portal-framework into a block and moving flow into a block. Why?
because the first is 'on top' of cocoon, the second is 'in cocoon'.
Nicely worded. I agree.
Now, I
David Crossley wrote:
Carsten Ziegeler wrote:
snip/
Ok, done (I hope) - I changed the implementation and the cocoon.xconf.
How can we test it to ensure that it works correctly?
The main way is via the samples/catalog/
(top Samples page = Catalog Entity Resolver)
Try the first sample
Hi:
I currently downloaded the lastest CVS from cocoon-2.1. I am using Tomcat
4.1.18. After a sucessfull compile of the sources. I noted the following:
1-If I install the cocoon.war into Tomcat, after this I shutdown it using
./shutdown.sh
Please note that I already can see the working
Antonio Gallardo wrote:
Hi:
I currently downloaded the lastest CVS from cocoon-2.1. I am using Tomcat
4.1.18. After a sucessfull compile of the sources. I noted the following:
1-If I install the cocoon.war into Tomcat, after this I shutdown it using
./shutdown.sh
Please note that I already can
I just did a fix for absolute paths on windows. All your
tests work for me on w2k.
Carsten
Nicola Ken Barozzi wrote:
Well, the fact is that some parts reference the CocoonServlet, and the
StreamGenerator is usable only on Servlets! Ok, this has already been
discussed, so I think we should get to a conclusion here.
Proposal:
1) move all environments in separate
Just a couple of corrections.
Carsten Ziegeler wrote, On 14/03/2003 14.13:
...
Ok, we should consider adding libs to an environment directory as well,
so the servlet.jar could become part of the servlet environment.
+1
...
Shouldn't this be added to the Request? The StreamGenerator does not
Stefano Mazzocchi wrote:
These RT propose two things:
1) move out flow as a block
2) make the sitemap syntax pluggable
Yes, but I see 1) as a need and would be happy about 2).
- people use cocoon in a non-servlet environment and would like to see
all servlet hooks removed
Yes.
On Fri, Mar 14, 2003 at 05:09:16AM -0600, Antonio Gallardo wrote:
Hi:
I currently downloaded the lastest CVS from cocoon-2.1. I am using Tomcat
4.1.18. After a sucessfull compile of the sources. I noted the following:
1-If I install the cocoon.war into Tomcat, after this I shutdown it
Carsten Ziegeler wrote:
- people don't like/use actions and would like to see support for it
removed
No, like Nicola said, these are usual sitemap components.
I don't use actions nor like them so they are not 'usual' for me as much
as flow is not 'usual' for you if you don't like nor use it.
]
prepare:
[echo]
+---+
[echo] Apache Cocoon 20030314 [1999-2003]
[echo
On Donnerstag, März 13, 2003, at 09:28 Uhr, Christopher Oliver wrote:
I've made a first cut at implementing the Java PetStore example
application using Cocoon. I started by converting the Ibatis PetStore
(https://sourceforge.net/projects/ibatisjpetstore)
I deployed it just now, using
Nicola Ken Barozzi wrote:
Stefano Mazzocchi wrote, On 14/03/2003 10.31:
...
First of all, there is a major architectural difference between moving
the portal-framework into a block and moving flow into a block. Why?
because the first is 'on top' of cocoon, the second is 'in cocoon'.
Nicely
Nicola Ken Barozzi wrote:
Carsten Ziegeler wrote, On 14/03/2003 8.23:
Upayavira wrote_
Do we have hard dependencies on servlet ? AFAIK we have some for those
components that can't live without it (e.g. JSPGenerator), but are
there others ?
Try running the CLI without a reference to
Stefano Mazzocchi wrote:
But: during the last two years, from time to time I had the need
to extend the sitemap syntax, because that would have made some things
much more easier. As it was not possible, we used some other methods
like actions etc.
Having a solid contracts doesn't mean we
Stefano Mazzocchi wrote, On 14/03/2003 14.49:
Nicola Ken Barozzi wrote:
...
- people don't like/use actions and would like to see support for it
removed
? I regard actions on par with all other Cocoon Sitemap Components.
I, for one, don't.
We know, we know ;-P
They are part of our basic
leo leonid wrote:
I never used velocity templates so far. In order to get your snapshot
running (so far I get a ConfigurationException: Type 'flow_velocity' is
not defined) I wanted to have a look at the velocity-cocoon samples.
Unfortunately the are not available in the latest 2.1 CVS build.
On Freitag, März 14, 2003, at 03:24 Uhr, Christopher Oliver wrote:
leo leonid wrote:
I never used velocity templates so far. In order to get your snapshot
running (so far I get a ConfigurationException: Type 'flow_velocity'
is not defined) I wanted to have a look at the velocity-cocoon
On Friday, March 14, 2003, at 09:03 AM, David Crossley wrote:
The main way is via the samples/catalog/
(top Samples page = Catalog Entity Resolver)
Try the first sample to ensure that default config
is okay.
No, I get :
An error occurredorg.apache.cocoon.ProcessingExceptionUnable to get
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18003.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On 14 Mar 2003 at 10:54, Nicola Ken Barozzi wrote:
./src/modules/flow
./src/modules/servlet-environment
./src/modules/cli-environment
./src/modules/bean-environment
./src/modules/instrumentation
./src/deprecated -- move it here for consistency
Minor point, but seeing as the cli uses the
Hi Jeff!
Thanks for the answer. I was going crazy with this. Also I was trying the
new 4.1.21 BETA for development purpose when the problrm starts.
This is why I changed all back and trying to resolve this issue. Well, I
looks like I have not Good luck when did the change. :-D
Best Regards,
Hi All,
Any idea why XSPs are throwing this? :
17:21:40.007 WARN!! Error for /samples/xsp/simple
java.lang.ExceptionInInitializerError: corrupted file parser2.rsc
at
org.eclipse.jdt.internal.compiler.parser.Parser.clinit(Parser.java:364
)
at
Here's a summary of some of the recent issues with the Flow for discussion:
1) Storing the flow context object and continuation in environment
attributes:
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=104673257019781w=2
This seems easy to fix. But I personally don't understand the
First the good news:
Avalon is no longer the problem preventing GUMP builds. As Avalon has
been going through its growing pains in its infancy, we have been taking
some serious strides toward stability and simplifying our code base.
As part of that effort, we are releasing all the Avalon
leo leonid wrote:
Eventually, I'd like to add this to the flow samples, but in the
meantime if anyone is interested in helping, let me know and I'll
check it into the scratchpad. (Unfortunately the scratchpad samples
are still broken though).
Please do. A sample like this would be sufficient
Hi,
Not sure quite where to send this, but I'm sure someone on this list can
deal with it ;-)
http://xml.apache.org/cvs.html is referring to the old xml-cocoon and
xml-cocoon2 repositories.
Andrew.
--
Andrew SavoryEmail: [EMAIL PROTECTED]
Managing Director
Berin Loritsch wrote:
First the good news:
Avalon is no longer the problem preventing GUMP builds. As Avalon has
been going through its growing pains in its infancy, we have been taking
some serious strides toward stability and simplifying our code base.
As part of that effort, we are releasing
Carsten Ziegeler wrote:
Stefano Mazzocchi wrote:
But: during the last two years, from time to time I had the need
to extend the sitemap syntax, because that would have made some things
much more easier. As it was not possible, we used some other methods
like actions etc.
Having a solid contracts
Stefano Mazzocchi wrote:
Berin Loritsch wrote:
First the good news:
Avalon is no longer the problem preventing GUMP builds. As Avalon has
been going through its growing pains in its infancy, we have been taking
some serious strides toward stability and simplifying our code base.
As part of that
It may not help you at the moment because its still under development,
but with the current XMLForm integration with the Cocoon flow layer, you
can also do validation in JavaScript, meaning you have regular
expressions, String operations, etc, the full power of JavaScript and
Java, if you need
Upayavira wrote, On 14/03/2003 18.19:
On 14 Mar 2003 at 10:54, Nicola Ken Barozzi wrote:
./src/modules/flow
./src/modules/servlet-environment
./src/modules/cli-environment
./src/modules/bean-environment
./src/modules/instrumentation
./src/deprecated -- move it here for consistency
Minor
Minor point, but seeing as the cli uses the bean, surely the CLI
environment should be replaced with a 'more generic'
bean-environment, rather than there being one of each.
Well, actually the CLI has an additional jar needed, the CLI jar (soon
switch as Avalon is doing to commons-cli).
Upayavira wrote, On 14/03/2003 22.50:
Well, actually the CLI has an additional jar needed, the CLI jar (soon
switch as Avalon is doing to commons-cli).
Let me know when we're ready to do so, and I'll happily send in a patch to move to
the commons-cli.
Even now. the sooner tha better :-)
--
With recent updates of Cocoon 2.1-dev from CVS I haven't been able to get
the embedded Jetty to start up (Windows ME, j2sdk1.4.0). Turning echo on I
discovered 2 endless loops in cocoon.bat. Initially there were duplicate
gotPort and gotWebapp labels; I changed the duplicate names.
I then
About 4 days ago the build was changed to differently
handle the way blocks are excluded. Now it looks like
those properties are ignored.
Today one of the blocks is broken. I tried to get around
it as usual by un-commenting the line in local.blocks.properties
to no avail.
Would people please
Hi everybody!
I wonder if anybody ever looked at jelly:
http://jakarta.apache.org/commons/sandbox/jelly/
I found a hint to it in the Wyona/Lenya users mailing list.
It consists of an XML syntax and a tool wich interprets the XML documents and
it seems to be similar to the way ant works.
Would
Folks,
while briefly checking the Wiki, I was confronted with some apparent
abuse: people uploading attachments which don't have much to do with
Cocoon (possibly just making benefit of the bandwidth we are
sponsoring), people playing around on certain non-Sandbox pages, even to
the extreme of
On Fri, 14 Mar 2003, Steven Noels wrote:
while briefly checking the Wiki, I was confronted with some apparent
abuse
Your thoughts, please: what kind of policy would you come up with, or
are willing to live up to?
Maybe raise the bar slightly so it's less easy to make initial edits - add
Hi all,
we've just released the 1.1 version of xReporter, our open source
Avalon/Cocoon-based database reporting framework, available from
http://xreporter.cocoondev.org/
xReporter consists of 2 main components:
* an Avalon Phoenix-based query server, which is configured through
XML-based
46 matches
Mail list logo
