Re: Use cocoon properties in flow
Hi Carlos,
you can also do this (directly in flowscript):
var props = new java.util.Properties();
props.load(new java.io.FileInputStream(your.properties));
var prop = props.getProperty(property.name);
I don't know if there's a more direct and elegant way.
Regards,
Johannes
Carlos Martínez schrieb:
Hello,
Thanks for the response.
Now i'm using this solucion but i want to know if it's possible to get
directly the variables in the flowscript.
Regards.
DAVIGNON Andre - CETE NP/DIODé/PANDOC escribió:
Hi,
If you can access it in a sitemap, you could try this to access it in
the flow :
In the sitemap :
map:call function=myFonction
map:parameter name=someName value=${my-variable}
/map:call
Then in the flow :
var myVariable = cocoon.parameters.someName;
Regards.
Andr�
Le 10/06/2008 07:51, Carlos Mart�nez (par Internet, d�p�t
[EMAIL PROTECTED])
a �crit :
Hello,
I have created a properties file with some interesting variables
in the folder WEB-INF/properties. I access this variables in the
sitemap easy using this notation ${my-variable}. But the problem
is how to access the same varible in the flowscript code.
Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Use cocoon properties in flow
Hello,
Thanks for the response.
Now i'm using this solucion but i want to know if it's possible to get
directly the variables in the flowscript.
Regards.
DAVIGNON Andre - CETE NP/DIODé/PANDOC escribió:
Hi,
If you can access it in a sitemap, you could try this to access it in
the flow :
In the sitemap :
map:call function=myFonction
map:parameter name=someName value=${my-variable}
/map:call
Then in the flow :
var myVariable = cocoon.parameters.someName;
Regards.
Andr�
Le 10/06/2008 07:51, Carlos Mart�nez (par Internet, d�p�t
[EMAIL PROTECTED])
a �crit :
Hello,
I have created a properties file with some interesting variables in the
folder WEB-INF/properties. I access this variables in the sitemap easy
using this notation ${my-variable}. But the problem is how to access
the same varible in the flowscript code.
Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Carlos Martínez Peña
Centre de Tecnologies de la Informació
Universitat de les Illes Balears
Cra. Valldemossa km 7.5 E-07122 Palma
Baleares Spain
tel.: +34 971 17 20 32
e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
problem with document() function
Hello everybody,
I have a for-each statement in my style sheet:
xsl:for-each select=*
td
input type=text value={current()} name={name()}/
/td
/xsl:for-each
This snippet puts out the content of all nodes into text fields. Now I
want to make a distinction. Some values should be in a text field and
some values should be displayed only. Which nodes should be displayed
and which not is stored in a persitent xml file. What I thought of, is
something like this:
xsl:for-each select=*
td
xsl:if test=CurrentNodeIsContentOfExampleNodeOfPersitentXmlFile')
input type=text value={current()} name={name()}/
/xsl:if
/td
/xsl:for-each
How can I do this? Is this possible?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Use cocoon properties in flow
Hi,
You can look up the settings bean directly like this in flow...
var settings = cocoon.getComponent
(Packages.org.apache.cocoon.configuration.Settings.ROLE);
var prop = settings.getProperty(my.property.name);
...
cocoon.releaseComponent(settings);
Cheers,
Robin
On 11 Jun 2008, at 09:30, Carlos Martínez wrote:
Hello,
Thanks for the response.
Now i'm using this solucion but i want to know if it's possible to
get directly the variables in the flowscript.
Regards.
DAVIGNON Andre - CETE NP/DIODé/PANDOC escribió:
Hi,
If you can access it in a sitemap, you could try this to access it
in the flow :
In the sitemap :
map:call function=myFonction
map:parameter name=someName value=${my-variable}
/map:call
Then in the flow :
var myVariable = cocoon.parameters.someName;
Regards.
Andr�
Le 10/06/2008 07:51, Carlos Mart�nez (par Internet, d�p�t
users-return-95314-andre.davignon=developpement-
[EMAIL PROTECTED]) a �crit :
Hello,
I have created a properties file with some interesting
variables in the folder WEB-INF/properties. I access this
variables in the sitemap easy using this notation ${my-
variable}. But the problem is how to access the same varible in
the flowscript code.
Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
==
==
Carlos Martínez Peña
Centre de Tecnologies de la Informació
Universitat de les Illes Balears
Cra. Valldemossa km 7.5 E-07122 Palma
Baleares Spain
tel.: +34 971 17 20 32 e-mail: [EMAIL PROTECTED]
==
==
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
IncludeCacheManager vs. SourceUtil.toSAX
hi, I wrote a generator that has to include several other pipelines. Now I have to migrate this to cocoon 2.2 and I have some doubt on how to include another pipeline. In the last version of my generator I was using (Default)IncludeCahceManager. But when I had a look at the IncludeTransformer in 2.2, I saw that it is using SourceUtil.toSAX() for the inclusion. What is the best practice on including another pipeline? Does SourceUtil does use the pipeline cache also. And is IncludeCacheManager really using the pipeline cache? Any recommendations? any help would be appreciated... regards, Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problem with document() function
Hi Johannes,
You should be able to use the document() function to interrogate the
contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and build
the tree in memory.
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 12:18
To: users@cocoon.apache.org
Subject: problem with document() function
Hello everybody,
I have a for-each statement in my style sheet:
xsl:for-each select=*
td
input type=text value={current()} name={name()}/
/td
/xsl:for-each
This snippet puts out the content of all nodes into text fields. Now I
want to make a distinction. Some values should be in a text field and
some values should be displayed only. Which nodes should be displayed
and which not is stored in a persitent xml file. What I thought of, is
something like this:
xsl:for-each select=*
td
xsl:if
test=CurrentNodeIsContentOfExampleNodeOfPersitentXmlFile')
input type=text value={current()} name={name()}/
/xsl:if
/td
/xsl:for-each
How can I do this? Is this possible?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB
NodeC
text
/NodeC
/NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate the
contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and build
the tree in memory.
Heather
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: problem with document() function
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your file or
the path to your nodes. The XML needs to be well formed, but if you're
not getting an error then that shouldn't be a factor. I'd make sure the
file path is correct by trying to output everything in the file
xsl:value-of select=document($filename)/* / or use doc-available to
tell you.
According to your XML input your xpath looks ok (assuming first /NodeB
is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB
NodeC
text
/NodeC
/NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate the
contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and build
the tree in memory.
Heather
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with document() function
Hi Johannes,
Johannes Hoechstaedter schrieb:
Hi Heather,
yes I thought the same. Thats what I tried, only to test the document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC/NodeB
/NodeA
Could it be still a path issue?
where is your XML file located? AFAIK source resolving is relative to
the location of the sitemap file.
-- Andreas
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate the
contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and build
the tree in memory.
Heather
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Authentication block
Hello
I am trying to move my cocoon applications from cocoon-2.1.10 to
cocoon-2.2.0. I cannot make the tomcat security (realm) work with
cocoon-2.2.0 so I tried to use authentication block instead.
=== My application context ===
bean name=org.apache.cocoon.auth.SecurityHandler/simple
class=org.apache.cocoon.auth.impl.SimpleSecurityHandler
scope=singleton
property name=userProperties
value
manager=mana
manager.roles=admin_admin
agent001=agen
agent001.roles=admin_user
/value
/property
/bean
bean name=org.apache.cocoon.auth.Application/cocoon-app
class=org.apache.cocoon.auth.impl.StandardApplication
scope=singleton
property name=securityHandler
ref=org.apache.cocoon.auth.SecurityHandler/simple/
/bean
=== My sitemap ===
map:match pattern=
map:redirect-to uri=login/
/map:match
map:match pattern=home
map:act type=cauth-is-logged-in
map:parameter name=application value=cocoon-app/
map:generate src=menu/home.xml/
map:transform type=role-filter/
map:transform type=i18nmap:parameter name=locale
value={request:locale}//map:transform
map:serialize type=xhtml/
/map:act
map:redirect-to uri=login/
/map:match
map:match pattern=login
map:act type=cauth-is-logged-in
map:parameter name=application value=cocoon-app/
map:redirect-to uri=home/
/map:act
map:generate src=menu/login.xml/
map:transform type=i18nmap:parameter name=locale
value={request:locale}//map:transform
map:serialize type=xhtml/
/map:match
map:match pattern=j_security_check
map:act type=cauth-login
map:parameter name=application value=cocoon-app /
map:parameter name=name value={request-param:j_username} /
map:parameter name=password value={request-param:j_password}
/
map:redirect-to uri=home /
/map:act
map:redirect-to uri=error /
/map:match
It looks like it logs in correctly, goes to home and displays menu/
home.xml, but the role-filter transformation can't see admin_admin role.
How to define roles in SimpleSecurityHandler? Are they recognised by
role-filter transformer?
My users are in MySQL database. I use Hibernate. Should I use
DAOSecurityHandler to get my users? How to use DAOSecurityHandler?
Best regards
Barbara
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with document() function
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error. Just an
empty value, where should be a value.
The file is located in COB-INF/resource/internal/sql/configuration,
and I access it by resource/internal/sql/configuration/filename. I
think it is correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your file or
the path to your nodes. The XML needs to be well formed, but if you're
not getting an error then that shouldn't be a factor. I'd make sure the
file path is correct by trying to output everything in the file
xsl:value-of select=document($filename)/* / or use doc-available to
tell you.
According to your XML input your xpath looks ok (assuming first /NodeB
is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB
NodeC
text
/NodeC
/NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate the
contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and build
the tree in memory.
Heather
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with document() function
Hi Johannes,
maybe you could try absolute path like:
* UNIX ... file:///foo/bar/this.xsl
* Windows ... file:///C:/foo/bar/this.xsl
Just to make sure that the file is fetched from the right location.
- mika -
Johannes Hoechstaedter kirjoitti:
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error. Just
an empty value, where should be a value.
The file is located in COB-INF/resource/internal/sql/configuration,
and I access it by resource/internal/sql/configuration/filename. I
think it is correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your file or
the path to your nodes. The XML needs to be well formed, but if you're
not getting an error then that shouldn't be a factor. I'd make sure the
file path is correct by trying to output everything in the file
xsl:value-of select=document($filename)/* / or use doc-available to
tell you.
According to your XML input your xpath looks ok (assuming first /NodeB
is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC /NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate the
contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and build
the tree in memory.
Heather
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with document() function
Go away with absolute paths
Lehtonen, Mika schrieb:
Hi Johannes,
maybe you could try absolute path like:
* UNIX ... file:///foo/bar/this.xsl
* Windows ... file:///C:/foo/bar/this.xsl
Just to make sure that the file is fetched from the right location.
- mika -
Johannes Hoechstaedter kirjoitti:
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error. Just
an empty value, where should be a value.
The file is located in COB-INF/resource/internal/sql/configuration,
and I access it by resource/internal/sql/configuration/filename. I
think it is correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your
file or
the path to your nodes. The XML needs to be well formed, but if you're
not getting an error then that shouldn't be a factor. I'd make sure the
file path is correct by trying to output everything in the file
xsl:value-of select=document($filename)/* / or use doc-available to
tell you.
According to your XML input your xpath looks ok (assuming first
/NodeB
is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC /NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate
the contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and build
the tree in memory.
Heather
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless
specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with document() function
Sorry Mika, whe it hits you too hard, what I wrote. The problem is now:
It works, but I don't want it this way :(
Johannes Hoechstaedter schrieb:
Go away with absolute paths
Lehtonen, Mika schrieb:
Hi Johannes,
maybe you could try absolute path like:
* UNIX ... file:///foo/bar/this.xsl
* Windows ... file:///C:/foo/bar/this.xsl
Just to make sure that the file is fetched from the right location.
- mika -
Johannes Hoechstaedter kirjoitti:
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error. Just
an empty value, where should be a value.
The file is located in
COB-INF/resource/internal/sql/configuration, and I access it by
resource/internal/sql/configuration/filename. I think it is
correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your
file or
the path to your nodes. The XML needs to be well formed, but if you're
not getting an error then that shouldn't be a factor. I'd make sure
the
file path is correct by trying to output everything in the file
xsl:value-of select=document($filename)/* / or use
doc-available to
tell you.
According to your XML input your xpath looks ok (assuming first
/NodeB
is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the
document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC /NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate
the contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and
build
the tree in memory.
Heather
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless
specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with document() function
Yep,
I understand, but as I wrote, this was just a test. Maybe some wiser
person could tell you how to get back to relative path. Maybe you could
make, if you are using Linux, some symbolic link to your file from the
root or utilize these:
Inside your components, you can also use these protocols whenever you
have a SourceResolver handy.
* context:// - get a resource using the servlet context
* cocoon:/ - get a pipeline from the current sitemap
* cocoon:// - get a pipeline using the root sitemap
* resource:// - get a resource from the context classloader
- mika -
Johannes Hoechstaedter kirjoitti:
Sorry Mika, whe it hits you too hard, what I wrote. The problem is
now: It works, but I don't want it this way :(
Johannes Hoechstaedter schrieb:
Go away with absolute paths
Lehtonen, Mika schrieb:
Hi Johannes,
maybe you could try absolute path like:
* UNIX ... file:///foo/bar/this.xsl
* Windows ... file:///C:/foo/bar/this.xsl
Just to make sure that the file is fetched from the right location.
- mika -
Johannes Hoechstaedter kirjoitti:
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error.
Just an empty value, where should be a value.
The file is located in
COB-INF/resource/internal/sql/configuration, and I access it by
resource/internal/sql/configuration/filename. I think it is
correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your
file or
the path to your nodes. The XML needs to be well formed, but if
you're
not getting an error then that shouldn't be a factor. I'd make
sure the
file path is correct by trying to output everything in the file
xsl:value-of select=document($filename)/* / or use
doc-available to
tell you.
According to your XML input your xpath looks ok (assuming first
/NodeB
is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the
document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC /NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate
the contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and
build
the tree in memory.
Heather
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless
specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
C22 - Maven artifact missing
I Just tried building Cocoon from svn by following these instructions [1] and got the build error listed below. I've tried deleting my local repository and tried building all the blocks with: mvn install -Dmaven.test.skip=true -P allblocks All with the same result. Should I just try again later or is their something I can do to resolve this? I'm still trying to get to grips with Maven and this sort of thing is very frustrating ;-) Regards, David Legg [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.cocoon:cocoon-pipeline-impl:test-jar:tests:1.1.0-SNAPSHOT Try downloading the file manually from the project website. ... Path to dependency: 1) org.apache.cocoon:cocoon-pipeline-components:jar:1.1.0-SNAPSHOT 2) org.apache.cocoon:cocoon-pipeline-impl:test-jar:tests:1.1.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.cocoon:cocoon-pipeline-components:jar:1.1.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), central (http://repo1.maven.org/maven2) [1] http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g4/g1/g1/798.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problem with document() function
Johannes, If you don't like absolute paths then you just need to figure
out where your XSLT is relative to your XML doc. If your XSL is in say,
'COB-INF/resource/internal/sql/transformation' you'll need
'../resource/internal/sql/configuration/filename' (with file extension
of course).
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 15:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Go away with absolute paths
Lehtonen, Mika schrieb:
Hi Johannes,
maybe you could try absolute path like:
* UNIX ... file:///foo/bar/this.xsl
* Windows ... file:///C:/foo/bar/this.xsl
Just to make sure that the file is fetched from the right location.
- mika -
Johannes Hoechstaedter kirjoitti:
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error. Just
an empty value, where should be a value.
The file is located in COB-INF/resource/internal/sql/configuration,
and I access it by resource/internal/sql/configuration/filename. I
think it is correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your
file or the path to your nodes. The XML needs to be well formed, but
if you're not getting an error then that shouldn't be a factor. I'd
make sure the file path is correct by trying to output everything in
the file xsl:value-of select=document($filename)/* / or use
doc-available to tell you.
According to your XML input your xpath looks ok (assuming first
/NodeB is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the
document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC /NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate
the contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and
build
the tree in memory.
Heather
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless
specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
CForms and DOJO
Hi there, I am still using Cocoon 2.1.9 and was wandering if the version of dojo used for CForms in Ajax-Mode is used in 2.1.10 and 2.2? Since my current application is currently using a lot of Dojo 1.1 Stuff and I was sort of annoyed of the problem having to use dojo 0.4 and 1.1 together, I startet creating my own forms-styling.xsl, which does the same as the original cocoon version, instead it uses dojo 1.1 with all its advanced features. It is currently working nicely. Does Cocoon in a version greater than 2.1.9 still use Dojo 0.4? If yes, it might be interesting for me to clean up my xslt and give it to the cocoon guys (It looks a lot nicer). While working on the Dojo 1.1 integration I found out that none of the validation-information is passed to the fi-stuff it would be great if this information was forwarded here, cause I could additionally use the Dojo client-side validation in addition to the server-side validation of CForms (I know this doesnt work for all validators) reducing some client-server-roundtrips. Rgards, Christofer [ C h r i s t o f e r D u t z ] C-Ware IT-Service Inhaber Dipl. Inf. Christofer Dutz Karlstraße. 104, 64285 Darmstadt fon: 0 61 51 / 27315 - 61 fax: 0 61 51 / 27315 - 64 mobil: 0171 / 7 444 2 33 email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.c-ware.de/ http://www.c-ware.de FA Darmstadt: 07 813 60581
Re: problem with document() function
Maybe you could wrote a pipeline with a matcher to your $filename and
with source pointing to your absolute file?
- mika -
Heather Rankin kirjoitti:
Johannes, If you don't like absolute paths then you just need to figure
out where your XSLT is relative to your XML doc. If your XSL is in say,
'COB-INF/resource/internal/sql/transformation' you'll need
'../resource/internal/sql/configuration/filename' (with file extension
of course).
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 15:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Go away with absolute paths
Lehtonen, Mika schrieb:
Hi Johannes,
maybe you could try absolute path like:
* UNIX ... file:///foo/bar/this.xsl
* Windows ... file:///C:/foo/bar/this.xsl
Just to make sure that the file is fetched from the right location.
- mika -
Johannes Hoechstaedter kirjoitti:
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error. Just
an empty value, where should be a value.
The file is located in COB-INF/resource/internal/sql/configuration,
and I access it by resource/internal/sql/configuration/filename. I
think it is correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your
file or the path to your nodes. The XML needs to be well formed, but
if you're not getting an error then that shouldn't be a factor. I'd
make sure the file path is correct by trying to output everything in
the file xsl:value-of select=document($filename)/* / or use
doc-available to tell you.
According to your XML input your xpath looks ok (assuming first
/NodeB is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the
document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC /NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate
the contents of an external XML file. It is also a good idea to use
doc-available() first to check for the existence of the file and
build
the tree in memory.
Heather
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless
specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
Re: C22 - Maven artifact missing
David Legg pisze: I Just tried building Cocoon from svn by following these instructions [1] and got the build error listed below. I've tried deleting my local repository and tried building all the blocks with: mvn install -Dmaven.test.skip=true -P allblocks Skipping test phase is not a good idea anymore and docs need an update (I've done it already). Anyway, this flag shouldn't make the build fail. David, you are the second person reporting this issue, the first one was Alexander[1] so there must be an issue with Cocoon dependencies here. All with the same result. Should I just try again later or is their something I can do to resolve this? Nope, I guess just bug local Maven gurus to find out what's wrong here ;-) I'm still trying to get to grips with Maven and this sort of thing is very frustrating ;-) I understand you. Since I'm now sure that's a problem of Cocoon and not local configuration I'll investigate into this issue a little more. [1] http://thread.gmane.org/gmane.text.xml.cocoon.devel/77945 -- Grzegorz Kossakowski - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ApplicationContext from sitemap component?
Boris Goldowsky pisze: So the archetype demos make it clear that from flowscript you can look up a Spring bean with cocoon.getComponent(name), but what is the recommended method for looking one up from inside a Transformer or other sitemap component? The recommended way is to have sitemap component as a Spring bean and use Dependency Injection for getting all dependencies resolved. -- Grzegorz Kossakowski - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problem with document() function
Jo,
Maybe you can work from the below example.
Example:
COB-INF/
content/
doc.xml
additional.xml
transforms/
example_document_func.xsl
sitemap.xmap
sitemap.xmap:
.
map:pipeline
map:match pattern=test-doc/
map:generate src=content/doc.xml/
map:transform
src=transforms/example_document_func.xsl/
map:serialize type=xml/
/map:match
/map:pipeline
.
doc.xml:
--
?xml version=1.0 encoding=UTF-8?
root
something
blah/
/something
insertdochere/
/root
Additional.xml:
?xml version=1.0 encoding=UTF-8?
frag
textbalh/text
/frag
example_document_func.xsl:
---
?xml version=1.0 encoding=UTF-8?
xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
version=1.0
xsl:param name=filename select='../content/additional.xml'/
xsl:template match=/root
root
xsl:for-each select=./*
xsl:choose
xsl:when test=name(.) = 'insertdochere'
xsl:copy-of select=document($filename) /
/xsl:when
xsl:otherwise
xsl:copy-of select=./
/xsl:otherwise
/xsl:choose
/xsl:for-each
/root
/xsl:template
/xsl:stylesheet
Call my block:
http://localhost:/blockname-mapping/test-doc/
results:
?xml version=1.0 encoding=UTF-8?
root
something
blah/
/something
frag
textbalh/text
/frag
/root
/dom
-Original Message-
From: Lehtonen, Mika [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 16:36
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Maybe you could wrote a pipeline with a matcher to your $filename and
with source pointing to your absolute file?
- mika -
Heather Rankin kirjoitti:
Johannes, If you don't like absolute paths then you just need to
figure out where your XSLT is relative to your XML doc. If your XSL is
in say, 'COB-INF/resource/internal/sql/transformation' you'll need
'../resource/internal/sql/configuration/filename' (with file extension
of course).
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 15:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Go away with absolute paths
Lehtonen, Mika schrieb:
Hi Johannes,
maybe you could try absolute path like:
* UNIX ... file:///foo/bar/this.xsl
* Windows ... file:///C:/foo/bar/this.xsl
Just to make sure that the file is fetched from the right location.
- mika -
Johannes Hoechstaedter kirjoitti:
The value of the variable $filename is correct, because I use this
variable three times in the same stylesheet within xi:include
statements, and it works. So the output of xsl:value-of
select=$filename / is correct. The output of xsl:value-of
select=document($filename)/* / is empty, and I get no error. Just
an empty value, where should be a value.
The file is located in
COB-INF/resource/internal/sql/configuration,
and I access it by resource/internal/sql/configuration/filename. I
think it is correct or?.
Heather Rankin schrieb:
Hi Johannes,
Well firstly if you're using a variable to store your filename you
shouldn't need quotes around it. Should just be xsl:value-of
select=document($filename)/NodeA/NodeB/NodeC /
If that doesn't work it could be a problem with the path to your
file or the path to your nodes. The XML needs to be well formed,
but
if you're not getting an error then that shouldn't be a factor. I'd
make sure the file path is correct by trying to output everything
in
the file xsl:value-of select=document($filename)/* / or use
doc-available to tell you.
According to your XML input your xpath looks ok (assuming first
/NodeB is NodeB).
Heather
-Original Message-
From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED]
Sent: 11 June 2008 14:58
To: users@cocoon.apache.org
Subject: Re: problem with document() function
Hi Heather,
yes I thought the same. Thats what I tried, only to test the
document()
function:
xsl:value-of select=document('$filename')/NodeA/NodeB/NodeC /
but I got no output. When I insert xsl:value-of
select=doc-available('$filename') / for example, nothing works
anymore :)
The content of $filename is correct.
The xml structure of the file is:
NodeA
/NodeB NodeC
text
/NodeC /NodeB
/NodeA
Could it be still a path issue?
Heather Rankin schrieb:
Hi Johannes,
You should be able to use the document() function to interrogate
the contents
Re: C22 - Maven artifact missing
Grzegorz Kossakowski wrote: David, you are the second person reporting this issue, the first one was Alexander[1] so there must be an issue with Cocoon dependencies here. I noticed that thread already thanks, but as it didn't conclude I wondered if it had been resolved. Since I'm now sure that's a problem of Cocoon and not local configuration I'll investigate into this issue a little more. Thanks Grek. If it's any help I tried this under Win XP SP2, with Maven 2.0.9 and JDK 1.6.0_02 Regards, David Legg [1] http://thread.gmane.org/gmane.text.xml.cocoon.devel/77945 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ApplicationContext from sitemap component?
Ah, I did not realize you could set up sitemap components as Spring beans -- I had been defining them the Cocoon 2.1 way, in a map:components element in the sitemap. Is there an example somewhere of how to set them up via Spring? Bng On Wed, 2008-06-11 at 18:02 +0200, Grzegorz Kossakowski wrote: Boris Goldowsky pisze: So the archetype demos make it clear that from flowscript you can look up a Spring bean with cocoon.getComponent(name), but what is the recommended method for looking one up from inside a Transformer or other sitemap component? The recommended way is to have sitemap component as a Spring bean and use Dependency Injection for getting all dependencies resolved. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: C22 - Maven artifact missing
Grzegorz Kossakowski wrote: Skipping test phase is not a good idea anymore and docs need an update (I've done it already). Anyway, this flag shouldn't make the build fail. Would you believe it! I tried it without the -Dmaven.test.skip=true flag and it passed all the tests and completed the build :-) I suspect that an artifact created as a result of the tests is a required dependency somewhere. Regards, David Legg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cocoon Form with Ajax
I have ONE page, in which the user can select from a folding tree (it folds using ajax). Once opened in the browser, no new page is opened nor refreshed. All the changes in the page are done with ajax. Ok! When someone clicks on an 'end item' from the tree, in the same page a DIV/-BLOCK will appear (using ajax). The problem is: I want to have a cocoon form in this DIV/-BLOCK. Is this possible? (So I do not want to open a new page with f.i. continuations..) Does someone have an idea? Or an example? Thanks and greetings! -- View this message in context: http://www.nabble.com/Cocoon-Form-with-Ajax-tp17783473p17783473.html Sent from the Cocoon - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: C22 - Maven artifact missing
David Legg pisze: Grzegorz Kossakowski wrote: Skipping test phase is not a good idea anymore and docs need an update (I've done it already). Anyway, this flag shouldn't make the build fail. Would you believe it! I tried it without the -Dmaven.test.skip=true flag and it passed all the tests and completed the build :-) I suspect that an artifact created as a result of the tests is a required dependency somewhere. I've got exactly the same result as you. The missing dependency is included in your previous mail: Missing: -- 1) org.apache.cocoon:cocoon-pipeline-impl:test-jar:tests:1.1.0-SNAPSHOT Try downloading the file manually from the project website. ... Path to dependency: 1) org.apache.cocoon:cocoon-pipeline-components:jar:1.1.0-SNAPSHOT 2) org.apache.cocoon:cocoon-pipeline-impl:test-jar:tests:1.1.0-SNAPSHOT So cocoon-pipeline-components depend on cocoon-pipeline-impl:test-jar and that's not a suprise: dependency groupIdorg.apache.cocoon/groupId artifactIdcocoon-pipeline-impl/artifactId typetest-jar/type scopetest/scope /dependency (taken from pom.xml of cocoon-pipeline-components) The crucial fragment is scope that declares this dependency as a test one so Maven should not try to obtain it when tests compiling and running is disabled. I don't have an idea why it behaves differently. Maybe it's another bug in Maven that we have found here? -- Grzegorz Kossakowski - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cocoon and Cometd
Hi, next to my current Dojo 1.1 integration project, I am currently working on a Tomcat NOI Servlet, which implements the Bayeux Protocol in version 1.0 utilizing Tomcat 5 Non Blocking IO features. This is working nicely with the Dojo frameworks cometd client. After implementing an IFrame based streaming transport for this, my work on this would be finished. I was thinking on integrating this Comet Service into Cocoon and just wanted to ask if there is anybody working on this too. Maybe we could combine our efforts. Regards, Chris [ C h r i s t o f e r D u t z ] C-Ware IT-Service Inhaber Dipl. Inf. Christofer Dutz Karlstraße. 104, 64285 Darmstadt fon: 0 61 51 / 27315 - 61 fax: 0 61 51 / 27315 - 64 mobil: 0171 / 7 444 2 33 email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.c-ware.de/ http://www.c-ware.de FA Darmstadt: 07 813 60581
Re: Cocoon in Eclipse??
I guess I am not expressing my question correct. I think basically what I need to know is what the web.xml-file should look like to configure the CocoonServlet and perhaps the 'cocoon.xconf'-file if this is needed as well. Where is this described in the documentation? Is everybody just guessing? :-) I am not able to find this information anywhere. Can anyone please point to this? Thanks -- View this message in context: http://www.nabble.com/Cocoon-in-Eclipse---tp17720458p17787698.html Sent from the Cocoon - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: C22 - Maven artifact missing
Grzegorz Kossakowski wrote: I don't have an idea why it behaves differently. Maybe it's another bug in Maven that we have found here? I think it's a conspiracy to always make us run regression tests ;-) Thanks for updating the web site. David. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
