XSP/Java - simple? problem
Hi
Can someone explain what is wrong with
the following code:
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
/xsp:logic
xsp:attribute name=rotate14/xsp:attribute
xsp:logic
} else {
/xsp:logic
xsp:attribute name=rotate1/xsp:attribute
xsp:logic
}
/xsp:logic
Gives an output of:
labels show=true label=null rotate=14 rotate=1
ie. if the fGraphPtLabel is null, the rotate should be equal to 1
and not 14 as well?!
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]
Re: XSP/Java - simple? problem
Hi Derek,
Derek Hohls wrote:
Hi
Can someone explain what is wrong with
the following code:
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
/xsp:logic
xsp:attribute name=rotate14/xsp:attribute
xsp:logic
} else {
/xsp:logic
xsp:attribute name=rotate1/xsp:attribute
xsp:logic
}
/xsp:logic
Gives an output of:
labels show=true label=null rotate=14 rotate=1
ie. if the fGraphPtLabel is null, the rotate should be equal to 1
and not 14 as well?!
it seems that your java code is not interpreted as such, and
the if condition is not added to the Java code ...
At a first glance it looks OK - did you take a look at the
generated Java source?
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP/Java - simple? problem
Andreas
Yes, the Java code generated does not seem to reflect
my *intent* in the XSP (see below) ie. the attributes
have been moved outside of the if test for some reason
- any ideas how to create a more appropriate code set??
!-- generated code snippet --
xspAttr.addAttribute(
,
label,
label,
CDATA,
String.valueOf(fGraphPtLabel)
);
xspAttr.addAttribute(
,
rotate,
rotate,
CDATA,
14
);
xspAttr.addAttribute(
,
rotate,
rotate,
CDATA,
1
);
this.contentHandler.startElement(
,
labels,
labels,
xspAttr
);
xspAttr.clear();
this.characters(\n \n );
this.characters(\n \n );
if ((fGraphPtLabel != null) (fGraphPtLabel.equals(name))) {
this.characters(\n);
this.characters(\n );
} else {
this.characters(\n);
this.characters(\n );
}
!-- generated code --
[EMAIL PROTECTED] 11/06/2003 10:00:53
Hi Derek,
Derek Hohls wrote:
Hi
Can someone explain what is wrong with
the following code:
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
/xsp:logic
xsp:attribute name=rotate14/xsp:attribute
xsp:logic
} else {
/xsp:logic
xsp:attribute name=rotate1/xsp:attribute
xsp:logic
}
/xsp:logic
Gives an output of:
labels show=true label=null rotate=14 rotate=1
ie. if the fGraphPtLabel is null, the rotate should be equal to 1
and not 14 as well?!
it seems that your java code is not interpreted as such, and
the if condition is not added to the Java code ...
At a first glance it looks OK - did you take a look at the
generated Java source?
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
Re: XSP/Java - simple? problem
On 11.Jun.2003 -- 08:43 AM, Derek Hohls wrote:
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
xsp:attribute name=rotate14/xsp:attribute
} else {
xsp:attribute name=rotate1/xsp:attribute
}
/xsp:logic
Can't see a problem here but you might like to know that you could
save yourself some of the xsp:logic tags (see above)
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP/Java - simple? problem
On 11.Jun.2003 -- 10:27 AM, Christian Haul wrote:
On 11.Jun.2003 -- 08:43 AM, Derek Hohls wrote:
labels show=true
xsp:attribute
name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
xsp:attribute name=rotate14/xsp:attribute
} else {
xsp:attribute name=rotate1/xsp:attribute
}
/xsp:logic
BTW (after looking at your followup including the generated code) you
could change the order to
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
rotate = 14;
} else {
rotate = 1;
}
/xsp:logic
xsp:attribute name=rotatexsp:exprrotate/xsp:expr/xsp:attribute
I'm afraid that putting the logic into the xsp:attribute tag is not
possible unless it is a java expression like
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:attribute name=rotatexsp:expr(
(fGraphPtLabel != null) amp;amp;
(fGraphPtLabel.equals(name)) ? 14 : 1)
/xsp:expr/xsp:attribute
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP/Java - simple? problem
This is due to a bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15841.
In the code
(cocoon-2.1\src\java\org\apache\cocoon\components\language\markup\xsp\java\xsp.xsl):
xsl:template match=*[not(namespace-uri(.) = 'http://apache.org/xsp')]
!-- matching on your label element --
xsl:apply-templates select=@*/
!-- catching all xsp:attributes
they are added to xspAttr --
xsl:apply-templates select=xsp:attribute |
xsp:logic[xsp:attribute]/
!-- create the element --
this.contentHandler.startElement(...);
xspAttr.clear();
!-- catching the rest of the elements --
xsl:apply-templates select=node()[not(
(namespace-uri(.) = $xsp-uri and local-name(.) = 'attribute') or
(namespace-uri(.) = $xsp-uri and local-name(.) = 'logic' and
./xsp:attribute)
)]/
!-- end element --
this.contentHandler.endElement(...);
/xsl:template
So first templates are applied for all your xsp:attribute/s. And
second the rest including xsp:logic/. This is of course completely
buggy, but I don't know how to fix it without breaking existing stuff.
The problem is, that you are creating the attributes in XSL and XSP
*after* the element, in SAX you must already have collected them when
the element is created.
Joerg
Christian Haul wrote:
On 11.Jun.2003 -- 08:43 AM, Derek Hohls wrote:
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
xsp:attribute name=rotate14/xsp:attribute
} else {
xsp:attribute name=rotate1/xsp:attribute
}
/xsp:logic
Can't see a problem here but you might like to know that you could
save yourself some of the xsp:logic tags (see above)
Chris.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[FIXED] Re: XSP/Java - simple? problem
Brilliant, thanks Chris.
To summarise, this:
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
/xsp:logic
xsp:attribute name=rotate14/xsp:attribute
xsp:logic
} else {
/xsp:logic
xsp:attribute name=rotate1/xsp:attribute
xsp:logic
}
/xsp:logic
should be:
xsp:attribute name=rotatexsp:expr
((fGraphPtLabel != null) amp;amp;
(fGraphPtLabel.equals(name)) ? 14 : 1)
/xsp:expr/xsp:attribute
[EMAIL PROTECTED] 11/06/2003 10:34:55
On 11.Jun.2003 -- 10:27 AM, Christian Haul wrote:
On 11.Jun.2003 -- 08:43 AM, Derek Hohls wrote:
labels show=true
xsp:attribute
name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
xsp:attribute name=rotate14/xsp:attribute
} else {
xsp:attribute name=rotate1/xsp:attribute
}
/xsp:logic
BTW (after looking at your followup including the generated code) you
could change the order to
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:logic
if ((fGraphPtLabel != null) amp;amp; (fGraphPtLabel.equals(name))) {
rotate = 14;
} else {
rotate = 1;
}
/xsp:logic
xsp:attribute name=rotatexsp:exprrotate/xsp:expr/xsp:attribute
I'm afraid that putting the logic into the xsp:attribute tag is not
possible unless it is a java expression like
labels show=true
xsp:attribute name=labelxsp:exprfGraphPtLabel/xsp:expr/xsp:attribute
xsp:attribute name=rotatexsp:expr(
(fGraphPtLabel != null) amp;amp;
(fGraphPtLabel.equals(name)) ? 14 : 1)
/xsp:expr/xsp:attribute
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
Im sure its a simple problem!
To anyone who can help, I now have installed the following: JDK 1.3 Cocoon 2.0.4 Tomcat 4.0.6 Apache 2.0.42 And they are all working! J When I say they are all working, I mean that they each show the own page, e.g http://192.168.0.5:8080/cocoon/ or http://192.168.0.5:8080/index.html for tomcat. What's not working: I had previously had installed Cocoon 1.3 and tomcat 3.3a, and I put a simple soundpool example in the webapps directory. This displayed only the source code of the xml file, hence the upgrade. I have got all the new versions installed and I have put the same example in the webapps directory in tomcat again, and tried viewing it through Internet Explorer 6. It is coming up with the following error: Apache Tomcat/4.0.6 - HTTP Status 404 - /soundpool/soundpool.xml type Status report message /soundpool/soundpool.xml description The requested resource (/soundpool/soundpool.xml) is not available. I have put the following code in my sitemap under pipelines: !-- soundpool -- map:pipeline map:match pattern=soundpool/soundpool map:generate src=soundpool.xml/ map:transform src=soundpool.xsl/ map:serialize/ /map:match /map:pipeline So I have put my xml and xsl file in directory called soundpool under webapps, so my directory structure looks like this: C:\tomcat\webapps\soundpool\soundpool.xml C:\tomcat\webapps\soundpool\soundpool.xsl + tomcat (folder) + webapps (folder) +- soundpool (folder) +- soundpool.xml (file) +- soundpool.xsl (file) I assume that webapps is the correct folder. I also used mod_jk to link tomcat and Apache, although this shouldn't make any difference at this stage. I followed Lajos's Flash guide to install the apache, tomcat and cocoon, found at the following sites: http://www.galatea.com/flashguides/apache-tomcat-4-win32.xml http://www.galatea.com/flashguides/tomcat-cocoon-42-win32.xml any suggestions? Thanks Richard. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Im sure its a simple problem!
On Thu, 30 Jan 2003, Richard Cunliffe wrote: Apache Tomcat/4.0.6 - HTTP Status 404 - /soundpool/soundpool.xml type Status report message /soundpool/soundpool.xml description The requested resource (/soundpool/soundpool.xml) is not available. !-- soundpool -- map:pipeline map:match pattern=soundpool/soundpool map:generate src=soundpool.xml/ map:transform src=soundpool.xsl/ map:serialize/ /map:match /map:pipeline Richard, From the looks of it, you're requesting /soundpool/soundpool.xml from your browser? your map:match will only match /soundpool/soundpool, however. Try requesting /soundpool/soundpool in your browser. At least, that's what it looks like to me right now. Regards, Tony - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Im sure its a simple problem!
Richard Cunliffe wrote: C:\tomcat\webapps\soundpool\soundpool.xml C:\tomcat\webapps\soundpool\soundpool.xsl + tomcat (folder) + webapps (folder) +- soundpool (folder) +- soundpool.xml (file) +- soundpool.xsl (file) I assume that webapps is the correct folder. nope, you should put them underneath your cocoon webapp folder: C:\tomcat\webapps\cocoon\soundpool.xml and access them using http://localhost:8080/cocoon/soundpool/soundpool I'm not sure whether it is that what you want. I'm pretty sure you want to access these resources using http://localhost:8080/soundpool/soundpool or similar http://xml.apache.org/cocoon/faq/faq-configure-environment.html#faq-1 might help you here. hope this helps, /Steven -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Im sure its a simple problem!
I have added a few remarks on this issue below as well. [EMAIL PROTECTED] 30/01/2003 09:18:28 Richard Cunliffe wrote: C:\tomcat\webapps\soundpool\soundpool.xml C:\tomcat\webapps\soundpool\soundpool.xsl + tomcat (folder) + webapps (folder) +- soundpool (folder) +- soundpool.xml (file) +- soundpool.xsl (file) I assume that webapps is the correct folder. nope, you should put them underneath your cocoon webapp folder: C:\tomcat\webapps\cocoon\soundpool.xml and access them using http://localhost:8080/cocoon/soundpool/soundpool *** Steven is right of course; the reason Cocoon cannot find the file is that does not know where to look - by default it can *only* look in its own directory or subdirectory unless you tell it otherwise. Bear in mind that the pattern match: map:match pattern=soundpool/soundpool is *not* an instruction for Cocoon to prepend a directory location; its a virtual URI that, when you type it in as part of a URL (as shown above), ONLY means - look for a match called soundpool/soundpool somewhere in the main Cocoon pipeline and process the instructions you find wrapped *inside* that match. In your example, Cocoon then goes off to look for a file called soundpool.xml which it assumes is located in its own directory (because you have not told it otherwise). In summary, yes the problem is simple but that does not mean you are stupid not to solve it! Understanding what is going on inside - both technically and conceptually - can take a while ... some recent estimates put it at anywhere from 2 weeks to 2 months to 2 years!! More reading: http://xml.apache.org/cocoon/faq/faq-configure-environment.html#faq-2 But I really think you need to look at sub-sitemaps - there's an example in the Cocoon samples (that startup by default) - also read through the various doc's and tutorials for examples and discussions. Start with: http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html and have a look at the section on Mounting sitemaps -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Simple problem?
Tim, In the XSL do you have a xsl:output tag? It looks like the stylesheet is assuming html for the output type. Todd Wright At 10:56 AM 1/21/2002 +1030, you wrote: Hi all, We have hopefully a simple problem using cocoon 1.8.2. I am editing html in a form field on a html page that is parsed by cocoon. The trouble is that cocoon is reading correctly formatted list items LIblah/LI and then parsing them back out as LIblah (no closing tag) and then when I submit the form data back cocoon throws an error because the list tag is not closed. I have tried to change the DTD currently REC-html40/strict.dtd to loose.dtd but this still wont output the closed list item tags. What I really would like to do is to disable the output escaping so that only raw code is output to the text field. The edit page is being with xsp and this is the code: util:include-uri util:hrefxsp:exprhttp://blah.com.au/blah.acgi$edit_Stories?+session:g et-attribute name=loginPageQueryString /+#038;anid= + session:get-attribute name=anid / + #038;cachebuster= + session:get-last-accessed-time as=long //xsp:expr/util:href /util:include-uri And this page of xml is being parsed by an xsl stylesheet ?xml-stylesheet href=/ls/xsl_edit.xsl type=text/xsl? Can anyone help? I hope this this is enough information. -- Regards Tim Cavanagh MindMedia Douglas Mawson Institute of Technology Phone +618 83032669 Fax +618 83032667 What can be done with fewer assumptions is done in vain with more William of Ockham - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Todd Wright Software Developer / Technical Trainer www.jtconsult.com Supposing is good, but finding out is better. - Mark Twain - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Simple problem?
Hi Todd, Hmm no we don¹t have that as I understand Cocoon does not support the xsl:output.. Here is the snip from the faq The Cocoon project doesn't implement the xsl:output feature for XSLT because we believe it breaks the separation of concerns and doesn't match the internal Cocoon architecture But yes this would solve the problem I believe and that¹s why I am asking the community for any ideas. We have the same problem with html entities being parsed and then reread from a form text field back into a database and then not being strict xml/xsl. FWIW The only browser that outputs html entities in form text fields as they are in the code is IE 5x on a mac and NOT the OSX version of the browser. We have tested Opera, Netscape, Icab etc etc. So some how we have to disable output escaping on the data contained in text fields that are in forms I have also tried to play with the PIs and still no success. Tim Cavanagh on 22/1/02 1:50 AM, Todd Wright at [EMAIL PROTECTED] wrote: Tim, In the XSL do you have a xsl:output tag? It looks like the stylesheet is assuming html for the output type. Todd Wright At 10:56 AM 1/21/2002 +1030, you wrote: Hi all, We have hopefully a simple problem using cocoon 1.8.2. I am editing html in a form field on a html page that is parsed by cocoon. The trouble is that cocoon is reading correctly formatted list items LIblah/LI and then parsing them back out as LIblah (no closing tag) and then when I submit the form data back cocoon throws an error because the list tag is not closed. I have tried to change the DTD currently REC-html40/strict.dtd to loose.dtd but this still wont output the closed list item tags. What I really would like to do is to disable the output escaping so that only raw code is output to the text field. The edit page is being with xsp and this is the code: util:include-uri util:hrefxsp:exprhttp://blah.com.au/blah.acgi$edit_Stories?+session:g et-attribute name=loginPageQueryString /+#038;anid= + session:get-attribute name=anid / + #038;cachebuster= + session:get-last-accessed-time as=long //xsp:expr/util:href /util:include-uri And this page of xml is being parsed by an xsl stylesheet ?xml-stylesheet href=/ls/xsl_edit.xsl type=text/xsl? Can anyone help? I hope this this is enough information. -- Regards Tim Cavanagh MindMedia Douglas Mawson Institute of Technology Phone +618 83032669 Fax +618 83032667 What can be done with fewer assumptions is done in vain with more William of Ockham - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Todd Wright Software Developer / Technical Trainer www.jtconsult.com Supposing is good, but finding out is better. - Mark Twain - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Simple problem?
Tim, Thanks for the info.. What is the root element of the stylesheet? If it is HTML then it is implicitly being set to HTML Todd Hi Todd, Hmm no we don¹t have that as I understand Cocoon does not support the xsl:output.. Here is the snip from the faq The Cocoon project doesn't implement the xsl:output feature for XSLT because we believe it breaks the separation of concerns and doesn't match the internal Cocoon architecture But yes this would solve the problem I believe and that¹s why I am asking the community for any ideas. We have the same problem with html entities being parsed and then reread from a form text field back into a database and then not being strict xml/xsl. FWIW The only browser that outputs html entities in form text fields as they are in the code is IE 5x on a mac and NOT the OSX version of the browser. We have tested Opera, Netscape, Icab etc etc. So some how we have to disable output escaping on the data contained in text fields that are in forms I have also tried to play with the PIs and still no success. Tim Cavanagh on 22/1/02 1:50 AM, Todd Wright at [EMAIL PROTECTED] wrote: Tim, In the XSL do you have a xsl:output tag? It looks like the stylesheet is assuming html for the output type. Todd Wright At 10:56 AM 1/21/2002 +1030, you wrote: Hi all, We have hopefully a simple problem using cocoon 1.8.2. I am editing html in a form field on a html page that is parsed by cocoon. The trouble is that cocoon is reading correctly formatted list items LIblah/LI and then parsing them back out as LIblah (no closing tag) and then when I submit the form data back cocoon throws an error because the list tag is not closed. I have tried to change the DTD currently REC-html40/strict.dtd to loose.dtd but this still wont output the closed list item tags. What I really would like to do is to disable the output escaping so that only raw code is output to the text field. The edit page is being with xsp and this is the code: util:include-uri util:hrefxsp:exprhttp://blah.com.au/blah.acgi$edit_Stories?+session:g et-attribute name=loginPageQueryString /+#038;anid= + session:get-attribute name=anid / + #038;cachebuster= + session:get-last-accessed-time as=long //xsp:expr/util:href /util:include-uri And this page of xml is being parsed by an xsl stylesheet ?xml-stylesheet href=/ls/xsl_edit.xsl type=text/xsl? Can anyone help? I hope this this is enough information. -- Regards Tim Cavanagh MindMedia Douglas Mawson Institute of Technology Phone +618 83032669 Fax +618 83032667 What can be done with fewer assumptions is done in vain with more William of Ockham - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Todd Wright Software Developer / Technical Trainer www.jtconsult.com Supposing is good, but finding out is better. - Mark Twain - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Todd Wright Software Developer / Technical Trainer www.jtconsult.com Supposing is good, but finding out is better. - Mark Twain - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Simple problem?
Hi all, We have hopefully a simple problem using cocoon 1.8.2. I am editing html in a form field on a html page that is parsed by cocoon. The trouble is that cocoon is reading correctly formatted list items LIblah/LI and then parsing them back out as LIblah (no closing tag) and then when I submit the form data back cocoon throws an error because the list tag is not closed. I have tried to change the DTD currently REC-html40/strict.dtd to loose.dtd but this still wont output the closed list item tags. What I really would like to do is to disable the output escaping so that only raw code is output to the text field. The edit page is being with xsp and this is the code: util:include-uri util:hrefxsp:exprhttp://blah.com.au/blah.acgi$edit_Stories?+session:g et-attribute name=loginPageQueryString /+#038;anid= + session:get-attribute name=anid / + #038;cachebuster= + session:get-last-accessed-time as=long //xsp:expr/util:href /util:include-uri And this page of xml is being parsed by an xsl stylesheet ?xml-stylesheet href=/ls/xsl_edit.xsl type=text/xsl? Can anyone help? I hope this this is enough information. -- Regards Tim Cavanagh MindMedia Douglas Mawson Institute of Technology Phone +618 83032669 Fax +618 83032667 What can be done with fewer assumptions is done in vain with more William of Ockham - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
