Java EE 6 with GlassFish 3 Application Server is another nice book from PACKT publishing.
It covers GlassFish administration. Then it talks about Java web technologies -- servlets, JSP, JSP STL, JSF. Also discusses database connections, Java Messaging Service, security of applications (you can find more about it in GlassFish Security book). The books also talks about EJBs and new possibilities in Java EE 6 -- contexts and dependency injection. In the last part it discusses JAX-WS and JAX-RS web services. And everything is accompanied with information how to do that with GlassFish application server.
I would very much recommend it to novice Java EE developers or just to developers, who want to have a glance on Java EE web technologies, JMS, Java EE 6 dependency injection, web services and how all that is configured in GlassFish application server. I would say, it is a crash course into Java EE.
The book is not covering each section is deep detail. But gives a broad view on different Java EE possibilities.
The book is full of working examples! What I very much like about it, is that it not only talks about the latest Java EE 6 technologies. But also briefly covers how application can be configured in order to work with older standards.
Just received my new PACKT book Java EE 6 with GlassFish 3 Application Server.
From the table of contents I conclude that this book gives quite broad view on Java EE technologies and how to use them with GlassFish v3 application server. Although it is not covering some particular technology very detailed.
First chapter is about GlassFish -- how to setup it and configure. The following ones are about Java web technologies: servlets, JavaServer Pages, JSP Standard Tag Library, JavaServer Faces. Next, books talks about Java Messaging Service and security. Last chapter are the most interesting, in my opinion: Enterprise JavaBeans, Contexts and Dependency Injection and Web Services.
Anxious to read it!
GlassFish Security by PACKT is lying on my table. What I can say about it? Pretty nice book about security. I still wonder, why it has name "GlassFish" in the title. It covers a lot of interesting topics about Java EE security and talks about other software, which can help to secure Java applications, such as OpenDS or OpenSSO.
So if you are just about to design or develop complex Java EE application, I would recommend to take a look into this book to at least grasp the ideas about security management. Beside this, book also covers topics of easy security policies migration, which also may be somewhat interesting in our changing world.
And again, thanks PACKT for publishing yet another wonderful book!
The book is about security in Java EE with EJB, Application Client modules and all the friends. Security in GlassFish is a central point of this book. And what is more, there are plenty of real world code and configuration samples. More information about the book can be found on dedicated page on Packt website.
You have probably seen this nasty exception if you tried launching applications in GlassFish v3:
java.lang.NullPointerException at org.glassfish.appclient.client.acc.ACCLogger$1.run(ACCLogger.java:149) at java.security.AccessController.doPrivileged(Native Method) at org.glassfish.appclient.client.acc.ACCLogger.reviseLogger(ACCLogger.java:146) at org.glassfish.appclient.client.acc.ACCLogger.init(ACCLogger.java:93) at org.glassfish.appclient.client.acc.ACCLogger.(ACCLogger.java:80) at org.glassfish.appclient.client.AppClientFacade.createBuilder(AppClientFacade.java:360) at org.glassfish.appclient.client.AppClientFacade.prepareACC(AppClientFacade.java:247) at org.glassfish.appclient.client.JWSAppClientContainerMain.main(JWSAppClientContainerMain.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.javaws.Launcher.executeApplication(Unknown Source) at com.sun.javaws.Launcher.executeMainClass(Unknown Source) at com.sun.javaws.Launcher.doLaunchApp(Unknown Source) at com.sun.javaws.Launcher.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
You are not alone!
Sometimes one needs a compound key for specifying
@Entity. TopLink website says that one should provide multiple
@Id and @IdClass for a composite primary key. But it actually works without specifing
Prior to today I used "JEE6" abbreviation to mean "Java EE 6". Now I have changed all "JEE6" occurrences to "Java EE 6".
The reason is that I received an email from Bill Shannon -- Java EE specification lead, who kindly asked me to use "Java EE" instead of "JEE". He provided following sources for Java naming:
I really respect his opinion and appreciate his feedback. So from now on I will use "Java EE" to mean "Java EE".
Say, you want to inject an object using
@javax.inject.Inject. And you would like to pass additional dynamic parameter upon initialization. You can do the following trick.