I discovered the problem, for my setup that is, was the build/run environment. Includes work as expected when I did a build of 2.1.8 using JDK 1.4.2_10 and running Cocoon under JDK 1.4.2_10/Tomcat 5.0.28. Building with JDK1.5.0_x and running under JDK1.5.0/Tomcat 5.0.28 and JDK1.5.0/Tomcat 5.5.12 didn't work. I also was frequently getting an initialization error when attempting to run under JDK1.5.0_x.
Is there any advantage to running Cocoon under JDK 1.5 and Tomcat 5.5.x? If not I will continue to use JDK 1.4 and Tomcat 5.0.x as I see more of an advantage to our agency to running Cocoon 2.1.8 versus running JDK 1.5 or Tomcat 5.5.x. Will there ever be a time in Cocoon development in which Cocoon will not run under JDK1.4.2_x and Tomcat 5.0.x? -----Original Message----- From: Schultz, Gary - COMM [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 1:16 PM To: 'users@cocoon.apache.org' Subject: RE: cinclude, include and xinclude in Cocoon 2.1.8 (failure in 2. 1.7 and 2.1.8) I tried in 2.1.7 and get the same results as 2.1.8. I've built Cocoon 2.1.7 and 2.1.8 on Linux and Windows using JDK 1.5. I tested again in our production environment running 2.1.5.1 and everything works fine. I've gone over the configuration and everything appears to be fine. I have to assume something has changed between 2.1.5.1 and 2.1.7 or 2.1.8 that requires changes to cinclude code. I'm trying to understand how something like this could fail this badly. It's a disappointment because our agency is now tied to Cocoon 2.1.5.1. -----Original Message----- From: Schultz, Gary - COMM [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 9:07 AM To: 'users@cocoon.apache.org' Subject: RE: cinclude, include and xinclude in Cocoon 2.1.8 Thanks for the verification. I have verified the output. I will check my setup. I most likely have missed something in configuration. -----Original Message----- From: Jason Johnston [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 8:41 AM To: users@cocoon.apache.org Subject: Re: cinclude, include and xinclude in Cocoon 2.1.8 Have you verified that the output of your XSLT is the same now as it was in the older version? e.g. by putting a <map:serialize type="xml" /> right after your xslt transform? I just did a quick test here with 2.1.8, and an xinclude transform immediately following an xsl transform (which creates the xi:include elements) works just fine. Schultz, Gary - COMM wrote: > I performed a pretty exhaustive search and only found information on > cinclude problems when using POST method. Nothing on cinclude problems > in general, and nothing detailed on the use of cocoon include transformer. > > I should have added that cincludes, includes and xincludes all work > when placed before the <map:transform. In 2.1.5.1 all three includes > also worked when placed after the <map:transform. In 2.1.8 the > includes only work before the <map:transform. The includes are not > working after the <map:transform. > This is a problem in that I'm using the XSLT transformation to create > cincludes dynamically based on parameters determined by element > attribute values passed from the XML source. > > -----Original Message----- > From: Ralph Goers [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 08, 2005 11:28 PM > To: users@cocoon.apache.org > Subject: Re: cinclude, include and xinclude in Cocoon 2.1.8 > > Did you search the mailing list for similar issues. I seem to > recollect that the namespace is different so your cinclude might be > ignored. But I could be wrong. > > Schultz, Gary - COMM wrote: > > >>The following code snippet worked in Cocoon 2.1.5.1 but isn't working >>in Cocoon 2.1.8 >> >> <map:match pattern="TSS-IncludeTest-01.html"> >> <map:generate >>src="d:/comwps/TSS/content/TSS-IncludeTest-01.html"/> >> <map:transform src="d:/comwps/xslt/page2html-tss01.xsl"> >> </map:transform> >> <map:transform type="cinclude"/> >> <map:serialize/> >> </map:match> >>Has there been a change to include transformation in Cocoon 2.1.8? Has >>the ability to use cinclude after transformations been eliminated? If >>it did, this is very discouraging. What I'm doing is inside an XHTML >>template I call a single template that builds a cinclude element. I >>call this cinclude template several times, each time passing different >>parameters to produce several cincludes. The cincludes are then >>processed at the end of the map:match. I need to process the cincludes >>at the end of the map:match after the transformation. >> >>I've thought about using i:include, but I did some searching and >>cannot find any good examples for using <i:include>. How does one go >>about using i:include to include only a portion of a xml document? >>Form what I could tell, the 2.1.8 i:include samples only show the use >>of i:include serving an entire xml file, not a part of a file. I tried >>using cinclude select but that did not work? >> >> >> >>Gary T. Schultz >>IT Administrator >>Wisconsin Department of Commerce >>201 W. Washington Ave >>Madison, WI 53214 >>608-266-1283 >>[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >> >> > > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
