Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Well, it made mine! Thanks Luca. PS. Any reason the pointer for the Fins schema in the FAQ does not link to the on-line version: http://svn.cocoondev.org/viewsvn/trunk/fins/fins-core/src/main/resources/COB-INF/schema/?root=fins On 2008/06/25 at 07:44, in message [EMAIL PROTECTED], Luca Morandini [EMAIL PROTECTED] wrote: I hope this will make the day for a few people :) http://www.lucamorandini.it/fins/faq.html Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
And a very stupid question - where is the link for the download? the ViewVC site seems to allow you to browse display files - but how does one get all of them at once? On 2008/06/25 at 07:44, in message [EMAIL PROTECTED], Luca Morandini [EMAIL PROTECTED] wrote: I hope this will make the day for a few people :) http://www.lucamorandini.it/fins/faq.html Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Derek Hohls wrote: And a very stupid question - where is the link for the download? the ViewVC site seems to allow you to browse display files - but how does one get all of them at once? You should get hold of an SVN client and issue something like: svn checkout http://svn.cocoondev.org/repos/fins/trunk fins Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Derek Hohls wrote: Well, it made mine! Thanks Luca. PS. Any reason the pointer for the Fins schema in the FAQ does not link to the on-line version: http://svn.cocoondev.org/viewsvn/trunk/fins/fins-core/src/main/resources/COB-INF/schema/?root=fins Hmmm... I think it works, just click on the View link. Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Sorry, I was not too clear here. I was suggesting that the plain text src/main/resources/COB-INF/schema/ in the FAQ be converted to a hyperlink to point to that URL. On 2008/06/25 at 08:44, in message [EMAIL PROTECTED], Luca Morandini [EMAIL PROTECTED] wrote: Derek Hohls wrote: Well, it made mine! Thanks Luca. PS. Any reason the pointer for the Fins schema in the FAQ does not link to the on-line version: http://svn.cocoondev.org/viewsvn/trunk/fins/fins-core/src/main/resources/COB-INF/schema/?root=fins Hmmm... I think it works, just click on the View link. Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: well formatted xhtml code
Then it's defined in a parent sitemap. On [1] you can find the configuration when org.apache.cocoon.serialization.XMLSerializer is used for XHTML. There is an (undocumented) parameter for this serializer: indentyes/indent (or no if you want it as one line,. So you will have something like map:sitemap map:components map:serializers !-- here go all your serializer definitions -- /map:serializers /map:components /map:sitemap [1] http://cocoon.apache.org/2.1/userdocs/xhtml-serializer.html Regards, Jasha Joachimsthal www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646 -Original Message- From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: dinsdag 24 juni 2008 17:40 To: users@cocoon.apache.org Subject: Re: well formatted xhtml code There are no serializers. Jasha Joachimsthal schrieb: Hi Johannes, Which class is used for the XHTML serialization (it's in map:components/map:serializers)? Jasha Joachimsthal www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646 -Original Message- From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: dinsdag 24 juni 2008 16:50 To: users@cocoon.apache.org Subject: well formatted xhtml code Hi, when I serialize my output into html, cocoon produces well readable html source code. But when I switch to xhtml, then it puts everything in one line. Is this changeable? cheers, Johannes - 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: well formatted xhtml code
ok, thank you. It woks. cheers Johannes Jasha Joachimsthal schrieb: Then it's defined in a parent sitemap. On [1] you can find the configuration when org.apache.cocoon.serialization.XMLSerializer is used for XHTML. There is an (undocumented) parameter for this serializer: indentyes/indent (or no if you want it as one line,. So you will have something like map:sitemap map:components map:serializers !-- here go all your serializer definitions -- /map:serializers /map:components /map:sitemap [1] http://cocoon.apache.org/2.1/userdocs/xhtml-serializer.html Regards, Jasha Joachimsthal www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646 -Original Message- From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: dinsdag 24 juni 2008 17:40 To: users@cocoon.apache.org Subject: Re: well formatted xhtml code There are no serializers. Jasha Joachimsthal schrieb: Hi Johannes, Which class is used for the XHTML serialization (it's in map:components/map:serializers)? Jasha Joachimsthal www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646 -Original Message- From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: dinsdag 24 juni 2008 16:50 To: users@cocoon.apache.org Subject: well formatted xhtml code Hi, when I serialize my output into html, cocoon produces well readable html source code. But when I switch to xhtml, then it puts everything in one line. Is this changeable? cheers, Johannes - 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: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Luca I am struggling to do this - have tried two clients so far... I know this is really not your problem, but does ViewVC really not have a download all for the source code - seems quite strange? Derek On 2008/06/25 at 08:44, in message [EMAIL PROTECTED], Luca Morandini [EMAIL PROTECTED] wrote: Derek Hohls wrote: And a very stupid question - where is the link for the download? the ViewVC site seems to allow you to browse display files - but how does one get all of them at once? You should get hold of an SVN client and issue something like: svn checkout http://svn.cocoondev.org/repos/fins/trunk fins Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.
i18n in JX Template
In my JX Template i've created a system to display menues. c:menu c:menuelement title=menu.topic link=admin/emner/ i18n:attr=title/ c:menuelement title=menu.resource link=admin/ressurser/ i18n:attr=title/ c:menuelement title=menu.user link=admin/brukere/ i18n:attr=title/ c:menuelement title=menu.publisher link=admin/utgivere/ i18n:attr=title/ c:menuelement title=menu.link link=admin/lenkesjekk/ i18n:attr=title/ c:menuelement title=menu.database link=admin/database/ i18n:attr=title/ /c:menu And I've tried to i18n the menus using the syntax above, but it shows as Menu.topic Menu.resource Menu.user Menu.publisher Menu.link Menu.database when the HTML is transformed. How do I fix this? IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Derek Hohls wrote: Luca I am struggling to do this - have tried two clients so far... Strange, usually SVN clients work like a charm. I would advise you to try harder, since SVN is so widely popular you will many occasions to use it in the future. I know this is really not your problem, but does ViewVC really not have a download all for the source code - seems quite strange? Apologies, but I cannot be of any assistance on this. Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
some words about property configuration
Hi, I want to have some infomations about configuration of cocoon by property files. The documentation on http://cocoon.apache.org/2.2/core-modules/core/2.2/1261_1_1.html seems to be not up to date. Can you please point out a place where I can find some updated documentation? Johannes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Derek Hohls wrote: Sorry, I was not too clear here. I was suggesting that the plain text src/main/resources/COB-INF/schema/ in the FAQ be converted to a hyperlink to point to that URL. Well, that's was not meant to be a link, just an indication on were the file is in the source tree... anyway, I've added a link to make it more user-friendly. Regards, Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Luca Perhaps its the URL. I am currently using RapidSVN. I added a bookmark for Pebble - https://pebble.svn.sourceforge.net/svnroot/pebble and it worked just fine... But when I use : http://svn.cocoondev.org/repos/fins/trunk I get an error - Error: Error while updating filelist (PROPFIND request failed on '/repos/fins/trunk' PROPFIND of '/repos/fins/trunk': could not connect to server (http://svn.cocoondev.org)) Have I used the correct path? On 2008/06/25 at 10:42, in message [EMAIL PROTECTED], Luca Morandini [EMAIL PROTECTED] wrote: Derek Hohls wrote: I am struggling to do this - have tried two clients so far... Strange, usually SVN clients work like a charm. I would advise you to try harder, since SVN is so widely popular you will many occasions to use it in the future. -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Derek Hohls wrote: Luca Perhaps its the URL. I am currently using RapidSVN. I added a bookmark for Pebble - https://pebble.svn.sourceforge.net/svnroot/pebble and it worked just fine... But when I use : http://svn.cocoondev.org/repos/fins/trunk I get an error - Error: Error while updating filelist (PROPFIND request failed on '/repos/fins/trunk' PROPFIND of '/repos/fins/trunk': could not connect to server (http://svn.cocoondev.org)) Have I used the correct path? Yes, that's the correct one: just tried a checkout with the Linux SVN client, version 1.4.6. Luca Morandini www.lucamorandini.it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN]: Fins 1.0 back-ported to Cocoon 2.1
Hi Lately svn released a new version (I think 1.5). Could it be that cocoondev uses the latest svn version and RapidSVN isn't up to date yet? Just an idea ... Felix Luca Perhaps its the URL. I am currently using RapidSVN. I added a bookmark for Pebble - https://pebble.svn.sourceforge.net/svnroot/pebble and it worked just fine... But when I use : http://svn.cocoondev.org/repos/fins/trunk I get an error - Error: Error while updating filelist (PROPFIND request failed on '/repos/fins/trunk' PROPFIND of '/repos/fins/trunk': could not connect to server (http://svn.cocoondev.org)) Have I used the correct path? On 2008/06/25 at 10:42, in message [EMAIL PROTECTED], Luca Morandini [EMAIL PROTECTED] wrote: Derek Hohls wrote: I am struggling to do this - have tried two clients so far... Strange, usually SVN clients work like a charm. I would advise you to try harder, since SVN is so widely popular you will many occasions to use it in the future. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: i18n in JX Template
Hi Magnus, everything seems to be ok. Did you try turning on the logger of the i18n transformer to see what might be wrong? Regards, Jeroen Reijn Magnus Haraldsen Amundsen wrote: In my JX Template i’ve created a system to display menues. c:menu c:menuelement title=”menu.topic link=admin/emner/ i18n:attr=title/ c:menuelement title=menu.resource link=admin/ressurser/ i18n:attr=title/ c:menuelement title=menu.user link=admin/brukere/ i18n:attr=title/ c:menuelement title=menu.publisher link=admin/utgivere/ i18n:attr=title/ c:menuelement title=menu.link link=admin/lenkesjekk/ i18n:attr=title/ c:menuelement title=menu.database link=admin/database/ i18n:attr=title/ /c:menu And I’ve tried to i18n the menus using the syntax above, but it shows as Menu.topic Menu.resource Menu.user Menu.publisher Menu.link Menu.database when the HTML is transformed. How do I fix this? IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: i18n in JX Template
Hi Jeroen, How do I enable logging on the i18nTransformer? -Original Message- From: Jeroen Reijn [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 11:06 To: users@cocoon.apache.org Subject: Re: i18n in JX Template Hi Magnus, everything seems to be ok. Did you try turning on the logger of the i18n transformer to see what might be wrong? Regards, Jeroen Reijn Magnus Haraldsen Amundsen wrote: In my JX Template i've created a system to display menues. c:menu c:menuelement title=menu.topic link=admin/emner/ i18n:attr=title/ c:menuelement title=menu.resource link=admin/ressurser/ i18n:attr=title/ c:menuelement title=menu.user link=admin/brukere/ i18n:attr=title/ c:menuelement title=menu.publisher link=admin/utgivere/ i18n:attr=title/ c:menuelement title=menu.link link=admin/lenkesjekk/ i18n:attr=title/ c:menuelement title=menu.database link=admin/database/ i18n:attr=title/ /c:menu And I've tried to i18n the menus using the syntax above, but it shows as Menu.topic Menu.resource Menu.user Menu.publisher Menu.link Menu.database when the HTML is transformed. How do I fix this? IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: some words about property configuration
Johannes, until someone with real knowledge comes along I think the Cocoon 2.2 way of configuring a project is to use the Spring Configurator [1]. In particular you should look at the property handling page [2]. It looks scary to me ;-) David Legg Johannes Hoechstaedter wrote: Hi, I want to have some infomations about configuration of cocoon by property files. The documentation on http://cocoon.apache.org/2.2/core-modules/core/2.2/1261_1_1.html seems to be not up to date. Can you please point out a place where I can find some updated documentation? [1] http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/1.0/1304_1_1.html [2] http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/1.0/1310_1_1.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: i18n in JX Template
2008/6/25 Magnus Haraldsen Amundsen [EMAIL PROTECTED]: In my JX Template i've created a system to display menues. c:menu c:menuelement title=menu.topic link=admin/emner/ i18n:attr=title/ ... but it shows as Menu.topic ... How do I fix this? Given that your tokens are all lower case but the output has a leading capital letter, it seems to me that either they *are* being substituted (and your catalog has menu.topic=Menu.topic etc.), or something else is altering the title attributes (to capitalise them) before the i18n transformer sees them and they aren't translated as the transformer is probably case sensitive as regards the key names (so it no longer thinks they match the keys in the catalog). Or were the capital letters introduced by your mail client and the original output is also lower case? One other thought - is the i18n namespace declared correctly in your template file? Perhaps the transformer isn't recognising the i18n:attr attributes, so doesn't think it needs to do anything with the titles. Andy -- http://pseudoq.sourceforge.net/ Open source java sudoku solver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: i18n in JX Template
The upper case was because of Outlook. The namespace is correct, and it works when the i18n:attr is used in the XSLT, but not in the JX Template. -Original Message- From: Andy Stevens [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 11:37 To: users@cocoon.apache.org Subject: Re: i18n in JX Template 2008/6/25 Magnus Haraldsen Amundsen [EMAIL PROTECTED]: In my JX Template i've created a system to display menues. c:menu c:menuelement title=menu.topic link=admin/emner/ i18n:attr=title/ ... but it shows as Menu.topic ... How do I fix this? Given that your tokens are all lower case but the output has a leading capital letter, it seems to me that either they *are* being substituted (and your catalog has menu.topic=Menu.topic etc.), or something else is altering the title attributes (to capitalise them) before the i18n transformer sees them and they aren't translated as the transformer is probably case sensitive as regards the key names (so it no longer thinks they match the keys in the catalog). Or were the capital letters introduced by your mail client and the original output is also lower case? One other thought - is the i18n namespace declared correctly in your template file? Perhaps the transformer isn't recognising the i18n:attr attributes, so doesn't think it needs to do anything with the titles. Andy -- http://pseudoq.sourceforge.net/ Open source java sudoku solver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: some words about property configuration
I use properties to configure my database connection.
In my block application context I have:
bean id=myDataSource
class=org.apache.commons.dbcp.BasicDataSource destroy-method=close
property name=driverClassName
value${myDatabase.driverClassName}/value
/property
property name=url
value${myDatabase.url}/value
/property
property name=username
value${myDatabase.username}/value
/property
property name=password
value${myDatabase.password}/value
/property
/bean
My properties are defined in cocoon/properties/application.properties
file in my application src/main/webapp/WEB-INF and in block
rcl.properties file for development environment:
myDatabase.driverClassName=com.mysql.jdbc.Driver
myDatabase.url=jdbc:mysql://localhost:3307/dbname?
useUnicode=trueamp;characterEncoding=utf8amp;autoReconnect=true
myDatabase.username=dbuser
myDatabase.password=dbpassword
Barbara
On 25 Jun, 2008, at 9:44 am, Johannes Hoechstaedter wrote:
Hi,
I want to have some infomations about configuration of cocoon by
property files. The documentation on http://cocoon.apache.org/2.2/
core-modules/core/2.2/1261_1_1.html seems to be not up to date. Can
you please point out a place where I can find some updated
documentation?
Johannes
-
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: some words about property configuration
Nice. :) It works. Thank you.
Johannes
Barbara Slupik schrieb:
I use properties to configure my database connection.
In my block application context I have:
bean id=myDataSource
class=org.apache.commons.dbcp.BasicDataSource destroy-method=close
property name=driverClassName
value${myDatabase.driverClassName}/value
/property
property name=url
value${myDatabase.url}/value
/property
property name=username
value${myDatabase.username}/value
/property
property name=password
value${myDatabase.password}/value
/property
/bean
My properties are defined in cocoon/properties/application.properties
file in my application src/main/webapp/WEB-INF and in block
rcl.properties file for development environment:
myDatabase.driverClassName=com.mysql.jdbc.Driver
myDatabase.url=jdbc:mysql://localhost:3307/dbname?useUnicode=trueamp;characterEncoding=utf8amp;autoReconnect=true
myDatabase.username=dbuser
myDatabase.password=dbpassword
Barbara
On 25 Jun, 2008, at 9:44 am, Johannes Hoechstaedter wrote:
Hi,
I want to have some infomations about configuration of cocoon by
property files. The documentation on
http://cocoon.apache.org/2.2/core-modules/core/2.2/1261_1_1.html
seems to be not up to date. Can you please point out a place where I
can find some updated documentation?
Johannes
-
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: i18n in JX Template
Does anyone have any ideas? I'm really stuck on this and my SCRUM-task won't budge until it's solved ;) -Original Message- From: Magnus Haraldsen Amundsen [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 12:06 To: users@cocoon.apache.org Subject: RE: i18n in JX Template The upper case was because of Outlook. The namespace is correct, and it works when the i18n:attr is used in the XSLT, but not in the JX Template. -Original Message- From: Andy Stevens [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 11:37 To: users@cocoon.apache.org Subject: Re: i18n in JX Template 2008/6/25 Magnus Haraldsen Amundsen [EMAIL PROTECTED]: In my JX Template i've created a system to display menues. c:menu c:menuelement title=menu.topic link=admin/emner/ i18n:attr=title/ ... but it shows as Menu.topic ... How do I fix this? Given that your tokens are all lower case but the output has a leading capital letter, it seems to me that either they *are* being substituted (and your catalog has menu.topic=Menu.topic etc.), or something else is altering the title attributes (to capitalise them) before the i18n transformer sees them and they aren't translated as the transformer is probably case sensitive as regards the key names (so it no longer thinks they match the keys in the catalog). Or were the capital letters introduced by your mail client and the original output is also lower case? One other thought - is the i18n namespace declared correctly in your template file? Perhaps the transformer isn't recognising the i18n:attr attributes, so doesn't think it needs to do anything with the titles. Andy -- http://pseudoq.sourceforge.net/ Open source java sudoku solver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: i18n in JX Template
Magnus, i'm not sure which cocoon versiom you are using, but in case you are using 2.1, try setting the loglevel for the i18n transformer to DEBUG. You can figure out what the logger is for your transformer by looking at the logger attribute of the i18n transformer definition. map:transformer name=i18n src=org.apache.cocoon.transformation.I18nTransformer logger=sitemap.transformer.i18n Now in my logkit.xconf there is a category named: category log-level=WARN name=sitemap log-target id-ref=sitemap/ log-target id-ref=error/ /category It may or may not contain additional nested categories. In your case you want to add a new nested category. category log-level=WARN name=sitemap log-target id-ref=sitemap/ log-target id-ref=error/ category log-level=WARN name=transformer.i18n log-target id-ref=sitemap/ log-target id-ref=error/ /category /category The name is the interesting part here. It should match the logger specified in your transformer configuration. Regards, Jeroen Magnus Haraldsen Amundsen wrote: Does anyone have any ideas? I'm really stuck on this and my SCRUM-task won't budge until it's solved ;) -Original Message- From: Magnus Haraldsen Amundsen [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 12:06 To: users@cocoon.apache.org Subject: RE: i18n in JX Template The upper case was because of Outlook. The namespace is correct, and it works when the i18n:attr is used in the XSLT, but not in the JX Template. -Original Message- From: Andy Stevens [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 11:37 To: users@cocoon.apache.org Subject: Re: i18n in JX Template 2008/6/25 Magnus Haraldsen Amundsen [EMAIL PROTECTED]: In my JX Template i've created a system to display menues. c:menu c:menuelement title=menu.topic link=admin/emner/ i18n:attr=title/ ... but it shows as Menu.topic ... How do I fix this? Given that your tokens are all lower case but the output has a leading capital letter, it seems to me that either they *are* being substituted (and your catalog has menu.topic=Menu.topic etc.), or something else is altering the title attributes (to capitalise them) before the i18n transformer sees them and they aren't translated as the transformer is probably case sensitive as regards the key names (so it no longer thinks they match the keys in the catalog). Or were the capital letters introduced by your mail client and the original output is also lower case? One other thought - is the i18n namespace declared correctly in your template file? Perhaps the transformer isn't recognising the i18n:attr attributes, so doesn't think it needs to do anything with the titles. Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: i18n in JX Template
Hi, It might help if you also posted snippets from your sitemap to show: 1. The pipeline handling the display of the JX template. 2. map:transformer/ element that defines the i18n transformer configuration. Robin On 25 Jun 2008, at 13:46, Magnus Haraldsen Amundsen wrote: Does anyone have any ideas? I'm really stuck on this and my SCRUM-task won't budge until it's solved ;) -Original Message- From: Magnus Haraldsen Amundsen [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 12:06 To: users@cocoon.apache.org Subject: RE: i18n in JX Template The upper case was because of Outlook. The namespace is correct, and it works when the i18n:attr is used in the XSLT, but not in the JX Template. -Original Message- From: Andy Stevens [mailto:[EMAIL PROTECTED] Sent: 25. juni 2008 11:37 To: users@cocoon.apache.org Subject: Re: i18n in JX Template 2008/6/25 Magnus Haraldsen Amundsen [EMAIL PROTECTED]: In my JX Template i've created a system to display menues. c:menu c:menuelement title=menu.topic link=admin/emner/ i18n:attr=title/ ... but it shows as Menu.topic ... How do I fix this? Given that your tokens are all lower case but the output has a leading capital letter, it seems to me that either they *are* being substituted (and your catalog has menu.topic=Menu.topic etc.), or something else is altering the title attributes (to capitalise them) before the i18n transformer sees them and they aren't translated as the transformer is probably case sensitive as regards the key names (so it no longer thinks they match the keys in the catalog). Or were the capital letters introduced by your mail client and the original output is also lower case? One other thought - is the i18n namespace declared correctly in your template file? Perhaps the transformer isn't recognising the i18n:attr attributes, so doesn't think it needs to do anything with the titles. Andy -- http://pseudoq.sourceforge.net/ Open source java sudoku solver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] IMPORTANT NOTICE: This message may contain confidential information. If you have received this e-mail in error, do not use, copy or distribute it. Do not open any attachments. Delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
RE: i18n in JX Template
Sitemap:
We have 2 sitemaps, one for the app and one for skins
From the sitemap-app
map:match pattern=xml2/*
map:generate src=templates/{1}.jx.xml type=jx/
map:serialize type=servletService
map:parameter name=service value=servlet:skin:/admin-styling/
/map:serialize
/map:match
Which uses from the sitemap-skin
map:match pattern=admin-styling
map:act type=locale
map:generate src=service-consumer:/
map:transform src=transform/admin-styling.xslt
map:parameter name=baseurl value={request:contextPath}/
map:parameter name=locale value={language}/
/map:transform
map:transform type=i18n
map:parameter name=locale value={language}/
/map:transform
map:serialize type=xhtml/
/map:act
/map:match
Where the i18nTransformer is configured as follows
map:components
map:transformers
map:transformer name=i18n
src=org.apache.cocoon.transformation.I18nTransformer
catalogues default=messages
catalogue id=messages name=messages location=translations
/
/catalogues
/map:transformer
/map:transformers
/map:components
-Original Message-
From: Robin Wyles [mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 14:56
To: users@cocoon.apache.org
Subject: Re: i18n in JX Template
Hi,
It might help if you also posted snippets from your sitemap to show:
1. The pipeline handling the display of the JX template.
2. map:transformer/ element that defines the i18n transformer
configuration.
Robin
On 25 Jun 2008, at 13:46, Magnus Haraldsen Amundsen wrote:
Does anyone have any ideas? I'm really stuck on this and my SCRUM-task
won't budge until it's solved ;)
-Original Message-
From: Magnus Haraldsen Amundsen
[mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 12:06
To: users@cocoon.apache.org
Subject: RE: i18n in JX Template
The upper case was because of Outlook.
The namespace is correct, and it works when the i18n:attr is used
in the
XSLT, but not in the JX Template.
-Original Message-
From: Andy Stevens [mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 11:37
To: users@cocoon.apache.org
Subject: Re: i18n in JX Template
2008/6/25 Magnus Haraldsen Amundsen
[EMAIL PROTECTED]:
In my JX Template i've created a system to display menues.
c:menu
c:menuelement title=menu.topic link=admin/emner/
i18n:attr=title/
...
but it shows as
Menu.topic
...
How do I fix this?
Given that your tokens are all lower case but the output has a leading
capital letter, it seems to me that either they *are* being
substituted (and your catalog has menu.topic=Menu.topic etc.), or
something else is altering the title attributes (to capitalise them)
before the i18n transformer sees them and they aren't translated as
the transformer is probably case sensitive as regards the key names
(so it no longer thinks they match the keys in the catalog).
Or were the capital letters introduced by your mail client and the
original output is also lower case?
One other thought - is the i18n namespace declared correctly in your
template file? Perhaps the transformer isn't recognising the
i18n:attr attributes, so doesn't think it needs to do anything with
the titles.
Andy
--
http://pseudoq.sourceforge.net/ Open source java sudoku solver
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: i18n in JX Template
And we use Cocoon 2.2, but the 2.1 i18nTransformer (at least the
namespace) since we couldn't find any documentation for 2.2.
-Original Message-
From: Magnus Haraldsen Amundsen
[mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 15:09
To: users@cocoon.apache.org
Subject: RE: i18n in JX Template
Sitemap:
We have 2 sitemaps, one for the app and one for skins
From the sitemap-app
map:match pattern=xml2/*
map:generate src=templates/{1}.jx.xml type=jx/
map:serialize type=servletService
map:parameter name=service value=servlet:skin:/admin-styling/
/map:serialize
/map:match
Which uses from the sitemap-skin
map:match pattern=admin-styling
map:act type=locale
map:generate src=service-consumer:/
map:transform src=transform/admin-styling.xslt
map:parameter name=baseurl value={request:contextPath}/
map:parameter name=locale value={language}/
/map:transform
map:transform type=i18n
map:parameter name=locale value={language}/
/map:transform
map:serialize type=xhtml/
/map:act
/map:match
Where the i18nTransformer is configured as follows
map:components
map:transformers
map:transformer name=i18n
src=org.apache.cocoon.transformation.I18nTransformer
catalogues default=messages
catalogue id=messages name=messages location=translations
/
/catalogues
/map:transformer
/map:transformers
/map:components
-Original Message-
From: Robin Wyles [mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 14:56
To: users@cocoon.apache.org
Subject: Re: i18n in JX Template
Hi,
It might help if you also posted snippets from your sitemap to show:
1. The pipeline handling the display of the JX template.
2. map:transformer/ element that defines the i18n transformer
configuration.
Robin
On 25 Jun 2008, at 13:46, Magnus Haraldsen Amundsen wrote:
Does anyone have any ideas? I'm really stuck on this and my SCRUM-task
won't budge until it's solved ;)
-Original Message-
From: Magnus Haraldsen Amundsen
[mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 12:06
To: users@cocoon.apache.org
Subject: RE: i18n in JX Template
The upper case was because of Outlook.
The namespace is correct, and it works when the i18n:attr is used
in the
XSLT, but not in the JX Template.
-Original Message-
From: Andy Stevens [mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 11:37
To: users@cocoon.apache.org
Subject: Re: i18n in JX Template
2008/6/25 Magnus Haraldsen Amundsen
[EMAIL PROTECTED]:
In my JX Template i've created a system to display menues.
c:menu
c:menuelement title=menu.topic link=admin/emner/
i18n:attr=title/
...
but it shows as
Menu.topic
...
How do I fix this?
Given that your tokens are all lower case but the output has a leading
capital letter, it seems to me that either they *are* being
substituted (and your catalog has menu.topic=Menu.topic etc.), or
something else is altering the title attributes (to capitalise them)
before the i18n transformer sees them and they aren't translated as
the transformer is probably case sensitive as regards the key names
(so it no longer thinks they match the keys in the catalog).
Or were the capital letters introduced by your mail client and the
original output is also lower case?
One other thought - is the i18n namespace declared correctly in your
template file? Perhaps the transformer isn't recognising the
i18n:attr attributes, so doesn't think it needs to do anything with
the titles.
Andy
--
http://pseudoq.sourceforge.net/ Open source java sudoku solver
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
RE: i18n in JX Template
I added a i18nTransform before the XSLT transform, just for the fun of
it, and then the menus is translated correctly.
-Original Message-
From: Magnus Haraldsen Amundsen
[mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 15:15
To: users@cocoon.apache.org
Subject: RE: i18n in JX Template
And we use Cocoon 2.2, but the 2.1 i18nTransformer (at least the
namespace) since we couldn't find any documentation for 2.2.
-Original Message-
From: Magnus Haraldsen Amundsen
[mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 15:09
To: users@cocoon.apache.org
Subject: RE: i18n in JX Template
Sitemap:
We have 2 sitemaps, one for the app and one for skins
From the sitemap-app
map:match pattern=xml2/*
map:generate src=templates/{1}.jx.xml type=jx/
map:serialize type=servletService
map:parameter name=service value=servlet:skin:/admin-styling/
/map:serialize
/map:match
Which uses from the sitemap-skin
map:match pattern=admin-styling
map:act type=locale
map:generate src=service-consumer:/
map:transform src=transform/admin-styling.xslt
map:parameter name=baseurl value={request:contextPath}/
map:parameter name=locale value={language}/
/map:transform
map:transform type=i18n
map:parameter name=locale value={language}/
/map:transform
map:serialize type=xhtml/
/map:act
/map:match
Where the i18nTransformer is configured as follows
map:components
map:transformers
map:transformer name=i18n
src=org.apache.cocoon.transformation.I18nTransformer
catalogues default=messages
catalogue id=messages name=messages location=translations
/
/catalogues
/map:transformer
/map:transformers
/map:components
-Original Message-
From: Robin Wyles [mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 14:56
To: users@cocoon.apache.org
Subject: Re: i18n in JX Template
Hi,
It might help if you also posted snippets from your sitemap to show:
1. The pipeline handling the display of the JX template.
2. map:transformer/ element that defines the i18n transformer
configuration.
Robin
On 25 Jun 2008, at 13:46, Magnus Haraldsen Amundsen wrote:
Does anyone have any ideas? I'm really stuck on this and my SCRUM-task
won't budge until it's solved ;)
-Original Message-
From: Magnus Haraldsen Amundsen
[mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 12:06
To: users@cocoon.apache.org
Subject: RE: i18n in JX Template
The upper case was because of Outlook.
The namespace is correct, and it works when the i18n:attr is used
in the
XSLT, but not in the JX Template.
-Original Message-
From: Andy Stevens [mailto:[EMAIL PROTECTED]
Sent: 25. juni 2008 11:37
To: users@cocoon.apache.org
Subject: Re: i18n in JX Template
2008/6/25 Magnus Haraldsen Amundsen
[EMAIL PROTECTED]:
In my JX Template i've created a system to display menues.
c:menu
c:menuelement title=menu.topic link=admin/emner/
i18n:attr=title/
...
but it shows as
Menu.topic
...
How do I fix this?
Given that your tokens are all lower case but the output has a leading
capital letter, it seems to me that either they *are* being
substituted (and your catalog has menu.topic=Menu.topic etc.), or
something else is altering the title attributes (to capitalise them)
before the i18n transformer sees them and they aren't translated as
the transformer is probably case sensitive as regards the key names
(so it no longer thinks they match the keys in the catalog).
Or were the capital letters introduced by your mail client and the
original output is also lower case?
One other thought - is the i18n namespace declared correctly in your
template file? Perhaps the transformer isn't recognising the
i18n:attr attributes, so doesn't think it needs to do anything with
the titles.
Andy
--
http://pseudoq.sourceforge.net/ Open source java sudoku solver
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT NOTICE:
This message may contain confidential information.
If you have received this e-mail in error, do not use, copy or
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you
have done so. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMPORTANT
Form base authentication in tomcat
Hi everybody, how can I etablixh a form based authentication in coconn running in tomcat? My web.xml login-config looks as follows: login-config auth-methodFORM/auth-method realm-nameExample Form-Based Authentication Area/realm-name form-login-config form-login-page/myBlock1/login/form-login-page form-error-page/myBlock1/login/form-error-page /form-login-config /login-config I have a match pattern in my sitemap for this: map:match pattern=login !-- init -- map:generate src=resource/internal/pageTemplate.xml / map:transform type=xslt src=resource/internal/transform2LoginForm.xsl / !-- html ouptut -- map:serialize type=xhtml/ /map:match Running this pattern in jetty works fine, and my login form is shown. But when I load my webapp into Tomcat and when I run it, Tomcat doesn't complain, too. I get no Error message as I am expecting. The thing is, that I get only an empty screen. Do anybody know something? cheers Johannes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form base authentication in tomcat
I had the same problem. I fixed it by adding: filter filter-namespringRequestContextFilter/filter-name filter-classorg.springframework.web.filter.RequestContextFilter/ filter-class /filter filter-mapping filter-namespringRequestContextFilter/filter-name url-pattern/*/url-pattern dispatcherFORWARD/dispatcher dispatcherREQUEST/dispatcher /filter-mapping to my application web.xml file. Barbara On 25 Jun, 2008, at 2:43 pm, Johannes Hoechstaedter wrote: Hi everybody, how can I etablixh a form based authentication in coconn running in tomcat? My web.xml login-config looks as follows: login-config auth-methodFORM/auth-method realm-nameExample Form-Based Authentication Area/realm-name form-login-config form-login-page/myBlock1/login/form-login-page form-error-page/myBlock1/login/form-error-page /form-login-config /login-config I have a match pattern in my sitemap for this: map:match pattern=login !-- init -- map:generate src=resource/internal/ pageTemplate.xml / map:transform type=xslt src=resource/internal/transform2LoginForm.xsl / !-- html ouptut -- map:serialize type=xhtml/ /map:match Running this pattern in jetty works fine, and my login form is shown. But when I load my webapp into Tomcat and when I run it, Tomcat doesn't complain, too. I get no Error message as I am expecting. The thing is, that I get only an empty screen. Do anybody know something? cheers Johannes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: i18n in JX Template
2008/6/25 Magnus Haraldsen Amundsen [EMAIL PROTECTED]: I added a i18nTransform before the XSLT transform, just for the fun of it, and then the menus is translated correctly. So what does the admin-styling XSLT do? Could it be interfering with the i18n namespace or stripping the i18n:attr attributes off the relevant elements? Andy. -- http://pseudoq.sourceforge.net/ Open source java sudoku application - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form base authentication in tomcat
YES !!! works ;) Barbara Slupik schrieb: I had the same problem. I fixed it by adding: filter filter-namespringRequestContextFilter/filter-name filter-classorg.springframework._web.filter.RequestContextFilter_ http://web.filter.RequestContextFilter//filter-class /filter filter-mapping filter-namespringRequestContextFilter/filter-name url-pattern/*/url-pattern dispatcherFORWARD/dispatcher dispatcherREQUEST/dispatcher /filter-mapping to my application _web.xml_ http://web.xml/ file. Barbara On 25 Jun, 2008, at 2:43 pm, Johannes Hoechstaedter wrote: Hi everybody, how can I etablixh a form based authentication in coconn running in tomcat? My web.xml http://web.xml login-config looks as follows: login-config auth-methodFORM/auth-method realm-nameExample Form-Based Authentication Area/realm-name form-login-config form-login-page/myBlock1/login/form-login-page form-error-page/myBlock1/login/form-error-page /form-login-config /login-config I have a match pattern in my sitemap for this: map:match pattern=login !-- init -- map:generate src=resource/internal/pageTemplate.xml / map:transform type=xslt src=resource/internal/transform2LoginForm.xsl / !-- html ouptut -- map:serialize type=xhtml/ /map:match Running this pattern in jetty works fine, and my login form is shown. But when I load my webapp into Tomcat and when I run it, Tomcat doesn't complain, too. I get no Error message as I am expecting. The thing is, that I get only an empty screen. Do anybody know something? cheers Johannes - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
load image with xslt in CocoonContext
hello Together
i have a problem to print image with xstl. both physical and relativ path don't
help me
my sitemap like :
map:match pattern=Doc_EntryForm_C.js
map:generate src=module:flow-attr:myXml/
map:transform type=xslt
src=context:/resources/stylesheets/v003_EntryForm.xslt
map:parameter name=filepath
value={flow-attribute:absolutePath} /
/map:transform
map:transform src=context:/resources/sources/saveFile.xsl
map:parameter name=serializer
value={flow-attribute:mediaType} /
map:parameter name=filepath
value={flow-attribute:path} /
map:parameter name=publish
value={flow-attribute:publish} /
map:parameter name=filename
value={flow-attribute:dateiname} /
/map:transform
map:transform type =savefiles/
map:serialize type=html/
/map:match
and in xslt :
src={concat('file:\\',$filepath,'\images\group.jpg')}
i need your help
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Odd Behavior with HSSFSerializer
I produced a simple Excel document by querying my database and using the HSSFSerializer. It's a simple document; the spreadsheet just formats the data into the same grid layout you would see on a database GUI upon submitting the query. Anyway, I realized that no matter the numerical data that goes into the HSSFSerializer, Excel defaults to outputting them with the trailing 0's cut off. (22.90 becomes 22.9.) I downloaded Gnumeric, formatted numbers to show 2 decimal places, saved the document to Gnumeric XML, and opened it to see what XML was needed to format the decimal properly. (I want all my numbers rounded to two decimal places.) Here is the XML I currently use in my stylesheet: xsl:when test=/page/title='MOU Alert' gmr:StyleRegion startCol=5 startRow=3 endCol=5 xsl:attribute name=endRow xsl:value-of select=count(/page/content/sql:rowset/sql:row)+3 / /xsl:attribute gmr:Style HAlign=1 VAlign=2 WrapText=0 ShrinkToFit=0 Rotation=0 Shade=0 Indent=0 Locked=1 Hidden=0 Fore=0:0:0 Back=:: PatternColor=0:0:0 Format=0.00 gmr:Font Unit=10 Bold=0 Italic=0 Underline=0 StrikeThrough=0 Script=0Arial/gmr:Font /gmr:Style /gmr:StyleRegion /xsl:when If you look at gmr:Style's Format attribute, this is the input that is needed to produce the correct decimal places. This specific snippet of code should round all data in Column 6 (Gnumeric starts counting at 0, so Col=5 is the sixth column) starting at row 3 and ending with the last row of data. If you look at the count function under xsl:attribute name=endRow, this returns the value 4500 from my particular test data. This dynamically tells what row to stop applying the formatting to. There is no way to specify unbounded for endRow, so this count function is the only way I can get it to apply the formatting to every row for any instance of data queried. Now here's the odd behavior. This code works perfectly when I query data that is a few hundred rows long. If there is, for example, 500 rows being queried the count function correctly returns 503, which is the last row I want formatted. (My data outputs on rows 3 to 503 to make room for a heading.) But when I query data from around 700 or so upward (I haven't found an exact cutoff yet), it will never apply the formatting. (All the numbers will have trailing 0's cut off and not rounded to two decimal places.) This is extremely irritating, and this will need to work for thousands of rows. If I simply replace the count fuction with a number like 250, it works. (Rows 3-253 are formatted properly, and the few thousand remaining are left unformatted.) If I start putting in values like 2000, 3500, 11480, it won't apply formatting to ANY row. It gives me the cold shoulder.:-O I was wondering if anyone ran has run into a similar problem and knows a fix. If I was ambiguous anywhere, just let me know and I'll clarify. Thanks, Matt -- View this message in context: http://www.nabble.com/Odd-Behavior-with-HSSFSerializer-tp18115088p18115088.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: Odd Behavior with HSSFSerializer
I had the same problem. I fixed it like this: !-- Style regions are built for each column for max 999 rows. Larger regions do not seem to work. That's why styles template is called more then once if number of rows to print exceedes 999. -- xsl:template name=styles xsl:param name=startRow/ xsl:param name=size/ xsl:variable name=endRow xsl:choose xsl:when test=($size - $startRow) gt; 999xsl:value-of select=$startRow + 998//xsl:when xsl:otherwisexsl:value-of select=$size//xsl:otherwise /xsl:choose /xsl:variable Styles StyleRegion ... xsl:attribute name=startRowxsl:value-of select=$startRow// xsl:attribute xsl:attribute name=endRowxsl:value-of select=$endRow// xsl:attribute Style ... ... /Style /StyleRegion ... /Styles xsl:if test=($size - $startRow) gt; 999 xsl:call-template name=styles xsl:with-param name=startRowxsl:value-of select=$startRow + 999//xsl:with-param xsl:with-param name=sizexsl:value-of select=$size// xsl:with-param /xsl:call-template /xsl:if /xsl:template The template is called for the first time with: xsl:call-template name=styles xsl:with-param name=startRow1/xsl:with-param xsl:with-param name=sizetotal-nr-of-elements/xsl:with-param /xsl:call-template Barbara On 25 Jun, 2008, at 4:21 pm, Matthew Monkan wrote: I produced a simple Excel document by querying my database and using the HSSFSerializer. It's a simple document; the spreadsheet just formats the data into the same grid layout you would see on a database GUI upon submitting the query. Anyway, I realized that no matter the numerical data that goes into the HSSFSerializer, Excel defaults to outputting them with the trailing 0's cut off. (22.90 becomes 22.9.) I downloaded Gnumeric, formatted numbers to show 2 decimal places, saved the document to Gnumeric XML, and opened it to see what XML was needed to format the decimal properly. (I want all my numbers rounded to two decimal places.) Here is the XML I currently use in my stylesheet: xsl:when test=/page/title='MOU Alert' gmr:StyleRegion startCol=5 startRow=3 endCol=5 xsl:attribute name=endRow xsl:value-of select=count(/page/content/sql:rowset/sql:row)+3 / /xsl:attribute gmr:Style HAlign=1 VAlign=2 WrapText=0 ShrinkToFit=0 Rotation=0 Shade=0 Indent=0 Locked=1 Hidden=0 Fore=0:0:0 Back=:: PatternColor=0:0:0 Format=0.00 gmr:Font Unit=10 Bold=0 Italic=0 Underline=0 StrikeThrough=0 Script=0Arial/gmr:Font /gmr:Style /gmr:StyleRegion /xsl:when If you look at gmr:Style's Format attribute, this is the input that is needed to produce the correct decimal places. This specific snippet of code should round all data in Column 6 (Gnumeric starts counting at 0, so Col=5 is the sixth column) starting at row 3 and ending with the last row of data. If you look at the count function under xsl:attribute name=endRow, this returns the value 4500 from my particular test data. This dynamically tells what row to stop applying the formatting to. There is no way to specify unbounded for endRow, so this count function is the only way I can get it to apply the formatting to every row for any instance of data queried. Now here's the odd behavior. This code works perfectly when I query data that is a few hundred rows long. If there is, for example, 500 rows being queried the count function correctly returns 503, which is the last row I want formatted. (My data outputs on rows 3 to 503 to make room for a heading.) But when I query data from around 700 or so upward (I haven't found an exact cutoff yet), it will never apply the formatting. (All the numbers will have trailing 0's cut off and not rounded to two decimal places.) This is extremely irritating, and this will need to work for thousands of rows. If I simply replace the count fuction with a number like 250, it works. (Rows 3-253 are formatted properly, and the few thousand remaining are left unformatted.) If I start putting in values like 2000, 3500, 11480, it won't apply formatting to ANY row. It gives me the cold shoulder.:-O I was wondering if anyone ran has run into a similar problem and knows a fix. If I was ambiguous anywhere, just let me know and I'll clarify. Thanks, Matt -- View this message in context: http://www.nabble.com/Odd-Behavior- with-HSSFSerializer-tp18115088p18115088.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: Odd Behavior with HSSFSerializer
Barbara, this worked flawlessly! I'm sure others will find this very helpful too. :jumping: Thanks, Matt Barbara Slupik-3 wrote: I had the same problem. I fixed it like this: !-- Style regions are built for each column for max 999 rows. Larger regions do not seem to work. That's why styles template is called more then once if number of rows to print exceedes 999. -- xsl:template name=styles xsl:param name=startRow/ xsl:param name=size/ xsl:variable name=endRow xsl:choose xsl:when test=($size - $startRow) gt; 999xsl:value-of select=$startRow + 998//xsl:when xsl:otherwisexsl:value-of select=$size//xsl:otherwise /xsl:choose /xsl:variable Styles StyleRegion ... xsl:attribute name=startRowxsl:value-of select=$startRow// xsl:attribute xsl:attribute name=endRowxsl:value-of select=$endRow// xsl:attribute Style ... ... /Style /StyleRegion ... /Styles xsl:if test=($size - $startRow) gt; 999 xsl:call-template name=styles xsl:with-param name=startRowxsl:value-of select=$startRow + 999//xsl:with-param xsl:with-param name=sizexsl:value-of select=$size// xsl:with-param /xsl:call-template /xsl:if /xsl:template The template is called for the first time with: xsl:call-template name=styles xsl:with-param name=startRow1/xsl:with-param xsl:with-param name=sizetotal-nr-of-elements/xsl:with-param /xsl:call-template Barbara On 25 Jun, 2008, at 4:21 pm, Matthew Monkan wrote: I produced a simple Excel document by querying my database and using the HSSFSerializer. It's a simple document; the spreadsheet just formats the data into the same grid layout you would see on a database GUI upon submitting the query. Anyway, I realized that no matter the numerical data that goes into the HSSFSerializer, Excel defaults to outputting them with the trailing 0's cut off. (22.90 becomes 22.9.) I downloaded Gnumeric, formatted numbers to show 2 decimal places, saved the document to Gnumeric XML, and opened it to see what XML was needed to format the decimal properly. (I want all my numbers rounded to two decimal places.) Here is the XML I currently use in my stylesheet: xsl:when test=/page/title='MOU Alert' gmr:StyleRegion startCol=5 startRow=3 endCol=5 xsl:attribute name=endRow xsl:value-of select=count(/page/content/sql:rowset/sql:row)+3 / /xsl:attribute gmr:Style HAlign=1 VAlign=2 WrapText=0 ShrinkToFit=0 Rotation=0 Shade=0 Indent=0 Locked=1 Hidden=0 Fore=0:0:0 Back=:: PatternColor=0:0:0 Format=0.00 gmr:Font Unit=10 Bold=0 Italic=0 Underline=0 StrikeThrough=0 Script=0Arial/gmr:Font /gmr:Style /gmr:StyleRegion /xsl:when If you look at gmr:Style's Format attribute, this is the input that is needed to produce the correct decimal places. This specific snippet of code should round all data in Column 6 (Gnumeric starts counting at 0, so Col=5 is the sixth column) starting at row 3 and ending with the last row of data. If you look at the count function under xsl:attribute name=endRow, this returns the value 4500 from my particular test data. This dynamically tells what row to stop applying the formatting to. There is no way to specify unbounded for endRow, so this count function is the only way I can get it to apply the formatting to every row for any instance of data queried. Now here's the odd behavior. This code works perfectly when I query data that is a few hundred rows long. If there is, for example, 500 rows being queried the count function correctly returns 503, which is the last row I want formatted. (My data outputs on rows 3 to 503 to make room for a heading.) But when I query data from around 700 or so upward (I haven't found an exact cutoff yet), it will never apply the formatting. (All the numbers will have trailing 0's cut off and not rounded to two decimal places.) This is extremely irritating, and this will need to work for thousands of rows. If I simply replace the count fuction with a number like 250, it works. (Rows 3-253 are formatted properly, and the few thousand remaining are left unformatted.) If I start putting in values like 2000, 3500, 11480, it won't apply formatting to ANY row. It gives me the cold shoulder.:-O I was wondering if anyone ran has run into a similar problem and knows a fix. If I was ambiguous anywhere, just let me know and I'll clarify. Thanks, Matt -- View this message in context:
Re: Odd Behavior with HSSFSerializer
Hi Matthew, I ran into the same issue no long ago. It is because MAX_AREA for the StyleRegion is limited to 2000 cells in EPStyleRegion.java. It is in cocoon-poi module . You can find a more detailed answer here: http://cocoon.markmail.org/message/qde5mge7sxnmvrg2 http://markmail.org/message/d4iemconxozxgb2v I also open an issue it is here: https://issues.apache.org/jira/browse/COCOON-2209 I hope it helps. Barbara, this worked flawlessly! I'm sure others will find this very helpful too. :jumping: Thanks, Matt Barbara Slupik-3 wrote: I had the same problem. I fixed it like this: !-- Style regions are built for each column for max 999 rows. Larger regions do not seem to work. That's why styles template is called more then once if number of rows to print exceedes 999. -- xsl:template name=styles xsl:param name=startRow/ xsl:param name=size/ xsl:variable name=endRow xsl:choose xsl:when test=($size - $startRow) gt; 999xsl:value-of select=$startRow + 998//xsl:when xsl:otherwisexsl:value-of select=$size//xsl:otherwise /xsl:choose /xsl:variable Styles StyleRegion ... xsl:attribute name=startRowxsl:value-of select=$startRow// xsl:attribute xsl:attribute name=endRowxsl:value-of select=$endRow// xsl:attribute Style ... ... /Style /StyleRegion ... /Styles xsl:if test=($size - $startRow) gt; 999 xsl:call-template name=styles xsl:with-param name=startRowxsl:value-of select=$startRow + 999//xsl:with-param xsl:with-param name=sizexsl:value-of select=$size// xsl:with-param /xsl:call-template /xsl:if /xsl:template The template is called for the first time with: xsl:call-template name=styles xsl:with-param name=startRow1/xsl:with-param xsl:with-param name=sizetotal-nr-of-elements/xsl:with-param /xsl:call-template Barbara On 25 Jun, 2008, at 4:21 pm, Matthew Monkan wrote: I produced a simple Excel document by querying my database and using the HSSFSerializer. It's a simple document; the spreadsheet just formats the data into the same grid layout you would see on a database GUI upon submitting the query. Anyway, I realized that no matter the numerical data that goes into the HSSFSerializer, Excel defaults to outputting them with the trailing 0's cut off. (22.90 becomes 22.9.) I downloaded Gnumeric, formatted numbers to show 2 decimal places, saved the document to Gnumeric XML, and opened it to see what XML was needed to format the decimal properly. (I want all my numbers rounded to two decimal places.) Here is the XML I currently use in my stylesheet: xsl:when test=/page/title='MOU Alert' gmr:StyleRegion startCol=5 startRow=3 endCol=5 xsl:attribute name=endRow xsl:value-of select=count(/page/content/sql:rowset/sql:row)+3 / /xsl:attribute gmr:Style HAlign=1 VAlign=2 WrapText=0 ShrinkToFit=0 Rotation=0 Shade=0 Indent=0 Locked=1 Hidden=0 Fore=0:0:0 Back=:: PatternColor=0:0:0 Format=0.00 gmr:Font Unit=10 Bold=0 Italic=0 Underline=0 StrikeThrough=0 Script=0Arial/gmr:Font /gmr:Style /gmr:StyleRegion /xsl:when If you look at gmr:Style's Format attribute, this is the input that is needed to produce the correct decimal places. This specific snippet of code should round all data in Column 6 (Gnumeric starts counting at 0, so Col=5 is the sixth column) starting at row 3 and ending with the last row of data. If you look at the count function under xsl:attribute name=endRow, this returns the value 4500 from my particular test data. This dynamically tells what row to stop applying the formatting to. There is no way to specify unbounded for endRow, so this count function is the only way I can get it to apply the formatting to every row for any instance of data queried. Now here's the odd behavior. This code works perfectly when I query data that is a few hundred rows long. If there is, for example, 500 rows being queried the count function correctly returns 503, which is the last row I want formatted. (My data outputs on rows 3 to 503 to make room for a heading.) But when I query data from around 700 or so upward (I haven't found an exact cutoff yet), it will never apply the formatting. (All the numbers will have trailing 0's cut off and not rounded to two decimal places.) This is extremely irritating, and this will need to work for thousands of rows. If I simply replace the count fuction with a number like 250, it works. (Rows 3-253 are formatted properly, and the few thousand remaining are left unformatted.) If I start putting in values like 2000, 3500, 11480, it won't apply formatting to ANY
[Cocoon 2.1.9] Internationlization i18n
Hey guys had a quick question. Is there a way to use gender specific internationilization in Cocoon??? Say, I am creating a letter. I wud rite Dear. Mr. John Doe to start with or Dear Mrs. Jane Doe In English, 'dear' can be used for both. But, I believe there are languages where it mite differ from gender to gender. Is there a way to handle this in cocoon? thanks Ed.
RCL vs Cocoon core.properties
I see that the cocoon core.properties contain parameters: org.apache.cocoon.reloading org.apache.cocoon.reloading.sitemap org.apache.cocoon.reload-delay.sitemap org.apache.cocoon.reloading.config org.apache.cocoon.reloading.flow These appear to work in a block created to run without the rcl webapp - plain jetty or tomcat. But the rcl appears to do some of these same things, such as reloading the sitemap. I'm a bit confused about when/why each of these mechanisms should be used. Are they independant? Why would a developer choose one or the other? Thanks to all, -Hugh Sparks, [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
