1 Reply Latest reply on Aug 29, 2007 4:02 PM by Weston M. Price

    Near term roadmap

    Scott Stark Master

      Weston, Alexey, I want to synch up on the near term roadmap items since I'm looking at working with the jca deployers to flesh out the data source management changes. Here is what Weston mentioned. Can we get jira issues for these and focus on getting 2 done?

      1) Complete the new deployment model for JBoss5
      Most of this work has been completed. The *-ds.xml deployment format has been put into an XSD and the new deployment stuff 'works' (JAXB based). There were issues with hot deployment that I didn't get a chance to look at. The JCAMetaDataRepository is up and running but really needs some work to become fully functional.

      2) Pull JCA out of JBossAS
      This is simply Maven based build/deployment stuff. JCA should follow with EJB3 in this regard. The legacy JCA implementation should stay in place while this is going on and then things can simply be switched over

      3) Core JCA
      This is the big one. Currently there is a JCA/MC prototype in CVS that captures a skeleton of how JCA would look in the MC. This needs to be fleshed out and ported into JBoss5 proper.

      4) Adapters
      In conjunction with #2, the adapter set needs to be pulled out of AS *and* given its own release cycle/model. JCA core and the JCA adapters should independent of one another. One of the problems that plagued legacy JCA was the cross pollination between the two code bases (ie Remote DataSources).

        • 1. Re: Near term roadmap
          Weston M. Price Newbie

          Good summary


          The JCAMetaDataRepository is up and running but really needs some work to become fully functional.


          The biggest areas that need addressing are for the other JCA deployment types

          ActivationSpec
          AdminObjects

          Further, this needs properly integrating with EJB3 to better support inbound adapter managment (ie activating endpoints etc, MEF managment). Also, the repository has rudimentary capabilities to report what's currently deployed. This could use some work as well.


          2) Pull JCA out of JBossAS
          3) Core JCA


          While the prototype has been checked into the SVN and Mavenized, it is indeed a prototype. I have some questions regarding the MC especially in terms of AOP integration. I will put these in a coherent format for discussion. Most of these questions simply amount to what I believe is my misunderstanding about the MC-->AOP integration stuff, as well as MC deployment in the 'new world'. Primarily my questions usually are of the form...'How to I get X attribute(s) into this interceptor for this particular JCA resource to manage things like Pool locking strategy, idle timeout etc'. Again, this is my lack of understanding about the MC/AOP model more than anything else.

          Fortunately, the new deployment framework was designed so that when JCA is ported to the MC, it's simply a matter of swapping in the MC objects for the JMX stuff used today. This was the point of the builder stuff where from a deployment, objects (you don't really know what type) can be generated and deployed into either the JMX or MC environment.


          4) Adapters
          In conjunction with #2, the adapter set needs to be pulled out of AS *and* given its own release cycle/model. JCA core and the JCA adapters should independent of one another.


          Correct. It is my plan to have the adapters evolve independently (as much as possible) from the core JCA container.