Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] ee4j-community Digest, Vol 5, Issue 76
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@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@xxxxxxxxxxx

You can reach the person managing the list at
        ee4j-community-owner@xxxxxxxxxxx

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@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

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@xxxxxxxxxxx <ee4j-community-bounces@xxxxxxxxxxx> 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@xxxxxxxxxxx<mailto:ee4j-community-request@xxxxxxxxxxx>> wrote:
Send ee4j-community mailing list submissions to
        ee4j-community@xxxxxxxxxxx<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@xxxxxxxxxxx<mailto:ee4j-community-request@xxxxxxxxxxx>

You can reach the person managing the list at
        ee4j-community-owner@xxxxxxxxxxx<mailto:ee4j-community-owner@xxxxxxxxxxx>

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:


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
________________________________

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@xxxxxxxxxxx<mailto:ee4j-community-request@xxxxxxxxxxx><mailto:ee4j-community-request@xxxxxxxxxxx<mailto:ee4j-community-request@xxxxxxxxxxx>>> wrote:
Send ee4j-community mailing list submissions to


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


You can reach the person managing the list at


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

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@xxxxxxxxx<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.
>
>
>
>
>

> *Sent: *20 January 2018 23:36

>
>
> *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
>
>
>
>
>

> wrote:
>
> Send ee4j-community mailing list submissions to

>
> 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

>
> You can reach the person managing the list at

>
> 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

> Subject: Re: [ee4j-community] JAX-RS Now Available in Git
> Message-ID:
>         <CAE=-

> 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@xxxxxxxxxxx<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@xxxxxxxxxx><mailto:dmitry.kornilov@xxxxxxxxxx<mailto:dmitry.kornilov@xxxxxxxxxx>>> wrote:
> >
> >> Great job, Santiago! Thank you very much!
> >>
> >> -- Dmitry
> >>
> >> ?????????? ?? ????????? Samsung Galaxy.
> >>
> >> -------- ???????? ????????? --------

> >> ????: 19.01.18 22:37 (GMT+01:00)

> >> ????: [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

> >> 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

> > 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

> Subject: Re: [ee4j-community] JAX-RS Now Available in Git
> Message-ID:
>         <

> 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@xxxxxxxxxxx<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@xxxxxxxxxx><mailto:dmitry.kornilov@xxxxxxxxxx<mailto:dmitry.kornilov@xxxxxxxxxx>>> wrote:
> >>
> >>> Great job, Santiago! Thank you very much!
> >>>
> >>> -- Dmitry
> >>>
> >>> ?????????? ?? ????????? Samsung Galaxy.
> >>>
> >>> -------- ???????? ????????? --------

> >>> ????: 19.01.18 22:37 (GMT+01:00)

> >>> ????: [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

> >>> 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

> >> 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

> > 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

> 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

> 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

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@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 82

*********************************************

-------------- next part --------------
An HTML attachment was scrubbed...


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

_______________________________________________
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

Back to the top