CForms Styling
Hi,
I had some troubles with the calendar positioning (as some of you may have
had too) and came up with the following behaviour:
(standard complience mode)
(div tag and calendar code are found in your woody-calendar-styling.xsl or
cforms equivalent file)
With normal cforms stuff:
1)Mozilla related (Mozilla 1.5, and firefox 0.8) : The calendar pops up
at the position of the div tag (div tag meaning the tag that the cforms
style sheets will place at the beginning of your body tag to initialize the
calendar) relative to your browser window. What (seems to) happens is that
if placed at the top of your inner body element, it will be placed at the
top of your browser window. If the div tag
is placed somewhere near the end, you'll notice the calendar is placed at
the bottom of the window, leaving only the top of the popup visible.
2)IE 6:The calendar shows up where the div tag is placed, and it
squishes itself in the html page, leaving a blank space when disappearing
(set to hidden). That's really ugly not?
I changed the div tag that initializes the calendar with the position
attribute set to absolute:
div style=position:fixed .
changed to:
div style=position:absolute
And got:
1)Mozilla related: The calendar pops up at the exact div element
position. (as with IE in previous test, but not showing in html page itself,
instead opens as popup)
2)IE 6: The calendar pops up at the position of your input element
(where you're a onclick=... is situated, but that's set by the woody
stylesheets)
In my case I could manage with the latter if I placed the div tag near my
date inputs. I have my date inputs grouped together on my page, thus with
mozilla, the calendar pops up at the same place for every input element, but
hey, they are all in the same area. Notice that if your div is positioned
with the first date input and it's out of sight, you're popup is also out of
sight(need to scroll to that input)! With IE all's fine, because the
calendar pops up at the input element itself.
Another catch: I need to set the div itself thus removing it from the woody
stylesheets. If you're having two div's the first is used, not the second!
The second case seems to be the best one and may be fixed (not sure, have
not tried it yet) completely if you change you're cforms calendar style
sheet with calendar code to do the following:
1) At the code insertion in the calendar styling: Seek through your form and
when encountering a date input, use it's ID to generate the javascript
variable cforms_calendar_ID_div, use this in you're script tags as
parameter, and use cforms_calendar_ID as javascript variable:
var cforms_calendar_ID =
CalendarPopup('cforms_calendar_ID_div');(this needs to be in your html
head section)
2) Then with your template that takes care of your style='date' element:
set a div element wich looks like:
div id=cforms_calendar_ID_div style=position:absolute;./
and use the correct js variable in your onclick:
onClick=cforms_calendar_ID.select(.
Here we do have the following drawbacks:
- We have codeblocks for each date input in the header
- We need to go through whole form to find the date intput's at step 1
(for inserting the code at html header)
But I think it should work as Mozilla related browsers will now popup where
their div is situated (and we did create one for each input, remember that a
copied div with same id does not work, only the first div will be handled in
that case, that's why we create a different id and variable for each date
input) and IE will just popup the calendar at it's input field, not really
making any difference with what we already got with the second testcase.
Well that's it, for now. I may test the fix if I can find some spare time.
It seems that a small difference in implementing that position attribute in
the browsers IE and Moz can really create a hell for us webbers:-)
Hope this can help some others, or at least draw some attention from others
who might have a fix for this prob,
Kind Regards,
Jan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! How to check is the session is valid in XSP
Hi Davide, I think you should check this at sitemap level, using action auth-logged-in : map:match pattern=login map:act type=auth-loggedIn map:parameter name=handler value=applicationhandler/ !-- User logged in : do some other stuff -- /map:act !-- User not logged in : do some stuff -- /map:match -- Olivier Davide wrote: Hi all! I would like to check into an xsp if the user is i'm logged or not; i'm using the authentication framework. I'd like something like this: xsp:page ... ... if user is logged admin links else lofgn form xsp:page I'm a beginner with cocoon and i can't resolve this problem. Any Idea?? Thanks a lot. Best Regards, Davide - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cocoon form validation and jpath
Hi,
I am having problem in using Form validation and JPath.
What i am trying to do is
1) validating a form with the Form validation provided by Cocoon.
2)in case of sucess in Form validation, it is calling javascript function
and which in turn is sending the same page in case of error
now i am using jpath to extract the error message which is giving error
because errorMsg can not be null during form validation
map:match pattern=changePwd
map:act type=formval
map:parameter name=descriptor value=descriptor.xml/
map:parameter name=validate-set
value=data_constraints/
!--+
| this is the success case
+--
map:call function=change_Password/
/map:act
!--+
| this branch contains the failed validation.
| Since the success pipeline ends with a serializer,
the following is only
| applied if validation has not been successful.
|
+--
map:call resource=dynamic-page
map:parameter name=target
value=changePassword/
map:parameter name=remove value={0}/
/map:call
map:call function=change_Password/
===
?xml version=1.0 encoding=iso-8859-1?
xsp:page language=java
xmlns:xsp=http://apache.org/xsp;
xmlns:jpath=http://apache.org/xsp/jpath/1.0;
document
resources
resource type=file href=prefs.jsFlowscript/resource
/resources
header
titleChange Password/title
/header
body
jpath:if test=errorMsg
strongjpath:value-of select=errorMsg//strong
/jpath:if
form
=
Regards
H. vardhan
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.614 / Virus Database: 393 - Release Date: 3/5/2004
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
XML Parsing Error: no element found
hi,
I am getting the above error message when I try and run the following xsp page. Can I do this? If not how do I??
?xml version=1.0 encoding=ISO-8859-1?>
xsp:page language=java
xmlns:xsp=http://apache.org/xsp
xmlns:util=http://apache.org/xsp/util/2.0
xmlns:xlink=http://www.w3.org/1999/xlink
xmlns=http://www.w3.org/2000/svg>
xsp:structure>
/xsp:include>
/xsp:structure>
xsp:element name=svg>
xsp:logic>
int svgWidth = Integer.parseInt(util:get-sitemap-parameter name=svgWidth/>);
int svgHeight = Integer.parseInt(util:get-sitemap-parameter name=svgHeight/>);
/xsp:logic>
xsp:attribute name=width>xsp:expr>svgWidth/xsp:expr>/xsp:attribute>
xsp:attribute name=height>xsp:expr>svgHeight/xsp:expr>/xsp:attribute>
xsp:logic>
... Code.
/xsp:logic>
!-- spit the image back to the browser requester -->
xsp:element name=svg>
xsp:attribute name=width>xsp:expr>svgWidth/xsp:expr>/xsp:attribute>
xsp:attribute name=height>xsp:expr>svgHeight/xsp:expr>/xsp:attribute>
xsp:attribute name=viewBox>0 0 /xsp:expr> /xsp:expr>/xsp:attribute>
xsp:element name=image>
xsp:attribute name=x>/xsp:attribute>
xsp:attribute name=y>/xsp:attribute>
xsp:attribute name=border>/xsp:attribute>
xsp:attribute name=width>xsp:expr>imgWidth/xsp:expr>/xsp:attribute>
xsp:attribute name=height>xsp:expr>imgHeight/xsp:expr>/xsp:attribute>
xsp:attribute name=xlink:href>data:image/jpeg;base64,/xsp:expr>/xsp:attribute>
/xsp:element>
/xsp:element>
/xsp:element>
My pipeline is:
map:match pattern=**artistImage/*/*/*/*.jpg>
map:generate type=serverpages src=xsp/svg.xsp>
map:parameter name=imageNum value={5}/>
map:parameter name=artistID value={2}/>
map:parameter name=svgWidth value={3}/>
map:parameter name=svgHeight value={4}/>
/map:generate>
map:serialize type=svg2jpeg/>
/map:match>
Re: XML Parsing Error: no element found
beyaNet Consultancy wrote:
hi,
I am getting the above error message when I try and run the following
xsp page. Can I do this? If not how do I??
?xml version=1.0 encoding=ISO-8859-1?
xsp:page language=java
xmlns:xsp=http://apache.org/xsp;
xmlns:util=http://apache.org/xsp/util/2.0;
xmlns:xlink=http://www.w3.org/1999/xlink;
xmlns=http://www.w3.org/2000/svg;
xsp:structure
xsp:includetest.ArtistImages/xsp:include
/xsp:structure
xsp:element name=svg
Why do you do that?
You could just use a svg/ tag instead.
map:match pattern=**artistImage/*/*/*/*.jpg
map:generate type=serverpages src=xsp/svg.xsp
Check the XML which comes out here.
E.g. serialize as plain xml first.
Does it look like you'd exspect it?
map:parameter name=imageNum value={5}/
map:parameter name=artistID value={2}/
map:parameter name=svgWidth value={3}/
map:parameter name=svgHeight value={4}/
/map:generate
map:serialize type=svg2jpeg/
/map:match
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: XML Parsing Error: no element found
Ok,
I have come across a solution which works! It is:
svg>
xsp:logic>
int svgWidth = Integer.parseInt(util:get-sitemap-parameter name=svgWidth/>);
int svgHeight = Integer.parseInt(util:get-sitemap-parameter name=svgHeight/>);
xsp:attribute name=width>xsp:expr>svgWidth/xsp:expr>/xsp:attribute>
xsp:attribute name=height>xsp:expr>svgHeight/xsp:expr>/xsp:attribute>
xsp:attribute name=viewBox>0 0 /xsp:expr> /xsp:expr>/xsp:attribute>
I was under the impression that you could only use xsp:attribute/> within an xsp:element/> tag. It seems not! very nice
Peter
On 22 Mar 2004, at 10:46, beyaNet Consultancy wrote:
hi,
I am getting the above error message when I try and run the following xsp page. Can I do this? If not how do I??
?xml version=1.0 encoding=ISO-8859-1?>
xsp:page language=java
xmlns:xsp=http://apache.org/xsp
xmlns:util=http://apache.org/xsp/util/2.0
xmlns:xlink=http://www.w3.org/1999/xlink
xmlns=http://www.w3.org/2000/svg>
xsp:structure>
/xsp:include>
/xsp:structure>
xsp:element name=svg>
xsp:logic>
int svgWidth = Integer.parseInt(util:get-sitemap-parameter name=svgWidth/>);
int svgHeight = Integer.parseInt(util:get-sitemap-parameter name=svgHeight/>);
/xsp:logic>
xsp:attribute name=width>xsp:expr>svgWidth/xsp:expr>/xsp:attribute>
xsp:attribute name=height>xsp:expr>svgHeight/xsp:expr>/xsp:attribute>
xsp:logic>
... Code.
/xsp:logic>
!-- spit the image back to the browser requester -->
xsp:element name=svg>
xsp:attribute name=width>xsp:expr>svgWidth/xsp:expr>/xsp:attribute>
xsp:attribute name=height>xsp:expr>svgHeight/xsp:expr>/xsp:attribute>
xsp:attribute name=viewBox>0 0 /xsp:expr> /xsp:expr>/xsp:attribute>
xsp:element name=image>
xsp:attribute name=x>/xsp:attribute>
xsp:attribute name=y>/xsp:attribute>
xsp:attribute name=border>/xsp:attribute>
xsp:attribute name=width>xsp:expr>imgWidth/xsp:expr>/xsp:attribute>
xsp:attribute name=height>xsp:expr>imgHeight/xsp:expr>/xsp:attribute>
xsp:attribute name=xlink:href>data:image/jpeg;base64,/xsp:expr>/xsp:attribute>
/xsp:element>
/xsp:element>
/xsp:element>
My pipeline is:
map:match pattern=**artistImage/*/*/*/*.jpg>
map:generate type=serverpages src=xsp/svg.xsp>
map:parameter name=imageNum value={5}/>
map:parameter name=artistID value={2}/>
map:parameter name=svgWidth value={3}/>
map:parameter name=svgHeight value={4}/>
/map:generate>
map:serialize type=svg2jpeg/>
/map:match>
Access coplet attributes from flow
Hi, Is there a way to get the current CopletData object from flowscript? One of my coplets uses Flow, and I would like to look up a custom attribute before doing a sendPageAndWait, so I can influence which page to send. A code snippet would be most appreciated! Thanks, Jon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using sitemap parameters in a cinclude transformation
The cinclude transformer itself does not have the capability to pass and
fill in parameters. You should combine the cinclude with another technique
such as:
1) JXTemplateGenerator:(preferred way) this uses Jexl and JXPath to
access variables, you got some standard objects you can use here such as
request/parameters and session, look for the docs in your cocoon under flow
map:generate type=jx
map:parameter name=url value=/
/map:generate
-sourcefile: something like cinclude:include
src=#{$cocoon/parameters/url}/
2) XSP: (old way) in XSP you can create your cinclude tags and use logic
to get your sitemapparameter (parameters.getParameter(..))
map:generate type=serverpages...
map:parameter name= value=/
/map:generator
-sourcefile
xsp:logic
String url = paramters.getParameter(...);
/xsp:logic
create your element and add an attribute
cinclude:include
xsp:attribute name=srcxsp:exprurl/xsp:expr/xsp:attribute
/cinclude:include
thus replace your normal xml generator with one of the previous generators
and adjust your source file.
Kind Regards,
Jan
- Original Message -
From: Björn Voigt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 22, 2004 8:38 AM
Subject: Using sitemap parameters in a cinclude transformation
Moin Cocooners,
I want aggregate some internal pipelines. The generated file
should have a more complex structure instead of only one root element,
which the simple sitemap aggregation is providing.
I want use the cinclude mechanism, but it seems to be not able to
handle parameters from the sitemap. Is this not possible with cinclude?
I will replace this:
map:match pattern=*.html
map:aggregate element=site
map:part src=cocoon:/menu-{0}/
map:part src=cocoon:/body-{0}/
/map:aggregate
map:transform type=encodeURL/
[...]
/map:match
with something like this:
map:match pattern=pattern=*.html
map:generate src=aggregation.xml/
map:transform type=cinclude
map:parameter name=value value={1}/
/map:transform
[...]
/map:match
site xmlns:cinclude=http://apache.org/cocoon/include/1.0;
cinclude:include src=cocoon:/menu-{value}/
cinclude:include src=cocoon:/menu-{value}/
/site
Thank you for helpfull ideas,
Björn Voigt
-
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]
2.0.x as default context on tomcat 5.0.19
Has anyone configured cocoon as the root context on tomcat 5.0.19? On 4.1.x it's sufficient to do Context path= docBase=cocoon debug=0 /Context On 5.0.19 i get the cocoon Resource Not Found page with above config. Sitemap that (should) execute: map:match pattern= map:generate type=file src=index.html/ map:serialize type=html/ /map:match if i change it to map:match pattern=index.html then it's working fine. Something i'm missing here? Regards Jorg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XML:DB questions
Hi there list! OK a few questions: 1. What in the XML:DB XUpdate spec has been implemented? 2. To access the embeded xindice within Cocoon through the Xindice CMD tool do I have to set Xindice home as : $COCOON_HOME/WEB-INF/lib/ ?? Many thanks Jason Lane Developer Root10 developments - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Calendar - Time Recommendation
I have come in late on this discussion, where Reinhard_Pötz [EMAIL PROTECTED] event start=2004-04-20T19:00Mom's Birthday suggested a time event for calendaring. I would recommend looking at the HR-XML (www.hr-xml.org) specification for date-times, which are useful for specifying the time of events more precisely. http://ns.hr-xml.org/2_2/HR-XML-2_2/CPO/DateTimeDataTypes.pdf The problem exists when several users are using the same calendaring system. Perhaps your time format implies UTC - in that case, HR-XML would only add a Z to the end. event start=2004-04-20T19:00ZMom's Birthday However, using their syntax, you could just as easily include not only the absolute time, but an indication of the time zone difference when the person creating event created it. event start=2004-04-20T19:00-05:00Mom's Birthday Think of that as it may be useful for clearing up discrepancies later on, which can be traced back to time zone differences. I placed an order at 14:20, clearly within your business hours. Why didn't I get that shipped Monday? Answer: Your order entry indicates that you are in the XXX time zone. The distribution center is 6 time zones ahead, and their work hours are 8-6, in the YYY time zone. Jeff Conrad __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Calendar - Time Recommendation
Jeff Conrad wrote: I have come in late on this discussion, where Reinhard_Pötz [EMAIL PROTECTED] event start=2004-04-20T19:00Mom's Birthday suggested a time event for calendaring. I would recommend looking at the HR-XML (www.hr-xml.org) specification for date-times, which are useful for specifying the time of events more precisely. Why is my name part of this mail -- Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XML:DB questions
Jason Lane wrote: Hi there list! OK a few questions: 1. What in the XML:DB XUpdate spec has been implemented? 2. To access the embeded xindice within Cocoon through the Xindice CMD tool do I have to set Xindice home as : $COCOON_HOME/WEB-INF/lib/ ?? I'd point it at $COCOON_HOME. As the Xindice libs are all in WEB-INF/lib, which I imagine is where XIndice would expect them. Also, you'll need to see whether the XIndice servlet is started or not, otherwise you'll have to use -l to use embedded mode on the CMD tool. If you are using embedded, don't write to the DB via the CMD tool when a servlet is running. You'll loose your changes. One XIndice DB per VM. Regards, Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: avoid setting the password in jdbc settings in cocoon.xconf
I think the answer to both questions is, don't use database pooling :) If you are using ESQL, all of these can be set dynamically by using java and xsp:expr inside the appropriate elements. I imagine it is even easier in SQL transformer. You'll have to pass in everything every time, though, so you'll probably want some way to cache your user's password in the session or some such, unless you have incredibly patient users... -Christopher |-+ | | Alex Kovacs| | | [EMAIL PROTECTED]| | | su.com.au | | || | | 03/21/2004 07:06 | | | PM | | | Please respond to| | | users| | || |-+ --| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: avoid setting the password in jdbc settings in cocoon.xconf | --| Hi, How is it possible to avoid setting the user/password for the jdbc connection in cocoon.xconf? This could be a security issue if the server sits in a DMZ. In addition, how is it possible to set a different dburl programmatically if, say I want to change the database host, port or sid? Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Coplets and Excel Generation
can someone please answer my question below ---BeginMessage--- OK. I posted the same question earlier but re-framed it so that someone can me suggestions. I have coplet which accepts some input keys and shoud generate a excel file. When I click on submit it takes to the ill formatted html file but does not generate a excel file. I use the same pipeline(generator,transfomer and serializer) outside a coplet like in a hyperlink. It works just fine. Can someone tell me where I am making a mistake. Is there anything we have to specify for a coplet to generate a xml file. my pipeline looks like this map:generate src=context://historyserver/coplets/search/sec.xml/ map:transform src=context://historyserver/styles/page2xls.xsl/ map:serialize type=xls/ Any help is greatly appreciated. Thanks, Anna. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---End Message--- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XMLDB more questions ;)
Hi again list, Thanks Upayavira for your reply that helped ;) OK so from what I can see this block implements both the XML:DB XUpdate and a Cocoon implementation of W3C XQuery, is this right? So my thoughts now are; if I wanted to create a form interface to populate Xindice embedded do we I still need to follow the old way of doing things as in Xindice within the XMLForm Framework as contained within the Cocoon docs and the Wiki? Doesn't this mean also that the whole process of populating Xindice through a form has become a whole lot easier? Lastly how would I go about using a simple form interface to do this now? In the meantime I shall be scanning the archives. Again many thanks in advance. Jason Lane Developer Root10 developments - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
logkit.xconf conf
Hi, How can I configure the logs to be written in $TOMCAT_HOME/logs?! Thx, CDias
[cron] OutOfMemoryError
Hi, I trying to run a pipeline using cron block by entering a cron expression into the sample and keep getting OutOfMemoryError. My expressions is: 0 * 9-23 * * ?, i.e. I run it every minute. It runs out of memory quicker when I use a fairly complex pipeline, but I was able to get the same error by using simply: map:pipeline type=noncaching map:match pattern=test map:generate src=empty.xml/ !-- just a single element -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:serialize type=xml/ map:match /map:pipeline Any ideas? Thanks, -Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [cron] OutOfMemoryError
Alex Romayev wrote: Hi, I trying to run a pipeline using cron block by entering a cron expression into the sample and keep getting OutOfMemoryError. My expressions is: 0 * 9-23 * * ?, i.e. I run it every minute. It runs out of memory quicker when I use a fairly complex pipeline, but I was able to get the same error by using simply: map:pipeline type=noncaching map:match pattern=test map:generate src=empty.xml/ !-- just a single element -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:serialize type=xml/ map:match /map:pipeline Any ideas? Thanks, -Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Do you use CVS head or a released version of Cocoon? Recently, Sylvain has refactored source resolving in the Cron block. -- Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [cron] OutOfMemoryError
I took the lasted version this morning. --- Reinhard_Pötz [EMAIL PROTECTED] wrote: Alex Romayev wrote: Hi, I trying to run a pipeline using cron block by entering a cron expression into the sample and keep getting OutOfMemoryError. My expressions is: 0 * 9-23 * * ?, i.e. I run it every minute. It runs out of memory quicker when I use a fairly complex pipeline, but I was able to get the same error by using simply: map:pipeline type=noncaching map:match pattern=test map:generate src=empty.xml/ !-- just a single element -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:transform src=copy.xml/ !-- copy all -- map:serialize type=xml/ map:match /map:pipeline Any ideas? Thanks, -Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Do you use CVS head or a released version of Cocoon? Recently, Sylvain has refactored source resolving in the Cron block. -- Reinhard - 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: logkit.xconf conf
On Mar 22, 2004, at 9:18 AM, Carlos Dias wrote: Hi, How can I configure the logs to be written in $TOMCAT_HOME/logs?! Specify a relative path using the context:/ pseudo-protocol, which resolves the path relative to the servlet context. ~ mark
Question in coplets
Hi, I have 4 coplets all displayed in one page. Each of them is a form. When I submit on one of these forms I want the output of this request to displayed in a 5th coplets and have the 4 coplets displayed underneath that as before. Is this possible? Right now when I click on submit I display the output in the same coplet. Can someone please tell me how I can display the output in a different coplet. Another point here is when any one of the 4 forms are submitted I want the output to be displayed in the same 5th coplet. The 5th coplet should not appear when no forms are submitted. Thanks, Anna. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: logkit.xconf conf
but you can't (shouldn't be able to) reach $TOMCAT_HOME/logs via context relative addressing (e.g. context:/../logs), since the context protocol should disallow access outside the context for security reasons. I guess you have to specifiy the absolute path. -Ursprngliche Nachricht-Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]Im Auftrag von Mark LundquistGesendet: Montag, 22. Mrz 2004 19:13An: [EMAIL PROTECTED]Betreff: Re: logkit.xconf confOn Mar 22, 2004, at 9:18 AM, Carlos Dias wrote: Hi,How can I configure the logs to be written in $TOMCAT_HOME/logs?!Specify a relative path using the "context:/" pseudo-protocol, which resolves the path relative to the servlet context.~ mark
Re: logkit.xconf conf
With "context:/" do you mean "${context-root}",
right?!
But this variable defines the servlets webapp
context?!
CD
- Original Message -
From:
Mark Lundquist
To: [EMAIL PROTECTED]
Sent: Monday, March 22, 2004 6:13
PM
Subject: Re: logkit.xconf conf
On Mar 22, 2004, at 9:18 AM, Carlos Dias wrote:
Hi,How
can I configure the logs to be written in $TOMCAT_HOME/logs?!Specify a
relative path using the "context:/" pseudo-protocol, which resolves the path
relative to the servlet context.~ mark
Caching and aggregate
Hi, I am using the 2.1.5-dev version and am experiencing really weird things when I use aggregation with caching pipelines. Has the caching mechanism changed between 2.1.5 and 2.1.4? Thanks __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Empty elements and the XML Serializer
Hey folks -- I've been using the XMLSerializer to serialize xhtml (set up in a similar way as the stock distribution's root sitemap), but I'm running into some problems with the way empty elements are treated, specifically the script and textarea tags. The XMLSerializer will render the empty element as: textarea / But according to the Dev Guru XHTML reference's page on the textarea element [1], a separate closing tag is mandatory: textarea/textarea Browsers seem to agree with this -- textarea tags and script tags rendered without a separate closing tag are just ignored. What can be done about this sort of inserting spaces between the tags to force the closing tag to be rendered? cheers, -steve [1] http://www.devguru.com/Technologies/xhtml/quickref/xhtml_textarea.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error in free() and crash : help need
hello, i have thousand lines of Error in free() error in my localhost_log (15 Go in one day), and then tomcat freeze any idea ? I'm too desesperate with this error. 2004-03-22 08:25:55 ERROR 10799 [root.sto] (): Error in free() java.util.NoSuchElementException at java.util.LinkedList.remove(LinkedList.java:557) at java.util.LinkedList.removeLast(LinkedList.java:127) at org.apache.cocoon.components.store.MRUMemoryStore.free(MRUMemoryStore.java:3 80) at org.apache.cocoon.components.store.MRUMemoryStore.hold(MRUMemoryStore.java:2 83) at org.apache.cocoon.components.store.MRUMemoryStore.get(MRUMemoryStore.java:32 8) at org.apache.cocoon.components.pipeline.CachingStreamPipeline.processReader(Ca chingStreamPipeline.java:160) at org.apache.cocoon.components.pipeline.AbstractStreamPipeline.process(Abstrac tStreamPipeline.java:116) at org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingS treamPipeline.java:255) at org.apache.cocoon.www.bethe2.sitemap_xmap.wildcardMatchN953(sitemap_xmap.jav a:9742) at org.apache.cocoon.www.bethe2.sitemap_xmap.process(sitemap_xmap.java:1928) at org.apache.cocoon.www.bethe2.sitemap_xmap.process(sitemap_xmap.java:1273) at org.apache.cocoon.sitemap.Handler.process(Handler.java:163) at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115) at org.apache.cocoon.www.sitemap_xmap.wildcardMatchN1FF(sitemap_xmap.java:2883) at org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2199) at org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:2134) at org.apache.cocoon.sitemap.Handler.process(Handler.java:163) at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:115) at org.apache.cocoon.Cocoon.process(Cocoon.java:446) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:520) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) 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.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) 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:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) 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:5 66) 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: 1017) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1115 ) at java.lang.Thread.run(Thread.java:479) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
Well, a hack would be to include a nbsp; in there... in the xml, you'll have to put the numeric value in though, as #160; (off the top of me little head). :) Though it would be handy if it were possible to create an instance of the xml serializer with a parameter like: collapse-emtpy-elements>false/collapse-emtpy-elements> jL On Mar 22, 2004, at 2:42 PM, Steve Krulewitz wrote: Hey folks -- I've been using the XMLSerializer to serialize xhtml (set up in a similar way as the stock distribution's root sitemap), but I'm running into some problems with the way empty elements are treated, specifically the script and textarea tags. The XMLSerializer will render the empty element as: textarea /> But according to the Dev Guru XHTML reference's page on the textarea element [1], a separate closing tag is mandatory: textarea>/textarea> Browsers seem to agree with this -- textarea tags and script tags rendered without a separate closing tag are just ignored. What can be done about this sort of inserting spaces between the tags to force the closing tag to be rendered? cheers, -steve [1] http://www.devguru.com/Technologies/xhtml/quickref/xhtml_textarea.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] John Lianoglou | Vice President | ARACHNEdesign http://www.arachnedesign.net PGP.sig Description: This is a digitally signed message part
Re: Empty elements and the XML Serializer
On Mon, 22 Mar 2004, Steve Krulewitz wrote: I've been using the XMLSerializer to serialize xhtml (set up in a similar way as the stock distribution's root sitemap), but I'm running into some problems with the way empty elements are treated, specifically the script and textarea tags. The XMLSerializer will render the empty element as: textarea / But according to the Dev Guru XHTML reference's page on the textarea element [1], a separate closing tag is mandatory: textarea/textarea Browsers seem to agree with this -- textarea tags and script tags rendered without a separate closing tag are just ignored. What can be done about this sort of inserting spaces between the tags to force the closing tag to be rendered? A quick check with the OpenSP validator shows that the textarea/ is fine with XHTML-1.1. I would expect the same for earlier versions of HTML. Mozilla does indeed render this incorrectly. However, konqueror renders it fine. As a work around, how about placing a non-visible character such as nbsp;? -- JP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
A quick check with the OpenSP validator shows that the textarea/ is fine with XHTML-1.1. I would expect the same for earlier versions of HTML. Mozilla does indeed render this incorrectly. However, konqueror renders it fine. Yes, lets ignore Mozilla ;-) Especially while this the browser I use for developing my webapps and ask other to use it. As a work around, how about placing a non-visible character such as nbsp;? I'm suffering the same problem, and of course I did the tick with nbsp; And the same situation is with script - it must have an ending tag. So, while loading scripts with src attribute, you must do those tricks. Speaking of Java Script - how to get rid of escaping and from XML - I need them in script, but they are converted to lt; and gt; which is not understood by browsers. Regards, Marcin Okraszewski - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
On Mon, Mar 22, 2004 at 02:42:17PM -0500, Steve Krulewitz wrote: Hey folks -- I've been using the XMLSerializer to serialize xhtml (set up in a similar way as the stock distribution's root sitemap), but I'm running into some problems with the way empty elements are treated, specifically the script and textarea tags. The XMLSerializer will render the empty element as: textarea / But according to the Dev Guru XHTML reference's page on the textarea element [1], a separate closing tag is mandatory: textarea/textarea snip/ I sent an email to the dev list about this, and here is the link: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=107999114518402w=2 --Tim Larson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
You need to put the correct DOCTYPE into the document in order to get Mozilla out of quirks mode. Check the Moz FAQ for all the details. I've tried the following document: !DOCTYPE HTML SYSTEM http://www.w3.org/TR/REC-html40/strict.dtd; html head titletitle/title /head body form action= textarea name=blah rows=10 cols=10/ /form /body /html Even though the page info reports Render Mode: Standards compliance mode, this does not get rendered properly on Firefox 0.8 -- the last 3 tags appear in the textarea's text box. Am I doing something wrong? Also, I tried to re-create the same problem with the script tag, but I'm unable to do it in a simple document. cheers, -steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
On 22.03.2004 23:25, Steve Krulewitz wrote: You need to put the correct DOCTYPE into the document in order to get Mozilla out of quirks mode. Check the Moz FAQ for all the details. I've tried the following document: !DOCTYPE HTML SYSTEM http://www.w3.org/TR/REC-html40/strict.dtd; html head titletitle/title /head body form action= textarea name=blah rows=10 cols=10/ /form /body /html Even though the page info reports Render Mode: Standards compliance mode, this does not get rendered properly on Firefox 0.8 -- the last 3 tags appear in the textarea's text box. Am I doing something wrong? The above is HTML, not XHTML (HTML DTD + no XHTML namespace). Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cocoon Tuning for Production
Hi, Is there a place in the documentation that discusses what should be done to ready a cocoon system for production? Other than turning off logging and sitemap and class reloading, what could I do to ready the system and improve performance as much as possible? __ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
Speaking of Java Script - how to get rid of escaping and > from XML - I need them in script, but they are converted to lt; and gt; which is not understood by browsers. I believe you might want to try CDATA blocks... haven't actually tried it, but then I haven't come across the need just yet... :) jL John Lianoglou | Vice President | ARACHNEdesign http://www.arachnedesign.net PGP.sig Description: This is a digitally signed message part
Re: Empty elements and the XML Serializer
Steve Krulewitz dijo: Hey folks -- I've been using the XMLSerializer to serialize xhtml (set up in a similar way as the stock distribution's root sitemap), but I'm running into some problems with the way empty elements are treated, specifically the script and textarea tags. The XMLSerializer will render the empty element as: textarea / AFAIK, this is OK by specs XHTML 1.0: http://www.w3.org/TR/xhtml1/#C_2 Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon Tuning for Production
Samuel Bruce dijo: Hi, Is there a place in the documentation that discusses what should be done to ready a cocoon system for production? Other than turning off logging and sitemap and class reloading, what could I do to ready the system and improve performance as much as possible? http://wiki.cocoondev.org/Wiki.jsp?page=CocoonPerformance Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: avoid setting the password in jdbc settings in cocoon.xconf
Hi Christopher, I think the answer to both questions is, don't use database pooling :) I understand your point If you are using ESQL, all of these can be set dynamically by using java and xsp:expr inside the appropriate elements. I imagine it is even easier in SQL transformer. You'll have to pass in everything every time, though, so you'll probably want some way to cache your user's password in the session or some such, unless you have incredibly patient users... I will try it, however it would be good to have an example of how you define the connection for ESQL in an xsp:expr tag. Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Calendar Generator
If I'm not mistaken, the xcal effort has stalled because they seem to be moving in the direction of rdf. There is an rdf calendar task force announcement at: http://www.ilrt.bris.ac.uk/discovery/2001/04/calendar/ You might want to consider monitoring this instead of using xcal. On Mar 21, 2004, at 9:25 PM, John Lianoglou wrote: That is my instinct as well. Unfortunately, everything seems to use iCal (mozilla, outlook, apple iCal) and from what I can find xcal seems to be stuck between draft 2 (from 2002?) and draft 3 which may change things up significantly if it is ever finished. Well, I feel like the xcal draft 2 features will be more than sufficient for use in cocoon. Thought if there were a draft 3 actually in active development, I'd naturally agree it's definitely worth planning for. :) Stan Dyck Note: I've sworn off sending email attachments. If you get an email from my address with an attachment, don't open it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Calendar Generator
If I'm not mistaken, the xcal effort has stalled because they seem to be moving in the direction of rdf. There is an rdf calendar task force announcement at: http://www.ilrt.bris.ac.uk/discovery/2001/04/calendar/ You might want to consider monitoring this instead of using xcal. On Mar 21, 2004, at 9:25 PM, John Lianoglou wrote: That is my instinct as well. Unfortunately, everything seems to use iCal (mozilla, outlook, apple iCal) and from what I can find xcal seems to be stuck between draft 2 (from 2002?) and draft 3 which may change things up significantly if it is ever finished. Well, I feel like the xcal draft 2 features will be more than sufficient for use in cocoon. Thought if there were a draft 3 actually in active development, I'd naturally agree it's definitely worth planning for. :) Stan Dyck Note: I've sworn off sending email attachments. If you get an email from my address with an attachment, don't open it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon Tuning for Production
Antonio Gallardo wrote: Samuel Bruce dijo: Hi, Is there a place in the documentation that discusses what should be done to ready a cocoon system for production? Other than turning off logging and sitemap and class reloading, what could I do to ready the system and improve performance as much as possible? http://wiki.cocoondev.org/Wiki.jsp?page=CocoonPerformance And do not forget the core documentation at: http://cocoon.apache.org/2.1/performancetips.html --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
On Mon, 22 Mar 2004, J.Pietschmann wrote: Jean Pierre LeJacq wrote: A quick check with the OpenSP validator shows that the textarea/ is fine with XHTML-1.1. I would expect the same for earlier versions of HTML. It is valid XML but *not* valid HTML, and pre-XHTML browsers will choke on it. A common workaround is to include a dummy foo=foo attribute which usually causes the slash to be silently ignored. Works for br and similar tags too. Mozilla does indeed render this incorrectly. You need to put the correct DOCTYPE into the document in order to get Mozilla out of quirks mode. Check the Moz FAQ for all the details. No, not quite right. I validated with the doctyple declaration of XHTML-1.1 and confirmed that Mozilla was rendering in standards compliance made. -- JP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
Jean Pierre LeJacq dijo: No, not quite right. I validated with the doctyple declaration of XHTML-1.1 and confirmed that Mozilla was rendering in standards compliance made. Hi: What version of Mozilla are you using? AFAIK, XHTML-1.1 is quite new (31 May 2001) and maybe older version does not support it at all. I already tried to find the info of supported standards on mozilla website and not have a clue where to find this info and after a while I give up. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Serving XHTML with Cocoon (was: Empty elements and the XML Serializer)
Thanks to everyone who responded to the Empty elements and the XML Serializer thread. Rather than change the way documents are serialized, the proper solution is to deliver the content to the browser in such a way that the browser knows it is getting XHTML. First of all, you need to specify an XHTML doctype and use the XHTML namespace for the xhtml elements in your document. You also need to send the application/xhtml+xml content type with your response. But here is the problem -- Internet Explorer does not like this, and will attempt to download the page if it receives this content type. It seems to work for most other browsers, but for Internet Explorer you still need to send the content as text/html. To handle this in Cocoon, I've declared two separate serializers: map:serializer name=xhtml mime-type=application/xhtml+xml; charset=utf-8 src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//W3C//DTD XHTML 1.0 Strict//EN/doctype-public doctype-systemhttp://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd/doctype-system encodingUTF-8/encoding indentyes/indent /map:serializer map:serializer name=xhtml-ie mime-type=text/html; charset=utf-8 src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//W3C//DTD XHTML 1.0 Strict//EN/doctype-public doctype-systemhttp://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd/doctype-system encodingUTF-8/encoding indentyes/indent /map:serializer And also a resource that is used in place of map:serialize/: map:resources map:resource name=serialize map:select type=browser map:when test=explorer map:serialize type=xhtml-ie/ /map:when map:otherwise map:serialize type=xhtml/ /map:otherwise /map:select /map:resource /map:resources So instead of calling map:serialize/, i call map:call resource=serialize/. The bad part about using a resource is that, as far as I know, a resource declared in the root sitemap can not be called by subsitemaps. Is this on par with other people's experience dealing with this problem? cheers, -steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Empty elements and the XML Serializer
On Mon, 22 Mar 2004, Antonio Gallardo wrote: Jean Pierre LeJacq dijo: No, not quite right. I validated with the doctyple declaration of XHTML-1.1 and confirmed that Mozilla was rendering in standards compliance made. What version of Mozilla are you using? AFAIK, XHTML-1.1 is quite new (31 May 2001) and maybe older version does not support it at all. I already tried to find the info of supported standards on mozilla website and not have a clue where to find this info and after a while I give up. I'm using both 1.5 and 1.6 as well as firefox 0.7 and 0.8. XHTML-1.1 is effectively a subset of and cleaned up version of HTML-4.01. My understanding is that Mozilla has default handling for HTML-4.01 and will render any valid XHTML as such. I always construct and validate XHTML-1.1 and haven't had any issues other than those already acknowledge as problems for HTML. -- JP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Serving XHTML with Cocoon (was: Empty elements and the XML Serializer)
On Mon, 22 Mar 2004, Steve Krulewitz wrote: First of all, you need to specify an XHTML doctype and use the XHTML namespace for the xhtml elements in your document. You also need to send the application/xhtml+xml content type with your response. But here is the problem -- Internet Explorer does not like this, and will ... map:serializer name=xhtml-ie mime-type=text/html; charset=utf-8 src=org.apache.cocoon.serialization.XMLSerializer doctype-public-//W3C//DTD XHTML 1.0 Strict//EN/doctype-public doctype-systemhttp://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd/doctype-system encodingUTF-8/encoding indentyes/indent /map:serializer ... Is this on par with other people's experience dealing with this problem? I see two problem. * This will not solve the problem in Mozilla. Even with properly declared doctype and a valid document, Mozilla will render textarea/ incorrectly. Its a bug in Mozilla. I didn't check to see if its in Mozilla's bug database. * I've run into a problem with the cocoon serializer not respecting content type UTF-8. I've only been able to get ISO Latin to work. See: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26997 -- JP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Alternate XML weblog - comments?
I wonder if anyone else saw this: http://www.xml.com/pub/a/2004/03/17/syncato.html and wondered if all of this is not already possible with Cocoon... comments? Thanks Derek. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
