These are chat archives for spring-cloud/spring-cloud

31st
Jan 2017
Stefan Pfeiffer
@dl1ely
Jan 31 2017 08:52
Is there any documentation on the state of the release trains? I am on Camden.SR4. What are the implications of changing over to Dalston? Is Dalston „newer“ as Camden.SR4?
Tommy Ludwig
@shakuzen
Jan 31 2017 08:55
The release trains are alphabetical. Dalston's first milestone was just released (not announced yet, AFAIK)
Stefan Pfeiffer
@dl1ely
Jan 31 2017 08:56
So Camden will receive no further updates once Dalston is out?
Tommy Ludwig
@shakuzen
Jan 31 2017 08:56
One of the Spring Cloud team members will have to confirm, but I would guess it'll still get service releases
Stefan Pfeiffer
@dl1ely
Jan 31 2017 08:57
ok...yes, i mean except for bugfixes and stuff. thank you
Tommy Ludwig
@shakuzen
Jan 31 2017 08:58
There are some (tentative) release dates here: https://github.com/spring-cloud/spring-cloud-release/milestones
Stefan Pfeiffer
@dl1ely
Jan 31 2017 09:03
Ah, great
Marcin Grzejszczak
@marcingrzejszczak
Jan 31 2017 10:36
For sure we won't update Brixton
Stefan Pfeiffer
@dl1ely
Jan 31 2017 11:32
@dsyer Boot 1.5.1 with Camden.BUILD-SNAPSHOT works fine indeed.
Josh Fix
@joshfix
Jan 31 2017 11:58
since we're on the release train topic... is it intentional that some project pages show older release trains, such as spring cloud stream? https://cloud.spring.io/spring-cloud-stream/
i'm not sure if that means i need to be on the older version to use stream or if the page just hasn't been updated
or if there just hasn't been a newer release train for spring-cloud-stream-dependencies
Tommy Ludwig
@shakuzen
Jan 31 2017 12:02
Spring Cloud Stream's release is on a different schedule than the Spring Cloud releases
Dave Syer
@dsyer
Jan 31 2017 12:04
That page needs an update still (there's no mention of Chelsea and there's an M1 already)
Stefan Pfeiffer
@dl1ely
Jan 31 2017 16:18

Just trying out Dalston.M1 and Boot 1.5.1, in my (at)EnableEurekaServer Boot App i get

Caused by: org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type 'org.springframework.cloud.netflix.zuul.filters.RouteLocator' available: more than one 'primary' bean found among candidates: [compositeRouteLocator, applicationRouteLocator, routeLocator, primaryRouteLocator, simpleRouteLocator]
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.determinePrimaryCandidate(DefaultListableBeanFactory.java:1365)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.determineAutowireCandidate(DefaultListableBeanFactory.java:1326)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1113)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1066)
        at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:835)
        at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:741)
        ... 51 common frames omitted

during startup.

The app is just a minimal Spring Boot app with (at)EnableEurekaServer
Do i have to select a matching primary bean for myself now?
Dave Syer
@dsyer
Jan 31 2017 16:28
Works for me
Maybe you stuffed up the classpath?
12010994
@12010994
Jan 31 2017 16:28
Hello! Does someone knows why my Sleuth correlations ids seems to not be propagated via my Messages (i am using spring cloud stream) ?
Stefan Pfeiffer
@dl1ely
Jan 31 2017 16:31
@dsyer Thanks for checking. No idea whats up there. Will investigate
Stefan Pfeiffer
@dl1ely
Jan 31 2017 16:38
Spring Boot Admin was an the classpath, that caused it
Sorry for false alarm
Eugenio Romano
@eromano
Jan 31 2017 16:48

Hi Guys I have a WebSecurityConfigurerAdapter with this configuration

@Override
    protected void configure(HttpSecurity http) throws Exception {

        // @formatter:off
        http
                    .sessionManagement().sessionCreationPolicy(SessionCreationPolicy.IF_REQUIRED)
                .and()
                    .authorizeRequests()
                    .antMatchers("/", "/accessDenied", "/login", "/oauth/authorize", "/oauth/confirm_access").permitAll()
                    .anyRequest().authenticated()
               .and()
                    .formLogin()
                    .loginPage(loginUrl).permitAll();
        // @formatter:on

    }

If I try to accesss to my user controller http://localhost:8080/user after the login in the browser all is fine.
If i try instead to access to http://localhost:8080/user with curl -i -H "Authorization: Bearer VALID_ACCESS_TOKEN" http://localhost:8080/user I got a 302 answer.
Can you explain what I am doing wrong?