Oh gosh... I'm terribly sorry to have confused you, because it DOES work on v2.0.1 !
I guess my problem was that during my testing I didn't give enough time to Jetspeed to clear its cache and reload the PSML correctly... Adding to that, the PSML I was using during the latest tests, had the security-constraint set to the layout fragment (containing the portlet fragments). Now they are set to the portlet ones, and it's working ! Well then, if it's working in 2.0.1, it should for 2.1 likewise. My mistake, Ludovic > Well Aaron, > > The work I have taken involves creating a new portal app. That's why I > wouldn't like to skip step 4 since it'd still be required for later > developments anyway. > On the other hand, since you've got a 2.1-dev upish already, maybe you > could test and confirm that security-constraints does work inside fragment > scope ? ;) > > Again, here's my goal : >>> >> >> <page ...> >>> >> >> <security-constraints> >>> >> >> <security-constraint> >>> >> >> <groups>groupOne,groupTwo</groups> >>> >> >> <permissions>view</permissions> >>> >> >> </security-constraint> >>> >> >> </security-constraints> >>> >> >> >>> >> >> <fragment ... type="layout"> >>> >> >> <fragment ... type="portlet"> >>> >> >> <security-constraints> >>> >> >> <security-constraint> >>> >> >> <groups>groupOne</groups> >>> >> >> </security-constraint> >>> >> >> <security-constraint> >>> >> >> <groups>groupTwo</groups> >>> >> >> <permissions>view</permissions> >>> >> >> </security-constraint> >>> >> >> </security-constraints> > > By the way, I have omitted one step when writing my procedure in the mail, > which was "maven allClean allBuild"... AFAIR, allClean goal clears the > maven cache like you mention. > > Ludovic > > >> I built from source (SVN head) using the 2.1-dev plugin the other day >> and it worked fine. You have to make sure you clear your maven cache >> and download the 2.1-dev plugin first >> and then follow the instructions for building from source. >> >> For building from source for these instructions: >> >> http://portals.apache.org/jetspeed-2/getting-started-source.html >> >> substitute 2.1-dev for the plugin version and skip section 4 but do >> section 5, "Build Jetspeed 2 from source". >> >> -aaron >> >> >> >> On 8/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >>> Randy, >>> >>> I wish I could help you testing, but I can't even succeed in deploying >>> a >>> J2.1 portal ! ;( >>> >>> So far, I've been following the same procedure (which works fine for >>> v2.0 >>> and v2.0.1) : >>> - edit build.properties >>> - check out from SVN (v2.0.1 and v2.1) or download from Maven (v2.0) >>> - maven initMavenPlugin >>> - maven j2:portal.genapp >>> - add missing wars to /target/jetspeed/WEB-INF/deploy >>> - maven war:install >>> - deploy war using Tomcat Manager >>> >>> Sorry if this is getting a bit out of topic, but here's the log : >>> INFO: Jetspeed Starting Initialization... >>> INFO: JetspeedServlet identifying web application root... >>> INFO: JetspeedServlet identifed web application root as >>> /usr/local/tomcat/webapps/jetspeed/ >>> INFO: JetspeedServlet attempting to create the portlet engine... >>> FATAL: Jetspeed: init() failed: java.lang.InstantiationError: >>> org.apache.jetspeed.JetspeedActions at >>> org.apache.jetspeed.JetspeedPortalContext.<init>(JetspeedPortalContext.java:77) >>> >>> Ludovic >>> >>> >>> > Ludovic, >>> > >>> > Ok. I'll see if I can get to testing in a few days. I am slammed with >>> > overly aggressive non J2 schedules at the moment. If you do find more >>> > information in the interim, please add it to this thread. >>> > >>> > Randy >>> > >>> > On Mon, 2006-08-28 at 08:09 +0200, [EMAIL PROTECTED] wrote: >>> >> Randy, >>> >> >>> >> I will try to test on 2.1 tomorrow, even though I highly doubt >>> migrating >>> >> to a "beta" version of J2 will make its way to prod... I so wish >>> there >>> >> could be a "stable" release with this feature integrated already. >>> >> >>> >> Hmm.. at worst, I think there's still a way to simulate this by >>> >> duplicating the whole page and putting the correct constraints on a >>> >> page-basis. Really not flexible, but in the meantime... >>> >> >>> >> One more thing: is there a readable log of modifications brought in >>> at >>> >> each version of J2 ? >>> >> >>> >> Thanks, >>> >> Ludovic >>> >> >>> >> >>> >> > Ludovic, >>> >> > >>> >> > Any way you can try this on the 2.1-dev/svn HEAD release? I'm a >>> bit >>> >> > pressed for time these days, but I'll give you a hand if you still >>> see >>> >> > the issue with 2.1-dev... yes, it should work. >>> >> > >>> >> > Randy >>> >> > >>> >> > On Fri, 2006-08-25 at 22:42 +0200, [EMAIL PROTECTED] >>> wrote: >>> >> >> Hi, >>> >> >> >>> >> >> Sorry to revive that old subject, but it looks like it's exactly >>> the >>> >> >> problem I am encountering. Basically here's what I'm trying to >>> >> achieve : >>> >> >> <page ...> >>> >> >> <security-constraints> >>> >> >> <security-constraint> >>> >> >> <groups>groupOne,groupTwo</groups> >>> >> >> <permissions>view</permissions> >>> >> >> </security-constraint> >>> >> >> </security-constraints> >>> >> >> >>> >> >> <fragment ... type="layout"> >>> >> >> <fragment ... type="portlet"> >>> >> >> <security-constraints> >>> >> >> <security-constraint> >>> >> >> <groups>groupOne</groups> >>> >> >> </security-constraint> >>> >> >> <security-constraint> >>> >> >> <groups>groupTwo</groups> >>> >> >> <permissions>groupTwo</permissions> >>> >> >> </security-constraint> >>> >> >> </security-constraints> >>> >> >> However, "groupOne" still has the rights to view the portlet... >>> >> >> >>> >> >> According to the replies, it *should* be possible, even if I am >>> >> reading >>> >> >> "Note that only the view permission is checked against these >>> >> >> constraints" >>> >> >> here: >>> >> >> http://portals.apache.org/jetspeed-2/guides/guide-security-declarative-psml.html >>> >> >> Just like Randy suggested, I have upgraded to 2.0.1, but still no >>> >> >> results. >>> >> >> >>> >> >> Does anyone see something else I could try ? >>> >> >> >>> >> >> Thanks, >>> >> >> Ludovic >>> >> >> >>> >> >> >>> >> >> > If you use eclipse, I suggest using the subclipse plugin... >>> >> >> > >>> >> >> > On 7/6/06, Enrique Perez <[EMAIL PROTECTED]> wrote: >>> >> >> >> Hi Randy, >>> >> >> >> >>> >> >> >> Ok, so I must install svn, get the source with that command >>> you >>> >> >> pointed >>> >> >> >> me out and follow the instructions described here >>> >> >> >> (http://portals.apache.org/jetspeed-2/getting-started-source.html, >>> >> >> >> sections 5&6), mustn't I? >>> >> >> >> Is it the same for 2.1-dev?? >>> >> >> >> >>> >> >> >> Thanks a lot, >>> >> >> >> Enrique >>> >> >> >> >>> >> >> >> >>> >> >> >> > -----Mensaje original----- >>> >> >> >> > De: Randy Watler [mailto:[EMAIL PROTECTED] >>> >> >> >> > Enviado el: miÃ(c)rcoles, 05 de julio de 2006 16:46 >>> >> >> >> > Para: Jetspeed Users List >>> >> >> >> > Asunto: RE: Security constraints for fragments >>> >> >> >> > >>> >> >> >> > Enrique, >>> >> >> >> > >>> >> >> >> > One must build that version from source. The 2.0.1 has not >>> been >>> >> >> pushed >>> >> >> >> > to the maven repository. Use the svn command below to pull >>> the >>> >> >> source >>> >> >> >> > and follow the instructions on building from source on the >>> web >>> >> >> site. >>> >> >> >> > >>> >> >> >> > HTH, >>> >> >> >> > >>> >> >> >> > Randy >>> >> >> >> > >>> >> >> >> > On Wed, 2006-07-05 at 13:29 +0200, Enrique Perez wrote: >>> >> >> >> > > Sorry Randy, >>> >> >> >> > > >>> >> >> >> > > But still don't know how to install that specific >>> version... >>> >> =S >>> >> >> >> > > I've tried to download "jetspeed plugin" (-Dversion=2.0.1) >>> but >>> >> >> maven >>> >> >> >> is >>> >> >> >> > > unable to find it in any repository... >>> >> >> >> > > >>> >> >> >> > > Is there any getting-started-guide for this release? Any >>> >> >> >> step-by-step >>> >> >> >> > > document?? >>> >> >> >> > > >>> >> >> >> > > Thanks, >>> >> >> >> > > Enrique >>> >> >> >> > > >>> >> >> >> > > > -----Mensaje original----- >>> >> >> >> > > > De: Randy Watler [mailto:[EMAIL PROTECTED] >>> >> >> >> > > > Enviado el: martes, 04 de julio de 2006 17:10 >>> >> >> >> > > > Para: Jetspeed Users List >>> >> >> >> > > > Asunto: RE: Security constraints for fragments >>> >> >> >> > > > >>> >> >> >> > > > Enrique, >>> >> >> >> > > > >>> >> >> >> > > > svn co >>> https://svn.apache.org/repos/asf/portals/jetspeed- >>> >> >> >> > > > 2/branches/JETSPEED-BRANCH-2.0.1 jetspeed-2 >>> >> >> >> > > > >>> >> >> >> > > > Yes, I believe that the sizes property was broken in 2.0 >>> as >>> >> >> well. >>> >> >> >> I >>> >> >> >> > > > think 2.0.1 fixes that as well. Nested layouts were >>> >> initially >>> >> >> >> fixed in >>> >> >> >> > > > 2.0.1, but Ate put in a ton of work to make them much >>> better >>> >> in >>> >> >> >> > > 2.1-dev. >>> >> >> >> > > > >>> >> >> >> > > > Randy >>> >> >> >> > > > >>> >> >> >> > > > On Tue, 2006-07-04 at 09:48 +0200, Enrique Perez wrote: >>> >> >> >> > > > > Hi Randy, >>> >> >> >> > > > > >>> >> >> >> > > > > Where can I find the version 2.0.1?? Or how can I >>> build >>> >> that >>> >> >> >> version >>> >> >> >> > > > > with Maven 1.0.2?? Maybe modifying build.properties >>> and >>> >> >> setting >>> >> >> >> > > > > "jetspeed.version" to the value "2.0.1"?? >>> >> >> >> > > > > >>> >> >> >> > > > > And do you know if there is also a bug with the >>> fragment's >>> >> >> >> property >>> >> >> >> > > for >>> >> >> >> > > > > setting the size of the columns in my version?? I >>> mean, >>> >> I'm >>> >> >> >> trying >>> >> >> >> > > to >>> >> >> >> > > > > set 20% for left column and 80% for right one with >>> this >>> >> tag: >>> >> >> >> > > > > <fragment id="x" type="layout" >>> >> >> >> > > > > name="jetspeed-layouts::VelocityTwoColumns"> >>> >> >> >> > > > > <property layout="TwoColumns" >>> name="sizes" >>> >> >> >> > > > > value="20%,80%"/> >>> >> >> >> > > > > >>> >> >> >> > > > > but it seems to have no effect. >>> >> >> >> > > > > >>> >> >> >> > > > > Thanks again, >>> >> >> >> > > > > Enrique >>> >> >> >> > > > > >>> >> >> >> > > >>> >> >> >> > > >>> >> >> >> > > >>> >> >> >> > > >>> >> >> >> --------------------------------------------------------------------- >>> >> >> >> > > 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] >>> >> >> >>> >> >> >>> >> > >>> >> > >>> >> > --------------------------------------------------------------------- >>> >> > 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] >> >> > > > > > > --------------------------------------------------------------------- > 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]
