Re: Access Denied for CXF release notes.

[Andrei Ivanov]

Hi,
As far as I know, it's exactly as mentioned in that error, Jira requires
you to be logged in to see the release notes.

On Tue, Aug 27, 2019 at 4:07 PM Erwin Hogeweg 
wrote:

> Hi Andriy,
>
> Thanks for the quick reply. Not sure what is going on either. I wiped my
> caches and tried again but I still get the :
>
> Welcome to ASF JIRA
> You must log in to access this page.
>
> If you think this message is wrong, please contact your Jira administrators
>
> When I browse to this page:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342902=12344246
>
> No biggie though, I was just surprised it didn’t work. Maybe you could
> just send me the CXF rel. notes, that is all I was looking for.
>
>
> Thanks,
>
> Erwin
>
>
> On Aug 26, 2019, at 19:43, Andriy Redko  drr...@gmail.com>> wrote:
>
> Hi Erwin,
>
> This is not supposed to be protected. I just tried it, even with `curl`,
> and things
> work as expected, showing the web page. Any chance you have proxies or
> other means
> to go through? Thanks.
>
> Best Regards,
>Andriy Redko
>
> EH> Hi,
>
> EH> I am getting an Access Denied when attempting to view the release
> notes from here:  https://cxf.apache.org/cxf-3118-release-notes.html
>
> EH> Not sure if that is intentional.
>
>
> EH> Cheers,
>
> EH> Erwin
>
> EH> Erwin Hogeweg
> EH> CTO
> EH> 3690 Airport Road
> EH> Boca Raton, FL 33431
> EH> P. +1 (954) 556-6565
> EH> M. +1 (561) 306-7395
> EH> F. +1 (561) 948-2730
> EH> [Seecago]
>
>
> Erwin Hogeweg
> CTO
> 3690 Airport Road
> Boca Raton, FL 33431
> P. +1 (954) 556-6565
> M. +1 (561) 306-7395
> F. +1 (561) 948-2730
> [Seecago]
>

Re: New Maven coordinates for Jakarta EE specs

[Andrei Ivanov]

On Thu, Jan 10, 2019 at 1:59 PM Dennis Kieselhorst  wrote:

>
> > It would be great to get CXF out soon enough, since more and more
> projects switch
> > to Java 11. From practical standpoint, releasing CXF 3.3.0 with JAXB
> deps would
> > make a lot of sense (in my opinion), since every other project around
> did exactly
> > that. However, we've already started moving to Jakarta EE artifacts.
> Should it be
> > reverted (to "old" ones)? Or should we wait for Jakarta EE to publish
> others?
> > Releasing CXF with the mix of both is not looking good I think. Thoughts?
> >
> > Best Regards,
> > Andriy Redko
> >
> > COh> I'm a bit concerned that we we delay indefinitely, when we need to
> get a
> > COh> release out that supports Java 11. Perhaps CXF 3.3.0 should just
> contain
> > COh> the JAXB upgrade and let CXF 3.4.0 pick up all of the newer
> dependencies?
> >
> Let's focus on JAX-WS and JAX-RS (along with JAXB) for 3.3.0 as those
> are the main implementations that we are offering. Everything else can
> be done for 3.4.0.
>
> I also agree that we should release soon (maybe next week?) and avoid
> another delay.
>
> Regards
> Dennis
>

For me, as a CXF user, the easiest way would be to get the old artifacts,
as I expect other frameworks
that I already have in the project would still use the existing Maven
coordinates and then I will have a mix of old and new coordinates until all
of them upgrade.

Regards,
Andrei

Re: 3.3.0 soon?

[Andrei Ivanov]

Hi,

On Fri, Dec 21, 2018 at 10:24 AM Dennis Kieselhorst  wrote:

> > > think we should definitely integrate the JakartaEE dependencies
> (groupId/
> > artifactId change as announced earlier). According to schedule they will
> be
> > release next Friday (14.12.2018).
> >
> > +1.
>
> Unfortunately the JAXB and JAX-WS releases are still not available on
> central. Haven't found an updated schedule yet. I asked on the mailinglist
> but so far I got no response :-(
>
> Since the JAX-RS API dependency was just updated, I was looking through
its changes and I noticed this:
https://github.com/eclipse-ee4j/jaxrs-api/commit/13f7fd093a0deaae3aea626bf35e4562f6439efd

Maybe that approach can also be used for CXF?


> Regards
> Dennis
>

Introduction

[Andrei Ivanov]

Hi,
As requested by Sergey Beryozkin, I'm sending this email to introduce
myself :-)

I'm a Java developer (though in the last year I've been derailed to ext.js
and Python), from Romania, and CXF user and fan.

I also like to keep an eye on the development progress on some of the
frameworks I use (like CXF, Spring or Hibernate), as I find it valuable to
see if there are any bugs that could affect me and also to see how various
features are implemented by people smarter than me :-)
That implies looking at GIT changes and I like to comment if happen to
notice something weird, which triggered the attention of Sergey.

Unfortunately, I rarely have the time to contribute more to the frameworks
I use, in the form of code changes.

Regards,
Andrei

[GitHub] cxf pull request #273: lock RefreshToken entity with pissimistic locking to ...

[andrei-ivanov]

Github user andrei-ivanov commented on a diff in the pull request:

https://github.com/apache/cxf/pull/273#discussion_r117438543
  
--- Diff: 
rt/rs/security/oauth-parent/oauth2/src/main/java/org/apache/cxf/rs/security/oauth2/provider/JPAOAuthDataProvider.java
 ---
@@ -213,6 +221,25 @@ public RefreshToken execute(EntityManager em) {
 });
 }
 
+protected void lockRefreshTokenForUpdate(final RefreshToken 
refreshToken) {
+try {
+execute(new EntityManagerOperation() {
+
+@Override
+public Void execute(EntityManager em) {
+Map<String, Object> options = Collections.emptyMap();
+if (pessimisticLockTimeout > 0) {
+
Collections.singletonMap("javax.persistence.lock.timeout", 
pessimisticLockTimeout);
--- End diff --

options = ... 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---