Re: Could there be a final Java 6 version of DeltaSpike released?
Hi Colin, Thanks for clarifying that. As I'm on vacation I did even tried to use 1.8.1, but AFAIK it shouldn't work. LA On Fri, Apr 27, 2018 at 9:20 PM, Astley, Colin (C.J.) wrote: > Hello, > > I'm writing to let you know that I tested 1.8.x with our applications and > it works. I replied on the '@Repository and @CacheResult(cacheName = > "my-cache")' thread above when someone else asked about a 1.8.2 release but > it might have gotten buried. That is quite an active thread. > > Thanks, > Colin > > -Original Message- > From: Astley, Colin (C.J.) > Sent: Wednesday, April 04, 2018 4:55 AM > To: users@deltaspike.apache.org > Subject: Re: Could there be a final Java 6 version of DeltaSpike released? > > Hi Thomas, > > I'll try it out and let you know. Thanks alot for your help. > > Colin > > From: Thomas Andraschko > Sent: Tuesday, April 3, 2018 4:47 AM > To: users@deltaspike.apache.org > Subject: Re: Could there be a final Java 6 version of DeltaSpike released? > > I backported the both mentioned issues. > Gerhard also did some backports of other features. > > Would you please give it a try? It's the 1.8.x branch. > If everything works fine, we could trigger a release. > > 2018-03-26 22:38 GMT+02:00 Gerhard Petracek : > > > +1 for your suggestion > > > > regards, > > gerhard > > > > > > > > 2018-03-26 17:51 GMT+02:00 Astley, Colin (C.J.) : > > > > > Hello, > > > > > > Would you be willing to release a final Java 6 binary compatible > > > version of DeltaSpike? Possibly a version 1.8.2? We are currently > > > using version 1.8.0. We are unable to move to version 1.8.1 because > > > it doesn't run on > > WAS > > > 8. Thomas made a code change after 1.8.1 was released that I tested > > > with WAS 8 and it worked. With your upcoming move to Java 8 I'm > > > wondering if > > his > > > fix can be made available in one final Java 6 release that will run > > > in > > WAS > > > 8's stock JRE 6. > > > > > > Thanks for your consideration, > > > > > > Colin > > > > > > > > >
Re: Seam 3 to Delta Spike
@mark: i spent about an hour to answer those and other questions with concrete links to sections of our documentation and different parts of [1] (as well as [2]). since ds is no 1:1 replacement for seam, there can't be a 1:1 transition. several of our parts are more powerful (but the style is different) and described in our documentation. others were dropped before v1 and continued e.g. (at [3] and later on) at [2] and everything else should be possible with std. cdi. @other users (reading this thread later on) : if you have the same (or a similar) question, feel free to ask it and i'll provide the detailed links once again. however, the docs of both projects should provide enough details already. regards, gerhard [1] https://github.com/CDIatWork [2] https://www.keycloak.org [3] http://picketlink.org 2018-04-28 8:58 GMT+02:00 Mark Struberg : > Gerhard, answers in the IRC channels are no answers. > > Please provide them on the list! > > "if it didn't happen on the list, it didn't happen" > > txs and LieGrue, > strub > > > Am 28.04.2018 um 00:21 schrieb Gerhard Petracek : > > > > hi sana, > > > > i don't think that you will see a diff. answer here (compared to the > answer > > we provided in the irc-channel). > > > > regards, > > gerhard > > > > > > > > 2018-04-27 13:13 GMT+02:00 sana hassan : > > > >> Hi, > >> > >> Can you please tell me how to convert migrate from Seam 3 to DeltaSpike > >> with following: > >> > >> S.No. Seam package class Referenced as > >> 1 org.picketlink.idm.api.User User class > >> 2 org.jboss.seam.security.IdentityIdentity class > >> 3 org.jboss.seam.security.Credentials Credentials class > >> 4 org.jboss.seam.security.IdentityImplIdentityImpl class > >> 5 org.picketlink.idm.impl.api.PasswordCredential > >> PasswordCredential class > >> 6 org.jboss.seam.faces.event.PhaseIdType PhaseIdType.RESTOREVIEW > >> 7 org.jboss.seam.faces.security.RestrictAtPhase > "@RestrictAtPhase" > >> 8 org.jboss.seam.security.annotations.SecurityBindingType > >> "@SecurityBindingType" > >> 9 org.jboss.seam.security.annotations.Secures "@Secures" > >> 10 org.jboss.seam.security.events.LoginFailedEvent "@LoginFailed" > >> 11 org.jboss.seam.faces.security.LoginListener LoginListener > >> 12 org.jboss.seam.security.Authenticator Authenticator class > >> 13 org.jboss.seam.faces.rewrite.FacesRedirect > "@FacesRedirect" > >> 14 org.jboss.seam.faces.security.AccessDeniedView > >> "@AccessDeniedView" > >> 15 org.jboss.seam.faces.security.LoginView "@LoginView" > >> 16 org.jboss.seam.faces.view.config.ViewConfig "@ViewConfig" > >> 17 org.jboss.seam.faces.view.config.ViewPattern"@ViewPattern" > >> 18 org.jboss.seam.security > >> > >> > >> > >> > >> Kind Regards, > >> Sana Korejo > >> > >
