Folks,
Can somebody point me to the successor of the deprecated type org.springframework.security.oauth2.client.filter.state.DefaultStateKeyGenerator
I am moreover interested in the Reactive flavor of it.
Unfortunately, there is no mention in the oAuth2 migration guide: https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
Related
How to mark APIs as unused in OpenAPI 3.x, when the library is not ready for consumption by other microservices which intend to use the API
Note: Right now, we build a lot of API(s) and they are in various stages of development. Is there a way to annotate this, so that other developers know that there are API(s) which are still work in progress
OpenAPI specification till 3.1.0 doesn't define a way to describe the maturity level of the API.
There was a proposal about adding /info/lifecycle to describe lifecycle and maturity information. But it doesn't seem to get conclusion.
You can define OpenAPI extension to store the information. Just like the /info/x-maturity in Smart API Specification:
x-maturity enum : Maturity of the API. Values to use: development, staging, production.
Another way is to represent your API maturity/readiness in the API version. The semantic versioning allows you to append additional labels for pre-release in the version. For example, any developer should know an API with version 1.0.0-alpha.1 or 1.0.0-dev.1 is still work in progress and not ready for use.
A pre-release version MAY be denoted by appending a hyphen and a
series of dot separated identifiers immediately following the patch
version. ...... A pre-release
version indicates that the version is unstable and might not satisfy
the intended compatibility requirements as denoted by its associated
normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7,
1.0.0-x.7.z.92, 1.0.0-x-y-z.–.
Looking at the Readme of the Journey Router (which is the Rails 4.0 router), it is rather empty. I was wondering how the router works conceptually, and if this 'abstract' grammer is catching the idea, of the router as mini-programming-language:
ROUTE := GET|POST|PUT|DELETE path
path := (static_path) | (dynamic_path)
So, how does the Rails 4.0 Router work?
If you want to understand Rails routing, the best place to start is Rails Routing from the Outside In in the edge guide.
After that, you'll have more luck looking at ActionDispatch::Routing's docs.
Note: The following relates to Journey v1.0.4, which was the latest at time of writing.
Journey itself is the Rails routing engine introduced in Rails 3.2. In the release notes, it is described with a single statement: "Route recognition also got a bunch faster thanks to the new Journey engine." That's not a lot of info specifically about Journey, of course, but Rails doesn't describe every implementation detail; that would take forever! :) Journey's gemspec also describes itself with the statement: "Journey is a router. It routes requests."
You could look at the api docs, but in v1.0.4, it has extremely sparse documentation (Journey::Router::Utils.normalize_path(path) is documented) other than the code itself and maybe its open and closed issues. You could take a look at the other S.O. posts with tag journey.
Some of the code is somewhat self-descriptive just via method names, etc. like in Journey::Routes. Journey's tests are also a great way to see how it works.
Some notes on the code itself:
It monkey-patches Hash in pre-1.9 versions of Ruby to add a keep_if method.
"gtg" stands for "generalized transition graph" (see here)
Funniest code is here (Easter egg: rails c then Journey::Path::Pattern.new(9))
Journey's visualizer might be interesting to play around with, also (note visualizer method in Journey::GTG::TransitionTable). Sample visualization here, and online demo here for now.
I want to create an app with Flex as frontend and Ruby on Rails 3 as backend. I have some experience with Rails but I've never used Flex before. So, I'm searching for any information about how to use them together.
I found that there are RubyAMF, WebORB, RestfulX... But the most of information about them is outdated. What is used now? What editors or IDEs are used (I'm using Redcar for Ruby and I don't have any idea if it is compatible with Flex)? What version of Flex is worth using in production (it's 4, isn't it)?
Also I found "Flexible Rails" book but it describes Flex 3 and Rails 2. Maybe someone knows more modern books?
Redcar is an editor, I'm not sure what you mean by "compatible with Flex".
In any case, there aren't any more recent Flex + Rails-specific books.
Using Rails as a service layer and Flex as the UI layer would be the only thing that makes sense (assuming it makes sense to use Flex on the client side at all, which is debatable).
Other than version-specific differences, this still holds true for Rails 3 + Flex 4.5, as far as I know.
There doesn't appear to be any recent information about using Open ID in Ruby on Rails... the only walkthroughs that I can find do not work anymore. Does anyone know of a walkthrough or documentation that will actually work with modern versions of ruby on rails and required software?
I've been struggling with this for days and cannot make anything work.
This screencast is well done and fairly recent (july 2009):
Railscast on openid with authlogic
I found the early OpenID Railscast (68) really useful when I implemented OpenID, as well as Dan Webb's guide.
What is the preferred method of implementing the OpenSocial platform? I'm aware of Apache Shindig but can't really find any useful information on it. Also, is it possible to use an existing solution like the Rails-based lovdbyless and add OpenSocial features to it?
I've ported shindig over to .NET at http://code.google.com/p/pesta/ and a sample site using it from partuza at http://www.codeplex.com/raya
There seems to be a plugin that someone started, Ruby on Rails, OpenSocial Container plugin 0.1.0, the comments have someone from Apache Shindig suggesting it get rolled into there as the Ruby server implementation.
I also found an article on rolling your own, Google's OpenSocial with Ruby on Rails.
I haven't tried, either, yet.
Even some of the guys on the Shindig team admit that the documentation is very sparse, to the extent that they say the source code is the documentation - and, believe me, there's quite a bit of source code to look at.
The most helpful links I've found are these:
http://mail-archives.apache.org/mod_mbox/incubator-shindig-dev/200805.mbox/raw/%3CF60DD781-F361-4865-AEC6-284644D0DFF3#xs4all.nl%3E/
http://cwiki.apache.org/confluence/display/SHINDIG/The+rough+guide+to+deploying+shindig
http://mail-archives.apache.org/mod_mbox/incubator-shindig-dev/200905.mbox/%3c4CC1540B3EC8D54AA01CC6BC40F71030E0991E#EXCHANGE.corp.shop.com%3e
and for an example of how to replace the default classes so as to interact with a database:
http://cwiki.apache.org/confluence/display/SHINDIG/Providing+your+own+data+service+implementation