Gwizard, appengine and objectify

[Huseyn Guliyev]

Hi Jeff,

thanks for very promising library. We have also looked at dropwizard a year or so ago, but didn't use it for number of reasons, some of them being the reasons you mentioned.

One thing I already like about Gwizard, it seems from first sight that with gwizard there is more control over the architecture of application, it is less opinionated.

We have some interesting suggestions and would be happy to also offer code to contribute. Jersey Exceptionmapper seems a good one to start with. Then we could continue with Mustache(Handlebars) and JSP backed template views

; would be great to have modules for Hibernate validator and Jackson; then  Authentication module. Seems a lot could be done.

Also, it will be interesting to get Gwizard to work with Appengine and Objectify.

Best,

Huseyn

[Jeff Schnitzer]

Yeah, with Guice the opinions can be a bit more flexible because the binding between components is looser. Dropwizard requires a lot of stuff to be passed around in the Environment and Boostrap; with Guice, you just inject interfaces when necessary. GWizard ends up being more of a toolkit than a framework.

Using this on GAE brings up an interesting question for the dependency chain. Originally I thought it wouldn't be of much use on GAE because most of GWizard just deals with setting up Jetty and configuration; it might make sense for a managed vm. But it would be nice to have one-line setup for RESTEasy or Jersey on vanilla GAE. Right now gwizard-rest and gwizard-jersey depend on gwizard-web (which sets up embedded Jetty), so that would have to somehow become modular.

This requires some thought.

Jeff

--
You received this message because you are subscribed to the Google Groups "GWizard Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gwizard+u...@googlegroups.com.
To post to this group, send email to gwi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gwizard/e4eeaf52-98c3-451b-8457-2ef7ead2fd47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Huseyn Guliyev]

Indeed, this modularity could be revolutionary. Back in its first days DropWizard became very prominent as a bootstrap framework, but then people stumbled upon its limitations. If modularity could be achieved with Gwizard, it would truly revolutionise java server app development.

Currently the closest thing we have are some maven archetypes, but they are even more opinionated than dropwizard. Although it is challenging and true modularity i think is impossible, i believe we still can get modularity for some really essential combination of libraries, like Guice, Jackson, Jersey, Resteasy, Hibernate, Hibernate validator, JOda, and etc.  I agree that lack of dependancy injection framework was what made DropWizard inflexible as it is, and having Guice here will make whole difference. 

Again it is easier to say than to realise, but gwizard could become a very good foundation for something really ground breaking. I  also think it is a great timing, as with advent of cloud computing, there is growing need to quickly come up with number of web applications and deploy. An organization which used to do just one app, will be required to have a number of web applications and here they will all be looking for a modular bootstrap solution to get them off the ground.

Thanks.

Huseyn