I really need your help on this, the deadline is fast approaching. If
the content is OK, what email addresses can I use for the co-submission?
Thanks in advance,
Reza Rahman wrote:
I hate to bug you guys, but have you had a chance to put any more
thought into this? If everything is kosher, I'll go ahead and submit
(I'll need your email addresses on the JavaOne submission site; I
would also advise a bio update that only you guys can do on your end).
Reza Rahman wrote:
> I made some minor changes to the proposal based on feedback from Emil
> Ong, Caucho Chief Evangelist:
> Title: CDI Implementations Frontier: Goals, Milestones and Perspectives
> Type: Birds-of-a-Feather
> The Context and Dependency Injection for Java EE (CDI) API is a key
> part of Java EE 6. It provides robust context management,
> conversations, type-safe next-generation generic dependency
> injection, stereotypes, interceptors, decorators, events and a
> comprehensive SPI intended for portable extensions. CDI already has a
> lot of industry traction with three independent open source
> implementations – Resin’s CanDI, Apache’s OpenWebBeans and JBoss’
> Weld/Seam 3.
> This session is your opportunity to get the perspectives of the folks
> working on these implementations. We will talk about each project's
> goals, approach, features, status, milestones, road map, modular
> portable extensions and perspectives on the future directions for
> CDI. Please do feel free to bring your questions, concerns and ideas!
> As a key part of Java EE 6, CDI already has three early open source
> implementations. This includes the JBoss reference implementation
> Weld (as well as the Seam 3 CDI modules), Caucho's CanDI included in
> the Resin application server as well as Apache's OpenWebBeans. This
> informal session is a chance for attendees to get an overview of
> these projects and interact closely with the folks working on them.
> The session will loosely follow the outline below:
> * An overview of CDI
> * Overview and details of each CDI project including:
> - Goals, implementation approach, features beyond the CDI
> specification, current status, milestones achieved, road-map and
> - Closely related projects such as JBoss Seam 3, JBoss Arquillian,
> Embedded JBoss, Apache OpenEJB and Resin
> - CDI portable extensions being developed with each implementation
> such as support for XML configuration, localization,
> internationalization, security, Spring, GWT, Quartz, Struts 2,
> Wicket, iBATIS, JUnit, Drools and Apache projects.
> * Views on future directions for CDI.
> * Open-ended Q & A with attendees.
> This session is intended for Java server side developers, architects
> and managers. A moderate understanding of dependency injection and
> Java EE is assumed.
> Please do let me know your feedback when you can.
> Dan Allen wrote:
>> I think you have proposed a really nice idea. It would be excellent
>> to get the folks who have translated the specification into working
>> software both to:
>> - get their perspective on the technology
>> - provide insight about how best leverage it
>> - where the implementation took initiative and went beyond the spec
>> - etc.
>> Plus, it presents a unified front of supporters of the specification
>> and its value to the platform.
>> If you are willing to prepare an abstract, then go ahead and post it
>> to this thread and we'll provide some feedback/revisions.
>> On Wed, Feb 17, 2010 at 12:34 PM, Reza Rahman <reza_rahman(a)lycos.com
>> <mailto:firstname.lastname@example.org>> wrote:
>> I am trying to organize and submit a CDI implementor panel BOF for
>> JavaOne 2010. I approached David Blevins (whom I've co-presented
>> with in
>> the past and is a good friend) and did get commitment from him to
>> participate on behalf of Apache/OpenWebBeans. I certainly would be
>> to represent Resin/CanDI in the panel. I was wondering if there
>> would be
>> interest from the Weld/Seam 3 team to co-submit for the
>> in a panel discussing our respective projects with the JavaOne
>> community. I believe it would demonstrate the kind of
>> cohesion/collaboration that often seems to lack between
>> competing Java
>> EE product vendors.
>> Personally, I don't care too much who does the actual submission
>> for the
>> panel/does the write-up/organizing. If it makes the most sense for
>> someone from the Weld/Seam team to do it, I am happy to defer
>> the leg
>> Thanks in advance for your help,
>> Reza Rahman
>> Resin EJB 3.1 Lite Container Developer
>> Expert Group Member, Java EE 6 and EJB 3.1
>> Author, EJB 3 in Action
>> weld-dev mailing list
>> weld-dev(a)lists.jboss.org <mailto:email@example.com>
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597