Re: Installing Cocoon-2.2 on Win2003

2008-02-03 Thread Grzegorz Kossakowski
[EMAIL PROTECTED] pisze:
 The Cocoon 2.2 installation instructions assume changing directories
 happens during the optional Import the block in Eclipse section.
 This causes confusion when skipping to the Run the block as Java web
 application.  Please change the order of sections to Install,
 Run, then Develop.  Why would anyone start development without
 verifying the Hello World example runs properly?

Good suggestion. I'll adjust docs as soon as I have some spare time.

 After changing to the block directory, mvn jetty:run runs for a long
 time and ends with errors about missing JARs for Jetty  (see below).

It runs for long time only at first usage because Maven needs to pull all 
dependencies.

 ===
 mvn --version
 Maven version: 2.0.8
 Java version: 1.4.2_15
 OS name: windows 2003 version: 5.2 arch: x86 Family: windows
 
 mvn jetty:run
 ...
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Failed to resolve artifact.
 
 Missing:
 --
 1) org.mortbay.jetty:jetty-util:jar:2.4.1
 
   Try downloading the file manually from the project website.
 
   Then, install it using the command:
   mvn install:install-file -DgroupId=org.mortbay.jetty 
 -DartifactId=jetty-ut
 il -Dversion=2.4.1 -Dpackaging=jar -Dfile=/path/to/file
 
   Alternatively, if you host your own repository you can deploy the file 
 there:
 
   mvn deploy:deploy-file -DgroupId=org.mortbay.jetty 
 -DartifactId=jetty-util
  -Dversion=2.4.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
 -DrepositoryId
 =[id]
 
   Path to dependency:
 1) org.mortbay.jetty:maven-jetty-plugin:maven-plugin:6.1.5
 2) org.mortbay.jetty:jetty:jar:6.1.5
 3) org.mortbay.jetty:jetty-util:jar:2.4.1

snip what=other dependencies on non-existing 2.4.1 version of artifacts/


Damn, you are unbelievably effective on stumbling upon Maven's 
bugs/limitations. ;-)

This problem is caused by infamous combo of Java 1.4.2, Maven 2.0.x and usage 
of ${project.version}
in one of POMs (in this case[1]). This bug is known as MNG-2339[2] and is my 
the most hated issue
with Maven.

Solutions are (all dirty, unfortunately):
1. Upgrade to Java 1.5.x OR
2. Add failing dependencies to your block's pom.xml with hardcoded versions 
instead of
{project.version} expressions OR
3. Attach -Dversion=6.1.5 to the cmd you are running, e.g.:
mvn clean jetty:run -Dversion=6.1.5

The third one is the quickest work-around but the most dirty one at the same 
time. The second
pollutes your pom but is reliable solution until MNG-2339 is fixed. The first 
one is rather
hypothetical options because I presume that if you still stick to Java 1.4.x 
you must have a good
reason for that.

Voting for this issue is probably a good idea. I'm really sorry that you are 
starting with C2.2 in a
such unfortunate way...

[1] http://repo1.maven.org/maven2/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.pom
[2] http://jira.codehaus.org/browse/MNG-2339

-- 
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
http://reflectingonthevicissitudes.wordpress.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Installing Cocoon-2.2 on Win2003

2008-02-03 Thread solprovider
On Sun, Feb 3, 2008 at 6:26 PM, Grzegorz Kossakowski
[EMAIL PROTECTED] wrote:
 [EMAIL PROTECTED] pisze:
  The Cocoon 2.2 installation instructions ...
  Good suggestion. I'll adjust docs as soon as I have some spare time.

Happy to help.

   After changing to the block directory, mvn jetty:run runs for a long
   time and ends with errors about missing JARs for Jetty  (see below).
  It runs for long time only at first usage because Maven needs to pull all 
 dependencies.

I understood that, but others might not.  A note about the lengthy
install might help; at least the screen keeps changing so the admin
knows something is happening. See the italic text on:
http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html

   ===
   mvn --version
   Maven version: 2.0.8
   Java version: 1.4.2_15
   OS name: windows 2003 version: 5.2 arch: x86 Family: windows
  
   mvn jetty:run
   ...
   [ERROR] BUILD ERROR
   [INFO] 
 
   [INFO] Failed to resolve artifact.
  snip what=other dependencies on non-existing 2.4.1 version of artifacts/
  Damn, you are unbelievably effective on stumbling upon Maven's 
 bugs/limitations. ;-)

