Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] JAX-RS Now Available in Git
Heiko,

I suppose it should be possible. Similar to what Jetty and many other projects did.
Especially if EE4J projects under Jersey cover similar aspects it would be a waste of time to create multiple nearly identical things one under the "official standard" the other outside which often uses those kinds of standards (like JAXRS itself)

Werner 



On Mon, Jan 22, 2018 at 4:33 PM, <ee4j-community-request@xxxxxxxxxxx> wrote:
Send ee4j-community mailing list submissions to
        ee4j-community@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/mailman/listinfo/ee4j-community
or, via email, send a message with subject or body 'help' to
        ee4j-community-request@eclipse.org

You can reach the person managing the list at
        ee4j-community-owner@eclipse.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."


Today's Topics:

   1. Re: ee4j-community Digest, Vol 5, Issue 76 (Derek Moore)
   2. Re: JAX-RS Now Available in Git (Heiko Rupp)
   3. Re: JAX-RS Now Available in Git (Werner Keil)


----------------------------------------------------------------------

Message: 1
Date: Mon, 22 Jan 2018 08:24:09 -0600
From: Derek Moore <derek.p.moore@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76
Message-ID:
        <CAMsgyKaW8ePeZf8t1zkQoraNcDUaVCSFCOd0ULfVbMu_T3vupQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

>
> We've had this technology since ~2010, it is kind of a shame that the
> community is just not getting on the bandwagon. But I always say Java is
> perpetually 5 to 10 years behind itself. Glad to see this trend of lag and
> slack finally try to correct itself.
>

Typo: the community is just now*

Derek Moore
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20180122/a77ad1ae/attachment.html>

------------------------------

Message: 2
Date: Mon, 22 Jan 2018 15:23:07 +0100
From: "Heiko Rupp" <hrupp@xxxxxxxxxx>
To: "EE4J community discussions" <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] JAX-RS Now Available in Git
Message-ID: <B65B4F02-F8AB-46F2-A2D0-19E24ADBFE26@xxxxxxxxxx>
Content-Type: text/plain; format=flowed

On 21 Jan 2018, at 0:49, Mrinal Kanti wrote:

> time. But, it is a question of "whether" the MicroProfile should go
> down the path of EPL considering that most other

I think this should be discussed in the MP mailinglists/google
group at oups.google.com/forum/#!forum/microprofile
Having said that, the new EPL allows for a secondary license,
which could be an option here.


------------------------------

Message: 3
Date: Mon, 22 Jan 2018 16:33:51 +0100
From: Werner Keil <werner.keil@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] JAX-RS Now Available in Git
Message-ID:
        <CAAGawe1uG0uhhFdry_cUVn6nUhMrDqbd+HOeMT0odMSrRbck1w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Derek,

Thanks a lot for the pointer and input about jersey-proxy-client. Jersey
will or already has been contributed to EE4J like the underlying standard,
so that is the kind of project I meant. I very much hope, there is no
"shutdown" or similar just because of licensing, but take Jetty for example
https://www.eclipse.org/jetty/licenses.html it also has a dual-license of
Apache 2 and EPL 1. So merging any project into EE4J from e.g. MicroProfile
there could be a double or even triple-license, except CDI or
BeanValidation maybe. If say Glassfish ends up using some of Jetty for the
Servlet implementation, it will also face all the existing licenses.

I put this thread under its old title btw. Mike accidentially pressed
"reply" so the subject was changed and for direct replies to his mesages I
kept his.


Werner


On Mon, Jan 22, 2018 at 3:12 PM, <ee4j-community-request@eclipse.org> wrote:

