We would like to kick off a discussion about what features we should include in the Vert.x future releases.
As it happened last year we would like this to be primarily determined by the needs and requirements of you, the community.
Also, we are not committing to any specific version since we would like to hear all sizes of features/fixes and do not want to impose any constraint in term of size, time or resources.
Last time we used this mail thread to discuss what we would focus, the thread grew to 88 posts from 55 authors which became a bit hard to track. This time, we would like to have a different approach:
If you have an idea/feature/fix you would like to see in Vert.x add it to https://github.com/vert-x3/issues/issues
If you would like to help us to know which things you consider the most important, visit the same link: https://github.com/vert-x3/issues/issues and this time go through the issues and vote the ones you consider more important (thumbs up).
Note that the number of votes is not binding for the developers to commit to work on the issue right away but gives the developers the hint we should consider to work on those first.
When issues are not clear engage in discussion on the issue itself so we can have a good understanding of your needs and you can also read about our feedback.
We will be reading the issue tracker for about 2 months so you can take you time and add what really is important.
So, now over to you... please contribute to the issue tracker:
https://github.com/vert-x3/issues/issues/issues
With what you would like to see in Vert.x!
On Jul 11, 2016, at 5:39 PM, ad...@cs.miami.edu wrote:The link to post issues in the above post gives me a 404.
I don't know if you want us to reply to this post with our thoughts, but since the above link was not working for me, I will just give one thought here.
The first thing that comes to mind is a more stable mysql postgres client. I have not had any problems with mysql integration, but the documentation labels it as a "tech preview". Since mysql is so highly adopted, a good vertx client will greatly help adoption of vertx (I think), and would give us developers confidence that the mysql client will not fail on us unexpectedly.
-Adam
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/a6577cf5-a995-4f25-b516-05e27fd05934%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/dadada21-d766-4246-be9d-c36c8672edd1%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/d4b74bf4-2e0d-4b84-9227-779c6dddd4c0%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/155626bb-2b79-42ef-a6de-6486a4620173%40googlegroups.com.
user.isAuthorised("printers:printer1234", res -> {
if (res.result()) {
System.out.println("User has the authority");
} else {
System.out.println("User does not have the authority");
}
});
@PreAuthorize("#group.ownerUserId == authentication.userId") public void removeUserFromGroup(@P("group") Group group, User userToRemove);
One Person(=User) in system has role (group owner) and he wants remove someone else from his group.
We want to check security on instance for current user, if he is owner of something in system. We can't do that properly on Vertx layer.
Hi Yuriy,
Vert.x has a simple authN/Z component called vertx-auth, of course it is not annotation based like spring but does follow the vert-x explicit way of doing things, having said that, you can perform authZ at any place like:user.isAuthorised("printers:printer1234", res -> {
We would like to kick off a discussion about what features we should include in the Vert.x future releases.
Let me start by saying how superb the progress in 2016 has been. We love using vert.x and are proud to be the first in our organisation to have a major product built fully with vert.x in production. Thank you!So, with that, here's a non-exhaustive list:1. Performance - any thoughts on techempower #13?
2. Streamed queries for MongoDB - if I'm not mistaken we're still packaging the full result set to an EB message. MongoDB's async driver is ideal for streaming results, which certain circumstances can very much improve memory profile.
3. DSL for declaring and wiring REST bindings with markup that emits swagger/raml documentation.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/cbfc8319-3915-48a7-a2c4-de0871480935%40googlegroups.com.
We would like to kick off a discussion about what features we should include in the Vert.x future releases.
https://github.com/vert-x3/issues/issues/237
[Feature request]: Route annotation support for vertx-web
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/6cde3175-13ef-4ac6-a2b3-db60c23aee27%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/25c38572-4eaf-4dbb-87ff-cfe256db138d%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/07f26f37-c80c-4d39-b69b-992c54d9f8c9%40googlegroups.com.
you could try to use Resteasy with Vert.x to create annotated controllers that works with a Vert.x HttpServer.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/eb36b42e-9e2e-40a8-b9a9-068489ae4dc8%40googlegroups.com.
I think that’s a discussion we can definitely have and most importantly the community can give his opinion.
On Feb 8, 2017, at 11:34 AM, Luke Hutchison <luke....@gmail.com> wrote:
On Tuesday, February 7, 2017 at 4:58:07 AM UTC-8, Julien Viet wrote:you could try to use Resteasy with Vert.x to create annotated controllers that works with a Vert.x HttpServer.Yes, I'm aware there are projects like this, but is there any interest in building annotation support into Vert.x itself, for cutting down the amount of boilerplate code? It could be used to allow users to much more simply specify routes, authentication/authorization attributes, etc.The support could be included in vertx-web, or in a separate vertx-annotations module, perhaps not available for all languages, if a language doesn't properly support annotations.--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/eb36b42e-9e2e-40a8-b9a9-068489ae4dc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/5835E7A9-2577-4379-8D9A-723B765DF59B%40julienviet.com.
On Feb 8, 2017, at 2:57 PM, Jochen Mader <jochen...@codecentric.de> wrote:Using annotations we will have to tackle various other things:Defining an API using a fluent API allows easy debugging and uhelps understanding how and where things happen.I'd be very cautious when it comes to annotations.We currently have a very readably way of creating Web-APIs using vertx-web and method handles.
- classpath scans need to be coordinated so handlers can be grouped inside a verticle
- we need additional annotations for security- all current vertx-web, vertx-security ... functionality has to be provided as annotations- is it going to be polyglot?
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CAAn-prXF7KJZM3E%2Bv61DaJ4KFKV1cvY-waCTGV8BdNOQ56L4kA%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CAAn-prXF7KJZM3E%2Bv61DaJ4KFKV1cvY-waCTGV8BdNOQ56L4kA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/1545189C-ACCC-43D1-BA26-D6CDC76A2A99%40julienviet.com.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CAAn-prXqXETY6c7p1YY4-kEJRA7vXK8NEdVzkj2xPgc5qEs8Tg%40mail.gmail.com.
we are investigating it actually.Julien
On Feb 7, 2017, at 10:22 PM, Roland Tepp <luo...@gmail.com> wrote:
What about integrating OpenTracing[1] api support into Vert.x.Traditional logging based (MDC) tracing falls apart in async reactive context and this is something that would make a lot of Ops people happy...--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/25c38572-4eaf-4dbb-87ff-cfe256db138d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/C248B207-C960-4E10-B29E-EF5818439880%40julienviet.com.
Defining an API using a fluent API allows easy debugging and uhelps understanding how and where things happen.I'd be very cautious when it comes to annotations.We currently have a very readably way of creating Web-APIs using vertx-web and method handles.
to be honest : I would simply use annotation processing to generate code that bootstraps Vert.x Web, i.e [...], as it is: 1/ debuggable : you can debug and see the code and it could be as good as if you wrote it yourself
Using annotations we will have to tackle various other things:
- classpath scans need to be coordinated so handlers can be grouped inside a verticle
- we need additional annotations for security
- all current vertx-web, vertx-security ... functionality has to be provided as annotations
- is it going to be polyglot?
I'd rather take a look at the current way of defining HTTP-APIs and try to figure out if we can improve things there.
to be honest : I would simply use annotation processing to generate code that bootstraps Vert.x Web, i.e@GET(“/foo”)void foobar(RoutingContext ctx) { … }would generate a class that does something like:ctx.get(controller::foobar).
to be honest : I would simply use annotation processing to generate code that bootstraps Vert.x Web, i.e
- there already is a module for it (codegen)
- we are already familiar with how it works
- there already is documentation for other codegen stuff, which isn't to different, the mechanisms are the same
- Vert.x sticks to what it is meant to be
- If you still think that this fluent API is really needed, I think it would be better to build a whole new MVC framework on top of Vert.x, to keep things in their scope. Because you would only choose to use Vert.x if you want performance, Spring isn't that bad when it comes to performance, but if you really need increase performance I think its only natural to go down on the abstraction layer (from Spring to Vert.x) since Vert.x gives you more control of what is going on.
Luke scores a very valid point regarding the "How vs. What"
I think a decent indicator of the routing API expressiveness is the ability to generate, from the code, the API detailed documentation.If I want to generate a full Swagger doc from vertx-web, I pretty much have to look at the implementation, looking for request.getParam(), request.getBodyAsJson(), etc.If I want to do so from Spring MVC, RestEasy or whatever, I just have to "parse" the method declaration / annotations.
A routing file is a good entry point, and is also very good for documentation.
1. Keep & enchance the Vert.x-Web approach of RouterWhy ?People start to get used to it : ExpressJS, Sinatra, Flask, etc.
Something like :get("/some/path").withBody(Something.class).andValidParams(["id", Long::valueOf], ["date", this::dateIsValidAndBeforeChristmas]).do(mongo::save).finalize(response::write);
Well I think we should not forget what the team initially introduced. "Vert.x it's an unopinionated tool-kit for building reactive applications on the JVM.", thus I think we should always keep this in my in mind. Also I've read some Tim Fox interviews and he almost always states that Vert.x doesn't want to replace any frameworks, it is meant to be used (together) with them. By introducing an annotation fluent API like Spring isn't it deviating a little bit from its purpose?
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/398d8090-8345-4403-8956-e1088a237324%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/d00393f6-168a-4a52-bb82-6503d3c181ad%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/6a9b2dc6-fdd0-4302-8638-bb25106c1c42%40googlegroups.com.
Currently Vert.x will not attempt to reconnect if a connection fails, reconnect attempts and interval only apply to creating initial connections.
Please could you enable it and confirm the version.
We would like to kick off a discussion about what features we should include in the Vert.x future releases.
As it happened last year we would like this to be primarily determined by the needs and requirements of you, the community.
Also, we are not committing to any specific version since we would like to hear all sizes of features/fixes and do not want to impose any constraint in term of size, time or resources.
Last time we used this mail thread to discuss what we would focus, the thread grew to 88 posts from 55 authors which became a bit hard to track. This time, we would like to have a different approach:
If you have an idea/feature/fix you would like to see in Vert.x add it to https://github.com/vert-x3/issues/issues
If you would like to help us to know which things you consider the most important, visit the same link: https://github.com/vert-x3/issues/issues and this time go through the issues and vote the ones you consider more important (thumbs up).
Note that the number of votes is not binding for the developers to commit to work on the issue right away but gives the developers the hint we should consider to work on those first.
When issues are not clear engage in discussion on the issue itself so we can have a good understanding of your needs and you can also read about our feedback.
We will be reading the issue tracker for about 2 months so you can take you time and add what really is important.
So, now over to you... please contribute to the issue tracker:
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c6fcce7a-bfaf-4bec-9763-4b1f9032bb99%40googlegroups.com.
I'd like to see more space devoted to best practices for using Web Components with Vert.x. Maybe an example using simple gateway with UI serving an endpoint UI. Also, Aurelia examples / integrations would be sweet too.
On Tuesday, April 25, 2017 at 2:59:14 AM UTC+2, kuwv wrote:I'd like to see more space devoted to best practices for using Web Components with Vert.x. Maybe an example using simple gateway with UI serving an endpoint UI. Also, Aurelia examples / integrations would be sweet too.
Do you mean, how to use the eventbus with your web framework?
Future.<SQLConnection>future(future ->{
client.getConnection(future);
}).<UpdateResult>compose(connection ->
Future.future(future -> connection.update("update table_1 set name = a where id = 001", future))
).setHandler(updateResult ->{
if(updateResult.succeeded()){
}else{
}
//is there any way to add updateResult.getConnection(); here?});
//thus we could use updateResult.getConnection().close();
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/88c7935f-9afc-480a-9d56-9dfdfd0c570b%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/7216f1a9-3264-4eb5-b203-cff56352881d%40googlegroups.com.
Socket.io support in Vert.x.--
You received this message because you are subscribed to a topic in the Google Groups "vert.x" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vertx/duFVIcSR0zg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/5f60dd75-6d59-42b7-866b-aaa31c2051c2%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CAMkunmJjB_dfM0V_G9EG3igW%3D6Re7CG%2BaggA8rDhJ9tZa-8KWw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/45468f47-ad90-4a7f-b74e-9c74990aebdf%40googlegroups.com.
CONFIDENTIALITY NOTICE: This email and files attached to it are confidential. If you are not the intended recipient you are hereby notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/2463c0e7-ed4e-4cd9-bde0-ad166e5b59dd%40googlegroups.com.
The change is not trivial as the api is a java interface and json types are not, plus the code generation needs to be verified if this is a valid construct.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/15c50cb1-555f-47e7-b2ff-7a8b1f4a8cd8%40googlegroups.com.
I would like to see surpport RocketMQ Client and FTPClient in vert.x
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/52602b2b-9938-4597-9930-6608ad7767d2%40googlegroups.com.
Take a look at this great example app from Clement and Julien
+1worse than having a void to fill with a book, we have a bad book...On Nov 14, 2016, at 8:05 PM, Luis Trigueiros <luistri...@gmail.com> wrote:I really love the see a Vert.x in Action book, the current books are old and they don't go into details in the Java side.
On Monday, July 11, 2016 at 10:25:46 AM UTC+1, jul...@julienviet.com wrote:We would like to kick off a discussion about what features we should include in the Vert.x future releases.
As it happened last year we would like this to be primarily determined by the needs and requirements of you, the community.
Also, we are not committing to any specific version since we would like to hear all sizes of features/fixes and do not want to impose any constraint in term of size, time or resources.
Last time we used this mail thread to discuss what we would focus, the thread grew to 88 posts from 55 authors which became a bit hard to track. This time, we would like to have a different approach:
If you have an idea/feature/fix you would like to see in Vert.x add it to https://github.com/vert-x3/issues/issues If you would like to help us to know which things you consider the most important, visit the same link: https://github.com/vert-x3/issues/issues and this time go through the issues and vote the ones you consider more important (thumbs up). Note that the number of votes is not binding for the developers to commit to work on the issue right away but gives the developers the hint we should consider to work on those first. When issues are not clear engage in discussion on the issue itself so we can have a good understanding of your needs and you can also read about our feedback.We will be reading the issue tracker for about 2 months so you can take you time and add what really is important.
So, now over to you... please contribute to the issue tracker:
https://github.com/vert-x3/issues/issues/issues
With what you would like to see in Vert.x!
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/dadada21-d766-4246-be9d-c36c8672edd1%40googlegroups.com.
On 1 Feb 2018, at 13:17, huang bo <dontmiss...@gmail.com> wrote:building_reactive_microservices_in_java.pdf is awsome.Is it ok that vertxs written by different language? Vertx supports so many language anyway.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/f24f9584-0484-48cc-aa89-2a03d020a307%40googlegroups.com.
You can also have a look at 2016 google summer of code project
https://github.com/sczyh30/vertx-blueprint-microservice
It describes a many moving parts application showcasing many vertx APIs.