10 Replies Latest reply on Jan 7, 2005 12:52 PM by adrian.brock

    Define components and Generate JIRA Tasks

      We need to define to the components that will make up the POJO server
      and generate JIRA tasks for these components.

      We also need a JIRA project for the POJO server where we can
      generate integration tasks.

        • 1. Re: Define components and Generate JIRA Tasks

          The initial list of components I have are:

          Common
          MicroContainer
          AOP
          Aspects
          EJB3
          WEB

          Requried By Aspects:
          Security
          Transaction
          Remoting

          Required By EJB3
          J2EE
          Naming
          Connector
          JMS (new or jbossmq?)
          Cache
          Server?
          Cluster?

          Required By WEB
          Tomcat

          Sundry Items
          hypersonic?

          This list needs to be tightened up.

          • 2. Re: Define components and Generate JIRA Tasks
            starksm64

            I have created two releases in the JBAS project:

            JBossPOJOServer-1.0 Alpha Release date 28/Feb/2005
            JBossPOJOServer-1.0 Final Release date 30/May/2005

            • 3. Re: Define components and Generate JIRA Tasks

              I probably misunderstood this which is where my disconnect is,
              but...

              I thought the plan was to create the POJO server as a standalone project.
              With JBossAS migrating later to be the full j2ee stack on top of it?

              They will eventually be the same thing.

              • 4. Re: Define components and Generate JIRA Tasks
                starksm64

                I would view the pojo server as a component of the app server. It will have standalone releases. I guess I'm leary of project explosion just causing confusion. Is there an ease of management argument for a seperate pojo server project?

                • 5. Re: Define components and Generate JIRA Tasks

                  No ease of management that I'm aware of, it is just how the project
                  was described to me originally.

                  It might be an idea to split out some of the integration points
                  so they are available more a la carte
                  e.g. At the moment they are mostly defined in the server module (along with some implementations like cmp or mdb).

                  Obvious candidates in the server module are:
                  invokers/proxy -> remoting
                  invocation -> aop/microcontainer?
                  container -> aop/microcontainer (if we really want to bother/risk migrating EJB2 to the new container)
                  server/security -> security
                  jmx -> management/jsr160
                  server/jndi -> naming
                  etc.

                  Although in general my preference is to have the integeration point
                  in a separate module to the implementations.
                  e.g. Both the connector and transaction modules define the
                  interfaces, management, implementation and helper classes
                  meaning the integration is ill defined and suspectible to being broken by
                  people who don't understand the abstraction.
                  This is abstraction is further complicated when a module has a client component.

                  • 6. Re: Define components and Generate JIRA Tasks
                    starksm64

                    The existing server module certainly needs to be split up and the suggested breakup makes sense. However, the only time there is an associated jira project for a cvs module(s) is if we are releasing it as a standalone product. I'm still confused as to how the refactoring of the legacy app server is being reflected in jira. Until that's clear, let's just go with the JBAS project JBossPOJOServer-1.0 versions as the container for the associated roadmap tasks.

                    • 7. Re: Define components and Generate JIRA Tasks
                      dimitris

                      Isn't that the JBossPOJO Server is really JBossAS 5 (over the JBoss MicroContainer), where there will be more freedom in combing components.

                      In this sense, why change name/version scheme?

                      In which case a JBossPOJO server will be offered standalone and not be named JBossAS?

                      If this is confusing to us, imagine how it'll be perceived by the users..

                      • 8. Re: Define components and Generate JIRA Tasks
                        starksm64

                        Yes, there will be a non-JBossAS release of the POJO server that does not include the full j2ee related services. The confusion is not in the names, its in what the associated jira project is.

                        • 9. Re: Define components and Generate JIRA Tasks
                          bill.burke

                          FYI: Aspects/EJB3 requires clustering as it uses the replicant manager and a few other services that are in clustering.

                          EJB3 does require Server because it reuses the EJB TImer service.

                          • 10. Re: Define components and Generate JIRA Tasks

                            At some point during the JBoss5 development I will work through
                            these depdencies so we can take the functionality in more manageable chunks.