> Send ee4j-community mailing list submissions to
>         ee4j-community@xxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://dev.eclipse.org/mailman/listinfo/ee4j-community
> or, via email, send a message with subject or body 'help' to
>         ee4j-community-request@eclipse.org
>
> You can reach the person managing the list at
>         ee4j-community-owner@eclipse.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ee4j-community digest..."
>
>
> Today's Topics:
>
>    1. Re: CFP open for EclipseCon France (Alex Theedom)
>    2. Re: ee4j-community Digest, Vol 5, Issue 76 (Derek Moore)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 22 Jan 2018 10:14:19 +0000
> From: Alex Theedom <alex.theedom@xxxxxxxxx>
> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
> Subject: Re: [ee4j-community] CFP open for EclipseCon France
> Message-ID:
>         <CAKKegfW40dqQwRkUi0BPAQmyNSh8TXkbCSd0P97newrruVpTHA@mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I have found that the number of conference I can attend is based on the
> financial cost I have to accept myself and as such select only those that I
> know well or are not too expensive to get to. Some kind of financial
> support, if only partial, would make it possible to attend more conferences
> and spread the word. Not everyone has a company behind them willing to
> cover costs and not all conference offer travel and subsistence cover to
> all speakers.
>
> Kind regards
>
> Alex Theedom
>
> *Course: *Java EE Video Courses
> <https://www.lynda.com/Alex-Theedom/7606196-1.html>
> *Blog*: readlearncode.com
> *Twitter*: @readlearncode <https://twitter.com/readlearncode>
> *Books*: Java EE 8: Only What's New <http://www.leanpub.com/javaee8>
> and Professional
> Java EE Design Patterns javaeedesignpatterns.com
>
>
>
>
>
> On 21 January 2018 at 10:16, reza_rahman <reza_rahman@xxxxxxxxx> wrote:
>
> > That's really great. Maybe not for this but for certain other conferences
> > that I would like to be able to go to but historically have been unable
> to
> > due to the out of pocket cost issue.
> >
> > Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
> >
> > -------- Original message --------
> > From: Ondrej Mih?lyi <ondrej.mihalyi@xxxxxxxxx>
> > Date: 1/21/18 4:45 AM (GMT-05:00)
> > To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
> > Subject: Re: [ee4j-community] CFP open for EclipseCon France
> >
> > Hi,
> >
> > As we spoke in another thread (I think the one about Java EE Guardians
> > open letter), evangelism by the community is very welcome. If we want to
> > act according to it, we also should be thinking about supporting
> evangelism
> > effort financially. As explained by Mike M., Eclipse PMC isn't going to
> > invest in marketing but individual vendors can.
> >
> > I hope that in the future we will be able to agree on some joint form of
> > sponsoring evangelism activities like travelling to conferences for
> > speakers with apprved talks on a relevant topic.
> >
> > Until then, I suggest everybody to submit to Eclipse Con and other
> > conferences topics related to Java EE, EE4J and MicroProfile and when
> > accepted, ask individual vendors for sponsorship. I can't promise
> anything
> > for Payara but let me know if you'd like to receive some help.
> >
> > Ondro
> >
> > 2018-01-19 20:16 GMT+01:00 Mike Milinkovich <mike.milinkovich@eclipse-
> > foundation.org>:
> >
> >> On 2018-01-19 2:06 PM, reza_rahman wrote:
> >>
> >>> For future reference, do you know if the conference covers speaker
> >>> travel costs?
> >>>
> >>
> >> Sorry, but no. We provide a free pass to the event but do not cover
> >> speaker travel. That is to keep the registration costs down for
> attendees.
> >>
> >> --
> >> Mike Milinkovich
> >> mike.milinkovich@eclipse-foundation.org
> >> (m) +1.613.220.3223
> >>
> >>
> >> _______________________________________________
> >> ee4j-community mailing list
> >> ee4j-community@xxxxxxxxxxx
> >> To change your delivery options, retrieve your password, or unsubscribe
> >> from this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >>
> >
> >
> > _______________________________________________
> > ee4j-community mailing list
> > ee4j-community@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
> > from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/
> 20180122/d13c036b/attachment.html>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 22 Jan 2018 14:12:43 +0000
> From: Derek Moore <derek.p.moore@xxxxxxxxx>
> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
> Subject: Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76
> Message-ID:
>         <CAMsgyKbfvq2+akb6gNfpbQff9s5MOuiQmecU2dbnFO
> PVaJXF_A@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> As a long-time user of jersey-proxy-client and as someone who came to
> microprofile-rest-client early to ensure it had feature parity with
> jersey-proxy-client (e.g., subresources and beanparams), I can second the
> notion that JAX-RS Proxy Clients would be huge for Java EE and Java SE.
>
> Besides my input on the kinda of
> interfaces being used in the wild, jersey-proxy-client had little to no
> influence on MicroProfile Rest Client. I haven't actually used MP Rest
> Client 1.0 yet, but I will soon.
>
> Like is happening with ConfigJSR, I kind of expect something to happen
> around a JAX-RS Proxy Client standard. I would like to see Jersey
> contributors, MicroProfile contributors and maybe even Retrofit
> contributors (who are talking about adopting JAX-RS for their 3.0 release)
> all working together on such a standard!
>
> You guys should see how my JAX-RS interfaces are unit & integration testing
> my JAX-RS endpoints!
>
> I use a very pedantic style of interface definition that directly models
> URL structure in the reflected proxy clients, causing `/` to become `().`,
> an approach that I think should be popularized for several reasons.
>
> We've had this technology since ~2010, it is kind of a shame that the
> community is just not getting on the bandwagon. But I always say Java is
> perpetually 5 to 10 years behind itself. Glad to see this trend of lag and
> slack finally try to correct itself.
>
>
> Derek Moore
>
> On Mon, Jan 22, 2018 at 3:00 AM Werner Keil <werner.keil@xxxxxxxxx> wrote:
>
> > Mike,
> >
> > You confirm a good case, that MicroProfile is simply moving too fast for
> > the Enterprise world and that vendors can barely cope with it, Payara is
> > certainly not alone in that ;-)
> >
> > That particular problem is not exactly for EE4J, but the initial
> > discussion was purely about how certain features like the REST client
> could
> > be more useful in EE4J than elsewhere, that belongs here I'd say.
> >
> > Werner
> >
> >
> > On Mon, Jan 22, 2018 at 9:55 AM, <ee4j-community-request@eclipse.org>
> > wrote:
> >
> >> Send ee4j-community mailing list submissions to
> >>         ee4j-community@xxxxxxxxxxx
> >>
> >> To subscribe or unsubscribe via the World Wide Web, visit
> >>         https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> or, via email, send a message with subject or body 'help' to
> >>         ee4j-community-request@eclipse.org
> >>
> >> You can reach the person managing the list at
> >>         ee4j-community-owner@eclipse.org
> >>
> >> When replying, please edit your Subject line so it is more specific
> >> than "Re: Contents of ee4j-community digest..."
> >>
> >>
> >> Today's Topics:
> >>
> >>    1. Re: ee4j-community Digest, Vol 5, Issue 76 (Mike Croft)
> >>
> >>
> >> ----------------------------------------------------------------------
> >>
> >> Message: 1
> >>
> > Date: Mon, 22 Jan 2018 08:55:42 +0000
> >
> >
> >> From: Mike Croft <mike.croft@xxxxxxxxxxx>
> >> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
> >> Subject: Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76
> >> Message-ID:
> >>
> >         <
> >> AM4PR03MB1458F13A382C674556C76E5992EC0@AM4PR03MB1458.
> eurprd03.prod.outlook.com
> >> >
> >>
> >> Content-Type: text/plain; charset="us-ascii"
> >
> >
> >>
> >> Werner - you'll notice that that list is of MP 1.2 specifications which,
> >> as I said earlier, will be implemented in Payara Server and Micro from
> the
> >> next release (hence "coming soon"). The omission of all MP 1.3
> >> specifications from that list does not mean they will not be implemented
> >> and it is disingenuous to claim otherwise.
> >>
> >
> >> Regardless - an EE4J mailing list is not the appropriate place to have
> >> discussions about MicroProfile.
> >>
> >> Thanks,
> >> Mike Croft
> >> Java Middleware Consultant
> >> Payara Services Limited
> >>
> >> Payara Server: Derived from GlassFish with 24/7 Production Support
> >> W: www.payara.fish<http://www.payara.fish/> | T: +44 207 754 0481 ; +1
> >> 415 523 0175 | Twitter: @Payara_Fish<https://twitter.com/Payara_Fish>
> >>
> >> ------------------------------------------------------------
> ----------------------------------------------------------------
> >> Payara Services Limited, Unit 11, Malvern Hills Science Park, Geraldine
> >> Road, Malvern, Worcestershire, WR14 3SZ
> >> ________________________________
> >> From: ee4j-community-bounces@eclipse.org <
> >> ee4j-community-bounces@eclipse.org> on behalf of Werner Keil <
> >> werner.keil@xxxxxxxxx>
> >> Sent: 22 January 2018 08:36:10
> >> To: EE4J community discussions
> >> Subject: Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76
> >>
> >> The mentioned page states clearly that
> >>
> >>   *   Config
> >>   *   Metrics
> >> (coming soon)
> >>   *   Healthcheck
> >> (coming soon)
> >>   *   JWT Propagation
> >> (coming soon)
> >>   *   Fault Tolerance
> >
> >
> >> (coming soon)
> >>
> >> would be supported later, but not the REST Client.
> >> Neither MicroProfile nor EE4J have mandatory requirements that you MUST
> >> support everything, and some features make more sense for the wider
> >> community than others.
> >>
> >> HTH,
> >> Werner
> >>
> >>
> >> On Mon, Jan 22, 2018 at 9:28 AM, <ee4j-community-request@eclipse.org
> >> <mailto:ee4j-community-request@xxxxxxxxxxx>> wrote:
> >> Send ee4j-community mailing list submissions to
> >>         ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>
> >>
> >> To subscribe or unsubscribe via the World Wide Web, visit
> >>         https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> or, via email, send a message with subject or body 'help' to
> >>         ee4j-community-request@eclipse.org<mailto:
> >> ee4j-community-request@eclipse.org>
> >>
> >> You can reach the person managing the list at
> >>         ee4j-community-owner@eclipse.org<mailto:
> >> ee4j-community-owner@eclipse.org>
> >>
> >> When replying, please edit your Subject line so it is more specific
> >> than "Re: Contents of ee4j-community digest..."
> >>
> >>
> >> Today's Topics:
> >>
> >>    1. Re: ee4j-community Digest, Vol 5, Issue 76 (Mike Croft)
> >>
> >>
> >> ----------------------------------------------------------------------
> >>
> >> Message: 1
> >> Date: Mon, 22 Jan 2018 08:28:06 +0000
> >> From: Mike Croft <mike.croft@xxxxxxxxxxx>
> >> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx<mailto:
> >> ee4j-community@xxxxxxxxxxx>>
> >> Subject: Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76
> >> Message-ID:
> >>
> >         <
> >> AM4PR03MB145818D4A0914255ACA2FAF792EC0@AM4PR03MB1458.
> eurprd03.prod.outlook.com
> >> <mailto:
> >> AM4PR03MB145818D4A0914255ACA2FAF792EC0@AM4PR03MB1458.
> eurprd03.prod.outlook.com
> >> >>
> >
> >
> >>
> >> Content-Type: text/plain; charset="us-ascii"
> >>
> >> "Nobody really implements most of the new MP features, except a single
> >> vendor maybe, sometimes specs or APIs don't have any implementation.
> >>
> >> Payara Micro has not gone beyond MP 1.1 and
> >> https://www.payara.fish/payara_micro shows only a few others are
> >> supported. Rest Client isn't, It is likely to see a broader vendor
> support
> >> in EE4J / a future JAX-RS spec for sure."
> >>
> >> This isn't very accurate. Payara (Server and Micro) are targeting the
> >> next release for MP 1.2 support, as we've announced previously and we
> are
> >> currently working on 1.3 specs.
> >>
> >>
> >> MicroProfile is a very fast moving specification and it's natural for
> >> there to be some lead time in implementing some specifications. MP 1.3
> has
> >> only been released for less than a month, so to use that as evidence
> that
> >> specs are not "likely to see broader vendor support" is misleading.
> >>
> >> Thanks,
> >> Mike Croft
> >> Java Middleware Consultant
> >> Payara Services Limited
> >>
> >> Payara Server: Derived from GlassFish with 24/7 Production Support
> >>
> > W: www.payara.fish<http://www.payara.fish/> | T: +44 207 754 0481
> <tel:%2B44%20207%20754%200481>
> >> ; +1 415 523 0175<tel:%2B1%20415%20523%200175> | Twitter: @Payara_Fish<
> >> https://twitter.com/Payara_Fish>
> >
> >
> >>
> >> ------------------------------------------------------------
> ----------------------------------------------------------------
> >> Payara Services Limited, Unit 11, Malvern Hills Science Park, Geraldine
> >> Road, Malvern, Worcestershire, WR14 3SZ
> >> ________________________________
> >>
> > From: ee4j-community-bounces@eclipse.org<mailto:
> >> ee4j-community-bounces@eclipse.org> <ee4j-community-bounces@eclipse.org
> >> <mailto:ee4j-community-bounces@xxxxxxxxxxx>> on behalf of Werner Keil <
> >> werner.keil@xxxxxxxxx<mailto:werner.keil@xxxxxxxxx>>
> >
> >
> >> Sent: 21 January 2018 15:44:50
> >> To: EE4J community discussions
> >> Subject: Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76
> >>
> >> CDI itself, Bean Validation or Ozark have also been Apache only and at
> >> least Ozark/MVC did, too.
> >> Whatever the PMC decided when incorporating all that, it should be
> >> possible to integrate field studies at MicroProfile into EE4J for wider
> >> adoption.
> >>
> >> Nobody really implements most of the new MP features, except a single
> >> vendor maybe, sometimes specs or APIs don't have any implementation.
> >> Payara Micro has not gone beyond MP 1.1 and
> >> https://www.payara.fish/payara_micro shows only a few others are
> >> supported. Rest Client isn't, It is likely to see a broader vendor
> support
> >> in EE4J / a future JAX-RS spec for sure.
> >>
> >> Werner
> >>
> >>
> >> On Sat, Jan 20, 2018 at 7:44 PM, <ee4j-community-request@eclipse.org
> >> <mailto:ee4j-community-request@xxxxxxxxxxx><mailto:
> >> ee4j-community-request@eclipse.org<mailto:
> >> ee4j-community-request@eclipse.org>>> wrote:
> >> Send ee4j-community mailing list submissions to
> >>
> >         ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> >> ><mailto:ee4j-community@eclipse.org<mailto:ee4j-community@xxxxxxxxxxx>>
> >
> >
> >>
> >> To subscribe or unsubscribe via the World Wide Web, visit
> >>         https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> or, via email, send a message with subject or body 'help' to
> >>
> >         ee4j-community-request@eclipse.org<mailto:
> >> ee4j-community-request@eclipse.org><mailto:
> >> ee4j-community-request@eclipse.org<mailto:
> >> ee4j-community-request@eclipse.org>>
> >
> >
> >>
> >> You can reach the person managing the list at
> >>
> >         ee4j-community-owner@eclipse.org<mailto:
> >> ee4j-community-owner@eclipse.org><mailto:ee4j-community-
> owner@xxxxxxxxxxx
> >> <mailto:ee4j-community-owner@eclipse.org>>
> >
> >
> >>
> >> When replying, please edit your Subject line so it is more specific
> >> than "Re: Contents of ee4j-community digest..."
> >>
> >>
> >> Today's Topics:
> >>
> >>    1. Re: JAX-RS Now Available in Git (John D. Ament)
> >>
> >>
> >> ----------------------------------------------------------------------
> >>
> >> Message: 1
> >> Date: Sat, 20 Jan 2018 18:44:39 +0000
> >>
> > From: "John D. Ament" <john.d.ament@xxxxxxxxx<mailto:
> >> john.d.ament@xxxxxxxxx><mailto:john.d.ament@xxxxxxxxx<mailto:
> >> john.d.ament@xxxxxxxxx>>>
> >> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx<mailto:
> >> ee4j-community@xxxxxxxxxxx><mailto:ee4j-community@eclipse.org<mailto:
> >> ee4j-community@xxxxxxxxxxx>>>
> >
> >
> >> Subject: Re: [ee4j-community] JAX-RS Now Available in Git
> >> Message-ID:
> >>
> >         <CAOqetn-C2prUoFyaL+n2P5dxzrtzEGfA2mVaAexnn5=
> >> 1ESyN2Q@xxxxxxxxxxxxxx<mailto:1ESyN2Q@xxxxxxxxxxxxxx><mailto:
> >> 1ESyN2Q@xxxxxxxxxxxxxx<mailto:1ESyN2Q@xxxxxxxxxxxxxx>>>
> >
> >
> >> Content-Type: text/plain; charset="utf-8"
> >>
> >> Assuming you mean the Apache License (since ASL stands for Amazon
> Software
> >> License), I believe you are correct.  I think it was also called out
> when
> >> the MicroProfile project was created that other projects within Eclipse
> >> wouldn't be able to directly use the source code due to the single
> Apache
> >> License state of all features.  Since its the original authors' IP, you
> >> would need those authors to relicense the IP.
> >>
> >> But I'll be honest, I'm not sure what the MP rest client has to do with
> >> the
> >> server runtime issues Arjan's mentioned.  I feel the same pain, but at
> the
> >> same time would recommend leveraging common annotations
> (javax.annotation)
> >> over coming up with a JAX-RS specific annotation, at the end of the day
> I
> >> would love to see an entire "EE4J feature" around security that doesn't
> >> require any runtime, maybe even just a plain CDI extension.
> >>
> >> I can tell you that I've been experimenting within Apache CXF around
> >> tighter CDI integration on the server components to make the CDI runtime
> >> work a bit nicer.  Some of the recent features done:
> >>
> >> - Support for CDI @Inject of all @Context objects
> >> - More ways to automatically register providers
> >>
> >> Most of this will be coming in the 3.2.2 release.  Would love to be able
> >> to
> >> help get some of these features into the JAX-RS spec (whatever that
> means
> >> in the future).
> >>
> >> John
> >>
> >> On Sat, Jan 20, 2018 at 1:25 PM Mrinal Kanti M <mrinal.kanti@xxxxxxxxx
> >> <mailto:mrinal.kanti@xxxxxxxxx><mailto:mrinal.kanti@gmail.com<mailto:
> >> mrinal.kanti@xxxxxxxxx>>>
> >
> >
> >> wrote:
> >>
> >> > I think there is a potential license compatibility issue with using
> >> > EPL2/GPL2CE licensed code in ASL which is used by MicroProfile
> (probably
> >> > due to the one-way-only compatibility). I believe this was discussed
> in
> >> the
> >> > context of the Ozark project during the last PMC meeting of Jan 9.
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> > > *From: *Werner Keil <werner.keil@xxxxxxxxx<mailto:
> werner.keil@xxxxxxxxx
> >> ><mailto:werner.keil@xxxxxxxxx<mailto:werner.keil@xxxxxxxxx>>>
> >
> >
> >> > *Sent: *20 January 2018 23:36
> >>
> > > *To: *EE4J community discussions <ee4j-community@xxxxxxxxxxx<mailto:
> >> ee4j-community@xxxxxxxxxxx><mailto:ee4j-community@eclipse.org<mailto:
> >> ee4j-community@xxxxxxxxxxx>>>
> >
> >
> >> >
> >> >
> >> > *Subject: *Re: [ee4j-community] JAX-RS Now Available in Git
> >> >
> >> >
> >> >
> >> > > These gaps become painfully obvious in the MicroProfile project,
> where
> >> > an ad-hoc mechanism had to be invented
> >> >
> >> >
> >> >
> >> > I said earlier on, this MicroProfile "REST Client" was a bit of a fork
> >> and
> >> > should better be integrated with JAX-RS in EE4J. As both are Eclipse
> >> > projects doing so should not be difficult. Sooner or later e.g.
> >> > MicroProfile Config will also be retired in favor of JSR 382 or just
> >> remain
> >> > a bridge like apache-commons-logging.
> >> >
> >> >
> >> >
> >> > Werner
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> > > On Sat, Jan 20, 2018 at 6:00 PM, <ee4j-community-request@eclipse.org
> >> <mailto:ee4j-community-request@xxxxxxxxxxx><mailto:
> >> ee4j-community-request@eclipse.org<mailto:
> >> ee4j-community-request@eclipse.org>>>
> >
> >
> >> > wrote:
> >> >
> >> > Send ee4j-community mailing list submissions to
> >>
> > >         ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> >> ><mailto:ee4j-community@eclipse.org<mailto:ee4j-community@xxxxxxxxxxx>>
> >
> >
> >> >
> >> > To subscribe or unsubscribe via the World Wide Web, visit
> >> >         https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> > or, via email, send a message with subject or body 'help' to
> >>
> > >         ee4j-community-request@eclipse.org<mailto:
> >> ee4j-community-request@eclipse.org><mailto:
> >> ee4j-community-request@eclipse.org<mailto:
> >> ee4j-community-request@eclipse.org>>
> >
> >
> >> >
> >> > You can reach the person managing the list at
> >>
> > >         ee4j-community-owner@eclipse.org<mailto:
> >> ee4j-community-owner@eclipse.org><mailto:ee4j-community-
> owner@xxxxxxxxxxx
> >> <mailto:ee4j-community-owner@eclipse.org>>
> >
> >
> >> >
> >> > When replying, please edit your Subject line so it is more specific
> >> > than "Re: Contents of ee4j-community digest..."
> >> >
> >> >
> >> > Today's Topics:
> >> >
> >> >    1. Re: JAX-RS Now Available in Git (arjan tijms)
> >> >    2. Re: JAX-RS Now Available in Git (Gaurav Gupta)
> >> >
> >> >
> >> > ------------------------------------------------------------
> ----------
> >> >
> >> > Message: 1
> >> > Date: Sat, 20 Jan 2018 14:49:05 +0000
> >>
> > > From: arjan tijms <arjan.tijms@xxxxxxxxx<mailto:arjan.tijms@xxxxxxxxx
> >> ><mailto:arjan.tijms@xxxxxxxxx<mailto:arjan.tijms@xxxxxxxxx>>>
> >> > To: EE4J community discussions <ee4j-community@xxxxxxxxxxx<mailto:
> >> ee4j-community@xxxxxxxxxxx><mailto:ee4j-community@eclipse.org<mailto:
> >> ee4j-community@xxxxxxxxxxx>>>
> >
> >
> >> > Subject: Re: [ee4j-community] JAX-RS Now Available in Git
> >> > Message-ID:
> >> >         <CAE=-
> >>
> > > AhAT1f7ROt4wQw0044Siz53u-sQYLqUdEZ9ucQYKchOC9g@mail.gmail.com<mailto:
> >> AhAT1f7ROt4wQw0044Siz53u-sQYLqUdEZ9ucQYKchOC9g@mail.gmail.com><mailto:
> >> AhAT1f7ROt4wQw0044Siz53u-sQYLqUdEZ9ucQYKchOC9g@mail.gmail.com<mailto:
> >> AhAT1f7ROt4wQw0044Siz53u-sQYLqUdEZ9ucQYKchOC9g@mail.gmail.com>>>
> >
> >
> >> > Content-Type: text/plain; charset="utf-8"
> >> >
> >> > Hi,
> >> >
> >> > Indeed, JAX-RS is pretty stable. There's a few gaps in how security
> >> works
> >> > in a standard way without any explicit (or even implicit) dependency
> on
> >> > Servlet, so that would be a good thing to address. These gaps become
> >> > painfully obvious in the MicroProfile project, where an ad-hoc
> mechanism
> >> > had to be invented on the spot (the not really ideal @LoginConfig
> >> > annotation) to setup security.
> >> >
> >> > There's also some security "backbone" missing, making it hard to
> answer
> >> > security queries like: "to which JAX-RS methods (endpoints) does the
> >> > current caller have access".
> >> >
> >> > Kind regards,
> >> > Arjan Tijms
> >> >
> >> >
> >> >
> >> >
> >>
> > > On Sat, Jan 20, 2018 at 12:52 PM, reza_rahman <reza_rahman@xxxxxxxxx
> >> <mailto:reza_rahman@xxxxxxxxx><mailto:reza_rahman@xxxxxxxxx<mailto:
> >> reza_rahman@xxxxxxxxx>>>
> >
> >
> >> > wrote:
> >> >
> >> > > +1. This is what I had in mind for JAX-RS too. In addition, JAX-RS
> >> needs
> >> > > to support Java SE 9 modules and possibly reactive streams.
> >> > >
> >> > > Other than this, I think JAX-RS is pretty much stable. I really
> think
> >> a
> >> > > "minor player" like someone from the community or the CXF folks
> could
> >> > take
> >> > > over JAX-RS now (hint, hint :-)). This will allow the "big guys" to
> >> focus
> >> > > on where the heavy lifting is necessary.
> >> > >
> >> > > Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
> >> > >
> >> > > -------- Original message --------
> >> > > From: arjan tijms <arjan.tijms@xxxxxxxxx<mailto:
> arjan.tijms@xxxxxxxxx
> >> ><mailto:arjan.tijms@xxxxxxxxx<mailto:arjan.tijms@xxxxxxxxx>>>
> >> > > Date: 1/19/18 5:41 PM (GMT-05:00)
> >> > > To: EE4J community discussions <ee4j-community@xxxxxxxxxxx<mailto:
> >> ee4j-community@xxxxxxxxxxx><mailto:ee4j-community@eclipse.org<mailto:
> >> ee4j-community@xxxxxxxxxxx>>>
> >> > > Subject: Re: [ee4j-community] JAX-RS Now Available in Git
> >> > >
> >> > > Super news! :)
> >> > >
> >> > > I hope we can start work on evolving the API soon.
> >> > >
> >> > > My two initial proposals would be to further align with CDI and to
> >> define
> >> > > support for the existing javax.annotation.security.RolesAllowed
> >> > > annotation (several JAX-RS implementations already support that in a
> >> > > proprietary way, and MicroProfile JWT-AUTH defines this for JAX-RS
> as
> >> > well).
> >> > >
> >> > > Kind regards,
> >> > > Arjan Tijms
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On Fri, Jan 19, 2018 at 9:53 PM, dmitry.kornilov <
> >> > > dmitry.kornilov@xxxxxxxxxx<mailto:dmitry.kornilov@oracle.com
> ><mailto:
> >> dmitry.kornilov@xxxxxxxxxx<mailto:dmitry.kornilov@oracle.com>>> wrote:
> >> > >
> >> > >> Great job, Santiago! Thank you very much!
> >> > >>
> >> > >> -- Dmitry
> >> > >>
> >> > >> ?????????? ?? ????????? Samsung Galaxy.
> >> > >>
> >> > >> -------- ???????? ????????? --------
> >>
> > > >> ??: Santiago Pericas-Geertsen <Santiago.PericasGeertsen@oracle.com
> >> <mailto:Santiago.PericasGeertsen@xxxxxxxxxx><mailto:
> >> Santiago.PericasGeertsen@oracle.com<mailto:
> >> Santiago.PericasGeertsen@oracle.com>>>
> >
> >
> >> > >> ????: 19.01.18 22:37 (GMT+01:00)
> >>
> > > >> ????: ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> >> ><mailto:ee4j-community@eclipse.org<mailto:ee4j-community@xxxxxxxxxxx>>
> >
> >
> >> > >> ????: [ee4j-community] JAX-RS Now Available in Git
> >> > >>
> >> > >> All,
> >> > >>
> >> > >>  The JAX-RS API sources are now available at [1].
> >> > >>
> >> > >> ? Santiago
> >> > >>
> >> > >> [1] https://github.com/eclipse-ee4j/jaxrs-api
> >> > >>
> >> > >> _______________________________________________
> >> > >> ee4j-community mailing list
> >>
> > > >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> ><mailto:
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>>
> >
> >
> >> > >> To change your delivery options, retrieve your password, or
> >> unsubscribe
> >> > >> from this list, visit
> >> > >> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> > >>
> >> > >>
> >> > >
> >> > > _______________________________________________
> >> > > ee4j-community mailing list
> >>
> > > > ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> ><mailto:
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>>
> >
> >
> >> > > To change your delivery options, retrieve your password, or
> >> unsubscribe
> >> > > from this list, visit
> >> > > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> > >
> >> > >
> >> > -------------- next part --------------
> >> > An HTML attachment was scrubbed...
> >> > URL: <
> >> >
> >> https://dev.eclipse.org/mailman/private/ee4j-community/attachments/
> 20180120/bf6b12f7/attachment.html
> >> > >
> >> >
> >> > ------------------------------
> >> >
> >> > Message: 2
> >> > Date: Sat, 20 Jan 2018 21:24:05 +0530
> >>
> > > From: Gaurav Gupta <gaurav.gupta.jc@xxxxxxxxx<mailto:
> >> gaurav.gupta.jc@xxxxxxxxx><mailto:gaurav.gupta.jc@gmail.com<mailto:
> >> gaurav.gupta.jc@xxxxxxxxx>>>
> >> > To: EE4J community discussions <ee4j-community@xxxxxxxxxxx<mailto:
> >> ee4j-community@xxxxxxxxxxx><mailto:ee4j-community@eclipse.org<mailto:
> >> ee4j-community@xxxxxxxxxxx>>>
> >
> >
> >> > Subject: Re: [ee4j-community] JAX-RS Now Available in Git
> >> > Message-ID:
> >> >         <
> >>
> > > CA+QLtA6KVdguQzBttbftcSHhb7u_gdD-88nutCYtmqesjHXi3g@mail.gmail.com
> >> <mailto:
> >> CA%2BQLtA6KVdguQzBttbftcSHhb7u_gdD-88nutCYtmqesjHXi3g@mail.gmail.com
> >> ><mailto:
> >> CA%2BQLtA6KVdguQzBttbftcSHhb7u_gdD-88nutCYtmqesjHXi3g@mail.gmail.com
> >> <mailto:
> >> CA%252BQLtA6KVdguQzBttbftcSHhb7u_gdD-88nutCYtmqesjHXi3g@mail.gmail.com
> >>>
> >
> >
> >> > Content-Type: text/plain; charset="utf-8"
> >> >
> >> > +1 for javax.annotation.security.RolesAllowed annotation support
> >> >
> >> > Thanks and kind regards,
> >> > Gaurav Gupta
> >> > <https://twitter.com/ImJeddict>  <https://jeddict.github.io/>
> >> > <https://www.youtube.com/JPAModeler>
> >> >
> >> >
> >> >
> >> >
> >>
> > > On Sat, Jan 20, 2018 at 8:19 PM, arjan tijms <arjan.tijms@xxxxxxxxx
> >> <mailto:arjan.tijms@xxxxxxxxx><mailto:arjan.tijms@xxxxxxxxx<mailto:
> >> arjan.tijms@xxxxxxxxx>>>
> >
> >
> >> > wrote:
> >> >
> >> > > Hi,
> >> > >
> >> > > Indeed, JAX-RS is pretty stable. There's a few gaps in how security
> >> works
> >> > > in a standard way without any explicit (or even implicit) dependency
> >> on
> >> > > Servlet, so that would be a good thing to address. These gaps become
> >> > > painfully obvious in the MicroProfile project, where an ad-hoc
> >> mechanism
> >> > > had to be invented on the spot (the not really ideal @LoginConfig
> >> > > annotation) to setup security.
> >> > >
> >> > > There's also some security "backbone" missing, making it hard to
> >> answer
> >> > > security queries like: "to which JAX-RS methods (endpoints) does the
> >> > > current caller have access".
> >> > >
> >> > > Kind regards,
> >> > > Arjan Tijms
> >> > >
> >> > >
> >> > >
> >> > >
> >>
> > > > On Sat, Jan 20, 2018 at 12:52 PM, reza_rahman <reza_rahman@xxxxxxxxx
> >> <mailto:reza_rahman@xxxxxxxxx><mailto:reza_rahman@xxxxxxxxx<mailto:
> >> reza_rahman@xxxxxxxxx>>>
> >
> >
> >> > > wrote:
> >> > >
> >> > >> +1. This is what I had in mind for JAX-RS too. In addition, JAX-RS
> >> needs
> >> > >> to support Java SE 9 modules and possibly reactive streams.
> >> > >>
> >> > >> Other than this, I think JAX-RS is pretty much stable. I really
> >> think a
> >> > >> "minor player" like someone from the community or the CXF folks
> could
> >> > take
> >> > >> over JAX-RS now (hint, hint :-)). This will allow the "big guys" to
> >> > focus
> >> > >> on where the heavy lifting is necessary.
> >> > >>
> >> > >> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
> >> > >>
> >> > >> -------- Original message --------
> >> > >> From: arjan tijms <arjan.tijms@xxxxxxxxx<mailto:
> >> arjan.tijms@xxxxxxxxx><mailto:arjan.tijms@xxxxxxxxx<mailto:
> >> arjan.tijms@xxxxxxxxx>>>
> >> > >> Date: 1/19/18 5:41 PM (GMT-05:00)
> >> > >> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx<mailto:
> >> ee4j-community@xxxxxxxxxxx><mailto:ee4j-community@eclipse.org<mailto:
> >> ee4j-community@xxxxxxxxxxx>>>
> >> > >> Subject: Re: [ee4j-community] JAX-RS Now Available in Git
> >> > >>
> >> > >> Super news! :)
> >> > >>
> >> > >> I hope we can start work on evolving the API soon.
> >> > >>
> >> > >> My two initial proposals would be to further align with CDI and to
> >> > define
> >> > >> support for the existing javax.annotation.security.RolesAllowed
> >> > >> annotation (several JAX-RS implementations already support that in
> a
> >> > >> proprietary way, and MicroProfile JWT-AUTH defines this for JAX-RS
> as
> >> > well).
> >> > >>
> >> > >> Kind regards,
> >> > >> Arjan Tijms
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >> On Fri, Jan 19, 2018 at 9:53 PM, dmitry.kornilov <
> >> > >> dmitry.kornilov@xxxxxxxxxx<mailto:dmitry.kornilov@oracle.com
> >> ><mailto:dmitry.kornilov@oracle.com<mailto:dmitry.kornilov@xxxxxxxxxx
> >>>
> >> wrote:
> >> > >>
> >> > >>> Great job, Santiago! Thank you very much!
> >> > >>>
> >> > >>> -- Dmitry
> >> > >>>
> >> > >>> ?????????? ?? ????????? Samsung Galaxy.
> >> > >>>
> >> > >>> -------- ???????? ????????? --------
> >>
> > > >>> ??: Santiago Pericas-Geertsen <Santiago.PericasGeertsen@oracle.com
> >> <mailto:Santiago.PericasGeertsen@xxxxxxxxxx><mailto:
> >> Santiago.PericasGeertsen@oracle.com<mailto:
> >> Santiago.PericasGeertsen@oracle.com>>>
> >
> >
> >> > >>> ????: 19.01.18 22:37 (GMT+01:00)
> >>
> > > >>> ????: ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> >> ><mailto:ee4j-community@eclipse.org<mailto:ee4j-community@xxxxxxxxxxx>>
> >
> >
> >> > >>> ????: [ee4j-community] JAX-RS Now Available in Git
> >> > >>>
> >> > >>> All,
> >> > >>>
> >> > >>>  The JAX-RS API sources are now available at [1].
> >> > >>>
> >> > >>> ? Santiago
> >> > >>>
> >> > >>> [1] https://github.com/eclipse-ee4j/jaxrs-api
> >> > >>>
> >> > >>> _______________________________________________
> >> > >>> ee4j-community mailing list
> >>
> > > >>> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> >> ><mailto:ee4j-community@eclipse.org<mailto:ee4j-community@xxxxxxxxxxx>>
> >
> >
> >> > >>> To change your delivery options, retrieve your password, or
> >> unsubscribe
> >> > >>> from this list, visit
> >> > >>> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> > >>>
> >> > >>>
> >> > >>
> >> > >> _______________________________________________
> >> > >> ee4j-community mailing list
> >>
> > > >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> ><mailto:
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>>
> >
> >
> >> > >> To change your delivery options, retrieve your password, or
> >> unsubscribe
> >> > >> from this list, visit
> >> > >> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> > >>
> >> > >>
> >> > >
> >> > > _______________________________________________
> >> > > ee4j-community mailing list
> >>
> > > > ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org
> ><mailto:
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>>
> >
> >
> >> > > To change your delivery options, retrieve your password, or
> >> unsubscribe
> >> > > from this list, visit
> >> > > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> > >
> >> > >
> >> > -------------- next part --------------
> >> > An HTML attachment was scrubbed...
> >> > URL: <
> >> >
> >> https://dev.eclipse.org/mailman/private/ee4j-community/attachments/
> 20180120/9976e639/attachment.html
> >> > >
> >> >
> >> > ------------------------------
> >> >
> >> > _______________________________________________
> >> > ee4j-community mailing list
> >>
> > > ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org><mailto:
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>>
> >
> >
> >> > To change your delivery options, retrieve your password, or
> unsubscribe
> >> > from this list, visit
> >> > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> >
> >> >
> >> > End of ee4j-community Digest, Vol 5, Issue 73
> >> > *********************************************
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > ee4j-community mailing list
> >>
> > > ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org><mailto:
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>>
> >
> >
> >> > To change your delivery options, retrieve your password, or
> unsubscribe
> >> > from this list, visit
> >> > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >> >
> >> -------------- next part --------------
> >> An HTML attachment was scrubbed...
> >> URL: <
> >> https://dev.eclipse.org/mailman/private/ee4j-community/attachments/
> 20180120/045553f1/attachment.html
> >> >
> >>
> >> ------------------------------
> >>
> >> _______________________________________________
> >> ee4j-community mailing list
> >>
> > ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org><mailto:
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>>
> >
> >
> >> To change your delivery options, retrieve your password, or unsubscribe
> >> from this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >>
> >>
> >> End of ee4j-community Digest, Vol 5, Issue 76
> >> *********************************************
> >>
> >> -------------- next part --------------
> >> An HTML attachment was scrubbed...
> >> URL: <
> >> https://dev.eclipse.org/mailman/private/ee4j-community/attachments/
> 20180122/9ed8c5f0/attachment.html
> >> >
> >>
> >> ------------------------------
> >>
> >> _______________________________________________
> >> ee4j-community mailing list
> >> ee4j-community@xxxxxxxxxxx<mailto:ee4j-community@eclipse.org>
> >> To change your delivery options, retrieve your password, or unsubscribe
> >> from this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >>
> >>
> >> End of ee4j-community Digest, Vol 5, Issue 82
> >
> >
> >> *********************************************
> >>
> >> -------------- next part --------------
> >> An HTML attachment was scrubbed...
> >>
> > URL: <
> >> https://dev.eclipse.org/mailman/private/ee4j-community/attachments/
> 20180122/85068229/attachment.html
> >> >
> >
> >
> >>
> >> ------------------------------
> >>
> >> _______________________________________________
> >> ee4j-community mailing list
> >> ee4j-community@xxxxxxxxxxx
> >> To change your delivery options, retrieve your password, or unsubscribe
> >> from this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >>
> >>
> >> End of ee4j-community Digest, Vol 5, Issue 84
> >> *********************************************
> >>
> >
> > _______________________________________________
> > ee4j-community mailing list
> > ee4j-community@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
> > from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/
> 20180122/e1e1507b/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> ee4j-community mailing list
> ee4j-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-community
>
>
> End of ee4j-community Digest, Vol 5, Issue 86
> *********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20180122/6bef4350/attachment.html>

------------------------------

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community


End of ee4j-community Digest, Vol 5, Issue 87
*********************************************

Back to the top