Simples Assim

Refer to the 3.1 section of the Reference Guide.

The next generation of JBoss Portal.

http://www.jboss.org/gatein/

http://pedentello.wordpress.com/2009/08/18/criando-um-projeto-com-apache-maven-archetype-portlet-bridge-jboss/

https://jira.jboss.org/jira/browse/JBPORTAL-2445 (vote for it!)

You can try to work around with 1.0.7, that worked for me.

Red Hat will continue to focus it’s JBoss Community Portal resources on high performance infrastructure and containers, security and rich application integration, while eXo will be contributing and continuing to evolve their excellent user interface and administration features.

Looks like very good news for the community.

http://press.redhat.com/2009/06/10/jboss-org-community-grows/

http://exoplatform.com/portal/public/website/aboutUS/eXoJBossPartnership

1) Add to the jboss-portal.sar/conf/identity/profile-config.xml file:

<property>
  <name>property</name>
  <type>java.lang.String</type> <!-- Mandatory -->
  <access-mode>read-write</access-mode>
  <usage>mandatory</usage>
  <display-name xml:lang="en">Display Name</display-name>
  <description xml:lang="en">Description</description>
  <mapping>
    <database>
      <type>dynamic</type>
      <value>propertyname</value>
    </database>
  </mapping>
</property>

2) Add to the jboss-portal.sar/portal-identity.sar/conf/identity-ui-configuration.xml file:

<ui-component name="property">
  <property-ref>property</property-ref>
  <required>true</required>
</ui-component>

3) Add to the resource bundle(s):

IDENTITY_PROPERTY=Property

4) Add to the jboss-portal-sar/portal-identity.sar/portal-identity.war/jsf/common/editProfileInfo.xhtml file:

<h:panelGroup>
  <h:outputText value="#{bundle.IDENTITY_PROPERTY}"/>
  <h:outputText value=" *" rendered="#{metadataservice.property.required}" />
</h:panelGroup>
<h:inputText id="#{metadataservice.property.name}" value="#{manager.uiUser.attribute.property}" required="#{metadataservice.property.required}"/>
<h:panelGroup />
<h:message for="#{metadataservice.property.name}" infoClass="portlet-msg-success" errorClass="portlet-msg-error" fatalClass="portlet-msg-error" warnClass="portlet-msg-alert"/>

5) Add to the jboss-portal-sar/portal-identity.sar/portal-identity.war/jsf/common/register.xhtml file:

<h:panelGroup>
  <h:outputText value="#{bundle.IDENTITY_PROPERTY}"/>
  <h:outputText value=" *" rendered="#{metadataservice.property.required}" />
</h:panelGroup>
<h:inputText id="#{metadataservice.property.name}" value="#{manager.uiUser.attribute.property}" required="#{metadataservice.property.required}" />
<h:panelGroup />
<h:message for="#{metadataservice.property.name}" infoClass="portlet-msg-success" errorClass="portlet-msg-error" fatalClass="portlet-msg-error" warnClass="portlet-msg-alert"/>

6) Add to the jboss-portal-sar/portal-identity.sar/portal-identity.war/jsf/common/viewProfileInfo.xhtml file:

<h:outputText value="#{bundle.IDENTITY_PROPERTY}:" rendered="#{editprofilemgr.uiUser.attribute.property != null}"/>
<h:outputText value="#{editprofilemgr.uiUser.attribute.property}" rendered="#{editprofilemgr.uiUser.attribute.property != null}"/>
<h:outputText value="#{bundle.IDENTITY_PROPERTY}"/>
<h:outputText id="#{metadataservice.property.name}" value="#{manager.uiUser.attribute.property}"/>
<h:panelGroup />

https://jira.jboss.org/jira/browse/JBPORTAL-2383 (vote for it!)

http://fernandoribeiro.eti.br/2009/02/02/xmllang-attribute/

Thanks to Paulo for the original report.

According to the Portlets 2.0 spec, if a portlet throws an exception in the processAction or processEvent method, all operations on the ActionResponse must be ignored including set events [e.g setRenderParameter]. The 5 portal/portlet-container should continue processing the other portlets visible in the portal page.

It also says that it is up to the portlet container implementation if the error is faced to the end user, the portlet is removed from the current request cycle or if the render method of the portlet is called.

In JBoss Portal, the responses are cleared and the render methods are called.

With the release of Alfresco v3.x a few months ago, the options for integrating with a portal or other custom web application have greatly increased.

Nice arguments, but I don’t think we should drop web scripts in favor of CMIS before it turns 1.0.

http://blogs.citytechinc.com/jeffbrown/?p=29

http://jboss.org/index.html?module=bb&op=viewtopic&p=4220720#4220720

https://jira.jboss.org/jira/browse/JBPORTAL-2350 (vote for it!)