Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Andy McCright
    @andymc12
    will do (ML == mailing list == Google Group?)
    Michał Szynkiewicz
    @michalszynkiewicz
    @andymc12 hi Andy, I was on sick leave last week and didn't notice your message, sorry
    checking now
    Michał Szynkiewicz
    @michalszynkiewicz
    SslMutualTest works for me with 1.3.RC1
    but in SmallRye we don't have the other features implemented yet
    SmallRye uses a newer wiremock version, and jetty version (jetty 9.2.26.v20180806) :(
    this may be the difference, let me check the test with the old wiremock
    Michał Szynkiewicz
    @michalszynkiewicz
    hmm... still works with the older wiremock/jetty pair
    @andymc12 the only thing that I did in SmallRye to pass the test was adding the keystore with password to the resteasy client builder:
    resteasyClientBuilder.keyStore(keyStore, keystorePassword);
    Michał Szynkiewicz
    @michalszynkiewicz
    could you send me a piece of your maven dependency tree with jetty dependencies?
    Andy McCright
    @andymc12
    Just an update for the rest of the room (Michal and I were chatting privately to avoid spamming the room) - it looks like the problem is with Jetty. We're not sure what regressed exactly, but it seems like the latest version of Jetty (9.4.18.v20190429) is failing but a slightly older version (9.4.14.v20181114) passes - Michal confirmed that it works for SmallRye and CXF. I'm in the process of updating the version in CXF. Thanks @michalszynkiewicz for all the hard work and investigation!
    Ken Finnigan
    @kenfinnigan
    Thanks @michalszynkiewicz
    Ken Finnigan
    @kenfinnigan
    @andymc12 @michalszynkiewicz do we have agenda items for a meeting today?
    Michał Szynkiewicz
    @michalszynkiewicz
    @kenfinnigan maybe celebrate the release? ;)
    Ken Finnigan
    @kenfinnigan
    you have champagne handy? ;-)
    Michał Szynkiewicz
    @michalszynkiewicz
    nope, but a convenience store with beer is not far away
    I don't have any items to discuss
    Ken Finnigan
    @kenfinnigan
    neither do i
    will wait for @andymc12
    Andy McCright
    @andymc12
    Nothing on my list but to celebrate! We can cancel today’s meeting.
    Andy McCright
    @andymc12

    Hey @kenfinnigan - was talking with Emily Jiang, and she was saying that by adding a hard dependency on JSON-B (which is an EE8 technology) in MP Rest Client, we should've made that a major version upgrade (2.0 instead of 1.3). The specific text in question is Implementations must provide built-in JSON-P and JSON-B entity providers.. In 1.2, we had this text (essentially making JSON-B optional): Implementations must provide a built-in JSON-P entity provider. If the implementation supports JSON-B, then it must also provide a built-in JSON-B entity provider.

    Would you be ok with releasing a 1.3.1 reverting that language?

    Ken Finnigan
    @kenfinnigan
    @andymc12 sounds ok
    Andy McCright
    @andymc12
    cool, thanks - I'll make the change a little later today. thanks!
    Ken Finnigan
    @kenfinnigan
    I don't have anything for the call on Wednesday
    Andy McCright
    @andymc12
    Me neither. I think the next thing to do is start planning for the next release (1.4 or 2.0), but I think we can wait a week or two yet.
    Ken Finnigan
    @kenfinnigan
    Sounds good
    Andy McCright
    @andymc12
    @michalszynkiewicz - we're planning to cancel today's meeting. We will probably cancel next week too unless something comes up. Have a good week!
    Derek P. Moore
    @derekm
    btw, I posted eclipse/microprofile-rest-client#201 about cache consistency in MP Rest Client
    Andy McCright
    @andymc12
    @derekm thanks - I'll take a look today now that I'm back in the office.
    @kenfinnigan @michalszynkiewicz is there anything urgent that you want to discuss today? If not, I'll go ahead and cancel today's meeting.
    Ken Finnigan
    @kenfinnigan
    I don't have anything
    Andy McCright
    @andymc12
    ok, I'll go ahead and cancel it. Thanks!
    Ken Finnigan
    @kenfinnigan
    FYI. I’m likely not attending these calls going forward. The implementation has been moved into RESTEasy directly, so the team working on that will look to begin attending
    Andy McCright
    @andymc12
    @kenfinnigan sorry to see you leave. on a similar topic, I was kinda thinking that this project might be a good one to go "full async" as has been discussed in the community hangout / google groups.
    Ken Finnigan
    @kenfinnigan
    I think that makes sense
    Derek P. Moore
    @derekm
    Is it possible in MP Rest Client to load a static header value from MP Config and inject that header into every request? I use an interface-only approach in my clients, and right now I'm falling back to using a ClientRequestFilter that I add to the underlying javax.ws.rs.client.Client
    I guess you have @ClientHeaderParam and @RegisterClientHeaders -- I suppose this means I need to finally stop using Jersey's WebResourceFactory!
    Andy McCright
    @andymc12
    @derekm no, but I think that is a good idea. if your client is in a JAX-RS resource method, it is possible to propagate headers from the inbound request via MP Config. You could also annotate your interfaces with @ClientHeaderParam(name="MyHeader", value="someValue") - but you'd have to do that for all interfaces.
    Derek P. Moore
    @derekm
    I use a lot of subresource locator techniques, so that I can actually propagate stuff from a parent-most interface
    I directly reflect the URL structure in my client APIs, e.g. client.root().v1().api().receivingAddress().handle(handle).get();
    then I re-use these interfaces when implementing the server
    Andy McCright
    @andymc12
    that sounds pretty cool. do you have an example on GitHub (or similar) that I could take a look at?
    Derek P. Moore
    @derekm
    sure, but it is all based on WebResourceFactory right now (since I've been using it since 2012)
    turning path parts into method calls makes for very discoverable client APIs, and codifying the URLs into the interfaces is like QA'ing the URL structure!
    Andy McCright
    @andymc12
    thanks
    Derek P. Moore
    @derekm
    handcash-io-api are the resource interfaces, handcash-io-client is the client wrapper based on WebResourceFactory & https://github.com/derekm/jersey-ext
    I use the handcash-io client in this server project: https://github.com/derekm/handcash-to
    where I also define resource interfaces & implement those interfaces for the server functionality