Just lucky.

  This problem is caused by infamous combo of Java 1.4.2, Maven 2.0.x and 
 usage of ${project.version}
  in one of POMs (in this case[1]). This bug is known as MNG-2339[2] and is my 
 the most hated issue
  with Maven.

  Solutions are (all dirty, unfortunately):
  1. Upgrade to Java 1.5.x OR
  2. Add failing dependencies to your block's pom.xml with hardcoded versions 
 instead of
  {project.version} expressions OR
  3. Attach -Dversion=6.1.5 to the cmd you are running, e.g.:
  mvn clean jetty:run -Dversion=6.1.5

  The third one is the quickest work-around but the most dirty one at the same 
 time. The second
  pollutes your pom but is reliable solution until MNG-2339 is fixed. The 
 first one is rather
  hypothetical options because I presume that if you still stick to Java 1.4.x 
 you must have a good
  reason for that.

The W2003 PC has several versions of Java installed.  I can easily
switch to Java 1.5 or 1.6, but I need Java 1.4.  Lenya 1.3 (my current
project) needs Java 1.4 and Cocoon-2.1.

My next project (an add-on to another company's product) will also
need Java 1.4 and Cocoon.  I was hoping to use Cocoon-2.2.  Assuming
Cocoon-2.2 is similar to Cocoon-2.1, I need to patch it and add
several components before creating an EAR.  Will Maven issues continue
to cause problems after Cocoon is download?

Why is -Dversion=6.1.5 dirty?  What is lost?  What software is being
versioned to 6.1.5?

  Voting for this issue is probably a good idea. I'm really sorry that you are 
 starting with C2.2 in a such unfortunate way...
  Grzegorz Kossakowski

I will vote when I am home.  (I forgot my JIRA logon.)

solprovider

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: installing cocoon docs

2007-02-15 Thread Manuel Mata
 Please forgive this beginners question:-

Everybody was beginner at any time ...

 drwxr-xr-x   64 fergus  fergus2176 Dec 22 00:28
 2.1/

Inside that folder you have an index.html that is the
root file of the docs.

If you want javadocs you have an ant task which
generates it. Type build -p to see all tasks, and
use build instead of ant.

See ya.



__ 
LLama Gratis a cualquier PC del Mundo. 
Llamadas a fijos y móviles desde 1 céntimo por minuto. 
http://es.voice.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Installing cocoon

2005-03-04 Thread Michel SALAIS
Title: Installing cocoon



Thanks 
for your reply Johnsont.
Itcompiles and works now with jdk1.5.
However I forgot to follow the procedure to modify the line 
"source.vm=1.3" in the file build.properties.
Should 
I modify it before building and what are the possible 
effects?

  -Message d'origine-De: Johnson 
  [mailto:[EMAIL PROTECTED]Envoy: jeudi 3 mars 2005 
  13:21: users@cocoon.apache.orgObjet: Re: 
  Installing cocoon
  do not use jdk1.5
  if you want to,see the mail list subject jdk1.5
  
  johnson
  
- Original Message - 
From: 
Michel SALAIS 

To: users@cocoon.apache.org 
Sent: Thursday, March 03, 2005 6:57 
PM
Subject: Installing cocoon

Hi all, 
I am new to XML Cocoona and co but I have some 
familiarity with Apache. 
I have Mandrake 10.0 with the default web server 
installed (ADVX - Based on apache server). I have my JAVA_HOME pointing to 
"/usr/java/jdk1.5.0_01". I have not installed Tomcat yet.
When I launch ./build.sh from the cocoon 
directory, I have the following error message: -- Beginning 
--- Compiling 5 source files to 
/usr/local/cocoon-2.1.6/tools/anttasks javac: target release 1.3 conflicts with default source release 
1.5 
BUILD FAILED /usr/localcocoon-2.1.6/tools/targets/init-build.xml:159:Compile 
failed; see the compiler error output for details. 
Total time: 2 seconds -- End 
--- 
Thanks in advance for your help. 
  


Re: Installing cocoon

2005-03-03 Thread Johnson
Title: Installing cocoon



do not use jdk1.5
if you want to,see the mail list subject jdk1.5

johnson

  - Original Message - 
  From: 
  Michel SALAIS 
  
  To: users@cocoon.apache.org 
  Sent: Thursday, March 03, 2005 6:57 
  PM
  Subject: Installing cocoon
  
  Hi all, 
  I am new to XML Cocoona and co but I have some 
  familiarity with Apache. 
  I have Mandrake 10.0 with the default web server 
  installed (ADVX - Based on apache server). I have my JAVA_HOME pointing to 
  "/usr/java/jdk1.5.0_01". I have not installed Tomcat yet.
  When I launch ./build.sh from the cocoon directory, 
  I have the following error message: -- Beginning 
  --- Compiling 5 source files to 
  /usr/local/cocoon-2.1.6/tools/anttasks javac: target release 1.3 conflicts with default source release 
  1.5 
  BUILD FAILED /usr/localcocoon-2.1.6/tools/targets/init-build.xml:159:Compile failed; 
  see the compiler error output for details. 
  Total time: 2 seconds -- End 
  --- 
  Thanks in advance for your help. 



RE: Installing Cocoon 2.1 on Tomcat 5.x

2004-08-11 Thread Perez Carmona, David



I
suppose like any standard web app, by placing the contents of build/webapp in a
directory inside the webapps directory of Tomcat 5.
I work
in this way for Tomcat 4.1.

  -Mensaje original-De: malikan jones
  [mailto:[EMAIL PROTECTED]Enviado el: miércoles, 11 de agosto de
  2004 7:21Para: [EMAIL PROTECTED]Asunto: Installing
  Cocoon 2.1 on Tomcat 5.x
  How would one install Cocoon 2.1 on Tomcat 5.x. I have looked for
  documentation but couldn't find any?
  
  thanks
  M
  
  
  Do you Yahoo!?New
  and Improved Yahoo! Mail - Send 10MB messages!
  


  *
Este correo ha sido procesado por el Antivirus del Grupo FCC.
*


*
Este correo ha sido procesado por el Antivirus del Grupo FCC
*


Re: Installing Cocoon 2.1 on Tomcat 5.x

2004-08-11 Thread Antonio Gallardo
malikan jones dijo:
 How would one install Cocoon 2.1 on Tomcat 5.x.  I have looked for
 documentation but couldn't find any?

Use the same aproach as for tomcat 4.1.x:

In short: Copy endorsed libs, deploy cocoon and run tomcat...

Best Regards,

Antonio Gallardo.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Installing Cocoon On debian

2004-03-11 Thread Lionel Crine
Glad you find the answer.

We use Cocoon 2.1.3 on a prod server and It's all good.
I think the 2.1 version is enough stable to use it.
Besides, there are so much more functionnalities.

Lionel

At 11:37 09/03/2004 +0100, you wrote:
Thank you very much.

All is ok...(^^)... and sorry for my beginner question (^^)

I use 2.0.4 'cause it's stable...
2.0.4  2.1.4 on dev server.
and
2.0.4 on my prod server.
More information about my problem :
http://cocoon.apache.org/2.0/installing/index.html
Chapter Java 1.4 configuration 
- Original Message -
From: Lionel Crine [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 08, 2004 5:19 PM
Subject: Re: Installing Cocoon On debian
I advise you to use cocoon 2.1.4 and tomcat 4.x on debian.

deb packages are not available on the woody, so get the source and compile
them.
If I remembered correctly : you only have to set the environment variables
(for tomcat, cocoon and the jdk) and launch the build script.
About you error : look at the tomcat and cocoon logs. You may not have the
newest xerces and xalan jars.
Lionel







At 16:58 08/03/2004 +0100, you wrote:
Hello,

(sorry for my poor english...)

I wanna install cocoon (v2.0.4) on debian (woody)

I use :
- JDK 1.4.3 (src)
- Tomcat 3.3a final (pkg)

I use src files (build is OK), I restart tomcat (Ok), but i have a problem
when i launch Cocoon on
http://myserver:myport/cocoon/http://myserver:myport/cocoon/

I have this error :

//

type fatal

message Error in sitemap configuration : UnnamedSelector:
ComponentSelector could not find the component for hint []

description
org.apache.avalon.framework.configuration.ConfigurationException: Error in
sitemap configuration : UnnamedSelector: ComponentSelector could not find
the component for hint []

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

stack-trace
org.apache.avalon.framework.configuration.ConfigurationException: Error in
sitemap configuration : UnnamedSelector: ComponentSelector could not find
the component for hint []
 at

org.apache.cocoon.www.sitemap_xmap.configure(/var/cache/tomcat/DEFAULT/cocoo
n/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:405)
 at

org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(De
faultComponentFactory.java:264)
 at

org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(
ThreadSafeComponentHandler.java:98)
 at

org.apache.cocoon.components.language.generator.GeneratorSelector.addGenerat
or(GeneratorSelector.java:187)
 at

org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createR
esource(ProgramGeneratorImpl.java:357)
 at

org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(Pr
ogramGeneratorImpl.java:312)
 at org.apache.cocoon.sitemap.Handler.run(Handler.java:267)
 at java.lang.Thread.run(Thread.java:534)
Caused by: org.apache.avalon.framework.component.ComponentException:
UnnamedSelector: ComponentSelector could not find the component for hint []
 at

org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(Exca
liburComponentSelector.java:198)
 at

org.apache.cocoon.sitemap.DefaultSitemapComponentSelector.select(DefaultSite
mapComponentSelector.java:101)
 at

org.apache.cocoon.sitemap.DefaultSitemapComponentSelector.select(DefaultSite
mapComponentSelector.java:104)
 at

org.apache.cocoon.www.sitemap_xmap.preparePattern(/var/cache/tomcat/DEFAULT/
cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:1554)
 at

org.apache.cocoon.www.sitemap_xmap.prepareMatchers(/var/cache/tomcat/DEFAULT
/cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:1573)
 at

org.apache.cocoon.www.sitemap_xmap.configure(/var/cache/tomcat/DEFAULT/cocoo
n/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:398)
 ... 7 more
request-uri
/cocoon/
path-info
//

I have the same problem when i use the cocoon2 debian package...
It-is a problem of jar's files loading order ?
may i change the server.xml configuration file of Tomcat ? i think not...

I'm sure there's a thread on this mailing list with the answer but i don't
found it !
Thank you for you help.

Laurent
laurent dot berthelot at studioblanc dot fr
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70

Re: Installing Cocoon On debian

2004-03-09 Thread Laurent BERTHELOT
Thank you very much.

All is ok...(^^)... and sorry for my beginner question (^^)

I use 2.0.4 'cause it's stable...
2.0.4  2.1.4 on dev server.
and
2.0.4 on my prod server.

More information about my problem :
http://cocoon.apache.org/2.0/installing/index.html
Chapter Java 1.4 configuration 


- Original Message - 
From: Lionel Crine [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 08, 2004 5:19 PM
Subject: Re: Installing Cocoon On debian


I advise you to use cocoon 2.1.4 and tomcat 4.x on debian.

deb packages are not available on the woody, so get the source and compile
them.
If I remembered correctly : you only have to set the environment variables
(for tomcat, cocoon and the jdk) and launch the build script.


About you error : look at the tomcat and cocoon logs. You may not have the
newest xerces and xalan jars.


Lionel







At 16:58 08/03/2004 +0100, you wrote:
Hello,

(sorry for my poor english...)

I wanna install cocoon (v2.0.4) on debian (woody)

I use :
- JDK 1.4.3 (src)
- Tomcat 3.3a final (pkg)

I use src files (build is OK), I restart tomcat (Ok), but i have a problem
when i launch Cocoon on
http://myserver:myport/cocoon/http://myserver:myport/cocoon/

I have this error :

//

type fatal

message Error in sitemap configuration : UnnamedSelector:
ComponentSelector could not find the component for hint []

description
org.apache.avalon.framework.configuration.ConfigurationException: Error in
sitemap configuration : UnnamedSelector: ComponentSelector could not find
the component for hint []

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

stack-trace
org.apache.avalon.framework.configuration.ConfigurationException: Error in
sitemap configuration : UnnamedSelector: ComponentSelector could not find
the component for hint []
 at

org.apache.cocoon.www.sitemap_xmap.configure(/var/cache/tomcat/DEFAULT/cocoo
n/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:405)
 at

org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(De
faultComponentFactory.java:264)
 at

org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(
ThreadSafeComponentHandler.java:98)
 at

org.apache.cocoon.components.language.generator.GeneratorSelector.addGenerat
or(GeneratorSelector.java:187)
 at

org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createR
esource(ProgramGeneratorImpl.java:357)
 at

org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(Pr
ogramGeneratorImpl.java:312)
 at org.apache.cocoon.sitemap.Handler.run(Handler.java:267)
 at java.lang.Thread.run(Thread.java:534)
Caused by: org.apache.avalon.framework.component.ComponentException:
UnnamedSelector: ComponentSelector could not find the component for hint []
 at

org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(Exca
liburComponentSelector.java:198)
 at

org.apache.cocoon.sitemap.DefaultSitemapComponentSelector.select(DefaultSite
mapComponentSelector.java:101)
 at

org.apache.cocoon.sitemap.DefaultSitemapComponentSelector.select(DefaultSite
mapComponentSelector.java:104)
 at

org.apache.cocoon.www.sitemap_xmap.preparePattern(/var/cache/tomcat/DEFAULT/
cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:1554)
 at

org.apache.cocoon.www.sitemap_xmap.prepareMatchers(/var/cache/tomcat/DEFAULT
/cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:1573)
 at

org.apache.cocoon.www.sitemap_xmap.configure(/var/cache/tomcat/DEFAULT/cocoo
n/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:398)
 ... 7 more
request-uri
/cocoon/
path-info
//

I have the same problem when i use the cocoon2 debian package...
It-is a problem of jar's files loading order ?
may i change the server.xml configuration file of Tomcat ? i think not...

I'm sure there's a thread on this mailing list with the answer but i don't
found it !
Thank you for you help.

Laurent
laurent dot berthelot at studioblanc dot fr

Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Installing Cocoon On debian

2004-03-08 Thread Lionel Crine
I advise you to use cocoon 2.1.4 and tomcat 4.x on debian.

deb packages are not available on the woody, so get the source and compile 
them.
If I remembered correctly : you only have to set the environment variables 
(for tomcat, cocoon and the jdk) and launch the build script.

About you error : look at the tomcat and cocoon logs. You may not have the 
newest xerces and xalan jars.

Lionel







At 16:58 08/03/2004 +0100, you wrote:
Hello,

(sorry for my poor english...)

I wanna install cocoon (v2.0.4) on debian (woody)

I use :
- JDK 1.4.3 (src)
- Tomcat 3.3a final (pkg)
I use src files (build is OK), I restart tomcat (Ok), but i have a problem 
when i launch Cocoon on 
http://myserver:myport/cocoon/http://myserver:myport/cocoon/

I have this error :

//

type fatal

message Error in sitemap configuration : UnnamedSelector: 
ComponentSelector could not find the component for hint []

description 
org.apache.avalon.framework.configuration.ConfigurationException: Error in 
sitemap configuration : UnnamedSelector: ComponentSelector could not find 
the component for hint []

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

stack-trace
org.apache.avalon.framework.configuration.ConfigurationException: Error in 
sitemap configuration : UnnamedSelector: ComponentSelector could not find 
the component for hint []
at 
org.apache.cocoon.www.sitemap_xmap.configure(/var/cache/tomcat/DEFAULT/cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:405)
at 
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:264)
at 
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:98)
at 
org.apache.cocoon.components.language.generator.GeneratorSelector.addGenerator(GeneratorSelector.java:187)
at 
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createResource(ProgramGeneratorImpl.java:357)
at 
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(ProgramGeneratorImpl.java:312)
at org.apache.cocoon.sitemap.Handler.run(Handler.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.apache.avalon.framework.component.ComponentException: 
UnnamedSelector: ComponentSelector could not find the component for hint []
at 
org.apache.avalon.excalibur.component.ExcaliburComponentSelector.select(ExcaliburComponentSelector.java:198)
at 
org.apache.cocoon.sitemap.DefaultSitemapComponentSelector.select(DefaultSitemapComponentSelector.java:101)
at 
org.apache.cocoon.sitemap.DefaultSitemapComponentSelector.select(DefaultSitemapComponentSelector.java:104)
at 
org.apache.cocoon.www.sitemap_xmap.preparePattern(/var/cache/tomcat/DEFAULT/cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:1554)
at 
org.apache.cocoon.www.sitemap_xmap.prepareMatchers(/var/cache/tomcat/DEFAULT/cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:1573)
at 
org.apache.cocoon.www.sitemap_xmap.configure(/var/cache/tomcat/DEFAULT/cocoon/cocoon-files/org/apache/cocoon/www/sitemap_xmap.java:398)
... 7 more
request-uri
/cocoon/
path-info
//

I have the same problem when i use the cocoon2 debian package...
It-is a problem of jar's files loading order ?
may i change the server.xml configuration file of Tomcat ? i think not...
I'm sure there's a thread on this mailing list with the answer but i don't 
found it !
Thank you for you help.

Laurent
laurent dot berthelot at studioblanc dot fr
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Installing cocoon

2004-01-30 Thread Anna Bikkina
I do not have spaces in my path.Its a linux box. I attached the build output

Thanks,
Anna.

On Thursday 29 January 2004 06:06 pm, Joerg Heinicke wrote:
 On 29.01.2004 23:52, Anna Bikkina wrote:
  I changed the local.block.properties and there are no error after
  restarting tomcat now. What is this deli block used for?

 http://wiki.cocoondev.org/Wiki.jsp?page=BlockDescriptions

  I am still having problems during building the war.

 I asked for spaced in the path? Can you post the build output?

 Joerg

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

Apache Cocoon Build System
--
Buildfile: build.xml

prepare:
+---+
 Apache Cocoon 2.1.3 [1999-2003]
+---+
 Building with Apache Ant version 1.5.4 compiled on August 12 2003
 using build file /home/anna/cocoon-2.1.3/build.xml
 Compiling with debug on, optimize on, deprecation off
+| W A R N I N G |--+
   This build is targeted for use with JVM 1.4
 Using this build on a virtual machine other than the one
   it is targeted for may result in runtime errors.
+---+

cocoon-block-cron-compile:
---
ATTENTION: cron is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-precept-compile:
---
ATTENTION: precept is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-eventcache-compile:
---
ATTENTION: eventcache is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-repository-compile:
---
ATTENTION: repository is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-slide-compile:
---
ATTENTION: slide is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-proxy-compile:
---
ATTENTION: proxy is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-asciiart-compile:
---
ATTENTION: asciiart is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-mail-compile:
---
ATTENTION: mail is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-axis-compile:
---
ATTENTION: axis is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-taglib-compile:
---
ATTENTION: taglib is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-woody-compile:
---
ATTENTION: woody is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-qdox-compile:
---
ATTENTION: qdox is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-portal-compile:
---
ATTENTION: portal is marked unstable.
It should be considered alpha quality
which means that its API might change without notice.
---

cocoon-block-xmlform-excluded:
---
ATTENTION: xmlform is excluded from the build.
---

cocoon-block-petstore-compile:
---
ATTENTION: petstore is 

Re: Installing cocoon

2004-01-30 Thread Joerg Heinicke
On 30.01.2004 15:51, Anna Bikkina wrote:
I do not have spaces in my path.Its a linux box. I attached the build output
...

BUILD SUCCESSFUL
Total time: 1 minute 39 seconds
Didn't you say you have problems with your build :-)

Also try a build clean war, otherwise some steps are skipped because 
of an uptodate test.

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Installing cocoon

2004-01-29 Thread Joerg Heinicke
How do you build it? Just build in the root directory of your Cocoon 
sources and everything should work. Is it possible that you do not use 
Cocoon's build script?

Joerg

On 29.01.2004 21:55, Anna Bikkina wrote:

Hi,

I am new to cocoon. Trying to install it . It gives compilation error saying 
ant is not found and javax.jdo.PersistenceManager is not found. can anyone 
help me to come over this. I tried to add ant to the classpath and place it 
in the lib directory in cocoon. It still doesnt work. Infact I see a ant jar 
in tools/lib directory. I am using cocoon2.1.3.

Thanks,
Anna.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Installing cocoon

2004-01-29 Thread Anna Bikkina
I did ./build.sh in the cocoon main directory. It does not find ant jar and 
jdo jar but then build turned out successful inspite of the errors.

When I deployed the war to tomcat and restarted tomcat I got the following 
errors in the tomcat logs. The examples and other can be accessed though 
using localhost:8080/cocoon link.

java.io.FileNotFoundException
java.io.FileNotFoundException
at 
org.apache.naming.resources.DirContextURLConnection.getInputStream(DirContextURLConnection.java:344)
at java.net.URL.openStream(URL.java:960)
at com.hp.hpl.deli.Workspace.getResource(Workspace.java:474)
at com.hp.hpl.deli.VocabularyConfig.init(VocabularyConfig.java:104)
at com.hp.hpl.deli.Vocabulary.init(Vocabulary.java:37)
at com.hp.hpl.deli.Workspace$1$CreateWorkspace.init(Workspace.java:191)
at com.hp.hpl.deli.Workspace.configure(Workspace.java:367)
at org.apache.cocoon.components.deli.DeliImpl.initialize(DeliImpl.java:148)
at 
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:282)
at 
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:310)
at 
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:143)
at 
org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:556)
at 
org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:547)
at 
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:282)
at org.apache.cocoon.Cocoon.initialize(Cocoon.java:340)
at 
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:2




