Hi,
On Thu, Apr 14, 2016 at 5:19 PM, Werner Keil <werner.keil_at_gmail.com> wrote:
> As we heard and the EC also discussed recently (it probably won't be the
> last time) a few Java EE JSRs have not progressed as much as the others.
> Can we expect an official JSR 375 demo by Alex and/or other members of the
> EG?
>
Would love to see Alex doing a demo again. Last year's one was very good,
but lately we haven't seen that much activity, unfortunately.
> If not, who else would like to step in and propose a talk? Ivar and I did
> a few talks on different occasions around the world (mostly EMEA region)
> and at least one or two other EG members did I recall.
>
I personally can't do a talk, but I'm more than willing to provide and/or
assist with the preparation of the slides.
Obvious topics are the identity store, authentication mechanism, and the
combination of those two.
The identity store part can be extended with a planned soon section, where
we incorporate the multi-store idea from Rudy. This is probably a good
occasion to actually provide a good proposal for this (we discussed it
earlier, but that discussion stalled).
Same holds for the multi-mechanism story idea from Darran. This too would
need a more complete proposal and some draft implementation would help with
putting concrete examples on the slides.
> We should propose something, given there is also a RI project and working
> pieces even if they may be at an early stage. After all, we're still
> supposed to produce an EDR 1. Would be awesome to have that happen before
> JavaOne, as the 1 year deadline for the next Renewal Ballot is only about 2
> months later.
>
We're running out of time pretty quickly now.
Even though we set out to mainly go for the "low hanging fruit", till so
far only the basic identity store and authentication mechanism have been
done, and the latter actually hasn't been discussed that much either (it's
largely still my early draft, almost nobody commented on the method
signatures etc that I quickly choose, e.g. should we not better return an
enum for the status, should we pass in the request, response and context,
or only the context, etc).
With still the multi-variants of the store and mechanism to be done, will
we even be able to look at the other planned topics like events, password
aliasing, interceptors etc?
Kind regards,
Arjan Tijms
> So a "life sign" of JSR 375 seems very important unless say the Spec Lead
> was to withdraw it due to resource or interest conflicts. We all hope that
> won't happen and I already mentioned in the EC call that "IP contributions"
> something they (EC and also Oracle to a large extent) care about very much
> in this case came almost entirely from the community and dedicated
> individuals like Arjan, David or a few others. So in reality this has
> become a very community driven JSR and it would be great, if e.g. via Spec
> Lead sharing or (if a situation like with JSF Portlet Bridge arose, where
> Oracle handed its Spec Lead over to Liferay) if necessary even transfer to
> others who want to help and already did so.
>
> Kind Regards,
>
> Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead |
> Eclipse UOMo Lead, Babel Language Champion | Apache Committer
>
> Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | @DeviceMap
> | #DevOps | #EclipseUOMo
> Skype werner.keil | Google+ gplus.to/wernerkeil
>
>
>
> ---------- Forwarded message ----------
> From: Reza Rahman <m.reza.rahman_at_gmail.com>
> Date: Thu, Apr 14, 2016 at 5:22 AM
> Subject: [javaee-guardians] Call to Action - JavaOne CFP is Now Open
> To: Java EE Guardians <javaee-guardians_at_googlegroups.com>
>
>
> Folks,
>
> The JavaOne CFP is now open:
> https://www.oracle.com/javaone/call-for-proposals.html. Let me remind you
> that the only way to make sure Java EE is properly covered is by submitting
> a quality and quantity of Java EE submissions. We should not be relying on
> anyone else to do that and certainly not Oracle. Here are the topics we
> definitely should be putting effort towards this year:
>
> * Java EE 8 JSRs: As I've explained in a previous message (
> https://groups.google.com/d/msg/javaee-guardians/_AnJbW12SlQ/0VQgxrAIJwAJ),
> this is the most important thing we need to ensure this year. There are
> still unaddressed topics so please read that message and step up on this.
> * Java EE FUD Busting: Pick your favorite Java EE FUD and bust it on
> stage. This year I am submitting on open standards vs. so called de-facto
> "standards". I am also submitting on what modern JTA is really all about
> with Oracle's JTA spec lead Paul Parkinson. One talk I would love to do but
> just don't have the time to take on is why JSF still shines by doing direct
> code comparisons with action-oriented web frameworks and the likes of
> AngularJS/ReactJS.
> * Java EE Ecosystem: Please submit on all the cool work that is going on
> to support Java EE in the community like Swarm, Hibernate OGM, KumuluzEE,
> Payara Embedded, TomEE embedded and so on. Kito and I are doing exactly
> this by covering everything that still going on in the ever vibrant JSF
> ecosystem.
> * Java EE Adoption Stories: Use Java EE in the real world? Brag about it.
> Never underestimate the value of doing this. It is perhaps the most
> important thing you could be doing for Java EE.
> * Java EE on the Cloud: Pick your favorite cloud platform and show how
> Java EE applications can run there. You can even do it on something as
> crazy as Heroku or Azure let alone OpenShift.
>
> This is just the start. The ends are the boundaries of your imagination as
> to where Java EE goes or can go.
>
> If you need help on any of this, please reach out now. We will try to get
> you everything you need from material, resources, know-how, expert help,
> just some advice or just some proofreading.
>
> Let's make it happen folks. This is important because JavaOne is still the
> premier event for everything Java. Everything you do here can also be
> reused just about anywhere else.
>
> Cheers,
> Reza
>
> --
> You received this message because you are subscribed to the Google Groups
> "Java EE Guardians" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to javaee-guardians+unsubscribe_at_googlegroups.com.
> To post to this group, send email to javaee-guardians_at_googlegroups.com.
> Visit this group at https://groups.google.com/group/javaee-guardians.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/javaee-guardians/f5244b76-2bdf-4afc-b971-7ae41be92cbf%40googlegroups.com
> <https://groups.google.com/d/msgid/javaee-guardians/f5244b76-2bdf-4afc-b971-7ae41be92cbf%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>