I am embedding xsp and xsl into a sitemap file.
Everything works, except when the embedded xsp code is modified.
Then cocoon seems to randomly choose whether or not to start
using the updated xsp code. Even when the java, class, and
cache files are deleted, no proxies are in use, and the
The submit button comes across just like text fields.
Here is a sample login page and post page:
?xml version=1.0?
!-- filename: login.xsp --
xsp:page xmlns:xsp=http://apache.org/xsp;
html
form method=post action=login.post
Sometext:br/input type=text name=sometext/br/
input
I'm trying to embed xsp in an xml document.
A stylesheet extracts it so I can use it in a pipeline like this:
map:match pattern=somepage.xsp
map:generate src=somepage.xmap/
map:transform src=get.xsl
map:parameter name=section value=xsp-section/
/map:transform
map:serialize type=xml/
In Cocoon 2.0.3, how is the base path determined for map:handle-errors?
I'm confused, because in different subsitemaps it either looks for files at the
same level as the current subsitemap or all the way out at the root sitemap.
Tim
/
/map:handle-errors
/map:pipeline
[EMAIL PROTECTED] 09/17/02 12:14PM
Timothy Larson wrote:
In Cocoon 2.0.3, how is the base path determined for map:handle-errors?
I'm confused, because in different subsitemaps it either looks for files at the
same level as the current subsitemap or all the way
Is the context supposed to always match the directory where the current
sitemap is stored?
Tim
[EMAIL PROTECTED] 09/18/02 01:36PM
Timothy Larson wrote:
...
Can you explicitly control the context from the sitemap?
No (see above
Timothy Larson wrote:
Anybody know how to take a url in a session attribute and encode the session onto it?
Non-working example to show what I am trying to do:
xsp:encode-urlxsp-session:get-attribute name=fruit//xsp:encode-url
You need xsp-response:encode-url
Vadim
Tim
:
second question : yes : see rotation tag in WEB-INF/logkit.xconf.
First question: use log categories. Change log level for category where
username/pwd are logged.If this is sitemap component, you can even
assign it separate log category.
Vadim
Babs
- Original Message -
From: Timothy
I need to create a database connection,
do some security checks,
and set a user role
before I have rights to run queries against the database.
I made an action to do all of the setup, but I do not know how
to make xsp/esql or xsl/sql use the established connection.
Any ideas how to make esql or
Each session needs to be logged into the database with a
different username and password.
How can I do this using a database pool?
Tim
[EMAIL PROTECTED] 09/26/02 04:33PM
Timothy Larson wrote:
I need to create a database connection,
Why not:
1. Get connection from the pool,
2.
do some
-in user and the specific report being run.
To interface with this system I wrote some working java code to
do the key exchange with the db and change the security role.
How can I integrate this with the reports I wrote in xsp/esql and xsl?
Tim
[EMAIL PROTECTED] 09/27/02 08:34AM
Timothy Larson
I am having the same problem and am using the same ugly workaround.
Tomcat 3.3.1
Cocoon 2.0.4dev (from CVS around 9-17-2002)
JDK 1.4.0_02
If I serialize the XSP page as XML it is always is up-to-date, but when I
use the XSP as a serverpage it is usually out-of-date. This tells me that
the XML
I had a similar problem. When I used the XInclude transformer, I got
a NullPointerException when I tried to refer to the results with the
cocoon:/ protocol. Here was my solution (bad hack, but it worked):
I made a stylesheet copy-of.xsl that simply copied what it was passed
without changing it.
I am sending this again because it did not seem to hit the list.
Sorry if you have already seen this email.
Using Saxon7.2 in Cocoon 2.0.4dev from Nov 13 2002,
I apply stylesheet A to stylesheet B.
This produces stylesheet C, which is NOT well formed.
(Notice the xsl:copy.../x2:copy)
Using
Any clue what would cause this error when using Saxon7.3 with Cocoon2.1,
but no error when using Saxon7.3 Cocoon2.0.4dev?
org.xml.sax.SAXException: Saxon requires an XML parser that reports the QName of each
element
at
Try map:match pattern=mysite/**
Notice the two asterisks.
Tim
[EMAIL PROTECTED] 12/11/02 12:44PM
Is there a way to specify a GENERAL pattern?
I know, the wildcards exists for this reason, but if I write in my sitemap:
map:match pattern=mysite/*
and the user write something like:
Check your log files...maybe the xsl:include is not looking in the
directory that you expect and so not finding the file to include.
Tim
[EMAIL PROTECTED] 12/12/02 02:21PM
Well no, I guess there isn't. The docs on include seem to say that it's
like a #includefile in a C source file. In other
What can I do in a Cocoon sitemap to send a redirect if
I also need to execute a pipeline to produce a side-effect?
Specifically, I am trying to respond to a POST by writing
a file to disk and redirecting back to the page that caused
the POST. The redirect is to drop the POST information
so page
Does Cocoon allow transforms after using the SourceWritingTransformer?
Example (note: xsl-file-B):
map:generate src=some-xml-file/
map:transform src=xsl-file-A/
map:transform type=SourceWritingTransformer/
map:transform src=xsl-file-B/
map:serialize/
In Cocoon-2.0.4 (compiled with
I am trying to use Saxon-7.3.1 with Cocoon-2.1 for XSP pages.
It worked until a couple weeks ago (using Saxon-7.3), but broke
around the time that the XSP changes were put in Cocoon-2.1
for the not-recompiling bug.
Anybody have ideans or a simillar setup working?
When I try to access:
More Info:
If I edit the sitemap to make Saxon pretend to be Xalan (to ensure that only Saxon is
used)
then the problem changes. A java source file is generated for the XSP page, but the
first line
in the file should not be there at all. Here are the first 5 lines from the file
You can use the cocoon:/ protocol to do this:
map:match pattern=some_page.xsp
map:generate src=some_file.xml/
map:transform src=some_stylesheet.xsl/
map:serialize type=xml/
/map:match
map:match pattern=some_page.html
map:generate src=cocoon:/some_page.xsp type=serverpages/
You coulde try the caching version of the cinclude transformer in place of the
non-caching xinclude transformer.
See http://xml.apache.org/cocoon/userdocs/transformers/cinclude-transformer.html
The only problem I see is that the cinclude transformer does not seem to have the
xpath features
that
Is it possible to call a pipeline to use the SourceWritingTransformer
and still only send a simple map:redirect-to ... back to the client?
Tim
-
Please check that your question has not already been answered in the
FAQ before
How can I get the current subsitemap directory when coding
java in an action or an xsp page?
Tim
-
Please check that your question has not already been answered in the
FAQ before posting.
If you are using XSP, then you can get the current path with:
xsp:exprresolver.resolve().getSystemId()/xsp:expr
Or the current path with a filename on the end with:
xsp:exprresolver.resolve(somefile.ext).getSystemId()/xsp:expr
Tim
[EMAIL PROTECTED] 01/01/03 01:57PM
Reinhard Poetz wrote:
You could make your XSP into an action:
http://wiki.cocoondev.org/Wiki.jsp?page=XSPAction
Then you could use the action's indication of success or failure
to redirect to different places:
map:match pattern=*.html
map:act type=xsp-action src=some.xsp
map:redirect-to
Anybody know a simple equivalent to use in XSL?
Tim
[EMAIL PROTECTED] 01/02/03 02:30PM
If you are using XSP, then you can get the current path with:
xsp:exprresolver.resolve().getSystemId()/xsp:expr
Or the current path with a filename on the end with:
What would be involved in the jpath logicsheet working with a
local copy of cocoon-2.0.4?
I tried copying jpath.xsl from schecoon to the main area
(where request, response, session, etc. are) and updated
the MANIFEST.MF to include it, but cocoon still says:
Caused by:
When I try to use the XSP Input logicsheet in cocoon-2.0.4 I get this error:
/org/apache/cocoon/components/language/markup/xsp/java/input.xsl; Line 199; Column
54;
Could not find template named: get-string-attribute
Looking in the cocoon source, get-string-attribute is only mentioned in
When I try to use the XSP Input logicsheet in cocoon-2.0.4 I get this error:
/org/apache/cocoon/components/language/markup/xsp/java/input.xsl; Line 199; Column
54;
Could not find template named: get-string-attribute
Looking in the cocoon source, get-string-attribute is only mentioned in
Thanks Chris, I got it mostly working with your information.
A couple of issues, though:
The first issue is that while this works fine:
input:get-attribute module=session-attr as=string name=attr1 default=(Does
not exist)/
this:
input:get-attribute-names module=session-attr as=string/
Is there a sample somewhere of using jxpath with the input logicsheet?
I am trying to pick apart a dom that is stored in the session.
Tim
-
Please check that your question has not already been answered in the
FAQ before
made for the cocoon_2_0_3_branch like we already have for HEAD:
http://cvs.apache.org/snapshots/xml-cocoon2/
Tim
[EMAIL PROTECTED] 01/10/03 11:48AM
On 09.Jan.2003 -- 10:02 AM, Timothy Larson wrote:
Thanks Chris, I got it mostly working with your information.
A couple of issues, though
Sun JDK 1.4.1_01 on Windows 2000 Professional
Tim
[EMAIL PROTECTED] 02/01/03 02:06PM
Hi all:
To better understand how you are using Cocoon product and serve your
needs better ;-)
Cocoon developers would like to know how many of our currect users are
deploying Cocoon on JDK 1.2 and why they
Has anyone tried setting the serializer when using the
SourceWriting-Transformer in Cocoon-2.0.5dev?
I am trying to use Cocoon-2.0.5dev from the 2003-02-12 snapshot
to write a PDF file to disk using the SourceWriting-Transformer.
The trouble is I cannot seem to set the serializer to fo2pdf.
It
Have the XSP-Action set a sitemap parameter, such as url,
and then have this in your sitemap:
map:act src=somepage.xsp type=xsp-action
map:redirect-to uri={uri}/
/map:act
Tim
[EMAIL PROTECTED] 02/20/03 10:48AM
I have used the XSP-as-action method to do redirection in the sitemap (based
Sorry for the typo, should be:
Have the XSP-Action set a sitemap parameter, such as uri,
and then have this in your sitemap:
map:act src=somepage.xsp type=xsp-action
map:redirect-to uri={uri}/
/map:act
Tim
[EMAIL PROTECTED] 02/20/03 10:48AM
I have used the XSP-as-action method to do
you use xsp:logicsitemapParams.put(param_name,
param_value)/xsp:logic? Is there an xsp logicsheet tag for setting sitemap
parameters?
Wayne
-Original Message-
From: Timothy Larson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 20, 2003 12:09 PM
To: [EMAIL PROTECTED]
Subject: RE
I did not find out how to get the {1} from the sitemap,
but this XSP page and XSP-Action may help you with calling resources.
Here is an XSP page that calls a resource:
(Using an XSP page prevents you from using a map:redirect-to .../)
?xml version=1.0?
xsp:page language=java
xmlns:xsp
40 matches
Mail list logo
