dropwizard

1.关于Dropwizard的一些闲扯 在我的上一篇博客《 Embedded Server：像写main函数一样写Web Server 》中，提到了使用Jetty Embedded Server进行 Java Web Server的开发比传统的Web Container 的方式进行开发的优势。如果直接使用Jetty提供的API进行Web Server的开发，特别是RESTful service的开发，难免看起来还是简单粗暴了一些。 然后期望着更多的程序员逃离java世界，奔向看起来很美好的Ruby, Python等等。我自己而言，我不关心java是不是已经死在沙滩上了，更多的是想，新语言引入的新的技术，或者一些新的思潮，能够折射出我们Java语言或者开发环境中的哪些不足。 有很多用Ruby on Rails的人，在对ruby知之甚少的情况下，就开始吭哧吭哧的写Server了。Rails提供了开发一个Server的完整技术栈，可以很方便的进行开发，后来又有很多人提供了很多RoR的的插件。 Dropwizard也是这么一个东西，提供了使用Java进行RESTful开发的所需要的最小的技术集合，使用了最轻量级的library。如之前博客里提到的Jetty，还有Jersey，Jackson等等。在Dropwizard官网上对其自身的介绍还是比较客气的

Looking for a dropwizard example I found: https://github.com/codahale/dropwizard/tree/master/dropwizard-example But I am interested in a more complete example with at least: a 1:n relationship like customer - account a html gui represenation at least with forms full crud support for xml 2 out of three would be a start and would earn "accepted" by me. Take a look at some of my Dropwzard projects In particular the MultiBit Merchant projects (Admin, Store and Platform) will provide you with a wealth of demonstration code that shows how to get stuff done in Dropwizard. There is also an example of

I am trying to add custom authorization in dropwizard but not able to successed. I have a custom authentication added for dropwizard by binding it to authFactory Authenticator ssoAuthenticator = createSSOAuthenticator(configuration.getSsoGrantClientConfiguration()); environment.jersey().register(AuthFactory.binder( new SSOTokenAuthFactory<SSOGrant>( ssoAuthenticator, SYSTEM_PREFIX, SSOGrant.class)) ); and adding a dynamicfeature for authorization environment.jersey().register(PermissionDynamicFeature.class); Below is the annotation created @Documented @Retention(java.lang.annotation

I'm creating a RESTful service for accessing data. So I started writing that service, first I created a ReadOnlyResource interface with the following code: public interface ReadOnlyResource<E, K> { Collection<E> getAll(); E getById(K id); } Where E is the returned type and K is the key element. So if I'm implementing with <Integer, Integer> I'll inject the key like t @GET @Path("/{id}") @Override public Integer getById(@PathParam("id") Integer id) { return null; } But when my key is more complex, like this: public class ComplexKey { private String name; private int value; } How can I inject

Using DropWizard(Jersey Server), Is it possible to access HttpServletRequest from an Authenticator? I would give it an attribute. I tried with: @Context private HttpServletRequest servletRequest; But it's not injected. I registered my Authenticator using: env.jersey().register( new AuthDynamicFeature(new BasicCredentialAuthFilter.Builder<User>().setAuthenticator(new FooAuthentificator()) .setRealm("Realm").buildAuthFilter())); It's possible, but the problem is, the Authenticator never goes through the DI lifecycle, so it never gets a chance to get injected. What we can do though is explicitly

In DropWizard, I can set up basic auth like so (in the Application#run impl): BasicAuthProvider<SimplePrincipal> authProvider = new BasicAuthProvider(authenticator, "SECRET_REALM"); environment.jersey().register(authProvider); I am wondering what the significance of the String realm (" SECRET_REALM ") is? From general security concepts, I understand a "realm" to be a place (database, directory, file, keystore, etc.) where users and roles/permissions are stored. What does a realm mean in DropWizard, and what's the significance of specifying it inside BasicAuthProvider ? Does it create something