Blogs by topic J2EE and user tchangu
| • Accessibility | • Ajax | • Blogging | • Business | • Community |
| • Databases | • Deployment | • Distributed | • Eclipse | • Education |
| • EJB | • Extreme Programming | • Games | • GlassFish | • Grid |
| • GUI | • IDE | • Instant Messaging | • J2EE | • J2ME |
| • J2SE | • Jakarta | • JavaFX | • JavaOne | • Jini |
| • JSP | • JSR | • JXTA | • LDAP | • Linux |
| • Mobility | • NetBeans | • Open Source | • OpenSolaris | • OSGi |
| • P2P | • Patterns | • Performance | • Porting | • Programming |
| • Research | • RMI | • RSS Feeds | • Search | • Security |
| • Servlets | • Struts | • Swing | • Testing | • Tools |
| • Virtual Machine | • Web Applications | • Web Design | • Web Development Tools | • Web Services and XML |
J2EE
Lately I have been playing with Glassfish and happened to look at the various security related aspects. In this blog entry, I hope to share some of my findings related to role based access control.
Switching the Java Persistence provider is straight forward and seamless if project /product uses Java Persistence API (EJB3.0) either as a standalone framework component or in a container managed environment.
Lately I have been tinkering with Glassfish and happened to look at the persistence API. The persistence API is based on the EJB 3.0 specification and is made available as a standalone component. I must admit that it’s fairly straight forward and a pleasure to use.
