| Author |
Message |
|
|
Tony,
I was not disagreeing by smiling. Didn't mean it as a diss. I'm sorry if it may have seemed that way. I was being terse for a reason. It's more of a shared all-knowing sort of smile. Terse because if I start ranting on the subject of acegi and jboss I might go all night long. And icesoft is not going to like what I have to say. I have no opinion about seam - was just looking from curiosity. Not going to do seam just yet. Too bleeding edge. Will look at it later. Meanwhile, keep up the good work!
dclounch
"Must control fist of death"
- Alice (from Dilbert)
|
 |
|
|
"p.s. Perhaps there is a good reason the seam team did not choose to use Acegi to begin with?"
;)
|
 |
|
|
Acegi filtering worked fine once Brad K. distributed the JSP to JSF bridge example version. And it works absolutely fantastic on tomcat. I have example pages with renderedOnUserRole working.
Alas, doesn't work in JBoss. I am going bald - no hair left to pull out.
There are JBoss examples available for non-filtering acegi scenarios. Sigh. Can't use those. I really like acegi....but.....
The problem with acegi is the spring hierarchical dynamic class loading is slightly different than the typical JBoss dynamic class loading, and I haven't found the magic combination. Jboss dynamic class loading is a bit of an advanced topic. Maybe there are folks out there who would say, "naw, its baby simple". But I am not at that point yet. And thats all before one adds in the spring differences. I've been ordered by management to stop wasting time on it.
Icefaces being in LifeRay doesn't help much because
we are also not using portals of any type. Just plain old JSF/IceFaces on JBossAS. Not using portals is important when considering acegi because various forum chatter seems to say acegi filtering doesnt work in portlets.
I basically started looking at JBoss4.2 + Seam yesterday because I discovered it uses SunRI now instead of MyFaces. And like I say, dvdstore being all JSF is impressive.
So, when will an icefaces demo like dvdstore be available? (hint hint) ;)
The showcase is one thing. Role based rendering is something else.
Thanks!
|
 |
|
|
I got the seam 1.3 source from cvs and it built ok. Its truly impressive seeing dvdstore run. Dvdstore is JSF pages with facelets and its encouraging to see it on jboss 4.2.0.GA. And even I could build it! :)
But I haven't yet sorted through all the mix'n'match patchwork quilt of the component showcase. If icefaces was in a demo like the dvdstore I would turn cartwheels. Dvdstore seems to do pretty much everything I currently want in a starter application, except run icefaces and acegi filters. Now, if we had a jboss portal or even a plain old jboss app (non-portal) that allowed acegi filtering and icefaces and facelets all in one, life would be sweet indeed. Alas, I ask too much, I know.
|
 |
|
|
jtp51 wrote:
David: My other approach did not work. I tried to use the MyFaces Tomahawk example - but of course that was wrong and doesn't work.
What MyFaces has in their Wiki for a acegi-security solution is wrong. I confirmed this on the Springframework forums.
Therefore, I will give up the nice JSF components for the login screen and use a .jsp page.
I tried the bean approach, but the information is so uncomplete, it's a waste of time.
If your interested, I've attached my login.jspx with the Tomahawk references.
Acegi-security does not work with the Controller model of JSF.
This is not an ICEfaces issue, just a JSF issue.
Thanks,
--Todd
About a year later I am wondering if things are better? I was looking at Phil's forwarding of variables via the loginProxyBean class. Does that help?
Or should I just give up now? I can see the j_username and j_password being set in the map, but is that enough? I am still not getting authenticated with good credentials.
I am new to icefaces and I am concerned about how to get renderedOnUserRole set up properly with authentication and authorization. If Acegi is hopeless then is there another framework that works with JSF/ice?
|
 |
|
|