no protocol: 
com.hp.hpl.jena.rdf.arp.ParseException: {E201} Syntax error when processing 
EOF.
Input to RDF parser ended prematurely. This is often related to an XML parser 
abort.
Encountered EOF Was expecting one of:
XML ELEMENT CONTENT 
 
start element rdf:RDF 
start element rdf:Description 
general start element tag 

at 
com.hp.hpl.jena.rdf.arp.RDFParser.generateParseException(RDFParser.java:2208)
at com.hp.hpl.jena.rdf.arp.RDFParser.jj_consume_token(RDFParser.java:2095)
at com.hp.hpl.jena.rdf.arp.RDFParser.root(RDFParser.java:1325)
at com.hp.hpl.jena.rdf.arp.RDFParser.embeddedFile(RDFParser.java:1308)
at com.hp.hpl.jena.rdf.arp.ARPFilter.parse(ARPFilter.java:293)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:227)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:256)
at com.hp.hpl.jena.rdf.model.impl.ModelCom.read(ModelCom.java:173)
at com.hp.hpl.deli.VocabularyConfig.schemaProcess(VocabularyConfig.java:250)
at com.hp.hpl.deli.VocabularyConfig.init(VocabularyConfig.java:105)
at com.hp.hpl.deli.Vocabulary.init(Vocabulary.java:37)
at com.hp.hpl.deli.Workspace$1$CreateWorkspace.init(Workspace.java:191)
at com.hp.hpl.deli.Workspace.configure(Workspace.java:367)
at org.apache.cocoon.components.deli.DeliImpl.initialize(DeliImpl.java:148)
at 
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:282)
at 
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:310)
at 
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:143)
at 
org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:556)
at 
org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:547)
at 
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:282)
at org.apache.cocoon.Cocoon.initialize(Cocoon.java:340)
at 
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:282)


