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> >>>>> <mandatory>true</mandatory> >>>>> <sizable>flase</sizable> >>>>> <active>true</active> >>>>> <timeout>5000</timeout> >>>>> </configuration> >>>>> <title>Menu</title> >>>>> <status> >>>>> <customize>false</customize> >>>>> <visible>true</visible> >>>>> <size>max</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 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]>
