Multiple views with Cocoon sunRise?
Hello I am investigating the possibility of offering multiple views to information for users of a portal. I had imagined that this would involve some kind of 'guest cookie' being set on the user's machine that holds the level at which the user would like to see the information (i.e. beginner, intermediate, expert). Then, the server side processing can choose the XML fragment and process with the XSL stylesheet, etc. Can I do this with the user authentication framework in Cocoon (aka sunRise?) More specifically, am I able to redirect new users to a page so that they are able to choose the level at which they can view the site? Many thanks for any pointers to this problem. Regards, Nic Hemley ** The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. ** - 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: forms
Actions were invented after XSPs, and their field / way of control is different. Actions set visible control in the sitemap (structured here). Look for former thread partially entitled avoid use of xsp or something similar. [EMAIL PROTECTED] So you'll see what best fits your needs... Babs - Original Message - From: Gabor Bartha [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 19, 2002 10:24 AM Subject: forms Hi, I'm new in xml, xsl, ... I try to understand how to make forms with post/get methods, ... but I begin to implicate the solutions. 1. I can make an xml, and an xsl (for the xml) to make a html form and post it to the other html. In this case I have to insert the map:parameter name=use-request-parameters value=true/ row in the sitemap, then I can access to the posted parameter from another xsl. This is clear. 2. There are actions. As I read I can use actions to post, obtain posted parameters, ... When have I use actions? eg for databeses 3. There is the request 2.0 logicsheet (xmlns:xsp-request=...) Can anybody explain the differences between these methods, and when can they be user and for what? many thanks, Gabor - 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] - 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]
Tomcat's automatic reload of classes and Cocoon
It works fine if I compile my classes with JBuilder and Tomcat running, but it says Cocoon was not initialized if I build my webapp with JBuilder and Tomcat running : i.e : JBuilder copies all the jars to WEB-INF/lib again, instead of only the classes to WEB-INF/classes. So Tomcat messes up with so many changed jars to reload at once and has problems with their order. Tomcat 4.0.4 with reloadable=true for my webapp. Cocoon 2.1 from several days ago CVS. JBuilder 6 Enterprise. JDK 1.3.1. Win NT4. Just my 2 cents, someone may forward to Tomcat users mailing-list... Babs - 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: XHTML Serilization instead of HTML S.
Greg Jones wrote: How are you creating your HTML. This looks like the issue might be in your .XSL file that is creating the A href/A tag. The two tags XHTML and HTML should work the same. how could this be an issue of the XSL file??? the xsl file has to be XML well-formed, hence you have to write XHTML. the xslt prozessor e.g. xalan then has the ability to create valid HTML instead of XHTML. the problem is, that mostly XHTML works the same like HTML in browsers, but especially mozilla showes strange behaviour when serving XHTML documents e.g. by using the a / element. the behaviour is the following: when you move the mouse over a text paragraph, where there is a a name=/ tag before, the text of the complete paragraph turns into the color of a link and behaves like a link, though it is no, off course, and clicking is ignored. when you move the mouse away, the link color is also away again. strange? yes it is. if you do not believe me, try http://popowa.ifs.tuwien.ac.at:9000/cocoon/oswp/index.html with Mozilla 1 and you will notify this behaviour. and this is off course not desired! Alex - 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: XHTML Serilization instead of HTML S.
Probably because what you have there is not XHTML. You don't have a DOCTYPE declaration. For more information about how Mozilla chooses between the XHTML and HTML display modes (using MIME, DOCTYPE and file extentions), see [1]. Your markup, is not XHTML; a namespace alone is not enough. AFAIK, there is no XHTML DTD that accepts marginheight attributes on the body tag ;-) [1] http://www.mozilla.org/newlayout/xml/ Manos Alexander Schatten wrote: Greg Jones wrote: How are you creating your HTML. This looks like the issue might be in your .XSL file that is creating the A href/A tag. The two tags XHTML and HTML should work the same. how could this be an issue of the XSL file??? the xsl file has to be XML well-formed, hence you have to write XHTML. the xslt prozessor e.g. xalan then has the ability to create valid HTML instead of XHTML. the problem is, that mostly XHTML works the same like HTML in browsers, but especially mozilla showes strange behaviour when serving XHTML documents e.g. by using the a / element. the behaviour is the following: when you move the mouse over a text paragraph, where there is a a name=/ tag before, the text of the complete paragraph turns into the color of a link and behaves like a link, though it is no, off course, and clicking is ignored. when you move the mouse away, the link color is also away again. strange? yes it is. if you do not believe me, try http://popowa.ifs.tuwien.ac.at:9000/cocoon/oswp/index.html with Mozilla 1 and you will notify this behaviour. and this is off course not desired! Alex - 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] - 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]
troubles with logging of non-cocoon classes...
I get a NPE. I followed :
http://outerthought.net/wiki/Wiki.jsp?page=JavaLogging method 1.
First class is a classical custom Action, which has its logger defined in
the sitemap.
Logging of this action works fine.
In this action I create an instance of a custom class that extends
AbstractLogEnabled :
TaminoAccess tamac = new TaminoAccess();(the void
constructor does anything)
tamac.enableLogging(this.getLogger());
tamac.setUri(this.uri);
in the method directly called by setUri(this.uri) I try to log as follow :
if (getLogger().isDebugEnabled()){
getLogger().debug(tamino server : + this.taminoServer);
getLogger().debug(tamino database : + this.taminoDatabase);
getLogger().debug(tamino collection : + this.taminoCollection);
}
This throws a NPE.
In sitemap.log I don't see anything related to enabling logging of tamac.
Any idea ? Thanks a lot.
Babs
-
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]
Impossible or not? Combining request-parameter wildcard matchers in 1 pipeline
Problem Summary **
I cannot figure out how to use matchers to capture an arbitrary
number of request-parameters, in combination with using a wildcard
matcher to parse the structure of the request URI. I seem to be
limited to capturing only a single request-parameter at once, in
a situation when the number names of parameters is not predictable.
***
Here's a more complete description of my problem:
I need to combine two kinds of matching in my sitemap, and so far neither
the documentation or sample sitemap can tell me how to accomplish it. There
are _two conditions_ that my pipeline needs to meet, and I can't figure out
how to meet them both at once:
1) Parsing the URI into its components, which I use to determine both the
data source (i.e. the url for the map:generate tag) and the particular
stylesheet that will get applied (the map:transform tag).
2) Acquiring *all* of the request parameters appended to the path portion of
the URI, and passing these parameters on as part of the URI for the
map:generate tag. For example, a filtering form might specify
subject=Goats, location=Tucson and
dateStart=10-09-02dateEnd=10-20-02.
Here's a sample pipeline which just uses the wildcard URI matcher:
--- Code snip --
map:match pattern=*/*/*.*.html*
map:generate type=file
src=http://localhost:8000/{1}/CalendarRegistry/{2}/EventCollection/getCataloguedEventsAsXML/
map:transform
src=http://localhost:8080/mightycal/{1}/{2}/{3}/intermediate-to-html.{4}.xsl/
map:serialize/
/map:match
End code snip -
To add one of the request parameters, I could wrap the above map:match tag
in another matcher, e.g.: map:match pattern=filter
type=request-parameter. The problem with this solution is that it only
gets me *one* of the potentially five or six parameters that might be passed
as part of the request. Do I have to wrap this matcher inside a separate
matcher for each parameter, so that I end up with a matcher structure that
is 6 levels deep? That seems crazy. It also doesn't allow for situations
where only *some* of the parameters are present, and not others.
What would work best is a matcher or other mechanism that would clump all of
the request parameters together in a single sstring, which I could then
append to the main map:generate component of my pipeline.
Can this be done with the existing matchers? Do I have to use actions? Or
do I have to write my own custom matcher?
Thanks in advance for advice.
Erik Norvelle
==
Support Systems Analyst
College of Agriculture and Life Sciences
The University of Arizona
_
Send and receive Hotmail on your mobile device: http://mobile.msn.com
-
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: XHTML Serilization instead of HTML S.
Probably because what you have there is not XHTML. You don't have a DOCTYPE declaration. For more information about how Mozilla chooses between the XHTML and HTML display modes (using MIME, DOCTYPE and file extentions), see [1]. Your markup, is not XHTML; a namespace alone is not enough. AFAIK, there is no XHTML DTD that accepts marginheight attributes on the body tag ;-) [1] http://www.mozilla.org/newlayout/xml/ Manos well, thank you, I basically know this, but to come back to the point: I DO NOT want to learn how to make correct XHTML, what I want is, that Cocoon renders correct HTML. *that* is the point! any suggestions? I mean, I cannot be the only one having this problem with this cocoon bug, as far as it is a bug, but I cannot see any option that is misconfigured in my setup! thank you alex -- DI Alexander Schatten Institute for Software Technology Vienna University of Technology [EMAIL PROTECTED] Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen - und tolle Preise absahnen! http://www.onlinestar.de - 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: XHTML Serilization instead of HTML S.
[EMAIL PROTECTED] wrote: I DO NOT want to learn how to make correct XHTML, what I want is, that Cocoon renders correct HTML. *that* is the point! any suggestions? Hmmm. Well, whatever you are doing produces XML. If you are using XSLT, try changing the output method to html: xsl:output method=html/ Manos - 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: XHTML Serilization instead of HTML S.
On Thu, 19 Sep 2002 [EMAIL PROTECTED] wrote:
well, thank you, I basically know this, but to come back to the point:
I DO NOT want to learn how to make correct XHTML, what I want is, that
Cocoon renders correct HTML.
*that* is the point!
any suggestions?
Sorry, I missed your initial message, so I'm not sure exactly
which aspect of the output is problematic for you. As you
know (?) you can certainly configure the DOCTYPE with suitable
doctype-public and doctype-system within map:serializer;
the problem I have encountered is that, nonetheless (and using
the HTML serializer) the output retains xhtml namespace
attribute(s). If this is your problem, you can use an xslt to get
rid of them, as a penultimate pipeline stage:
map:match ...
...
map:transform src=xslt/strip-xhtmlns.xslt/
map:serialize/
/map:match
where strip-xhtmlns.xslt is attached below.
(Of course namespace attributes will still appear if the input to
strip-xhtmlns has elements with any namespace other than xhtml;
and this use of xslt may be taking a sledgehammer to crack a
nut - with consequent performance impact).
Does this help?
- Barry.
?xml version=1.0?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:xlink=http://www.w3.org/1999/xlink;
xmlns:xhtml=http://www.w3.org/1999/xhtml;
exclude-result-prefixes=xlink xhtml
!-- Match the document to bootstrap... --
xsl:template match=/
xsl:apply-templates /
/xsl:template
!-- For all xhtml elements we throw away the xhtml namespace;
this is based on the assumption that the output
will be HTML 4 (rather than XHTML). Note that we can't do
this with xsl:copy which provides no mechanism to change the
namespace on the copied nodes; so, instead, we use
xsl:element to manually copy. The throwing away of the
namespace then occurs by virtue of the
exclude-result-prefixes on the xsl:stylesheet element
(above). I expected that the same effect would be achieved
more elegantly via the namespace attribute on xsl:element
(by giving it the empty string value ) - but that doesn't
seem to work, so my expectations are evidently mistaken
there! --
xsl:template match=xhtml:*
xsl:element name={local-name()}
xsl:apply-templates select=@*|node()/
/xsl:element
/xsl:template
!--
Whereof we cannot speak, thereof we must be silent
- Ludwig Wittgenstein.
--
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
/xsl:stylesheet
-
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: How to handle 3 input fields to store it in one date column?
On 14.Sep.2002 -- 07:17 AM, Antonio Gallardo Rivera wrote: This can be changed to a question: how to manipulate parameters before form-validation. You can use a custom action that stores the result in a request attribute and validate against that. El Sábado, 14 de Septiembre de 2002 06:56, Antonio Gallardo Rivera escribió: Hi folks! 1-Given a date format: dd-mm- 2-Given a database field in a table. 2-We have 3 input fields: 1 input for day (2 digits) 1 input for month (2 digits) 1 input for year (4 digits). We use: form-validator. The question is: How to code the 3 fields in the form to add or update the date using dbAdd or dbUpd action? You could write your own InputModule that combines input from several other parameters into one. 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 - 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: form validation
On 12.Sep.2002 -- 03:12 PM, Barbara Post wrote: I just wonder whether I can do the following in my xsl : The field validation can trigger 2 types of errors : 1. the field is null - show message 1 2. the field is not null but has wrong regex syntx - show message 2. I just have troubles to find the documentation again... For now I have 2 error tags but both messages appear despite xsl:attribute name=whenis-null/xsl:attribute or xsl:attribute name=whenno-match/xsl:attribute... Barbara, this looks OK to me. Documentation is in javadocs for SimpleFormTransformer. Sure you use the transformer? 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 - 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: form validation
I solved it after restarting cocoon, it worked... Indeed I used the SimpleFormTransformer. I also used 2 error tags. - Original Message - From: Christian Haul [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 19, 2002 1:58 PM Subject: Re: form validation On 12.Sep.2002 -- 03:12 PM, Barbara Post wrote: I just wonder whether I can do the following in my xsl : The field validation can trigger 2 types of errors : 1. the field is null - show message 1 2. the field is not null but has wrong regex syntx - show message 2. I just have troubles to find the documentation again... For now I have 2 error tags but both messages appear despite xsl:attribute name=whenis-null/xsl:attribute or xsl:attribute name=whenno-match/xsl:attribute... Barbara, this looks OK to me. Documentation is in javadocs for SimpleFormTransformer. Sure you use the transformer? 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 - 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] - 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]
doubt in i18n
Hi, I want to use supreg;/sup(which is for ®) in messages_de.xml and messages_en.xml.My messages_en.xml is as follows: ?xml version=1.0 encoding=UTF-8? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; catalogue xml:lang=en xmlns=http://www.w3.org/1999/xhtml; message key=testHello supreg;/sup Kavitha /message /catalogue I want the out put as Hello ® Kavitha.But Iam getting just Hello. If I use #174; for ® it works,,,But I dont want to use it,,, If someone knows please help me,,, Kavitha __ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com - 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]
[solved] Re: troubles with logging of non-cocoon classes...
I did not express clearly so you partly misunderstood (the code you wondered
about was in fact in the act() method of my custom action to create and
initialize my custom non-Cocoon class) but you helped me anyway, thanks
Marcus : indeed the 2 loggers I have have the same ID (LogKitLogger@2d5534),
and it works now... I forgot this. before getLogger() in the bottom
code, damn ! :-p
So maybe there is a slight correction to
http://outerthought.net/wiki/Wiki.jsp?page=JavaLogging with some this. in
this section ?
import org.apache.avalon.framework.logger.AbstractLogEnabled;
public class SomeClass extends AbstractLogEnabled {
public void someMethod() {
...
getLogger().debug( Hello, log. It worked! );
getLogger().info( Hello, log. Here is info );
getLogger().error( Hello, log. Here is an error );
//..etc.
...
}
}
Babs after a good lunch, so better coding now.
- Original Message -
From: Marcus Crafter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 1:59 PM
Subject: Re: troubles with logging of non-cocoon classes...
Hi Barbara,
On Thu, Sep 19, 2002 at 12:04:07PM +0200, Barbara Post wrote:
I get a NPE. I followed :
http://outerthought.net/wiki/Wiki.jsp?page=JavaLogging method 1.
First class is a classical custom Action, which has its logger defined
in
the sitemap.
Logging of this action works fine.
ok.
In this action I create an instance of a custom class that extends
AbstractLogEnabled :
TaminoAccess tamac = new TaminoAccess();(the void
constructor does anything)
tamac.enableLogging(this.getLogger());
tamac.setUri(this.uri);
Where exactly this this code above ? I suspect it's in the
constructor of your custom action ?
If this is the case then the call to 'this.getLogger()' will
return null because the Avalon component manager won't have yet
enabled logging on that sitemap component (and hence your
non-cocoon class won't have a logging object to log to)
To fix this, implement Initializable on your custom action and add
the code to create and set the logger on your non-cocoon class there.
The initialize() method on your action will be called well after
enableLogging() by the ComponentManager, so you should have a valid
logging object then.
(BTW - If the variable happened to be created at within the class
(ie. not in the constructor) then an alternative could be to overload
enableLogging() on your custom action and propogate the logger
object there).
If that's not the case, can you print out what 'this.getLogger()'
returns and set us in a stacktrace of the NPE.
Hope that helps.
Cheers,
Marcus
in the method directly called by setUri(this.uri) I try to log as follow
:
if (getLogger().isDebugEnabled()){
getLogger().debug(tamino server : + this.taminoServer);
getLogger().debug(tamino database : + this.taminoDatabase);
getLogger().debug(tamino collection : + this.taminoCollection);
}
This throws a NPE.
--
.
,,$, Marcus Crafter
;$' ':Computer Systems Engineer
$: : ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$,_/\ :' 60327 Frankfurt Germany
' /(
\_'
.
:
-
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]
-
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: Cocoon 2.0.3 under Enhydra 3.1
Matthew,
The code generated with 2.0.1 means that session logicsheet was not applied. Please
look at 2.0.1 samples for session logicsheet usage. It might be that with 2.0.1 you
have to use session namespace, not xsp-session. This bug was fixed, now (2.0.3)
you can use any namespace prefix you want.
Vadim
Matthew Hailstone wrote:
oops. Yeah, I put the xsp:content elements in the 'if' condition to see
if it would help.
But, after comparing the working java file from 2.0.3 with the one
created with 2.0.1, I found the following commented below:
Matthew Hailstone wrote:
Vadim,
Here is a portion of my xsp file:
if( xsp:contentxsp-session:get-attribute
name=test-name-wcart//xsp:content == null
||
((String)xsp:contentxsp-session:get-attribute
name=test-name-wcart//xsp:content).length() == 0
){
xsp:content
Oh no, not like this, but:
if(xsp-session:get-attribute
name=test-name-wcart/ == null
||
((String)xsp-session:get-attribute
name=test-name-wcart/).length() == 0
){
xsp:content
.
/xsp:content
}
Here is the java file that is created to be compiled:
if (xspAttr.addAttribute(, name, name, CDATA,
test-name-wcart);
Notice here, though, how the code should be:
XSPSessionHelper.getSessionAttribute(session,
String.valueOf(test-name-wcart),
null)
this.contentHandler.startElement(http://apache.org/xsp/session/2.0;,
get-attribute,
xsp-session:get-attribute,
xspAttr);
xspAttr.clear();
this.contentHandler.endElement(http://apache.org/xsp/session/2.0;,
get-attribute,
xsp-session:get-attribute);
== null || ((String) xspAttr.addAttribute(, name, name,
CDATA, test-name-wcart);
this.contentHandler.startElement(http://apache.org/xsp/session/2.0;,
get-attribute,
xsp-session:get-attribute,
xspAttr);
xspAttr.clear();
this.contentHandler.endElement(http://apache.org/xsp/session/2.0;,
get-attribute,
xsp-session:get-attribute);
).length() == 0) {
It seems that the xslt (I'm guessing) is not producing the
correct java
code from the xsp-session namespace tags.
The working java file created from 2.0.3 looks like this with the same
xsp:
if(
(
XSPSessionHelper.getSessionAttribute(session,
String.valueOf(test-name-wcart),
null)
)
== null
|| ((String)
(
XSPSessionHelper.getSessionAttribute(session,
String.valueOf(test-name-wcart),
null)
)
).length() == 0){
Matthew
-
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]
saving xml to file - server prob
I am using the stylesheet below to save generated xml to a file. It works
fine, locally on my computer.
But when I try to use the webapp on the (linux)server (ten-web), nothing is
saved!
What could be the problem?
Thanks for any help!
xsl:stylesheet
version=1.0
xmlns:xsp=http://apache.org/xsp;
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:=http://www.w3.org/TR/xhtml1/transitional;
xmlns:add=http://www.w3.org/TR/xhtml1/transitional;
xmlns:redirect=org.apache.xalan.xslt.extensions.Redirect
extension-element-prefixes=redirect
xsl:output method=xml version=1.0 indent=yes encoding=iso-8859-1/
xsl:param name=framework select=//requirements/@framework/
xsl:template match=/
xsl:variable name=filename
select=concat('\\Ten-web\webapps\reqDyn\requirement\', $framework, '.xml')/
megatop
redirect:write file={$filename}
xsl:apply-templates/
/redirect:write
/megatop
/xsl:template
xsl:template match=@*|*|text()|processing-instruction()
xsl:copy
xsl:apply-templates select=@*|*|text()|processing-instruction()/
/xsl:copy
/xsl:template
/xsl:stylesheet
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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: Tomcat's automatic reload of classes and Cocoon
Barbara Post wrote: It works fine if I compile my classes with JBuilder and Tomcat running, but it says Cocoon was not initialized if I build my webapp with JBuilder and Tomcat running : i.e : JBuilder copies all the jars to WEB-INF/lib again, instead of only the classes to WEB-INF/classes. So Tomcat messes up with so many changed jars to reload at once and has problems with their order. shameless plug So don't use JBuilder! Use IDEA. :) /shameless plug Configure project output to WEB-INF/classes, and compile only modified classes in there. another plug With Resin, you don't have to even (re)compile: have .java and .class in WEB-INF/classes, and once you modify .java, Resin recompiles it and reloads app. /another plug Vadim Tomcat 4.0.4 with reloadable=true for my webapp. Cocoon 2.1 from several days ago CVS. JBuilder 6 Enterprise. JDK 1.3.1. Win NT4. Just my 2 cents, someone may forward to Tomcat users mailing-list... Babs - 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: saving xml to file - server prob
maybe the way you wrote the path with antislashes Linux system uses
slashes... Do you use Windows system on your local computer ?
Maybe a write rights problem too.
Babs
- Original Message -
From: Hans Wursten [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 2:45 PM
Subject: saving xml to file - server prob
I am using the stylesheet below to save generated xml to a file. It works
fine, locally on my computer.
But when I try to use the webapp on the (linux)server (ten-web), nothing
is
saved!
What could be the problem?
Thanks for any help!
xsl:stylesheet
version=1.0
xmlns:xsp=http://apache.org/xsp;
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:=http://www.w3.org/TR/xhtml1/transitional;
xmlns:add=http://www.w3.org/TR/xhtml1/transitional;
xmlns:redirect=org.apache.xalan.xslt.extensions.Redirect
extension-element-prefixes=redirect
xsl:output method=xml version=1.0 indent=yes
encoding=iso-8859-1/
xsl:param name=framework select=//requirements/@framework/
xsl:template match=/
xsl:variable name=filename
select=concat('\\Ten-web\webapps\reqDyn\requirement\', $framework,
'.xml')/
megatop
redirect:write file={$filename}
xsl:apply-templates/
/redirect:write
/megatop
/xsl:template
xsl:template match=@*|*|text()|processing-instruction()
xsl:copy
xsl:apply-templates select=@*|*|text()|processing-instruction()/
/xsl:copy
/xsl:template
/xsl:stylesheet
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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]
-
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: saving xml to file - server prob
I have writing-rights.
Yes, I am using windows. But if I write xyz.xml as filename instead of the
\\ten-web\...
or use slashes, nothing is saved as well.
maybe the way you wrote the path with antislashes Linux system uses
slashes... Do you use Windows system on your local computer ?
Maybe a write rights problem too.
Babs
- Original Message -
From: Hans Wursten [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 2:45 PM
Subject: saving xml to file - server prob
I am using the stylesheet below to save generated xml to a file. It
works
fine, locally on my computer.
But when I try to use the webapp on the (linux)server (ten-web), nothing
is
saved!
What could be the problem?
Thanks for any help!
xsl:stylesheet
version=1.0
xmlns:xsp=http://apache.org/xsp;
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:=http://www.w3.org/TR/xhtml1/transitional;
xmlns:add=http://www.w3.org/TR/xhtml1/transitional;
xmlns:redirect=org.apache.xalan.xslt.extensions.Redirect
extension-element-prefixes=redirect
xsl:output method=xml version=1.0 indent=yes
encoding=iso-8859-1/
xsl:param name=framework select=//requirements/@framework/
xsl:template match=/
xsl:variable name=filename
select=concat('\\Ten-web\webapps\reqDyn\requirement\', $framework,
'.xml')/
megatop
redirect:write file={$filename}
xsl:apply-templates/
/redirect:write
/megatop
/xsl:template
xsl:template match=@*|*|text()|processing-instruction()
xsl:copy
xsl:apply-templates select=@*|*|text()|processing-instruction()/
/xsl:copy
/xsl:template
/xsl:stylesheet
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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]
-
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]
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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: saving xml to file - server prob
nothing is saved as well., are you sure any file of name xyz.xml is
created, in usr/home for example ? I don't know much with Linux but if this
is supposed to write a file, it should...
Sorry.
- Original Message -
From: Hans Wursten [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 3:09 PM
Subject: Re: saving xml to file - server prob
I have writing-rights.
Yes, I am using windows. But if I write xyz.xml as filename instead of
the
\\ten-web\...
or use slashes, nothing is saved as well.
maybe the way you wrote the path with antislashes Linux system uses
slashes... Do you use Windows system on your local computer ?
Maybe a write rights problem too.
Babs
- Original Message -
From: Hans Wursten [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 2:45 PM
Subject: saving xml to file - server prob
I am using the stylesheet below to save generated xml to a file. It
works
fine, locally on my computer.
But when I try to use the webapp on the (linux)server (ten-web),
nothing
is
saved!
What could be the problem?
Thanks for any help!
xsl:stylesheet
version=1.0
xmlns:xsp=http://apache.org/xsp;
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:=http://www.w3.org/TR/xhtml1/transitional;
xmlns:add=http://www.w3.org/TR/xhtml1/transitional;
xmlns:redirect=org.apache.xalan.xslt.extensions.Redirect
extension-element-prefixes=redirect
xsl:output method=xml version=1.0 indent=yes
encoding=iso-8859-1/
xsl:param name=framework select=//requirements/@framework/
xsl:template match=/
xsl:variable name=filename
select=concat('\\Ten-web\webapps\reqDyn\requirement\', $framework,
'.xml')/
megatop
redirect:write file={$filename}
xsl:apply-templates/
/redirect:write
/megatop
/xsl:template
xsl:template match=@*|*|text()|processing-instruction()
xsl:copy
xsl:apply-templates select=@*|*|text()|processing-instruction()/
/xsl:copy
/xsl:template
/xsl:stylesheet
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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]
-
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]
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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]
-
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]
Deploying Cocoon 2.0.3 in JBoss 3.0.2 with Embedded Catalina 4.0.4
Hello, we are using cocoon with JBoss/Catalina. We have packed the cocoon.war file into an .ear file to set the context-root to /cocoon. Everything works fine with 3.0.0/4.0.3 JDK 1.3.1_03. Now we have upgraded JBoss/Catalina from 3.0.0/4.0.3 to 3.0.2/4.0.4. Result: we cannot deploy Cocoon 2.0.3 anymore - worse: we cannot deploy our enterprise-application using cocoon anymore. Stack Trace: java.io.FileNotFoundException: C:\MIDDLE_TIER\jboss-3.0.2_tomcat-4.0.4\bin\jndi:\localhost\sitemap.xmap (Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:59) at java.io.FileInputStream.(FileInputStream.java:90) at org.apache.cocoon.components.source.FileSource.getInputStream(FileSource.jav a:140) at org.apache.cocoon.components.source.AbstractStreamSource.getInputSource(Abst ractStreamSource.java:161) at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.generat eResource(ProgramGeneratorImpl.java:367) at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createR esource(ProgramGeneratorImpl.java:333) at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(Pr ogramGeneratorImpl.java:292) at org.apache.cocoon.sitemap.Handler.run(Handler.java:265) at java.lang.Thread.run(Thread.java:479) Any help would be appreciated. mfg Klaus Richarz Andre Hegerath Hamburger Berater Team GmbH Hamburg, Germany - 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]
Error deploying cocoon.war (Version 2.0.3) to Tomcat 4.1.10
Hi all, i've downloaded the Cocoon 2.0.3 and tried to deploy the file cocoon.war to my Tomcat server (4.1.10) using the Tomcat Manager (or 'Deployment tool' by Sun) After deployment the manager reports the Cocoon application as running whenn calling /cocoon on my Tomcat Server i get the following error: -- Cocoon 2 - Internal server error: description org.apache.cocoon.ProcessingException: Language Exception: org.apache.cocoon.components.language.LanguageException: Error compiling sitemap_xmap: Line 22, column 49: cannot access class Component; file org/apache/avalon/framework/component/Component.class not found Line 23, column 53: cannot access class Configurable; file org/apache/avalon/framework/configuration/Configurable.class not found Line 24, column 53: cannot access class Configuration; file org/apache/avalon/framework/configuration/Configuration.class not found Line 25, column 53: cannot access class ConfigurationException; file org/apache/avalon/framework/configuration/ConfigurationException.class not found Line 26, column 53: cannot access class DefaultConfiguration; file -- In Tomcat/work/Standalone/localhost/cocoon/WEB-INF/lib i can see all libraries which classes cocoon servlet claims not to find, e.g avalon-framework-4.1.2.jar for org/apache/avalon/framework/component/Component.class. When i manualy unpack cocoon.war into Tomcat/webapps everything works fine. Due to some circumstances this way of deployment is unacceptable for the firm i work in. Please cc your answer to [EMAIL PROTECTED] Thanks in advance! -- Andrei Svirida, Projekte Entwicklung MIDRAY GmbH - a debitel company Phone: +49.221.8884 435 Fax:+49.221.8884 455 http://www.midray.com/ - 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: i18n question
Hi list,
thanks for your help and advices :)
Sure it will couse a nullpointerexception. First of all you need to to get
from this snip something like this:
a href=/test
img
xsl:attribute name=src
/images/test.svg?label_text=helloamp;label_color=red
/xsl:attribute
/img
/a
and than use this stylesheet
See example:
Your sitemap should have:
map:match pattern=stylesheets/*.xsl
map:generate src=stylesheets/{1}.xsl/
map:transform type=i18n/ !-- will generate a valid xsl without i18n
tags, and it will not couse an error anymore --
map:serialize type=xml/
/map:match
map:match pattern=...
map:generate src=you-source/
map:transform src=cocoon:/stylesheets/stylesheet-with-my-snip.xsl/ !--
use stylesheet generated by previous pipeline --
map:serialize/
/map:match
--
Mathias Ochsendorf
www: www.ochsendorf.net | www.ochsendorf.de
ICQ: 68556900
-
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: saving xml to file - server prob
Yeah, you were right. :)
The path was wrong.
The right is: /usr/java/tomcat/webapps/reqDyn/requirement/
Thank you!
greets
nothing is saved as well., are you sure any file of name xyz.xml is
created, in usr/home for example ? I don't know much with Linux but if
this
is supposed to write a file, it should...
Sorry.
- Original Message -
From: Hans Wursten [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 3:09 PM
Subject: Re: saving xml to file - server prob
I have writing-rights.
Yes, I am using windows. But if I write xyz.xml as filename instead of
the
\\ten-web\...
or use slashes, nothing is saved as well.
maybe the way you wrote the path with antislashes Linux system
uses
slashes... Do you use Windows system on your local computer ?
Maybe a write rights problem too.
Babs
- Original Message -
From: Hans Wursten [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 2:45 PM
Subject: saving xml to file - server prob
I am using the stylesheet below to save generated xml to a file. It
works
fine, locally on my computer.
But when I try to use the webapp on the (linux)server (ten-web),
nothing
is
saved!
What could be the problem?
Thanks for any help!
xsl:stylesheet
version=1.0
xmlns:xsp=http://apache.org/xsp;
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:=http://www.w3.org/TR/xhtml1/transitional;
xmlns:add=http://www.w3.org/TR/xhtml1/transitional;
xmlns:redirect=org.apache.xalan.xslt.extensions.Redirect
extension-element-prefixes=redirect
xsl:output method=xml version=1.0 indent=yes
encoding=iso-8859-1/
xsl:param name=framework select=//requirements/@framework/
xsl:template match=/
xsl:variable name=filename
select=concat('\\Ten-web\webapps\reqDyn\requirement\', $framework,
'.xml')/
megatop
redirect:write file={$filename}
xsl:apply-templates/
/redirect:write
/megatop
/xsl:template
xsl:template match=@*|*|text()|processing-instruction()
xsl:copy
xsl:apply-templates select=@*|*|text()|processing-instruction()/
/xsl:copy
/xsl:template
/xsl:stylesheet
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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]
-
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]
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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]
-
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]
--
Werden Sie mit uns zum OnlineStar 2002! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de
-
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: Umlauts in cocoon 2.0.2
Thanks to everyone who replied to this thread, I managed to crack it in the end. The solution to my umlaut problem consisted of: 1. Putting this action at the top of the pipeline which handles the UTF-8 post: map:act type=set-encoding map:parameter name=form-encoding value=UTF-8/ /map:act 2. Saving all my files ensuring the bytes written to disk were UTF-8 (as Ugo, Antonio and Joerg told me). Specifically, my sitemap, web.xml, all xsl files, and any static xml files I read in my pipelines. 3. Putting an encoding child in my serializers, e.g. map:serializer name=xhtml ... encodingUTF-8/encoding !-- KR added -- /map:serializer Step 3 may be optional, but I know the container-encoding of cocoon defaults to ISO-8859-1 so I thought it best left in. I am sure that step 1 can be replaced by setting the form-encoding parameter in the cocoon init-params, but doing this has knock on effects I hinted at in an earlier post, as I think there is a bug in the cocoon code (2.0.2, anyway). Fortunately, for the moment I can avoid this. Thanks for everyone's help! Kenneth On Wed, 2002-09-18 at 15:41, Kenneth Roper wrote: Firstly, thanks for everyone's suggestions, this is a very helpful list! Unfortunately, I am no further forward. Changing the encoding of the sitemap.xmap and the web.xml file has no effect. Changing the encoding of the xhtml serializer looked like I was on the right track, but unfortunately doesn't work: I have a this string in my db: ÄäÖöÜüß It is displayed on an html page generated by a cocoon pipeline. If I change my serializer definition in my sitemap and add this: encodingISO-8859-1/encoding The above string appears in my browser (and in the page source) as 7 question marks, i.e. ??? If I change the encoding back to this: encodingUTF-8/encoding I can then see my original string correctly. However, if I post this string back to my application, my application receives the string as first detailed in the original post (i.e. ÃäÃöÃüÃ). There is obviously a difference in encoding (or something) between text coming from the server to the browser, and the text posted from the browser back to the server. Any more ideas? Thanks again. Kenneth - 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] - 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]
Install problems WAS3.5.5
Hello, I searched the archives, and google, and haven't found a good explanation about how to go about getting Cocoon working in Websphere 3.5.x. I am close I think. I used the WAR file converter in the Admin Console, but I get an exception during init of the Cocoon servlet: javax.servlet.ServletException: Init parameter 'configuration' doesn't name an existing resource : /web-inf/cocoon.xconf I have tried different paths, I tried adding cocoon.xconf as a web resource, I added the SimpleFileServlet. Doesn't seem to fix it. I am considering modifying the servlet to use the real path instead of the URI. Anyone have any pointers or info that can help me out before I go re-writting things? Thanks! Dan Feather Sr. Programmer/Analyst [EMAIL PROTECTED] - 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: how to prevent logging passwords in request and sessionparams?
second question : yes : see rotation tag in WEB-INF/logkit.xconf. Babs - Original Message - From: Timothy Larson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 19, 2002 6:17 PM Subject: how to prevent logging passwords in request and sessionparams? How do you prevent logging of passwords held in request parameters and session attributes? I do not want to turn off logging completely. By the way, is there any sort of automated log rotation for cocoon to prevent the logs getting too big? Tim - 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] - 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: Install problems WAS3.5.5
[EMAIL PROTECTED] wrote: I searched the archives, and google, and haven't found a good explanation about how to go about getting Cocoon working in Websphere 3.5.x. I am close I think. I used the WAR file converter in the Admin Console, but I get an exception during init of the Cocoon servlet: javax.servlet.ServletException: Init parameter 'configuration' doesn't name an existing resource : /web-inf/cocoon.xconf In the Websphere 3.5 I have to use, the path entered as value of the configuration parameter is appended to the first additional classpath entry for the servlet. J.Pietschmann - 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]
New Riders book review
I've reviewed the New Riders Cocoon book and the review is available here. http://news.diversebooks.com/article.pl?sid=02/09/19/1722242 Oh ok, here it is too. Title: Cocoon: Building XML Applications Author: Matthew Langham Author: Carsten Ziegler Publisher: New Riders URL: http://www.newriders.com ISBN: 0735712352 Price: 30.99 UKP Topic: non-fiction Topic: computing Topic: XML Reviewer: Alex McLintock Reviewer URL: http://www.DiverseBooks.com/ If you have a genuine need for an XML backed website and you want to build it using java tools then you could do a lot worse than to choose Apache's Cocoon suite of tools. Cocoon is built up froma a large number of different java based programs (all from Apache Software Foundation) but has suffered up till now from a lack of paper based documentation. This is the first Cocoon book which I have seen and I recommend it as such... your first Apache Cocoon book. The book starts off with far too much information about web applications without specific relevance to Cocoon. I don't see how this could be relevant to someone wanting to build a web application - surely they would know this already. Do we really need step by step instructions on how to install Tomcat? Surely it is the readers' responsibility to sort that sort of thing out. We don't expect explanations of how to run Unix for instance. The step by step explanation of the sitemap and pipelines whilst looking at the Hello World app is most welcome. Understanding the sitemap is the most important feature specific to Cocoon. It does use Java, JSP, JDBC, XML, XSLT, and loads of other techniques, but these aren't unique to Cocoon. The sitemap is an XML file which basically describes the whole site... and how to respond to any request. I have been using Cocoon for several months now and so I was hoping for a book which could teach me a lot. Unfortunately it only taught me a few things, but what it did show me were gems. One thing which I have been looking for for ages was how to do a photo album which changes often. This book gives a nice clean example of that so I can drop files in a directory and have them listed in my website properly. But... There is always a but. This book doesn't have enough examples. They could have put loads on the CD, but didn't. For instance, one could write a whole book on the subject of FOP - the component of Cocoon which can take XML and convert it to PDF and other fancy formats. There is an SVG example, but just the one. There is one big example: a news portal. It is fine as far as it goes, but I wanted more. There are some reference chapters for those who want to understand more about the Internals, and the different sitemap components. Chapter 10 introduces XSP (the XML equivalent to JSP) which is used to enhance the news portal example. The reference Appendices are a hefty 120 pages long, and much more readable than the online equivalent, but we shall see how up to date it stays. Openweb Analysts Ltd, London. Software For Complex Websites http://www.OWAL.co.uk/ Open Source Software Companies please register here http://www.OWAL.co.uk/oss_support/ - 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]
redirect-to error causes Cocoon servlet exception
Cocoon users, I am using Cocoon 2.0.3 and Tomcat 4.0.4. I have a redirect-to in place in my sitemap that looks like this: !-- Redirect to index page. -- map:match pattern= map:redirect-to uri=index/ /map:match Everytime I hit the page http://localhost:8080/gwd_webapp/ I get the following error message in access.log: . . . DEBUG (2002-09-19) 13:36.25:108 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/AbstractEnvironment: from context (file:/C:/java/tomcat404/webapps/gwd_webapp/) and prefix() DEBUG (2002-09-19) 13:36.25:108 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/AbstractEnvironment: to context(sitemap.xmap) and prefix() DEBUG (2002-09-19) 13:36.25:108 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/AbstractEnvironment: at URI DEBUG (2002-09-19) 13:36.25:108 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/AbstractEnvironment: New context is file:/C:/java/tomcat404/webapps/gwd_webapp/ DEBUG (2002-09-19) 13:36.25:118 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/HttpEnvironment: Sending redirect to 'index' DEBUG (2002-09-19) 13:36.25:118 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/AbstractEnvironment: Set the URI Prefix (OLD=, NEW=) DEBUG (2002-09-19) 13:36.25:118 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/AbstractEnvironment: Reset context to file:/C:/java/tomcat404/webapps/gwd_webapp/ INFO(2002-09-19) 13:36.25:118 [access] (/gwd_webapp/) HttpProcessor[8080] [4]/CocoonServlet: '' Processed by Apache Cocoon 2.0.3 in 30 milliseconds. ERROR (2002-09-19) 13:36.25:118 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon servlet threw 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:1126) 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) . . . The page redirects correctly, but that error message is worrisome. I looked in the cocoon access.log, and it is showing the same error on redirects. If I access http://localhost:8080/cocoon/documents/index.html I get this error: . . . DEBUG (2002-09-19) 13:42.47:709 [access]
Re: Install problems WAS3.5.5
[EMAIL PROTECTED] wrote: I searched the archives, and google, and haven't found a good explanation about how to go about getting Cocoon working in Websphere 3.5.x. I am close I think. I used the WAR file converter in the Admin Console, but I get an exception during init of the Cocoon servlet: javax.servlet.ServletException: Init parameter 'configuration' doesn't name an existing resource : /web-inf/cocoon.xconf In the Websphere 3.5 I have to use, the path entered as value of the configuration parameter is appended to the first additional classpath entry for the servlet. J.Pietschmann I am closer now thanks to that bit of info. However, now when I open http://stuff.domain.com/Cocoon; I get a nicely formatted Cocoon 2 - Internal server error: - 8 Snip--- java.lang.NullPointerException org/apache/cocoon/servlet/CocoonServlet.service(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V+0 (CocoonServlet.java:901) javax/servlet/http/HttpServlet.service(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+25 (HttpServlet.java:853) com/ibm/servlet/engine/webapp/StrictServletInstance.doService(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+21 (ServletManager.java:644) ... - 8 Snip--- The Servlet Web Path List contains default_host/Cocoon/,default_host/Cocoon/*.jsp, and default_host/Cocoon/*.html I have two directories in the classpath for the web app: /QIBM/UserData/WebASAdv/default/hosts/default_host/Cocoon/web and /QIBM/UserData/WebASAdv/default/hosts/default_host/Cocoon/servlets web-inf is in the first directory. After I added that first directory (it was just the servlets directory) the servlet actually loaded. FYI - if those paths look odd, it is because this is on an AS/400 (IBM iSeries). Any ideas what I am over looking? Am I just not reading something somewhere? Any help is greatly appreciated. Dan Feather [EMAIL PROTECTED] - 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: Install problems WAS3.5.5
[EMAIL PROTECTED] wrote: I am closer now thanks to that bit of info. However, now when I open http://stuff.domain.com/Cocoon; I get a nicely formatted Cocoon 2 - Internal server error: - 8 Snip--- java.lang.NullPointerException [...] (CocoonServlet.java:901) ... Any ideas what I am over looking? Am I just not reading something somewhere? Any help is greatly appreciated. Get the Cocoon source and look into CocoonServlet.java, line 901, the code there may give you a hint what's missing. Did you try your WebApp with Tomcat before? I recommend debugging it this way. J.Pietschmann - 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: Impossible or not? Combining request-parameter wildcard matchers in 1 pipe
Barbara:
Thanks for the tip. What ended up working was using the
org.apache.cocoon.acting.RequestParamAction Action class. For the sake of
anyone reading this in the future, here's what I did.
I created an action as follows:
map:actions
map:action name=request
src=org.apache.cocoon.acting.RequestParamAction/
/map:actions
I then used this new Action in my pipeline:
map:match pattern=*/*/*.*.html*
map:act type=request
map:generate type=file
src=http://localhost:8000/{../1}/CalendarRegistry/{../2}/EventCollection/getCataloguedEventsAsXML{requestQuery}/
/map:act
map:transform
src=http://localhost:8080/mightycal/{1}/{2}/{3}/intermediate-to-html.{4}.xsl/
map:serialize/
/map:match
The request Action provided me with the {requestQuery} parameter that I
could use to append *all* of the query string to the URI for my XML source.
Note that in order to reference the original positional parameters from the
WildcardURIMatcher, I had to change {1} to {../1}, etc.
-Erik
==
Support Systems Analyst
College of Agriculture and Life Sciences
The University of Arizona
From: Barbara Post [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Impossible or not? Combining request-parameter wildcard
matchers in 1 pipeline
Date: Thu, 19 Sep 2002 12:22:31 +0200
Just an idea, I am busy yet : use an Action and getParameterNames() method
if I remember well (look at the API docs), so that you have all the request
parameters. Then you can put sitemap parameters as you want.
HTH,
Babs
- Original Message -
From: Erik Norvelle [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 12:18 PM
Subject: Impossible or not? Combining request-parameter wildcard matchers
in 1 pipeline
Problem Summary **
I cannot figure out how to use matchers to capture an arbitrary
number of request-parameters, in combination with using a wildcard
matcher to parse the structure of the request URI. I seem to be
limited to capturing only a single request-parameter at once, in
a situation when the number names of parameters is not predictable.
***
Here's a more complete description of my problem:
I need to combine two kinds of matching in my sitemap, and so far
neither
the documentation or sample sitemap can tell me how to accomplish it.
There
are _two conditions_ that my pipeline needs to meet, and I can't figure
out
how to meet them both at once:
1) Parsing the URI into its components, which I use to determine both
the
data source (i.e. the url for the map:generate tag) and the particular
stylesheet that will get applied (the map:transform tag).
2) Acquiring *all* of the request parameters appended to the path
portion
of
the URI, and passing these parameters on as part of the URI for the
map:generate tag. For example, a filtering form might specify
subject=Goats, location=Tucson and
dateStart=10-09-02dateEnd=10-20-02.
Here's a sample pipeline which just uses the wildcard URI matcher:
--- Code snip --
map:match pattern=*/*/*.*.html*
map:generate type=file
src=http://localhost:8000/{1}/CalendarRegistry/{2}/EventCollection/getCatal
oguedEventsAsXML/
map:transform
src=http://localhost:8080/mightycal/{1}/{2}/{3}/intermediate-to-html.{4}.xs
l/
map:serialize/
/map:match
End code snip -
To add one of the request parameters, I could wrap the above map:match
tag
in another matcher, e.g.: map:match pattern=filter
type=request-parameter. The problem with this solution is that it
only
gets me *one* of the potentially five or six parameters that might be
passed
as part of the request. Do I have to wrap this matcher inside a
separate
matcher for each parameter, so that I end up with a matcher structure
that
is 6 levels deep? That seems crazy. It also doesn't allow for
situations
where only *some* of the parameters are present, and not others.
What would work best is a matcher or other mechanism that would clump
all
of
the request parameters together in a single sstring, which I could then
append to the main map:generate component of my pipeline.
Can this be done with the existing matchers? Do I have to use actions?
Or
do I have to write my own custom matcher?
Thanks in advance for advice.
Erik Norvelle
==
Support Systems Analyst
College of Agriculture and Life Sciences
The University of Arizona
_
Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: XMLForm stylesheet change suggestion
Phil, Sorry it took me a while to respond, I am having some problems with the 2.1 build. The XForms spec mandates one caption/ sub element. I think if you need additional text, you can use other custom tags from your own namespace. xf:textbox xf:captionMy field/xf:caption additionalElementCustom Text/additionalElement /xf:textbox Another option is to not set display text directly in the caption tag, but instead specify a lookup key like my.field which is then replaced via i18n tags. As far as wizard2html.xsl is concerned, it is only intended as a demo. xmlform2html.xsl on the other hand should be generic. Looking forward to your comments, Ivelin - Original Message - From: Phil [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 16, 2002 11:09 PM Subject: Re: XMLForm stylesheet change suggestion That does take care of the phantom text, but what if someone wanted some additional text on the form. The patch that I posted is based on the assumption that someone would not want a double post of the first caption, but any additional captions they would want to see. With the patch that is in cvs, what element would you use to go about getting additional text into the form (current problem I am working on)? Also, is the wizard2html.xsl supposed to be app specific or general to all xmlform apps? Thanks, Phil On Monday 16 September 2002 08:41 pm, Ivelin Ivanov wrote: Thanks for reminding me that this is an outstanding bug. I have applied a patch and closed it. It is a little different than yours, but it achieves the same effect. Please do a diff and let me know if you think the patch won't work. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9716 Best, Ivelin - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 16, 2002 9:46 PM Subject: XMLForm stylesheet change suggestion I have a change for the file wizard2html.xsl which will remove the caption that appears on the side of the page. If someone would tell me the proper way to submit this information in the future, I would be happy to comply. original code: xsl:for-each select=*[name() != 'xf:submit'] xsl:choose xsl:when test=name() = 'error'/ xsl:when test=xf:* xsl:apply-templates select=./ /xsl:when xsl:otherwise xsl:copy-of select=./ /xsl:otherwise /xsl:choose /xsl:for-each modified code: xsl:for-each select=*[name() != 'xf:submit'] xsl:choose xsl:when test=name() = 'error'/ !-- start new code -- xsl:when test=name() = 'xf:caption' xsl:if test=count(parent::node()/xf:caption) 1 xsl:if test=parent::node()/xf:caption[1] != . tr td align=center colspan=3 xsl:value-of select=./ /td /tr tr td colspan=3 /td /tr /xsl:if /xsl:if /xsl:when !-- end new code -- xsl:when test=xf:* xsl:apply-templates select=./ /xsl:when xsl:otherwise xsl:copy-of select=./ /xsl:otherwise /xsl:choose /xsl:for-each tr td align=center colspan=3 xsl:for-each select=*[name() = 'xf:submit'] xsl:copy-of select=. / xsl:text /xsl:text /xsl:for-each - 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] - 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] - 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] - 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: Sendmail again :(
On Wednesday 18 September 2002 15:33, Ivan Luzyanin wrote: Hi! I'm having a problem with sendmail. I've successfuly set up sendmail logicsheet, put mail.jar from JavaMail 1.3 pakage to WEB-INF/lib. Transformed XSP page (Java source in work dir, attached) seemes to be ok and no errors reported in log-file... But still i can't recieve an e-mail, and most strange thing is that result of pipeline execution is empty document... I try to apply not valid e-mail address and still the same result - no result (empty document). Desired result: page upsaUPSA/upsa /page and an e-mail message in my inbox :) My XSP: ?xml version=1.0 encoding=UTF-8? xsp:page language=java xmlns:xsp=http://apache.org/xsp; xmlns:xsp-request=http://apache.org/xsp/request/2.0; xmlns:sendmail=http://apache.org/cocoon/sendmail/1.0; page xsp:logic String text = Hi,\n+ this mail has been send through a web form ...\n; /xsp:logic sendmail:send-mail sendmail:charsetISO-8859-1/sendmail:charset sendmail:from[EMAIL PROTECTED]/sendmail:from sendmail:to[EMAIL PROTECTED]/sendmail:to sendmail:subjectCocoon send mail test/sendmail:subject !-- Modify the next line to point to your mail server -- sendmail:smtphost192.168.0.3/sendmail:smtphost sendmail:body xsp:exprtext/xsp:expr /sendmail:body /sendmail:send-mail upsaUPSA/upsa /page /xsp:page Sitemap pipeline: map:match pattern=mail.xml map:generate src=docs/mail.xsp type=serverpages/ map:serialize type=xml/ /map:match Snip from sitemap logfile: DEBUG (2002-09-18) 15:12.29:482 [sitemap] (/proza-new/mail.xml) HttpProcessor[8080][4]/sitemap_xmap: Matched wildcard pattern *.xml DEBUG (2002-09-18) 15:12.29:483 [sitemap] (/proza-new/mail.xml) HttpProcessor[8080][4]/AbstractSitemap: Current Sitemap Parameters: PARAM: '1' VALUE: 'mail' PARAM: '0' VALUE: 'mail.xml' DEBUG (2002-09-18) 15:12.29:483 [sitemap.selector.request-parameter] (/proza-new/mail.xml) HttpProcessor[8080][4]/RequestParameterSelector: Request parameter 'action' not set -- failing. DEBUG (2002-09-18) 15:12.29:484 [sitemap] (/proza-new/mail.xml) HttpProcessor[8080][4]/sitemap_xmap: Matched wildcard pattern mail.xml DEBUG (2002-09-18) 15:12.29:485 [sitemap] (/proza-new/mail.xml) HttpProcessor[8080][4]/AbstractSitemap: Current Sitemap Parameters: PARAM: '0' VALUE: 'mail.xml' PARAM: '../1' VALUE: 'mail' PARAM: '../0' VALUE: 'mail.xml' DEBUG (2002-09-18) 15:12.29:485 [sitemap] (/proza-new/mail.xml) HttpProcessor[8080][4]/sitemap_xmap: Component generator:serverpages(Parameters.EMPTY_PARAMETERS) DEBUG (2002-09-18) 15:12.29:486 [sitemap] (/proza-new/mail.xmll) HttpProcessor[8080][4]/sitemap_xmap: Source= docs/mail.xsp DEBUG (2002-09-18) 15:12.29:487 [sitemap] (/proza-new/mail.xml) HttpProcessor[8080][4]/sitemap_xmap: Component serializer:xml(Parameters.EMPTY_PARAMETERS) Help me, please! I've killed 2 hours to find out where is the problem... My env: Cocoon 2.0.3, Tomcat 4.0.4, JDK 1.4.0_01, SuSE 8.0 Ivan Luzyanin. I found where was a problem. I forget to put activation.jar from JAF package. Now it works fine. Regards! Ivan Luzyanin. - 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]
