Re: Portal question [ the request parameters are available from insidethe coplets?]
Hi Carsten, Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my coplets displayed. But when I changed to cocoon:/ without the raw, the portal displays the (The content is not avilable now) message ! Here's one of my coplets defintion. coplet id=menu resource uri=cocoon:raw:/menu/ configuration mandatorytrue/mandatory sizableflase/sizable activetrue/active timeout5000/timeout /configuration titleMenu/title status customizefalse/customize visibletrue/visible sizemax/size /status /coplet where menu is a normal pipeline. Does the change from cocoon:raw:/ to cocoon:/ requires any other changes, maybe in the coplet pipeline? Actually, I don't know exactly what raw adds to cocoon: as a protocol, and I didn't find any information regarding this point (even in your very nice book with Matthew). Maybe you could tell me where can I find any information about that? Best Regards. Carsten Ziegeler wrote: Ramy Mamdouh wrote: Thanks for replying, but handlesParameters just handles the parameters of the portal engine (like size, customize, etc). True. And handlesParameters is true by default. Yes. What I'm asking about is handling any other parameters passed with the main portal uri. handlesParameters has no effect as -it seems to me- regarding these parameters, it just handles the portal engine parameters. What URI protocol do you use to invoke your coplets? I assume you use the internal cocoon: protocol - if you simply use cocoon:/coplet, the parameters are passed from the main pipeline to the coplet pipeline. If you use cocoon:raw:/coplet, then the parameters are not passed. Carsten Carsten Ziegeler Chief Architect Open Source Group, SN AG -- Cocoon Consulting, Training and Projects -- mailto:[EMAIL PROTECTED] http://www.s-und-n.de http://ziegeler.bei.t-online.de - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ramy Mamdouh Kamel Software Engineer Ute Imkenberg [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: Portal question [ the request parameters are available from inside the coplets?]
Ramy Mamdouh wrote: Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my coplets displayed. But when I changed to cocoon:/ without the raw, the portal displays the (The content is not avilable now) message ! Here's one of my coplets defintion. coplet id=menu resource uri=cocoon:raw:/menu/ configuration mandatorytrue/mandatory sizableflase/sizable activetrue/active timeout5000/timeout /configuration titleMenu/title status customizefalse/customize visibletrue/visible sizemax/size /status /coplet where menu is a normal pipeline. Does the change from cocoon:raw:/ to cocoon:/ requires any other changes, maybe in the coplet pipeline? Hmmm, usually not - but without raw: all parameters that where send to the main pipeline are send to the coplet as well, perhaps there is a problem? Actually, I don't know exactly what raw adds to cocoon: as a protocol, and I didn't find any information regarding this point (even in your very nice book with Matthew). ;) - Yes, the cocoon:raw protocol is very new and was added to Cocoon after we wrote the book, so The one and only distinction is, that with the subprotocol raw no request parameters are passed on to the called internal pipeline and without raw all are passed. Carsten - 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: Portal question [ the request parameters are available from insidethe coplets?]
Hello Carsten, It seems I don't have any problems in my coplets. And to be sure, I just tried to remove the raw sub-protocol from the sample portal (Sunsoptdemo), and it didn't work as well, giving the same message (The coplet is currently not available) in the coplets I removed the raw from its definition. here what I've done : resource uri=cocoon:raw:/sunspotdemosunlet-onlinesundn.xml/ changed to resource uri=cocoon:/sunspotdemosunlet-onlinesundn.xml/ Also, a tiny error in the log ERROR (2002-08-21) 15:57.25:601 [core.portal-manager] (/last/samples/portal/sunspotdemo-portlets) Thread-13/CopletThread: Exception during processing of coplet: sundnnews org.apache.cocoon.ProcessingException: Relative cocoon: URIs currently not supported. at org.apache.cocoon.webapps.session.connector.Resource.init(Resource.java:93) at org.apache.cocoon.webapps.portal.components.CopletThread.run(CopletThread.java:157) at java.lang.Thread.run(Thread.java:484) Currently, to come over this problem, I use the cocoon:raw: but with adding a little action that store certain parameters in session for the coplets, but clearly that would be overkill if the requests should be available to the coplets. You have any ideas about that? And thanks for the quick info about the raw subprotocol. Best Regards. Carsten Ziegeler wrote: Ramy Mamdouh wrote: Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my coplets displayed. But when I changed to cocoon:/ without the raw, the portal displays the (The content is not avilable now) message ! Here's one of my coplets defintion. coplet id=menu resource uri=cocoon:raw:/menu/ configuration mandatorytrue/mandatory sizableflase/sizable activetrue/active timeout5000/timeout /configuration titleMenu/title status customizefalse/customize visibletrue/visible sizemax/size /status /coplet where menu is a normal pipeline. Does the change from cocoon:raw:/ to cocoon:/ requires any other changes, maybe in the coplet pipeline? Hmmm, usually not - but without raw: all parameters that where send to the main pipeline are send to the coplet as well, perhaps there is a problem? Actually, I don't know exactly what raw adds to cocoon: as a protocol, and I didn't find any information regarding this point (even in your very nice book with Matthew). ;) - Yes, the cocoon:raw protocol is very new and was added to Cocoon after we wrote the book, so The one and only distinction is, that with the subprotocol raw no request parameters are passed on to the called internal pipeline and without raw all are passed. Carsten - 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] -- Ramy Mamdouh Kamel Software Engineer Ute Imkenberg [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: Portal question [ the request parameters are available from inside the coplets?]
Ramy Mamdouh wrote: Hello Carsten, It seems I don't have any problems in my coplets. And to be sure, I just tried to remove the raw sub-protocol from the sample portal (Sunsoptdemo), and it didn't work as well, giving the same message (The coplet is currently not available) in the coplets I removed the raw from its definition. here what I've done : resource uri=cocoon:raw:/sunspotdemosunlet-onlinesundn.xml/ changed to resource uri=cocoon:/sunspotdemosunlet-onlinesundn.xml/ Also, a tiny error in the log ERROR (2002-08-21) 15:57.25:601 [core.portal-manager] (/last/samples/portal/sunspotdemo-portlets) Thread-13/CopletThread: Exception during processing of coplet: sundnnews org.apache.cocoon.ProcessingException: Relative cocoon: URIs currently not supported. at Ahh, great, you found a bug! - Ok, I will try to fix it asap - so currently you don't have a choice: you have to use cocoon:raw until the bug is fixed. Thanks! Carsten org.apache.cocoon.webapps.session.connector.Resource.init(Resour ce.java:93) at org.apache.cocoon.webapps.portal.components.CopletThread.run(Cople tThread.java:157) at java.lang.Thread.run(Thread.java:484) Currently, to come over this problem, I use the cocoon:raw: but with adding a little action that store certain parameters in session for the coplets, but clearly that would be overkill if the requests should be available to the coplets. You have any ideas about that? And thanks for the quick info about the raw subprotocol. Best Regards. Carsten Ziegeler wrote: Ramy Mamdouh wrote: Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my coplets displayed. But when I changed to cocoon:/ without the raw, the portal displays the (The content is not avilable now) message ! Here's one of my coplets defintion. coplet id=menu resource uri=cocoon:raw:/menu/ configuration mandatorytrue/mandatory sizableflase/sizable activetrue/active timeout5000/timeout /configuration titleMenu/title status customizefalse/customize visibletrue/visible sizemax/size /status /coplet where menu is a normal pipeline. Does the change from cocoon:raw:/ to cocoon:/ requires any other changes, maybe in the coplet pipeline? Hmmm, usually not - but without raw: all parameters that where send to the main pipeline are send to the coplet as well, perhaps there is a problem? Actually, I don't know exactly what raw adds to cocoon: as a protocol, and I didn't find any information regarding this point (even in your very nice book with Matthew). ;) - Yes, the cocoon:raw protocol is very new and was added to Cocoon after we wrote the book, so The one and only distinction is, that with the subprotocol raw no request parameters are passed on to the called internal pipeline and without raw all are passed. Carsten - 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] -- Ramy Mamdouh Kamel Software Engineer Ute Imkenberg [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Portal question [ the request parameters are available from inside the coplets?]
Hi Ramy, I just checked-in a fix - could you please test, if it now works for you? Thanks Carsten -Original Message- From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 21, 2002 3:15 PM To: [EMAIL PROTECTED] Subject: RE: Portal question [ the request parameters are available from inside the coplets?] Ramy Mamdouh wrote: Hello Carsten, It seems I don't have any problems in my coplets. And to be sure, I just tried to remove the raw sub-protocol from the sample portal (Sunsoptdemo), and it didn't work as well, giving the same message (The coplet is currently not available) in the coplets I removed the raw from its definition. here what I've done : resource uri=cocoon:raw:/sunspotdemosunlet-onlinesundn.xml/ changed to resource uri=cocoon:/sunspotdemosunlet-onlinesundn.xml/ Also, a tiny error in the log ERROR (2002-08-21) 15:57.25:601 [core.portal-manager] (/last/samples/portal/sunspotdemo-portlets) Thread-13/CopletThread: Exception during processing of coplet: sundnnews org.apache.cocoon.ProcessingException: Relative cocoon: URIs currently not supported. at Ahh, great, you found a bug! - Ok, I will try to fix it asap - so currently you don't have a choice: you have to use cocoon:raw until the bug is fixed. Thanks! Carsten org.apache.cocoon.webapps.session.connector.Resource.init(Resour ce.java:93) at org.apache.cocoon.webapps.portal.components.CopletThread.run(Cople tThread.java:157) at java.lang.Thread.run(Thread.java:484) Currently, to come over this problem, I use the cocoon:raw: but with adding a little action that store certain parameters in session for the coplets, but clearly that would be overkill if the requests should be available to the coplets. You have any ideas about that? And thanks for the quick info about the raw subprotocol. Best Regards. Carsten Ziegeler wrote: Ramy Mamdouh wrote: Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my coplets displayed. But when I changed to cocoon:/ without the raw, the portal displays the (The content is not avilable now) message ! Here's one of my coplets defintion. coplet id=menu resource uri=cocoon:raw:/menu/ configuration mandatorytrue/mandatory sizableflase/sizable activetrue/active timeout5000/timeout /configuration titleMenu/title status customizefalse/customize visibletrue/visible sizemax/size /status /coplet where menu is a normal pipeline. Does the change from cocoon:raw:/ to cocoon:/ requires any other changes, maybe in the coplet pipeline? Hmmm, usually not - but without raw: all parameters that where send to the main pipeline are send to the coplet as well, perhaps there is a problem? Actually, I don't know exactly what raw adds to cocoon: as a protocol, and I didn't find any information regarding this point (even in your very nice book with Matthew). ;) - Yes, the cocoon:raw protocol is very new and was added to Cocoon after we wrote the book, so The one and only distinction is, that with the subprotocol raw no request parameters are passed on to the called internal pipeline and without raw all are passed. Carsten - 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] -- Ramy Mamdouh Kamel Software Engineer Ute Imkenberg [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portal question [ the request parameters are available from insidethe coplets?]
Hello Carsten, Well, it seems that everything is working just fine now :) I made a quick test with the cocoon:/ protocol, and the request are available to the coplets correctly and ofcourse the error is not there anymore. Thanks a lot for this quick fix. Best Regards. Carsten Ziegeler wrote: Hi Ramy, I just checked-in a fix - could you please test, if it now works for you? Thanks Carsten -Original Message- From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 21, 2002 3:15 PM To: [EMAIL PROTECTED] Subject: RE: Portal question [ the request parameters are available from inside the coplets?] Ramy Mamdouh wrote: Hello Carsten, It seems I don't have any problems in my coplets. And to be sure, I just tried to remove the raw sub-protocol from the sample portal (Sunsoptdemo), and it didn't work as well, giving the same message (The coplet is currently not available) in the coplets I removed the raw from its definition. here what I've done : resource uri=cocoon:raw:/sunspotdemosunlet-onlinesundn.xml/ changed to resource uri=cocoon:/sunspotdemosunlet-onlinesundn.xml/ Also, a tiny error in the log ERROR (2002-08-21) 15:57.25:601 [core.portal-manager] (/last/samples/portal/sunspotdemo-portlets) Thread-13/CopletThread: Exception during processing of coplet: sundnnews org.apache.cocoon.ProcessingException: Relative cocoon: URIs currently not supported. at Ahh, great, you found a bug! - Ok, I will try to fix it asap - so currently you don't have a choice: you have to use cocoon:raw until the bug is fixed. Thanks! Carsten org.apache.cocoon.webapps.session.connector.Resource.init(Resour ce.java:93) at org.apache.cocoon.webapps.portal.components.CopletThread.run(Cople tThread.java:157) at java.lang.Thread.run(Thread.java:484) Currently, to come over this problem, I use the cocoon:raw: but with adding a little action that store certain parameters in session for the coplets, but clearly that would be overkill if the requests should be available to the coplets. You have any ideas about that? And thanks for the quick info about the raw subprotocol. Best Regards. Carsten Ziegeler wrote: Ramy Mamdouh wrote: Yes, I'm using the internal protocol ( cocoon:raw:/ ) in getting my coplets displayed. But when I changed to cocoon:/ without the raw, the portal displays the (The content is not avilable now) message ! Here's one of my coplets defintion. coplet id=menu resource uri=cocoon:raw:/menu/ configuration mandatorytrue/mandatory sizableflase/sizable activetrue/active timeout5000/timeout /configuration titleMenu/title status customizefalse/customize visibletrue/visible sizemax/size /status /coplet where menu is a normal pipeline. Does the change from cocoon:raw:/ to cocoon:/ requires any other changes, maybe in the coplet pipeline? Hmmm, usually not - but without raw: all parameters that where send to the main pipeline are send to the coplet as well, perhaps there is a problem? Actually, I don't know exactly what raw adds to cocoon: as a protocol, and I didn't find any information regarding this point (even in your very nice book with Matthew). ;) - Yes, the cocoon:raw protocol is very new and was added to Cocoon after we wrote the book, so The one and only distinction is, that with the subprotocol raw no request parameters are passed on to the called internal pipeline and without raw all are passed. Carsten - 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] -- Ramy Mamdouh Kamel Software Engineer Ute Imkenberg [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ramy Mamdouh
RE: Portal question [ the request parameters are available from inside the coplets?]
Ramy,
the coplet needs to be configured to handle parameters. Check the
handlesParameters entry in the portal documentation. This is optional - so
you will need to turn it on using the portal tool or by editing the coplet
profile.
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
=
-Original Message-
From: Ramy Mamdouh [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 20, 2002 4:57 PM
To: [EMAIL PROTECTED]
Subject: Portal question [ the request parameters are available from
inside the coplets?]
Hello,
I have a small portal [cocoon 2.1-dev] question here.
The requests parameters passed to the main portal pipeline (that one
containing the portal generator) are available to the coplets?
I mean if we invoked the portal generator pipeline with some parameters
(e.g /index?abc=10), where /index matchs to the portal generator,
Is this abc parameter available to all the coplets??
Thanks
--
Ramy Mamdouh Kamel
[EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portal question [ the request parameters are available from insidethe coplets?]
Hi Matthew,
Thanks for replying, but handlesParameters just handles the parameters
of the portal engine (like size, customize, etc).
And handlesParameters is true by default.
What I'm asking about is handling any other parameters passed with the
main portal uri.
handlesParameters has no effect as -it seems to me- regarding these
parameters, it just handles the portal engine parameters.
Am I missing something here??
Best Regards.
Matthew Langham wrote:
Ramy,
the coplet needs to be configured to handle parameters. Check the
handlesParameters entry in the portal documentation. This is optional - so
you will need to turn it on using the portal tool or by editing the coplet
profile.
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
=
-Original Message-
From: Ramy Mamdouh [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 20, 2002 4:57 PM
To: [EMAIL PROTECTED]
Subject: Portal question [ the request parameters are available from
inside the coplets?]
Hello,
I have a small portal [cocoon 2.1-dev] question here.
The requests parameters passed to the main portal pipeline (that one
containing the portal generator) are available to the coplets?
I mean if we invoked the portal generator pipeline with some parameters
(e.g /index?abc=10), where /index matchs to the portal generator,
Is this abc parameter available to all the coplets??
Thanks
--
Ramy Mamdouh Kamel
[EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ramy Mamdouh Kamel
Software Engineer
Ute Imkenberg
[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: Portal question
Hi Paul, well we wrote the portal components currently in Cocoon, so I guess I can comment on them :-). We originally (1 1/2 years ago) looked at JetSpeed (back then) but decided we didn't want a solution that was an add-on to Cocoon. We wanted to integrate a solution into Cocoon and do this with components that adhere to the Cocoon architecture. And the portal is completely XML / XSL / Cocoon pipeline based. You can find a first overview of the portal here: http://www.need-a-cake.com/stories/2002/02/14/cocoonPortalFirstLook.html You might also like to look here: http://www.sparkasse-gelsenkirchen.de This is a live financial portal (in German) using the components. Login with guest / guest. Perhaps you can post some specific questions on what you want to do and then I can comment on whether this is currently possible with the solution. How does that sound? plug Depending on where you are in the world :-). You might also consider going to one of these - where we will be presenting the portal: http://www.jax2002.de http://conferences.oreillynet.com/os2002/ /plug Best regards Matthew Langham -- Open Source Group sunShine - Lighting up e:Business = Matthew Langham, SN AG, Klingenderstrasse 5, D-33100 Paderborn Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de Weblogging at: http://www.need-a-cake.com Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352 = -Original Message- From: Paul Pattison [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 6:53 AM To: Cocoon Mailing List Subject: Portal question I'm looking to develop a xml portal web application. So far I'm loving Cocoon. Now I'm just trying to figure out how to tackle the portal side of things... I've read up a bit on sunSpot and JetSpeed. It sounds like they're pretty similar. Could someone who's actually used them comment on the pros and cons of each one? Thanks, Paul - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.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/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
