[jboss-dev] M2 planning and timeline
Carlo de Wolf
cdewolf at redhat.com
Mon Dec 14 06:25:31 EST 2009
On 12/14/2009 12:03 PM, Ales Justin wrote:
Module as in JavaEE module. E.g. a deployment unit which might be
assembled in an EAR containing META-INF/validation.xml (BV 1.0 Final Ch 7).
Injection should then happen in accordance to JavaEE 6 PFD EE 5.16.
@Resource Validator validator;
@Resource ValidatorFactory validatorFactory;
and the associated JNDI names:
The BV deployer should bind a ValidatorFactory into global JNDI per module.
The setup of JNDI namespaces need to be refactored. First I need to
expedite RELOADED-9 into trunk. That should be easy now that the name
server has become a MC bean.
Second we need to get JNDI namespace deployers, so that java:app,
java:module and java:comp are basically installed via deployments.
Third we need to refactor the current EncInjectors to make them more
generic (and out of ejb3-core) so that they can setup the java:comp
environment for real. This would probably be a deployer (or part of
java:comp deployer) with incallbacks.
Last we need to change all the current JavaEE containers to consume the
newly created JNDI context.
And finally create an 'EncInjector' for java:comp/Validator...
> As in sub-deployment?
> You once tried to explain me this via JEE modules,
> which I know nothing about. OK, I guess did/should, but forgot. :-)
> Can you explain it now?
> Emmanuel Bernard wrote:
>> We should probably implement the module injection BV requires. Today
>> we have a global BV ValidatorFactory for the whole application.
>> On 11 déc. 2009, at 23:02, Jason T. Greene wrote:
>>> Hi Guys,
>>> Now that M1 is out lets talk about M2 and what can make the
>>> release. The tentative release plan we have talked about is a
>>> integration freeze on Feb 1, with an eventual freeze in late Feb.
>>> However, before we get more absolute dates we really need to nail
>>> down on what we aim to deliver in that time frame.
>>> From an EE perspective it seems the following are close enough that
>>> they could make such a schedule:
>>> Full Servlet 3 Full JPA 2 Some EJB 3.1 capabilities (but which
>>> Other updates that have been proposed: - Inclusion of Remoting 3
>>> (but full service porting to occur later) - Inclusion of HornetQ
>>> (need to understand more about the effort to migrate)
>>> If your project is on the above list, let me know what your
>>> schedule is like, and if it can fit the above timeline.
>>> If your project update is not on the list, but would like to have
>>> it included, and the above timeframe is workable, let me know.
>>> -- Jason T. Greene JBoss, a division of Red Hat
>>> _______________________________________________ jboss-development
>>> mailing list jboss-development at lists.jboss.org
>> _______________________________________________ jboss-development
>> mailing list jboss-development at lists.jboss.org
> jboss-development mailing list
> jboss-development at lists.jboss.org
More information about the jboss-development