Thanks,
Anna.


On Thursday 29 January 2004 05:20 pm, Joerg Heinicke wrote:
 How do you build it? Just build in the root directory of your Cocoon
 sources and everything should work. Is it possible that you do not use
 Cocoon's build script?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Installing cocoon

2004-01-29 Thread Joerg Heinicke
Strange. Do you have spaces in your directory name? The error with deli 
is well-known and you have to exclude the block from build (see 
install.txt for more info).

Joerg

On 29.01.2004 23:32, Anna Bikkina wrote:

I did ./build.sh in the cocoon main directory. It does not find ant jar and 
jdo jar but then build turned out successful inspite of the errors.

When I deployed the war to tomcat and restarted tomcat I got the following 
errors in the tomcat logs. The examples and other can be accessed though 
using localhost:8080/cocoon link.
... deli stacktrace snipped ...

Thanks,
Anna.
On Thursday 29 January 2004 05:20 pm, Joerg Heinicke wrote:

How do you build it? Just build in the root directory of your Cocoon
sources and everything should work. Is it possible that you do not use
Cocoon's build script?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Installing cocoon

2004-01-29 Thread Anna Bikkina
I changed the local.block.properties and there are no error after restarting 
tomcat now. What is this deli block used for?

I am still having problems during building the war. 

