JDev 10.1.3 ADF- eliminate XML

Question

We are evaluating JDeveloper 10.1.3 and OC4J for a critical project. We are committed to moving to EE5 as rapidly as possible. The ADF Faces components are very useful. However, creating the necessary data controls produces too many extraneous XML files. We are trying to reduce source files, not add more. In fact, we would like this application to be entirely free of XML within the enterprise.
So, back to just plain JSF. My question is, is it possible to do JNDI lookups using the @EJB annotation in the managed bean to the session facade? I can't seem to make it work. Also, how soon before EE5 JDeveloper will be available for Solaris? Please advise on both questions. Thank you.
Josh Foster

Answer 1

Thanks kindly for your responses. I should have re-phrased my questions better. What I meant to say was:
I have the following architecture:
- JSF on the View/Controller
- a Business Delegate session bean that calls Session Facades that encapsulate Entity Beans on the Model
QUESTION 1. I can inject @EJB annotations on my Business Delegate to call Session Facade interfaces just fine. Similarly, I can use an @Resource annotation on the Session Facades to inject an EntityManager to call Entity Beans. No problem.
But, when I try to inject @EJB(name="ejb/BusinessDelegate") on my JSF backing-beans (or some other JSF managed bean), OC4J just ignores the injection. I have the JNDI name registered in web.xml as <ejb-local-ref>.
Now, it works fine if I go through the trouble of writing a service locator, using an InitialContext lookup. But I want to avoid writing this ugly code.
So, my question is, should the @EJB annotation work from View to Model?
QUESTION 2. I'm not against having a couple of standard XML files such as web.xml and faces-config.xml. I didn't mean to imply that those were troubling. But, when I create a data control on the Business Delegate so that I can use ADF Faces components on my JSPs, JDeveloper insists on creating XML files for ALL of my Session Facades, AND, for each one of my Entity Beans. This literally DOUBLES the number of source files I have to carry around.
Is it possible this information can be annotated on the bean itself, preferably generated automatically by the IDE?
3. Will JDeveloper 10.1.3 production work on Solaris? We have many new Solaris workstations on our team. This is imperative if we are going to be able to switch over to Oracle AS from BEA.
Please kindly advise. And thank you again.
Josh