RE: Cocoon Portal - User Roles
Hi, thank you for the tip. :-) I will have a try. Wolfgang *Hi, * *try using the log transformer between your transformation step *with the login.xsl and the sql transformer and you will see, *if the correct xml is outputted by your stylesheet. *If this is correct, put the log transformer behind the sql *transformer and you will see what the sql transformer does. * *Maybe this gives a clue. * *Carsten * *Carsten Ziegeler *Open Source Group, SN AG * * * -Original Message- * From: Wolle [mailto:[EMAIL PROTECTED]] * Sent: Thursday, January 16, 2003 2:09 PM * To: [EMAIL PROTECTED] * Subject: RE: Cocoon Portal - User Roles * * * Hi Guys, * * I tried all this. Maybe somebody can give some completing hints. * I described all in the file email.txt * * Thank You * * Wolfgang * * * * * * *Since the the new role function in the portal sample is mapped to * *new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using * this sitemap * *snippet right? * * * *map:match pattern=sunrise* * *map:generate src=resources/sunrise{1}.xml/ * *map:transform type=session/ * *map:transform type=cinclude/ * *map:transform type=write-source/ * *map:transform src=styles/portal.xsl/ * *map:serialize type=xml/ * */map:match * * * *and the documentations says that * * * *The new-role resource creates a new role in the system. It gets the * *parameters type with the value role and role with the new rolename. * * * *Where is the type and role parameter? * *and why does it have to serialized in an xml type in the end? * * * * * *You need to take a look at the file sunrise-newrole.xml. That * file contains * *most of the dirty work. The transformers session, cinclude and * writesource * *act on the information contained in there. Because * sunrise-newrole.xml also * *flows through the pipeline it is then formatted by the stylesheet and * *returned to the browser. It is serialized to xml because it is being used * *inside the portal (in this case). * * * *If you wanted to write this to a database you would need to change the * *sunrise-newrole.xml and use the sqltransformer instead of cinclude and * *write-source. In all this should take you around 5 minutes or * less to adapt. * *:-) * * * *So it really is quite simple really. * * * *Matthew * *-- * *Open Source Group Cocoon { Consulting, Training, Projects } * *= * *Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn * *Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de * *- * *Cocoon book: * * http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20 * *Weblog: * * http://radio.weblogs.com/0103021/ * *= * * * * -Original Message- * * From: Richard Reyes [mailto:[EMAIL PROTECTED]] * * Sent: Tuesday, November 12, 2002 12:53 PM * * To: cocoon-users * * Subject: RE: Cocoon Portal - User Roles * * * * * * * * * * Hi Matthew / Guys, * * * * Just want to confirm some things * * * * Since the the new role function in the portal sample is mapped to * *new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using * this sitemap * *snippet right? * * * * map:match pattern=sunrise* * * map:generate src=resources/sunrise{1}.xml/ * * map:transform type=session/ * * map:transform type=cinclude/ * * map:transform type=write-source/ * * map:transform src=styles/portal.xsl/ * * map:serialize type=xml/ * * /map:match * * * * and the documentations says that * * * * The new-role resource creates a new role in the system. It gets the * *parameters type with the value role and role with the new rolename. * * * * Where is the type and role parameter? * * and why does it have to serialized in an xml type in the end? * * * * Also, for the sunrise-newrole resource, the only thing this * pipeline does * *is save a new role in the xml file ( sunrise-roles.xml )? whose * responsible * *for displaying the next page after saving the new role? * * * * And since this sitemap snippet is called inside a map:pipeline internal * *only clause I think it is being called by the portal generator or action. * * * * If in case I'd used custom actions over this pipeline, How would I know * *the parameters that * * have been passed and are being expected by the caller of this pipeline? * * * * Thanks a lot * * Richard * *- Original Message - * *From: Richard Reyes * *To: cocoon-users * *Cc: Alex * *Sent: Tuesday, November 12, 2002 7:18 PM * *Subject: Re: Cocoon Portal - User Roles * * * * * *Hi Matthew, * * * *Thanks for the reminder! * * * * * *Hi, * * * *each function of the portal
RE: Cocoon Portal - User Roles
Hi Guys, I tried all this. Maybe somebody can give some completing hints. I described all in the file email.txt Thank You Wolfgang * *Since the the new role function in the portal sample is mapped to *new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using this sitemap *snippet right? * *map:match pattern=sunrise* *map:generate src=resources/sunrise{1}.xml/ *map:transform type=session/ *map:transform type=cinclude/ *map:transform type=write-source/ *map:transform src=styles/portal.xsl/ *map:serialize type=xml/ */map:match * *and the documentations says that * *The new-role resource creates a new role in the system. It gets the *parameters type with the value role and role with the new rolename. * *Where is the type and role parameter? *and why does it have to serialized in an xml type in the end? * * *You need to take a look at the file sunrise-newrole.xml. That file contains *most of the dirty work. The transformers session, cinclude and writesource *act on the information contained in there. Because sunrise-newrole.xml also *flows through the pipeline it is then formatted by the stylesheet and *returned to the browser. It is serialized to xml because it is being used *inside the portal (in this case). * *If you wanted to write this to a database you would need to change the *sunrise-newrole.xml and use the sqltransformer instead of cinclude and *write-source. In all this should take you around 5 minutes or less to adapt. *:-) * *So it really is quite simple really. * *Matthew *-- *Open Source Group Cocoon { Consulting, Training, Projects } *= *Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn *Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de *- *Cocoon book: * http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20 *Weblog: * http://radio.weblogs.com/0103021/ *= * * -Original Message- * From: Richard Reyes [mailto:[EMAIL PROTECTED]] * Sent: Tuesday, November 12, 2002 12:53 PM * To: cocoon-users * Subject: RE: Cocoon Portal - User Roles * * * * * Hi Matthew / Guys, * * Just want to confirm some things * * Since the the new role function in the portal sample is mapped to *new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using this sitemap *snippet right? * * map:match pattern=sunrise* * map:generate src=resources/sunrise{1}.xml/ * map:transform type=session/ * map:transform type=cinclude/ * map:transform type=write-source/ * map:transform src=styles/portal.xsl/ * map:serialize type=xml/ * /map:match * * and the documentations says that * * The new-role resource creates a new role in the system. It gets the *parameters type with the value role and role with the new rolename. * * Where is the type and role parameter? * and why does it have to serialized in an xml type in the end? * * Also, for the sunrise-newrole resource, the only thing this pipeline does *is save a new role in the xml file ( sunrise-roles.xml )? whose responsible *for displaying the next page after saving the new role? * * And since this sitemap snippet is called inside a map:pipeline internal *only clause I think it is being called by the portal generator or action. * * If in case I'd used custom actions over this pipeline, How would I know *the parameters that * have been passed and are being expected by the caller of this pipeline? * * Thanks a lot * Richard *- Original Message - *From: Richard Reyes *To: cocoon-users *Cc: Alex *Sent: Tuesday, November 12, 2002 7:18 PM *Subject: Re: Cocoon Portal - User Roles * * *Hi Matthew, * *Thanks for the reminder! * * *Hi, * *each function of the portal is mapped to a pipeline. So in order to *change the storage - all you have to do is to modify the pipeline to use say *the SQLGenerator etc. * *Read the documentation. *http://xml.apache.org/cocoon/developing/webapps/authentication.html * *It explains this in detail (see under User Administration). Then look at *the pipelines that are currently used to get a feel for how it works at the *moment. * *Matthew * *-- *Open Source Group Cocoon { Consulting, Training, Projects } *= *Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn *Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de *- *Cocoon book: * http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20 *Weblog: * http
RE: Cocoon Portal - User Roles
Hi, try using the log transformer between your transformation step with the login.xsl and the sql transformer and you will see, if the correct xml is outputted by your stylesheet. If this is correct, put the log transformer behind the sql transformer and you will see what the sql transformer does. Maybe this gives a clue. Carsten Carsten Ziegeler Open Source Group, SN AG -Original Message- From: Wolle [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 2:09 PM To: [EMAIL PROTECTED] Subject: RE: Cocoon Portal - User Roles Hi Guys, I tried all this. Maybe somebody can give some completing hints. I described all in the file email.txt Thank You Wolfgang * *Since the the new role function in the portal sample is mapped to *new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using this sitemap *snippet right? * *map:match pattern=sunrise* *map:generate src=resources/sunrise{1}.xml/ *map:transform type=session/ *map:transform type=cinclude/ *map:transform type=write-source/ *map:transform src=styles/portal.xsl/ *map:serialize type=xml/ */map:match * *and the documentations says that * *The new-role resource creates a new role in the system. It gets the *parameters type with the value role and role with the new rolename. * *Where is the type and role parameter? *and why does it have to serialized in an xml type in the end? * * *You need to take a look at the file sunrise-newrole.xml. That file contains *most of the dirty work. The transformers session, cinclude and writesource *act on the information contained in there. Because sunrise-newrole.xml also *flows through the pipeline it is then formatted by the stylesheet and *returned to the browser. It is serialized to xml because it is being used *inside the portal (in this case). * *If you wanted to write this to a database you would need to change the *sunrise-newrole.xml and use the sqltransformer instead of cinclude and *write-source. In all this should take you around 5 minutes or less to adapt. *:-) * *So it really is quite simple really. * *Matthew *-- *Open Source Group Cocoon { Consulting, Training, Projects } *= *Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn *Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de *- *Cocoon book: * http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20 *Weblog: * http://radio.weblogs.com/0103021/ *= * * -Original Message- * From: Richard Reyes [mailto:[EMAIL PROTECTED]] * Sent: Tuesday, November 12, 2002 12:53 PM * To: cocoon-users * Subject: RE: Cocoon Portal - User Roles * * * * * Hi Matthew / Guys, * * Just want to confirm some things * * Since the the new role function in the portal sample is mapped to *new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using this sitemap *snippet right? * * map:match pattern=sunrise* * map:generate src=resources/sunrise{1}.xml/ * map:transform type=session/ * map:transform type=cinclude/ * map:transform type=write-source/ * map:transform src=styles/portal.xsl/ * map:serialize type=xml/ * /map:match * * and the documentations says that * * The new-role resource creates a new role in the system. It gets the *parameters type with the value role and role with the new rolename. * * Where is the type and role parameter? * and why does it have to serialized in an xml type in the end? * * Also, for the sunrise-newrole resource, the only thing this pipeline does *is save a new role in the xml file ( sunrise-roles.xml )? whose responsible *for displaying the next page after saving the new role? * * And since this sitemap snippet is called inside a map:pipeline internal *only clause I think it is being called by the portal generator or action. * * If in case I'd used custom actions over this pipeline, How would I know *the parameters that * have been passed and are being expected by the caller of this pipeline? * * Thanks a lot * Richard *- Original Message - *From: Richard Reyes *To: cocoon-users *Cc: Alex *Sent: Tuesday, November 12, 2002 7:18 PM *Subject: Re: Cocoon Portal - User Roles * * *Hi Matthew, * *Thanks for the reminder! * * *Hi, * *each function of the portal is mapped to a pipeline. So in order to *change the storage - all you have to do is to modify the pipeline to use say *the SQLGenerator etc. * *Read the documentation. *http://xml.apache.org/cocoon/developing
Re: Cocoon Portal - User Roles
Hi Matthew / Guys, I have been able to replace the addrole and load role functions into an Action. Will I have a problem if i didn't serialize any xml? (see sitemap below) map:match pattern="sunrise-newrole" map:act type="SaveRole" map:parameter name="descriptor" value="context://myportal/descriptor/vxs_employees-dx.xml"/ map:parameter name="use-request-parameters" value="true" / map:generate type="serverpages" src="xsp/saverole.xsp"/ map:serialize type="xml" / /map:act /map:match If I create an action for the delrole function, how can I delete the generated roleprofile-xxx.xml file? or i cannot delete it and have to dele it manually? Thanks Again. Richard - Original Message - From: Richard Reyes To: [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 3:04 PM Subject: Re: Cocoon Portal - User Roles Hi Matthew, If I understand it right, I have to change thesunrise-newrole.xml into something that the sql transformer would understand and remove the cinclude and writesource transformer on the pipeline? In this case... Whats the advantage of using transformer than an action? In the end of this map:matchpattern it is returning an xml like this... ?xml version="1.0" encoding="UTF-8" ? - !-- $Id: sunrise-newrole.xml,v 1.1 2002/06/03 11:45:54 cziegeler Exp $ Description: Add a new role-- - addrole xmlns:source="http://apache.org/cocoon/source/1.0" xmlns:session="http://cocoon.apache.org/session/1.0" - sourceResult executionsuccess/execution messagecontent inserted at: roles/message behaviourinsert/behaviour actionoverwritten/action sourcefile:/C:/ApacheGroup/Tomcat4.1/webapps/cocoon/myportal/resources/sunrise-roles.xml/source serializerxml/serializer /sourceResult /addrole If I'd use an action, do I have to serialized these kinds of xml? And can you tell me where the sunrise-newrole resource is being called and returned to? Thanks again. Richard - Original Message - From: Matthew Langham To: [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 8:16 PM Subject: RE: Cocoon Portal - User Roles Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? You need to take a look at the file sunrise-newrole.xml. That file contains most of the dirty work. The transformers session, cinclude and writesource act on the information contained in there. Because sunrise-newrole.xml also flows through the pipeline it is then formatted by the stylesheet and returned to the browser. It is serialized to xml because it is being used inside the portal (in this case). If you wanted to write this to a database you would need to change the sunrise-newrole.xml and use the sqltransformer instead of cinclude and write-source. In all this should take you around 5 minutes or less to adapt. :-) So it really is quite simple really. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/===== -Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 12,
RE: Cocoon Portal - User Roles
Will I have a problem if i didn't serialize any xml? (see sitemap below) Try it :-). Seriously, you will probably have to change the user interface of the tools as I think they expect something to be returned. If you add a new role using the tool then you would expect that role to appear in the tool once the action was complete - wouldn't you? Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/= -Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Wednesday, November 13, 2002 12:36 PMTo: [EMAIL PROTECTED]Subject: Re: Cocoon Portal - User Roles Hi Matthew / Guys, I have been able to replace the addrole and load role functions into an Action. Will I have a problem if i didn't serialize any xml? (see sitemap below) map:match pattern="sunrise-newrole" map:act type="SaveRole" map:parameter name="descriptor" value="context://myportal/descriptor/vxs_employees-dx.xml"/ map:parameter name="use-request-parameters" value="true" / map:generate type="serverpages" src="xsp/saverole.xsp"/ map:serialize type="xml" / /map:act /map:match If I create an action for the delrole function, how can I delete the generated roleprofile-xxx.xml file? or i cannot delete it and have to dele it manually? Thanks Again. Richard - Original Message - From: Richard Reyes To: [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 3:04 PM Subject: Re: Cocoon Portal - User Roles Hi Matthew, If I understand it right, I have to change thesunrise-newrole.xml into something that the sql transformer would understand and remove the cinclude and writesource transformer on the pipeline? In this case... Whats the advantage of using transformer than an action? In the end of this map:matchpattern it is returning an xml like this... ?xml version="1.0" encoding="UTF-8" ? - !-- $Id: sunrise-newrole.xml,v 1.1 2002/06/03 11:45:54 cziegeler Exp $ Description: Add a new role-- - addrole xmlns:source="http://apache.org/cocoon/source/1.0" xmlns:session="http://cocoon.apache.org/session/1.0" - sourceResult executionsuccess/execution messagecontent inserted at: roles/message behaviourinsert/behaviour actionoverwritten/action sourcefile:/C:/ApacheGroup/Tomcat4.1/webapps/cocoon/myportal/resources/sunrise-roles.xml/source serializerxml/serializer /sourceResult /addrole If I'd use an action, do I have to serialized these kinds of xml? And can you tell me where the sunrise-newrole resource is being called and returned to? Thanks again. Richard - Original Message - From: Matthew Langham To: [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 8:16 PM Subject: RE: Cocoon Portal - User Roles Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? You need to take a look at the file sunrise-newrole.xml.
Re: Cocoon Portal - User Roles
We are doing this with XSPs to provide the XML, rather the the SQL transformer. But we are actually part way through replacing all of the file-based pipelines for these componenets with XSP driven database equivalents. so far, only a few problems have cropped up Hi Matthew, If I understand it right, I have to change the sunrise-newrole.xml into something that the sql transformer would understand and remove the cinclude and writesource transformer on the pipeline? In this case... Whats the advantage of using transformer than an action? In the end of this map:match pattern it is returning an xml like this... ?xml version=1.0 encoding=UTF-8 ? - !-- $Id: sunrise-newrole.xml,v 1.1 2002/06/03 11:45:54 cziegeler Exp $ Description: Add a new role -- - addrole xmlns:source=http://apache.org/cocoon/source/1.0; xmlns:session=http://cocoon.apache.org/session/1.0; - sourceResult executionsuccess/execution messagecontent inserted at: roles/message behaviourinsert/behaviour actionoverwritten/action sourcefile:/C:/ApacheGroup/Tomcat4.1/webapps/cocoon/myportal/resources/sunrise-roles.xml/source serializerxml/serializer /sourceResult /addrole If I'd use an action, do I have to serialized these kinds of xml? And can you tell me where the sunrise-newrole resource is being called and returned to? Thanks again. Richard - Original Message - From: Matthew Langham To: [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 8:16 PM Subject: RE: Cocoon Portal - User Roles Since the the new role function in the portal sample is mapped to new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using this sitemap snippet right? map:match pattern=sunrise* map:generate src=resources/sunrise{1}.xml/ map:transform type=session/ map:transform type=cinclude/ map:transform type=write-source/ map:transform src=styles/portal.xsl/ map:serialize type=xml/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters type with the value role and role with the new rolename. Where is the type and role parameter? and why does it have to serialized in an xml type in the end? You need to take a look at the file sunrise-newrole.xml. That file contains most of the dirty work. The transformers session, cinclude and writesource act on the information contained in there. Because sunrise-newrole.xml also flows through the pipeline it is then formatted by the stylesheet and returned to the browser. It is serialized to xml because it is being used inside the portal (in this case). If you wanted to write this to a database you would need to change the sunrise-newrole.xml and use the sqltransformer instead of cinclude and write-source. In all this should take you around 5 minutes or less to adapt. :-) So it really is quite simple really. Matthew -- Open Source Group Cocoon { Consulting, Training, Projects } Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de - Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20 Weblog: http://radio.weblogs.com/0103021/ -Original Message- From: Richard Reyes [mailto:seyer_drahcir;hotmail.com] Sent: Tuesday, November 12, 2002 12:53 PM To: cocoon-users Subject: RE: Cocoon Portal - User Roles Hi Matthew / Guys, Just want to confirm some things Since the the new role function in the portal sample is mapped to new-role uri=cocoon:raw:/sunrise-newrole/ uri, it is using this sitemap snippet right? map:match pattern=sunrise* map:generate src=resources/sunrise{1}.xml/ map:transform type=session/ map:transform type=cinclude/ map:transform type=write-source/ map:transform src=styles/portal.xsl/ map:serialize type=xml/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters type with the value role and role with the new rolename. Where is the type and role parameter? and why does it have to serialized in an xml type in the end? Also, for the sunrise-newrole resource, the only thing this pipeline does is save a new role in the xml file ( sunrise-roles.xml )? whose responsible for displaying the next page after saving the new role? And since this sitemap snippet is called inside a map:pipeline internal only clause I
Re: Cocoon Portal - User Roles
ey, i am not totally aware of the ideas behind the authentication-fw but i think you could use xsp/esql to generate an xml file from your database conforming to the authentication-fw specs. HTH, wouter Hi Guys, I am trying to use the C2 portal application and would like to transfer the storage of the roles from xml files to a mysql database. Can someone teach me how to do this? I cannot find anything on the sitemap file that transforms or uses the sunrise roles.xml btw, im using tomcat 4.1 sdk 1.3 c2.1 dev thanks - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon Portal - User Roles
thanks for the input. - Original Message - From: Wouter Scheele [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 4:49 PM Subject: Re: Cocoon Portal - User Roles ey, i am not totally aware of the ideas behind the authentication-fw but i think you could use xsp/esql to generate an xml file from your database conforming to the authentication-fw specs. HTH, wouter Hi Guys, I am trying to use the C2 portal application and would like to transfer the storage of the roles from xml files to a mysql database. Can someone teach me how to do this? I cannot find anything on the sitemap file that transforms or uses the sunrise roles.xml btw, im using tomcat 4.1 sdk 1.3 c2.1 dev thanks - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon Portal - User Roles
Hi again guys, I have checked the source codes of the portal sample... I found out that if I am to add new user or to add new roles, both task will end up submitting forms with different parameters to this resource /cocoon/myportal/sunspotdemo-sunriseconf which inturn would exactly matchthis sitemap snippet in the process... map:match pattern="sunspotdemo-sunriseconf" !-- This pipeline can only be accessed if the current user is allowed to configure the 'administration' coplet -- map:act type="portal-auth" map:parameter name="coplet" value="administration"/ /map:act map:generate type="auth-conf"/ map:transform src="styles/sunriseconfHTML.xsl"/ map:transform type="encodeURL"/ map:serialize / Am I correct? Now I have checked the source codes for the "portal-auth" action and the "auth-conf" genarator, and I dont think they're very easy to modify. I hope I do not have to createour own portal genarators to use a database as a storage for user and roles. any ideas? thanks - Original Message - From: Richard Reyes To: cocoon-users Sent: Tuesday, November 12, 2002 2:18 PM Subject: Cocoon Portal - User Roles Hi Guys, I am trying to use the C2 portal application and would like to transfer the storage of the roles from xml files to a mysql database. Can someone teach me how to do this? I cannot find anything on the sitemap file that transforms or uses the sunrise roles.xml btw, im using tomcat 4.1 sdk 1.3 c2.1 dev thanks
RE: Cocoon Portal - User Roles
Hi, each function of the portal is mapped to a pipeline. So in order to change the storage - all you have to do is to modify the pipeline to use say the SQLGenerator etc. Read the documentation. http://xml.apache.org/cocoon/developing/webapps/authentication.html It explains this in detail (see under User Administration). Then look at the pipelines that are currently used to get a feel for how it works at the moment. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/= -Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 12, 2002 10:06 AMTo: [EMAIL PROTECTED]Subject: Re: Cocoon Portal - User Roles Hi again guys, I have checked the source codes of the portal sample... I found out that if I am to add new user or to add new roles, both task will end up submitting forms with different parameters to this resource /cocoon/myportal/sunspotdemo-sunriseconf which inturn would exactly matchthis sitemap snippet in the process... map:match pattern="sunspotdemo-sunriseconf" !-- This pipeline can only be accessed if the current user is allowed to configure the 'administration' coplet -- map:act type="portal-auth" map:parameter name="coplet" value="administration"/ /map:act map:generate type="auth-conf"/ map:transform src="styles/sunriseconfHTML.xsl"/ map:transform type="encodeURL"/ map:serialize / Am I correct? Now I have checked the source codes for the "portal-auth" action and the "auth-conf" genarator, and I dont think they're very easy to modify. I hope I do not have to createour own portal genarators to use a database as a storage for user and roles. any ideas? thanks - Original Message - From: Richard Reyes To: cocoon-users Sent: Tuesday, November 12, 2002 2:18 PM Subject: Cocoon Portal - User Roles Hi Guys, I am trying to use the C2 portal application and would like to transfer the storage of the roles from xml files to a mysql database. Can someone teach me how to do this? I cannot find anything on the sitemap file that transforms or uses the sunrise roles.xml btw, im using tomcat 4.1 sdk 1.3 c2.1 dev thanks
Re: Cocoon Portal - User Roles
Hi Matthew, Thanks for the reminder! Hi, each function of the portal is mapped to a pipeline. So in order to change the storage - all you have to do is to modify the pipeline to use say the SQLGenerator etc. Read the documentation. http://xml.apache.org/cocoon/developing/webapps/authentication.html It explains this in detail (see under User Administration). Then look at the pipelines that are currently used to get a feel for how it works at the moment. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/= -Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 12, 2002 10:06 AMTo: [EMAIL PROTECTED]Subject: Re: Cocoon Portal - User Roles Hi again guys, I have checked the source codes of the portal sample... I found out that if I am to add new user or to add new roles, both task will end up submitting forms with different parameters to this resource /cocoon/myportal/sunspotdemo-sunriseconf which inturn would exactly matchthis sitemap snippet in the process...
Re: Cocoon Portal - User Roles
Hi Matthew / Guys, Just want to confirm some things Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? Also, for the sunrise-newrole resource,the only thing this pipeline does is save a new role in the xml file (sunrise-roles.xml )? whose responsible for displaying the next page after saving the new role? And since this sitemap snippet is called inside a map:pipeline internal only clause I think it is being called by the portal generator or action. If in case I'd used custom actions over this pipeline, How would I know the parameters that have been passed and are being expected by the caller of this pipeline? Thanks a lot Richard - Original Message ----- From: Richard Reyes To: cocoon-users Cc: Alex Sent: Tuesday, November 12, 2002 7:18 PM Subject: Re: Cocoon Portal - User Roles Hi Matthew, Thanks for the reminder! Hi, each function of the portal is mapped to a pipeline. So in order to change the storage - all you have to do is to modify the pipeline to use say the SQLGenerator etc. Read the documentation. http://xml.apache.org/cocoon/developing/webapps/authentication.html It explains this in detail (see under User Administration). Then look at the pipelines that are currently used to get a feel for how it works at the moment. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/= -Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 12, 2002 10:06 AMTo: [EMAIL PROTECTED]Subject: Re: Cocoon Portal - User Roles Hi again guys, I have checked the source codes of the portal sample... I found out that if I am to add new user or to add new roles, both task will end up submitting forms with different parameters to this resource /cocoon/myportal/sunspotdemo-sunriseconf which inturn would exactly matchthis sitemap snippet in the process...
RE: Cocoon Portal - User Roles
Hi Matthew / Guys, Just want to confirm some things Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? Also, for the sunrise-newrole resource,the only thing this pipeline does is save a new role in the xml file (sunrise-roles.xml )? whose responsible for displaying the next page after saving the new role? And since this sitemap snippet is called inside a map:pipeline internal only clause I think it is being called by the portal generator or action. If in case I'd used custom actions over this pipeline, How would I know the parameters that have been passed and are being expected by the caller of this pipeline? Thanks a lot Richard - Original Message ----- From: Richard Reyes To: cocoon-users Cc: Alex Sent: Tuesday, November 12, 2002 7:18 PM Subject: Re: Cocoon Portal - User Roles Hi Matthew, Thanks for the reminder! Hi, each function of the portal is mapped to a pipeline. So in order to change the storage - all you have to do is to modify the pipeline to use say the SQLGenerator etc. Read the documentation. http://xml.apache.org/cocoon/developing/webapps/authentication.html It explains this in detail (see under User Administration). Then look at the pipelines that are currently used to get a feel for how it works at the moment. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/= -Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 12, 2002 10:06 AMTo: [EMAIL PROTECTED]Subject: Re: Cocoon Portal - User Roles Hi again guys, I have checked the source codes of the portal sample... I found out that if I am to add new user or to add new roles, both task will end up submitting forms with different parameters to this resource /cocoon/myportal/sunspotdemo-sunriseconf which inturn would exactly matchthis sitemap snippet in the process...
RE: Cocoon Portal - User Roles
Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? You need to take a look at the file sunrise-newrole.xml. That file contains most of the dirty work. The transformers session, cinclude and writesource act on the information contained in there. Because sunrise-newrole.xml also flows through the pipeline it is then formatted by the stylesheet and returned to the browser. It is serialized to xml because it is being used inside the portal (in this case). If you wanted to write this to a database you would need to change the sunrise-newrole.xml and use the sqltransformer instead of cinclude and write-source. In all this should take you around 5 minutes or less to adapt. :-) So it really is quite simple really. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/= -Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 12, 2002 12:53 PMTo: cocoon-usersSubject: RE: Cocoon Portal - User Roles Hi Matthew / Guys, Just want to confirm some things Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? Also, for the sunrise-newrole resource,the only thing this pipeline does is save a new role in the xml file (sunrise-roles.xml )? whose responsible for displaying the next page after saving the new role? And since this sitemap snippet is called inside a map:pipeline internal only clause I think it is being called by the portal generator or action. If in case I'd used custom actions over this pipeline, How would I know the parameters that have been passed and are being expected by the caller of this pipeline? Thanks a lot Richard - Original Message - From: Richard Reyes To: cocoon-users Cc: Alex Sent: Tuesday, November 12, 2002 7:18 PM Subject: Re: Cocoon Portal - User Roles Hi Matthew, Thanks for the reminder! Hi, each function of the portal is mapped to a pipeline. So in order to change the storage - all you have to do is to modify the pipeline to use say the SQLGenerator etc. Read the documentation. http://xml.apache.org/cocoon/developing/webapps/authentication.html It explains this in detail (see under User Administration). Then look at the pipelines that are currently used to get a feel for how it works at the moment. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon
Re: Cocoon Portal - User Roles
Hi Matthew, If I understand it right, I have to change thesunrise-newrole.xml into something that the sql transformer would understand and remove the cinclude and writesource transformer on the pipeline? In this case... Whats the advantage of using transformer than an action? In the end of this map:matchpattern it is returning an xml like this... ?xml version="1.0" encoding="UTF-8" ? - !-- $Id: sunrise-newrole.xml,v 1.1 2002/06/03 11:45:54 cziegeler Exp $ Description: Add a new role-- - addrole xmlns:source="http://apache.org/cocoon/source/1.0" xmlns:session="http://cocoon.apache.org/session/1.0" - sourceResult executionsuccess/execution messagecontent inserted at: roles/message behaviourinsert/behaviour actionoverwritten/action sourcefile:/C:/ApacheGroup/Tomcat4.1/webapps/cocoon/myportal/resources/sunrise-roles.xml/source serializerxml/serializer /sourceResult /addrole If I'd use an action, do I have to serialized these kinds of xml? And can you tell me where the sunrise-newrole resource is being called and returned to? Thanks again. Richard - Original Message - From: Matthew Langham To: [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 8:16 PM Subject: RE: Cocoon Portal - User Roles Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? You need to take a look at the file sunrise-newrole.xml. That file contains most of the dirty work. The transformers session, cinclude and writesource act on the information contained in there. Because sunrise-newrole.xml also flows through the pipeline it is then formatted by the stylesheet and returned to the browser. It is serialized to xml because it is being used inside the portal (in this case). If you wanted to write this to a database you would need to change the sunrise-newrole.xml and use the sqltransformer instead of cinclude and write-source. In all this should take you around 5 minutes or less to adapt. :-) So it really is quite simple really. Matthew --Open Source Group Cocoon { Consulting, Training, Projects }=Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 PaderbornTel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de-Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20Weblog: http://radio.weblogs.com/0103021/===== -----Original Message-From: Richard Reyes [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 12, 2002 12:53 PMTo: cocoon-usersSubject: RE: Cocoon Portal - User Roles Hi Matthew / Guys, Just want to confirm some things Since the the "new role" function in the portal sample is mapped to new-role uri="cocoon:raw:/sunrise-newrole"/ uri, it is using this sitemap snippet right? map:match pattern="sunrise*" map:generate src="resources/sunrise{1}.xml"/ map:transform type="session"/ map:transform type="cinclude"/ map:transform type="write-source"/ map:transform src="styles/portal.xsl"/ map:serialize type="xml"/ /map:match and the documentations says that The new-role resource creates a new role in the system. It gets the parameters "type" with the value "role" and "role" with the new rolename. Where is the "type" and "role" parameter? and why does it have to serialized in an xml type in the end? Also, for the sunrise-newrole resource,the only thing this pipeline does is save a new role in the xml
Cocoon Portal - User Roles
Hi Guys, I am trying to use the C2 portal application and would like to transfer the storage of the roles from xml files to a mysql database. Can someone teach me how to do this? I cannot find anything on the sitemap file that transforms or uses the sunrise roles.xml btw, im using tomcat 4.1 sdk 1.3 c2.1 dev thanks