7 Replies Latest reply on Jun 8, 2007 12:38 AM by maiky

    About JBoss Portal 2.6 ...

    fquimbay

      Greetings ...

      I will think use JBoss Portal 2.6 for a project and I appreciate if you could help me answering this questions:

      1. Is JBoss Portal 2.6 sufficiently stable for a production project ?
      2. Is possible separate the portal tables and bussiness tables in diferent databases required for JBoss Portal Project ? This is advisable ?
      3. If we need to modify the behaviour of add users and roles (more or less fields in the form), any problem with the initial and stable behaviour of the JBoss Portal ?

      Thanks, for your help.

      --
      fabio quimbay

        • 1. Re: About JBoss Portal 2.6 ...
          theute

           

          "fquimbay" wrote:

          1. Is JBoss Portal 2.6 sufficiently stable for a production project ?


          JBoss Portal 2.4 is used in production in many places, 2.6 will be final late in June and is already used in production on jboss.org

          "fquimbay" wrote:

          2. Is possible separate the portal tables and bussiness tables in diferent databases required for JBoss Portal Project ? This is advisable ?


          Sure, as any web application, create any number of datasource you want.

          "fquimbay" wrote:

          3. If we need to modify the behaviour of add users and roles (more or less fields in the form), any problem with the initial and stable behaviour of the JBoss Portal ?


          You can add remove any number of user properties (those are Strings). For the form, just modify the form of the user portlet and the backend to take them into account.

          You can store those porperties in LDAP or database out of the box (or anywhere if you implement some interfaces)

          • 2. Re: About JBoss Portal 2.6 ...
            andres.bustamante

            Hi.

            I've got a question about the last topic: What are the implications of making a change in the backend of the users management? Is it necessary to recompile the source code of JBoss Portal to make my changes effective?

            Basically, I need to manage user and roles in a different way than just a portal access. Users are so much important for other bussiness logic. So, I'm not sure if it's a good idea to make changes directly on the users module already available in Portal, or maybe it could be better to make my own users module apart, using another database and under my own rules. In that case, I should disable the default portal users module, and actually, I don't know wheter it is possible or not, and how this could affect Portal functionality.

            Another interesting topic for me is Usability of software in my project. In the case I work over the modules that Portal currently offers, I could need to change some messages for the UI. How might I customise my outputs for final users? Again, should be necessary to recompile Portal sources to make my changes effective?

            Thanks.

            • 3. Re: About JBoss Portal 2.6 ...
              theute

              The user management is basically divided into 2 parts, a user service that takes care of storing user properties and the interface itself (the user portlet).

              What you can do is just work on the portlet that communicates with the service. You wouldn't have to touch the service itself.
              Of course you can use the existing portlet as a start and modify the existing one.

              It's flexible so you can drop part of the portal without afffecting the other components. (you can disable the embedded user portlet and add your own, you could also replace the user management service if you don't like it)

              Output for final users rely in portlets and themes, you can keep the portal framework, add your own portlets and layout/theme without having to recompile the sources.

              • 4. Re: About JBoss Portal 2.6 ...
                fquimbay

                Thomas ... Thank you very much.

                --
                fabio quimbay

                • 5. Re: About JBoss Portal 2.6 ...
                  theute

                  You're very welcome :)

                  By the way our new blog contains precious information about general concepts about JBoss Portal and portal in general. I hope it worths the read.

                  http://jbossportal.blogspot.com

                  • 6. Re: About JBoss Portal 2.6 ...
                    javatwo

                    Hi Thomas, the blog is a great read.

                    For the User service/portlet, we already have User, Role and User_Role tables in our own datatase that are similar to jbp_users, jbp_roles, and jbp_membership. But the user table has different columns such as totalNumberOfLogin, and lastLoginTime, etc. We am using JSF, and already have JSF pages to manage users/roles.

                    We can create a portlet for creating/modifying users/roles using existing JSF page. but my question is: how to replace the jboss portal User service part? basically let jboss portal read User from our user table, and make jboss portal work. we do not need the additional user profile properties.

                    Another question is: our User table has totalNumberOfLogin, and lastLoginTime. When user login, the user table needs to be modified. Is there a callback after authentication?

                    Thanks for advice.
                    Dave

                    • 7. Re: About JBoss Portal 2.6 ...
                      maiky

                       

                      "thomas.heute@jboss.com" wrote:

                      JBoss Portal 2.4 is used in production in many places, 2.6 will be final late in June and is already used in production on jboss.org


                      Is there an approxymate date for the final version ? (next week or later ?)
                      I want to use the 2.6 version in production but I must make it soon.

                      I want to use ldap connection and at time I have bugs.


                      Thanks in advance.

                      Sorry for my bad English.