Re: Ant:NoClassDefFoundError after Cocoon install
Download the newest release of Ant (1.5.1 or higher), install it and set the ANT_HOME environment variable to the installation - dir. In addition you can set the PATH variable to the installation/bin - dir. After that it should (hopefully) work. Helmut On Tue, 01 Apr 2003 10:30:16 +0900, a847356549/mail.h7.dion.ne.jp [EMAIL PROTECTED] wrote: Hello I used Ant1.4.1 with JWSDP-1.0-ea1 under Win98se fairly well until I installed Tomcat4.1.18 Cocoon2.0 and began first Cocoon Lessons. So far, Tomcat4.1.18 Cocoon2.0 work fine. But everytime I want to use Ant1.4.1 by command line input, it fails with Exception in thread 'main' java.lang.NoClassDefFounError:org/apache/tools/ant/Main. To fix it, I updated every ant.jar on my computer with one originally in Tomcat4.1.18\common\lib but in vain. I searched some ANT-maillist archive for this trouble but no clear remedy, finally got an impression, to use Ant1.4.1 like before I may have to cancel Tomcat4.1.18 Cocoon2.0. I hesitated for some time to post this question because it may be off topics. I appreciate slightest hint and any advice will be grateful. ttkaya - 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: [ANN] sunBow 1.0
A great tool. THANK YOU Helmut On Fri, 28 Mar 2003 10:02:12 +0100, Martin Dulisch [EMAIL PROTECTED] wrote: The SN sunBow team are proud to announce version 1.0. This free version is available immediately for download at: http://radio.weblogs.com/0108489/. In addition to numerous bug-fixes, the new version now also supports sub-sitemaps and no longer requires a licence key. sunBow is a collection of Eclipse (2.1) plugins that make it easier to develop Cocoon based applications and XML solutions in general. * XML editor - completition proposals from associated schema - well formed check on save - automatic insertion of closing tags - formatting of the XML content * XSLT development - XSLT transformation - transformation trace * Cocoon - dialog orientated sitemap editor with drag and drop support and validation against a sitemap schema - management of sitemap fragments - configuration of the log level in logkit.xconf * Web application - deployment: automatic tracking of changes - testing: Apache Latka tests can be executed Regards Martin Dulisch - sn AG, Open Source Competence Center Tel.: 05251/1581-75 Klingenderstr. 5mailto:[EMAIL PROTECTED] D-33100 Paderborn http://www.s-und-n.de - - 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: Portal session-context in the portal-fw
Hi,
thanks to everyone who thought about my problem. In the meantime its
working like documented. The problem was that I mixed the xsp-session
logicsheet with the session transformer. After separating these and using
them in the correct manner it worked.
Helmut
On Wed, 26 Mar 2003 15:16:54 +0100, Helmut Tammen [EMAIL PROTECTED]
wrote:
Here are some additional informations:
Cocoon - Verion: 2.1-dev (CVS)
All attributes in the session:
Name: uprofile:portalhandler|sunspotdemo:user_5_guest_guest Value:
{misc=[Lorg.w3c.dom.Node;124154, typeConfPaths=[profile/layout-
profile[not(*)]/portal[not(*)]/layouts[not(*)]/layout[not(*)
]/background[not(*)]/[EMAIL PROTECTED] and formpath and
formdescription], profile/layout-profile[not(*)]/portal[not(*)
]/layouts[not(*) ]/layout[not(*)]/font[not(*)]/[EMAIL PROTECTED] and
formpath and formdescription], profile/layout-profile[not(*)
]/portal[not(*) ]/columns[not(*)]/[EMAIL PROTECTED] and formpath and
formdescription], profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/[EMAIL PROTECTED] and formpath and formdescription],
profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/coplets[not(*)]/[EMAIL PROTECTED] and number and
position]/status[not(*)]/[EMAIL PROTECTED] and formpath and
formdescription], profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/coplets[not(*)]/[EMAIL PROTECTED] and number and
position]/status[not(*)]/[EMAIL PROTECTED] and formpath and
formdescription]], portalLayouts={html=[layout: null], wap=[layout:
null]}, copletLayouts={html=[layout: null], wap=[layout: null]},
typePaths=[profile/layout-profile[not(*)]/portal[not(*)
]/layouts[not(*) ]/layout[not(*)]/background[not(*)]/color[not(*)
]/backgroundcolor|Backgroundcolor, profile/layout-profile[not(*)
]/portal[not(*)]/layouts[not(*)]/layout[not(*)]/font[not(*)
]/color[not(*)]/textcolor|Fontcolor, profile/layout-profile[not(*)
]/portal[not(*)]/columns[not(*)]/number[not(*)]/columnnumber|Amount,
profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/width[not(*)]/CARDINAL|Width, profile/portal-
profile[not(*)]/content[not(*)]/[EMAIL PROTECTED]/coplets[not(*)
]/[EMAIL PROTECTED] and number and position]/status[not(*)]/visible[not(*)
]/BOOLEAN|Visibile, profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/coplets[not(*)]/[EMAIL PROTECTED] and number and
position]/status[not(*)]/size[not(*)]/copletsize|Size],
defCoplets={sundnnews=[coplet: null], customnews=[coplet: null],
feedback=[coplet: null], personalizeguest=[coplet: null], S0=[coplet:
null], consultantprofile=[coplet: null], germany=[coplet: null],
S1=[coplet: null], banknews=[coplet: null]}, profile=[#document-fragment:
null], mediaCoplets={html={}, wap={}}}
Name: portalConfportalhandler:sunspotdemo Value: {S=sunspotdemo-portal,
D=profiles/copletprofile.xml, M=cocoon:raw:/sunspotdemoresource-
userprofile, R=profiles/admintypes.xml,
K=cocoon:raw:/sunspotdemoresource-saveroleprofile, F=profiles/types.xml,
H=cocoon:raw:/sunspotdemoresource-saveglobalprofile, U=false,
J=cocoon:raw:/sunspotdemoresource-roleprofile,
C=profiles/layoutprofile.xml, T=sunspotdemo,
N=cocoon:raw:/sunspotdemoresource-saveuserprofile,
P=cocoon:raw:/sunspotdemoresource-userstatus, B=sunspotdemo-portal,
Q=cocoon:raw:/sunspotdemoresource-saveuserstatus,
G=profiles/globalprofile.xml, V=1, E=profiles/copletprofile.xml}
Name: org.apache.cocoon.webapps.authentication.Handlers Value:
{portalhandler=authentication-Handler portalhandler}
Name: org.apache.cocoon.webapps.authentication.SessionContext Value:
[EMAIL PROTECTED]
Name: org.apache.cocoon.webapps.session.context.TransactionState Value:
[EMAIL PROTECTED]@f2625f}
Name: org.apache.cocoon.webapps.session.context.SessionContext Value:
{org.apache.cocoon.webapps.portal.context.SessionContext:[EMAIL PROTECTED]
Hi,
I cant get any information from the session-context portal.
Following situation:
1. Coplet resource uri: resource uri=cocoon:/sunspotdemo-test/
2. pipeline in sitemap.xmap: map:match pattern=sunspotdemo-test
map:generate src=resources/auth/test.xsp type=serverpages/
map:transform type=session/
map:serialize type=xml/
/map:match
3. xsp - file test.xsp (excerpt):
xsp:page xmlns:xsp=http://apache.org/xsp;
xmlns:session=http://apache.org/xsp/session/2.0;
URI:session:getxml context=portal path=/configuration/uri/br/
color:session:getxml context=portal
path=/layout/coplets/content/background/color/
/xsp:page
Result:
Test.xsp is called and executed (I do some more other things inside it
which work fine) but the strings after URI: and color: are emtpy.
Thanks Helmut
-
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
Bug in portal-fw ??
Hi, I think Ive found a little bug in the portal framework. I hope this is the right place to report it. Changing the resource uri of a coplet has no effect as long as tomcat is not shut down, the files in cache-dir are deleted manually and tomcat is restarted. It does make no difference it the uri is changed via the admin pages of the portal or directly in the file copletprofile.xml. Is there any workaround? Helmut - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Portal session-context in the portal-fw
Hi, I cant get any information from the session-context portal. Following situation: 1. Coplet resource uri: resource uri=cocoon:/sunspotdemo-test/ 2. pipeline in sitemap.xmap: map:match pattern=sunspotdemo-test map:generate src=resources/auth/test.xsp type=serverpages/ map:transform type=session/ map:serialize type=xml/ /map:match 3. xsp - file test.xsp (excerpt): xsp:page xmlns:xsp=http://apache.org/xsp; xmlns:session=http://apache.org/xsp/session/2.0; URI:session:getxml context=portal path=/configuration/uri/br/ color:session:getxml context=portal path=/layout/coplets/content/background/color/ /xsp:page Result: Test.xsp is called and executed (I do some more other things inside it which work fine) but the strings after URI: and color: are emtpy. Thanks Helmut - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portal session-context in the portal-fw
Here are some additional informations:
Cocoon - Verion: 2.1-dev (CVS)
All attributes in the session:
Name: uprofile:portalhandler|sunspotdemo:user_5_guest_guest Value:
{misc=[Lorg.w3c.dom.Node;124154, typeConfPaths=[profile/layout-
profile[not(*)]/portal[not(*)]/layouts[not(*)]/layout[not(*)
]/background[not(*)]/[EMAIL PROTECTED] and formpath and formdescription],
profile/layout-profile[not(*)]/portal[not(*)]/layouts[not(*)
]/layout[not(*)]/font[not(*)]/[EMAIL PROTECTED] and formpath and
formdescription], profile/layout-profile[not(*)]/portal[not(*)
]/columns[not(*)]/[EMAIL PROTECTED] and formpath and formdescription],
profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/[EMAIL PROTECTED] and formpath and formdescription],
profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/coplets[not(*)]/[EMAIL PROTECTED] and number and
position]/status[not(*)]/[EMAIL PROTECTED] and formpath and
formdescription], profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/coplets[not(*)]/[EMAIL PROTECTED] and number and
position]/status[not(*)]/[EMAIL PROTECTED] and formpath and
formdescription]], portalLayouts={html=[layout: null], wap=[layout:
null]}, copletLayouts={html=[layout: null], wap=[layout: null]},
typePaths=[profile/layout-profile[not(*)]/portal[not(*)]/layouts[not(*)
]/layout[not(*)]/background[not(*)]/color[not(*)
]/backgroundcolor|Backgroundcolor, profile/layout-profile[not(*)
]/portal[not(*)]/layouts[not(*)]/layout[not(*)]/font[not(*)
]/color[not(*)]/textcolor|Fontcolor, profile/layout-profile[not(*)
]/portal[not(*)]/columns[not(*)]/number[not(*)]/columnnumber|Amount,
profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/width[not(*)]/CARDINAL|Width, profile/portal-
profile[not(*)]/content[not(*)]/[EMAIL PROTECTED]/coplets[not(*)
]/[EMAIL PROTECTED] and number and position]/status[not(*)]/visible[not(*)
]/BOOLEAN|Visibile, profile/portal-profile[not(*)]/content[not(*)
]/[EMAIL PROTECTED]/coplets[not(*)]/[EMAIL PROTECTED] and number and
position]/status[not(*)]/size[not(*)]/copletsize|Size],
defCoplets={sundnnews=[coplet: null], customnews=[coplet: null],
feedback=[coplet: null], personalizeguest=[coplet: null], S0=[coplet:
null], consultantprofile=[coplet: null], germany=[coplet: null],
S1=[coplet: null], banknews=[coplet: null]}, profile=[#document-fragment:
null], mediaCoplets={html={}, wap={}}}
Name: portalConfportalhandler:sunspotdemo Value: {S=sunspotdemo-portal,
D=profiles/copletprofile.xml, M=cocoon:raw:/sunspotdemoresource-
userprofile, R=profiles/admintypes.xml, K=cocoon:raw:/sunspotdemoresource-
saveroleprofile, F=profiles/types.xml, H=cocoon:raw:/sunspotdemoresource-
saveglobalprofile, U=false, J=cocoon:raw:/sunspotdemoresource-roleprofile,
C=profiles/layoutprofile.xml, T=sunspotdemo,
N=cocoon:raw:/sunspotdemoresource-saveuserprofile,
P=cocoon:raw:/sunspotdemoresource-userstatus, B=sunspotdemo-portal,
Q=cocoon:raw:/sunspotdemoresource-saveuserstatus,
G=profiles/globalprofile.xml, V=1, E=profiles/copletprofile.xml}
Name: org.apache.cocoon.webapps.authentication.Handlers Value:
{portalhandler=authentication-Handler portalhandler}
Name: org.apache.cocoon.webapps.authentication.SessionContext Value:
[EMAIL PROTECTED]
Name: org.apache.cocoon.webapps.session.context.TransactionState Value:
[EMAIL PROTECTED]@f2625f}
Name: org.apache.cocoon.webapps.session.context.SessionContext Value:
{org.apache.cocoon.webapps.portal.context.SessionContext:[EMAIL PROTECTED]
Hi,
I cant get any information from the session-context portal.
Following situation:
1. Coplet resource uri: resource uri=cocoon:/sunspotdemo-test/
2. pipeline in sitemap.xmap: map:match pattern=sunspotdemo-test
map:generate src=resources/auth/test.xsp type=serverpages/
map:transform type=session/
map:serialize type=xml/
/map:match
3. xsp - file test.xsp (excerpt):
xsp:page xmlns:xsp=http://apache.org/xsp;
xmlns:session=http://apache.org/xsp/session/2.0;
URI:session:getxml context=portal path=/configuration/uri/br/
color:session:getxml context=portal
path=/layout/coplets/content/background/color/
/xsp:page
Result:
Test.xsp is called and executed (I do some more other things inside it
which work fine) but the strings after URI: and color: are emtpy.
Thanks Helmut
-
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: Eclipse, Tomcat and Sysdeo Plugin
Thank you Hussayn, I compiled my sources, got no compiler errors and mostly everything inside cocoon worked fine. But when I started the portal application which I wanted to debug Ive got the error that org.appache.cocoon.webapps.authentication.components.AuthenticationManager could not be loaded in spite of being present under WEB-INF/classes. I then copied the cocoon*.jar files that were build with the ant script back to WEB-INF/lib and deleted WEB-INF/classes and everything worked fine again, even the portal application. Any ideas? Thanks Helmut On Tue, 25 Mar 2003 18:51:25 +0100, Hussayn Dabbous [EMAIL PROTECTED] wrote: ok, here is what i did (briefly): 1.) Set up an eclipse java-project named cocoon 2.) Import all cocoon-2.0.4 sources into the cocoon-project (i did this during project creation). 3.) Setup project environment to compile cocoon from within eclipse. You need to add all necessary libs by hand. I also had to discard some classes due to unavailable jars (i remeber about 5 classes only to be deleted from the cocon distrib). Otherwise the project would not compile ;-( 4.) create a launch config as already described on default port 8000 (in fact you can use anything else too) 5.) place breakpoints into any point of the cocoon sources I had no problems as you describe... 6.) Set the JAVA_OPTS as already described. 7.) Start tomcat with startup.sh 8.) Launch the launch config from 4.) 9.) Sit back and watch your appserver beeing fully under your control... no other tricks here ... One question: Why would you prefer to set the JAVA_OPTS by hand? And how are you starting the tomcat server, if you set the JAVA_OPTS by hand ??? I think it is much easier to simply cretae the JAVA_OPTS environment var possibly on a startup script and never think about this again... Ok, remember about this, when you go to production ;-) regards, hussayn ePost wrote: Hi Hussayn, Im just coming back to the debug problem in eclipse (learning a lot of new stuff at the moment). Ive set the startup option for tomcat as you adviced (but via command line not via JAVA_OPTS). In eclipse I start the remote debug session which successfully connects to port 8000. But I cant set any breakpoints in the Cocoon Java Source. Do I have to adjust the source lookup path in eclipse? Ive already tried some settings but nothing worked. Thanks for your answer. Helmut On Thu, 20 Mar 2003 09:34:06 +0100, SAXESS - Hussayn Dabbous [EMAIL PROTECTED] wrote: Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. regards, hussayn Helmut Tammen wrote: Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/ endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2
Eclipse, Tomcat and Sysdeo Plugin
Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) FATAL_E (2003-03-20) 08:33.57:218 [access] (/cocoon21/samples/welcome) HttpProcessor[8080][4]/CocoonServlet: The Cocoon engine failed to process the request. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