Thank you for the information.

Anna.


On Thursday 29 January 2004 05:39 pm, Joerg Heinicke wrote:
 Strange. Do you have spaces in your directory name? The error with deli
 is well-known and you have to exclude the block from build (see
 install.txt for more info).

 Joerg

 On 29.01.2004 23:32, Anna Bikkina wrote:
  I did ./build.sh in the cocoon main directory. It does not find ant jar
  and jdo jar but then build turned out successful inspite of the errors.
 
  When I deployed the war to tomcat and restarted tomcat I got the
  following errors in the tomcat logs. The examples and other can be
  accessed though using localhost:8080/cocoon link.

 ... deli stacktrace snipped ...

  Thanks,
  Anna.
 
  On Thursday 29 January 2004 05:20 pm, Joerg Heinicke wrote:
 How do you build it? Just build in the root directory of your Cocoon
 sources and everything should work. Is it possible that you do not use
 Cocoon's build script?

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Installing cocoon

2004-01-29 Thread Joerg Heinicke
On 29.01.2004 23:52, Anna Bikkina wrote:

I changed the local.block.properties and there are no error after restarting 
tomcat now. What is this deli block used for?
http://wiki.cocoondev.org/Wiki.jsp?page=BlockDescriptions

I am still having problems during building the war. 
I asked for spaced in the path? Can you post the build output?

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: installing cocoon 2.1 from source code

