Posted by vilpan
on July 1, 2009 at 12:20 AM PDT
we are planning to implement applications for mobicents requiring advanced features not present in JCC. Most of them are defined in JCAT draft, though. Due to the fact we will have to implement them anyway it seems reasonable to build the interfaces according to the JCAT (I believe v0.3.1 is the latest available version of the spec). We are aware of the non-final state of JCAT, nonetheless it seems more reasonable to follow the guidelines outlined in JCAT, than to "invent" something anew, since we're implementing most of the same features anyway.
My question is what is the proper way to introduce JCAT (or we can call it an interface based on JCAT v0.3.1, since JCAT is not a standard on its own yet and is subject to change) in mobicents? Would it be best to define a new RA type and RA extending the existing JCC interfaces? Or is some other approach superior in the context of established patterns applicable in this particular scenario?
Unfortunately, I did not stumble upon any definitive source of information regarding the status of JCAT. "In progress" in jcp.org is not informative enough in this case. I did notice the "Inactive" label, but this could mean 18 months of inactivity as well as much more than 2 years if PMO has decided to retain the JSR. We'd probably reconsider this if we knew, e.g. that JCAT is in a permanent dead-end for some reason.
I will very much appreciate any comments, critique and reasonings on all of the above.