[JBoss Portal Development] - Re: Jboss portal on JBoss AS5
by soheil_has
I got the same error and I managed to solve it.
The problem is with the xml schema of portal-identity (core-identity/src/resources/portal-identity-sar/conf/schema/identity-ui-configuration.xsd)
| <?xml version="1.0"?>
| <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| ~ JBoss, a division of Red Hat ~
| ~ Copyright 2006, Red Hat Middleware, LLC, and individual ~
| ~ contributors as indicated by the @authors tag. See the ~
| ~ copyright.txt in the distribution for a full listing of ~
| ~ individual contributors. ~
| ~ ~
| ~ This is free software; you can redistribute it and/or modify it ~
| ~ under the terms of the GNU Lesser General Public License as ~
| ~ published by the Free Software Foundation; either version 2.1 of ~
| ~ the License, or (at your option) any later version. ~
| ~ ~
| ~ This software is distributed in the hope that it will be useful, ~
| ~ but WITHOUT ANY WARRANTY; without even the implied warranty of ~
| ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ~
| ~ Lesser General Public License for more details. ~
| ~ ~
| ~ You should have received a copy of the GNU Lesser General Public ~
| ~ License along with this software; if not, write to the Free ~
| ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA ~
| ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org. ~
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-->
|
| <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb"
| elementFormDefault="qualified">
|
| <xsd:element name="identity-ui-configuration">
| <xsd:complexType>
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:class impl="org.jboss.portal.core.identity.services.metadata.IdentityUIConfiguration"/>
| </xsd:appinfo>
| </xsd:annotation>
|
| <xsd:sequence>
| <!-- User portlet and user management portlet preferences -->
| <xsd:element name="subscription-mode" type="subscriptionMode" default="jbp_identity_validation_workflow"/>
| <xsd:element name="admin-subscription-mode" type="subscriptionMode" default="automatic"/>
| <xsd:element name="overwrite-workflow" type="xsd:boolean" default="false"/>
| <xsd:element name="email-domain" minOccurs="1" maxOccurs="1" type="xsd:string" default="example.com" />
| <xsd:element name="email-from" minOccurs="1" maxOccurs="1" type="xsd:string" default="no-reply(a)example.com" />
| <xsd:element name="password-generation-characters" minOccurs="1" maxOccurs="1" type="xsd:string"/>
| <xsd:element name="default-roles" type="defaultRoles" minOccurs="1" maxOccurs="1"/>
|
| <!-- user interface components -->
| <xsd:element name="ui-components">
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:class impl="java.util.HashMap"/>
| </xsd:appinfo>
| </xsd:annotation>
| <xsd:complexType>
| <xsd:sequence>
| <xsd:element name="ui-component" minOccurs="1" maxOccurs="unbounded" type="UIComponent" />
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
| <!-- end: user interface components -->
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
|
| <!-- restictions for subscription-modes -->
|
| <xsd:simpleType name="subscriptionMode">
| <xsd:restriction base="xsd:string">
| <xsd:enumeration value="custom" />
| <xsd:enumeration value="automatic" />
| <xsd:enumeration value="jbp_identity_validation_workflow" />
| <xsd:enumeration value="jbp_identity_validation_approval_workflow" />
| </xsd:restriction>
| </xsd:simpleType>
|
| <xsd:complexType name="defaultRoles">
| <xsd:sequence>
| <xsd:element name="role" minOccurs="1" type="xsd:string" maxOccurs="unbounded"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:complexType name="validators">
| <xsd:sequence>
| <xsd:element name="validator" minOccurs="1" type="xsd:string" maxOccurs="unbounded"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:complexType name="componentValues">
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:mapEntry nonNullValue="true"/>
| </xsd:appinfo>
| </xsd:annotation>
| <xsd:choice minOccurs="1" maxOccurs="1">
| <xsd:element name="value" maxOccurs="unbounded">
| <xsd:complexType>
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:mapEntry/>
| <jbxb:characters>
| <jbxb:mapEntryValue/>
| </jbxb:characters>
| </xsd:appinfo>
| </xsd:annotation>
| <xsd:simpleContent>
| <xsd:extension base="xsd:string">
| <xsd:attribute name="key" type="xsd:string">
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:mapEntryKey/>
| </xsd:appinfo>
| </xsd:annotation>
| </xsd:attribute>
| </xsd:extension>
| </xsd:simpleContent>
| </xsd:complexType>
| </xsd:element>
| </xsd:choice>
| </xsd:complexType>
|
| <xsd:complexType name="UIComponent">
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:mapEntry impl="org.jboss.portal.core.identity.services.metadata.UIComponentConfiguration" getKeyMethod="getName" setKeyMethod="setName" />
| </xsd:appinfo>
| </xsd:annotation>
| <xsd:sequence>
| <xsd:element name="property-ref" maxOccurs="1" minOccurs="1" type="xsd:string" />
| <xsd:element name="localization-bundle" type="xsd:string" minOccurs="0" maxOccurs="1"/>
| <xsd:element name="validators" type="validators" minOccurs="0"/>
| <xsd:element name="converter" type="xsd:string" minOccurs="0" />
| <xsd:element name="required" type="xsd:boolean" default="false" minOccurs="0"/>
| <xsd:element name="read-only" type="xsd:boolean" default="false" minOccurs="0"/>
| <xsd:element name="values" type="componentValues" minOccurs="0">
| <xsd:annotation>
| <xsd:appinfo>
| <jbxb:class impl="java.util.HashMap"/>
| </xsd:appinfo>
| </xsd:annotation>
| </xsd:element>
| </xsd:sequence>
| <!-- attribute name -->
| <xsd:attribute name="name" type="xsd:string" use="required" />
| </xsd:complexType>
|
| </xsd:schema>
|
|
And also I have made a simple change to core-identity/src/resources/portal-identity-sar/conf/identity-ui-configuration.xml
| <?xml version="1.0" encoding="UTF-8"?>
| <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| ~ JBoss, a division of Red Hat ~
| ~ Copyright 2006, Red Hat Middleware, LLC, and individual ~
| ~ contributors as indicated by the @authors tag. See the ~
| ~ copyright.txt in the distribution for a full listing of ~
| ~ individual contributors. ~
| ~ ~
| ~ This is free software; you can redistribute it and/or modify it ~
| ~ under the terms of the GNU Lesser General Public License as ~
| ~ published by the Free Software Foundation; either version 2.1 of ~
| ~ the License, or (at your option) any later version. ~
| ~ ~
| ~ This software is distributed in the hope that it will be useful, ~
| ~ but WITHOUT ANY WARRANTY; without even the implied warranty of ~
| ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ~
| ~ Lesser General Public License for more details. ~
| ~ ~
| ~ You should have received a copy of the GNU Lesser General Public ~
| ~ License along with this software; if not, write to the Free ~
| ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA ~
| ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org. ~
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-->
|
| <identity-ui-configuration>
| <!--
| subscription mode - defines the workflow used for registering users
| available default options:
| - automatic: No email validation, No admin approval
| - jbp_identity_validation_workflow: Email verification, No admin approval
| - jbp_identity_validation_approval_workflow: Email verification, Admin approval
| -->
| <subscription-mode>automatic</subscription-mode>
|
| <admin-subscription-mode>automatic</admin-subscription-mode>
| <!--
| overwrite-workflow: overwrites existing process definitions
| -->
| <overwrite-workflow>false</overwrite-workflow>
| <!--
| email-domain: used in the email template sent for email verification
| -->
| <email-domain>jboss.org</email-domain>
| <!--
| email-from: sender address
| -->
| <email-from>do-no-reply(a)jboss.com</email-from>
| <!--
| password-generation-characters: characters used for generating a random password
| -->
| <password-generation-characters>0123456789aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWyYzZ*#!+-/"</password-generation-characters>
| <!--
| default-roles: roles set on user registration
| -->
| <default-roles>
| <role>User</role>
| </default-roles>
|
| <!-- user interface components -->
| <ui-components>
| <ui-component name="givenname">
| <property-ref>user.name.given</property-ref>
| </ui-component>
| <ui-component name="familyname">
| <property-ref>user.name.family</property-ref>
| </ui-component>
| <ui-component name="location">
| <property-ref>portal.user.location</property-ref>
| </ui-component>
| <ui-component name="occupation">
| <property-ref>portal.user.occupation</property-ref>
| </ui-component>
| <ui-component name="extra">
| <property-ref>portal.user.extra</property-ref>
| </ui-component>
| <ui-component name="signature">
| <property-ref>portal.user.signature</property-ref>
| </ui-component>
| <ui-component name="interests">
| <property-ref>portal.user.interests</property-ref>
| </ui-component>
| <ui-component name="icq">
| <property-ref>portal.user.im.icq</property-ref>
| </ui-component>
| <ui-component name="aim">
| <property-ref>portal.user.im.aim</property-ref>
| </ui-component>
| <ui-component name="msnm">
| <property-ref>portal.user.im.msnm</property-ref>
| </ui-component>
| <ui-component name="yim">
| <property-ref>portal.user.im.yim</property-ref>
| </ui-component>
| <ui-component name="skype">
| <property-ref>portal.user.im.skype</property-ref>
| </ui-component>
| <ui-component name="xmmp">
| <property-ref>portal.user.im.xmmp</property-ref>
| </ui-component>
| <ui-component name="homepage">
| <property-ref>portal.user.homepage</property-ref>
| </ui-component>
| <ui-component name="securityquestion">
| <property-ref>portal.user.security.question</property-ref>
| </ui-component>
| <ui-component name="securityanswer">
| <property-ref>portal.user.security.answer</property-ref>
| </ui-component>
| <ui-component name="timezone">
| <property-ref>portal.user.time-zone-offset</property-ref>
| <values>
| <value key="org.jboss.portal.core.identity.timezone" />
| </values>
| </ui-component>
| <ui-component name="theme">
| <property-ref>portal.user.theme</property-ref>
| <values>
| <value key="org.jboss.portal.core.identity.theme" />
| </values>
| </ui-component>
| <ui-component name="locale">
| <property-ref>portal.user.locale</property-ref>
| <values>
| <value key="org.jboss.portal.core.identity.locale" />
| </values>
| </ui-component>
| <ui-component name="email">
| <property-ref>user.business-info.online.email</property-ref>
| <validators>
| <validator>EmailValidator</validator>
| </validators>
| <required>true</required>
| </ui-component>
| <ui-component name="registrationdate">
| <property-ref>portal.user.registration-date</property-ref>
| </ui-component>
| <ui-component name="enabled">
| <property-ref>portal.user.enabled</property-ref>
| </ui-component>
| <ui-component name="lastlogin">
| <property-ref>portal.user.last-login-date</property-ref>
| </ui-component>
| <ui-component name="nickname">
| <property-ref>user.name.nickName</property-ref>
| <required>true</required>
| </ui-component>
| </ui-components>
| </identity-ui-configuration>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252993#4252993
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252993
16 years, 1 month
[JBoss ESB Development] - Re: JBESB-2805 - Splitter EAI Pattern
by tfennelly
"rferreir" wrote : Actually, the current implementation can route separated messages for the services, since every route-to request contain a smooks trans. The idea behind this is: You pass for the splitter a huge message (eg: An Complete Order), and the splitter process each smooks trans for this message, and the resulting messages (Eg: Separeted Items) are routed for the services.
I must be reading the code incorrectly in that case Ricardo. I'll have a look at your example.
When I look at the code, it says to me, for each route-to config:
1. Apply a smooks.filterSource opp using the PayloadProcessor,
2. If there's a result, route it to the target service defined in the route-to.
So... as I read it, yes it may route multiple messages if there are multiple destinations configured, but it routes a max of one message to each destination for a given exec of the action. No?
"rferreir" wrote : But let's talk about improvements. I've not work yeat with this FragmentRouter, I'm going to learn how it works and try to use in the implementation. Could you help in this class usage?
|
| I've not found a description of this router in the programmers guide, I've only the source code. But it seems that I should instantiate a copy of this router for every routing that I'm planning to do, it's correct? If so, I've to pass a instance of a executionContext that wrapps a smooks transformed object.
Take a look at the smooks_file_splitter_router quickstart in the 4.6 release.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252885#4252885
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252885
16 years, 1 month