[JBoss Portal] - Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
by thomas.heute@jboss.com
"swestbom" wrote : JBoss Portal has sort of lost its way as well. There are more and more features in the Portal that have nothing to do with JSR-168 and everything to do with bells and whistles for marketing. It would be far more useful if they were to do something like create a portal bridge for AJAX4JSF or better document the security module implementation.
JSR-168 portlet contained is implemented and is not much, customers and community wants something that they can use out of the box, if they can't manage pages, can't have a dashboard and so on, it's not usable. This is not about marketing, this is about value-added.
Ajax4JSF (then RichFaces) support is on the way, but we also need to define some standards, Stan Silvert and Julien Viet are part of JSR-301 to define the JSF bridge first. Same thing for a full support of JBoss Seam)
I don't know what you mean by "security module implementation" but if you are talking about the identity related authentication and authorization mechanism, you should have a look at the nightly build of the documentation. If something is missing let us know.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047100#4047100
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047100
18 years, 11 months
[JBoss Portal] - Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
by thomas.heute@jboss.com
"bsmithjj" wrote : One comment on the google gadget thingy - I have nothing against a google-gadget portlet or add-on module, but I really think that JBoss Portal would do better if it was a delivered as a basic Portal 'engine' with a lot of the bells and whistles available as easy-drop-in add ons. Unfortunately, a lot of the bells and whistles (such as a google-gadget portlet) are simply lumped into the basic portal - making the whole product complex, hard to document, and fragile at times.
| Splitting the Portal into logical pieces allows each piece to evolve independently - most likely the core engine won't change too much because the fundamental building blocks are a JSR168 portlet container plus the paging and customization system.
|
Again all the bells and whistles are totally pluggable.
Look into jboss-portal.sar ou have several packages, remove what you don't want.
You don't want the google widgets ? Delete widget.war, everything related to it will be removed. You don't like the CMS ? remove portal-cms.war. You don't want the test pages and news portlets ? Remove portal-samples.war...
If we don't put it as default noone see that we have it.
What is interesting about Google widget is to show you that you can integrate other kind of stuff (Content-types). Out of the box we show you that you can put in a window: A JSR-168 portlet, a CMS resource, a Google widget, the content of a file, *Your content type*...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047099#4047099
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047099
18 years, 11 months