Can we develop web without EJB and Spring with ease?

For the most java developer, they cannot do something that look like
"simple" or "easy". Most of us always put everything into the framework.
The framework supports everything even you couldn't imagine.
Have you ever imagined about Servlet that does not relate to HTTP?
The HttpServlet is extended from GenericServlet and GenericServlet
implements Servlet interface. I think 99% of us never use GenericServlet directly.

Java Application Server is the ideal example for "everything is inside it".
It seems like you don't need to do anything because it will do for you ,
but for the real life it's definitely not true. I said about <=EJB2
I don't know the benefit of using EJB2 except it looks like "Pro".
In recent year new concept of simplification come into the Java world.
The spring framework is the most famous framework for Java EE happened.
It seems like EJB will be replaced by Spring until EJB3 came out.
Now both EJB3 and Spring is the significant ingredient for the project.
Someone cannot live without it, it like addictive substance.
Someone means not all , the rest people still don't use EJB3 or Spring (or Guice)
for managing his/her enterprise system. They decide to design and implement
it by themselves. The reason is both EJB3 and Spring are still difficult to
understand at a glance. They need the time for investigate and look through
its document. But someone doesn't have the time to do so.

I'd like to introduce new generation lightweight framework to manage
your enterprise application with proven concept and the new concept
that I invent it. I know I'm not a expert person and you may think it just the
another frame(doesn't)work. Before judging me read the features first:

1. Ngai glue JPA and Stripes Framework and its own Service, DAO
2. Ngai supports annotation @PersistenceContext, @PersistenceUnit so you can access EntityManager and EntityManagerFactory easily.
3. Ngai have its own annotations to help your task easier.
   @Inject - to inject your custom resource to service/DAO
   @Jndi - to inject JNDI resource (You may inject Datasource via this annotation)
   @Request - to inject HttpServletRequest to your service
   @NativeQueryMethod - mark the method to enable query magic.
   @QueryMethod - mark the method to enable query magic too. (I will explain about this later)
   @NgaiService - to inject another service to current service
   @NgaiDao - to inject another DAO to current DAO or service.
   
4. Ngai has CRUD feature. It doesn't use code generation (both static and runtime)
   it just provide simple base Action, Service, DAO for the crud system. you can extend
   it and use default or override the default on your wish.
   
5. Ngai doesn't force you to separate your application layer.
   The possible combination is
   - Web Action + Service
   - Web Action + DAO
   - Web Action + Service + DAO
   
6. Ngai provides the most common code in every layer you can use or don't use.
   

In fact the feature is much more than this. but I'm not the technical writer I love writing
software more than its document. Please wait a moment I'm working on the example
and document for Ngai-Framework.