They dont share the same "js_peid". Does that help ? Nikhil
-----Original Message----- From: Mark Orciuch [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 2:18 PM To: Jetspeed Users List Subject: RE: Strange behaviour from the JSPAction class that uses setTemplate Ooops! All the JspPortlets on the page share the same request attribute now? I guess we'll have to use another means of storing the template. I'll try to work on this Monday. Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ > -----Original Message----- > From: Damle, Nikhil [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 31, 2003 1:56 PM > To: 'Jetspeed Users List' > Subject: Strange behaviour from the JSPAction class that uses > setTemplate > > > Starting off a new thread here. > > I was encountering problems using the setTemplate method within the > JSPAction subclass. Thanks to the fix that Mark Orciuch made, > setTemplate(..) works fine. > > However, the problem now is that all the JSPPortlets on the page use the > same template, even the JSP1_1andJetspeedTagLib. By that I mean the > contents within all the JSP portlets on the page are exactly the same. Did > anyone ever encounter this problem ? How can I fix this ? > > Thanks, > > Nikhil > > --------------------------------------------------------------------- > 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]
