Deployers ordering and write access to the private naming co

[deruelle_jean]

Hi all,

Sorry in advance for the long post,

As part of the Mobicents Jboss project, we are currently building a sip servlets 1.1 (JSR 289) implementation that run both on top of Tomcat and Jboss. (available at https://sip-servlets.dev.java.net/).

The spec mandates in its section 18.2.7 Annotation for SipFactory Injection that for converged containers, a SipFactory would appear as java:/comp/env/sip//SipFactory in the JNDI mapping or injected as an @Resource annotation. This annotation can be used in any SIP Servlet or a JEE application component deployed on the converged container in the same EAR archive file.

The SipFactory is an interface for a variety of SIP Servlet API abstractions, which could allow an EJB to initiate a sip call by example.

In an EAR, we could have many Sip Servlets Applications, so we would need to first deploy the web applications (contexts) before EJB, webservices, mdb, ... and then when starting those other JEE components be able to access their private naming context (java:/comp/env/) to inject the SipFactory of each app bundled within the EAR.

Could you provide some informations/tips/tricks/guildelines on how to extend/modify the current deployers in order to achieve that ?

I can provide more information if this is not clear enough.

Thanks in advance
Best regards
Jean Deruelle

[alesj]

Moved this to User forum, where it should be in the first place. ;-)

What's the env you're running this?

[starksm64]

Not necessarily as its a question of a new resource injection type. This will only be reasonably doable in jbossas5. Its not a question of startup ordering. Its an issue of a new resource type showing up in the component ENC.

[deruelle_jean]

We are currently adding sip servlets spec implementation on top of JBoss 4.2.2.GA as we are targeting the same version used by Mobicents (JAIN SLEE) to be able to bundle them together to provide full telco features.
There is no way at all to do it in a 4.x version ? Even if it's a bit hacky in waiting for Jboss 5 or through some kind of interceptors...

Ideally, we don't want to do any modifications into the jboss code just extend it to provide this feature, will Jboss 5 be easily extendable regarding this matter ?

Thanks a lot for your valuable feeback.

[deruelle_jean]

By something hacky I meant something like :

Let the EARDeployer deploys everything then iterate through all webapps/sipapps modules, get their SipFactory and inject them into the ENC of every other JEE modules (EJB, Web Service MDB and so on)...

Everything done in EARDeployer that might have access to ENC of deployed modules of the EAR and access to the webapps/sipapps contexts.

Just a thought even if not great

Jean