2003-09-16 Thread Joerg Heinicke
Geoff Howard wrote:

alpana wrote:

please use *build war *to create the war file


I am trying to install Cocoon version 2.1 from source code by 
compiling the source using Jakarta Ant with the commands: 
.\build.bat Dinclude.webapp.libs=yes webapp.

 The cocoon website documentation states very clearly that the command 
I entered is the command I need in order to create the cocoon.war file.


Um, where does it give this incorrect information in the documentation?

Geoff
It's easy if you mix Cocoon 2.0 and 2.1 on the website :-)
The 2.0 installing instructions were out of date and I have updated them 
on the website. They are still not up to date (e.g. include.webapp.libs 
is no longer required, because it's set by default), but at least there 
is no longer the wrong description (build all and so on).

Joerg



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: installing cocoon 2.1 from source code

2003-09-16 Thread Geoff Howard
Joerg Heinicke wrote:
Geoff Howard wrote:

alpana wrote:

please use *build war *to create the war file

I am trying to install Cocoon version 2.1 from source code by 
compiling the source using Jakarta Ant with the commands: 
.\build.bat Dinclude.webapp.libs=yes webapp.

 The cocoon website documentation states very clearly that the 
command I entered is the command I need in order to create the 
cocoon.war file.
Um, where does it give this incorrect information in the documentation?

Geoff
It's easy if you mix Cocoon 2.0 and 2.1 on the website :-)
The 2.0 installing instructions were out of date and I have updated them 
on the website. They are still not up to date (e.g. include.webapp.libs 
is no longer required, because it's set by default), but at least there 
is no longer the wrong description (build all and so on).
Hmm, thought I had checked that after reading his email.  Did something 
happen or did I just not notice how bad it was?

Geoff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: installing cocoon 2.1 from source code

2003-09-16 Thread Joerg Heinicke
http://marc.theaimsgroup.com/?l=xml-cocoon-cvsm=106142924930218w=2
http://marc.theaimsgroup.com/?l=xml-cocoon-cvsm=106142929730259w=2
Some time ago a user used the 2.0 build without any target (= 
defaulting to all, which did not really all) and wondered about all 
the errors. He fixed the complete cocoon.xconf by hand. I changed the 
build.xml and the install docs that time, the website was only not updated.

Joerg

Geoff Howard wrote:

Joerg Heinicke wrote:

I am trying to install Cocoon version 2.1 from source code by 
compiling the source using Jakarta Ant with the commands: 
.\build.bat Dinclude.webapp.libs=yes webapp.

 The cocoon website documentation states very clearly that the 
command I entered is the command I need in order to create the 
cocoon.war file.
Um, where does it give this incorrect information in the documentation?

Geoff
It's easy if you mix Cocoon 2.0 and 2.1 on the website :-)
The 2.0 installing instructions were out of date and I have updated 
them on the website. They are still not up to date (e.g. 
include.webapp.libs is no longer required, because it's set by 
default), but at least there is no longer the wrong description 
(build all and so on).


Hmm, thought I had checked that after reading his email.  Did something 
happen or did I just not notice how bad it was?

Geoff


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: installing cocoon 2.1 from source code

2003-08-28 Thread Geoff Howard
  wrote:
Hi and good day to you all!

I am using the binary version of Cocoon version 2.0.4 for JDK 1.4.

My server is the Apache Jakarta Tomcat version 4.1.27.

My database is MySQL version 4.0.13 using the JConnector driver version 
3.0.8.

My computers operating system is Microsoft Windows 2000 Professional.

I am trying to install Cocoon version 2.1 from source code by compiling 
the source using Jakarta Ant with the commands: .\build.bat 
Dinclude.webapp.libs=yes webapp.

As a result of the compilation a folder called build is created and in 
it are the folders cocoon-2.1 and webapp. In the folder build should 
be a file called cocoon.war but it is not there. It tried searching 
the entire build directory and couldnt find it. What needs to be done 
in order to create this file? The cocoon website documentation states 
very clearly that the command I entered is the command I need in order 
to create the cocoon.war file.

Any help is welcome and greatly appreciated, god bless
The build process has changed significantly since 2.0 and you are using 
2.0 procedures.  Read the INSTALL.txt in the 2.1 directory and the 
install instructions at http://cocoon.apache.org/2.1/

The short answer about building a war, is just do build.bat war  the 
include.webapp.libs is no longer necessary.

Geoff Howard

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: installing cocoon 2.1 from source code

2003-08-28 Thread Timothy Larson
--- àåøé ëäï [EMAIL PROTECTED] wrote:
 Hi and good day to you all!

Good day to you.

 I am trying to install Cocoon version 2.1 from source code by compiling
 the source using Jakarta “Ant” with the commands: “.\build.bat
 –Dinclude.webapp.libs=yes webapp”.

Try .\build.bat war instead.

--Tim Larson


__
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]