 |
Search |
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Blogs by topic J2EE and user ss141213
J2EE
autodpeloy-bundles directory has been moved to autodeploy/bundles. In my earlier blog titled Using filesystem operations to manage OSGi bundles in GlassFish, I had mentioned the directory name to be ${domain_dir}/autodeploy-bundles/. Based on feedback from co-developers and users, I have moved it to ${domain_dir}/autodeploy/bundles/. As you may be knowing, ${domain_dir}/autodeploy is already...
Learn how you can use REST APIs to administer OSGi runtime in GlassFish.
In this short article, I will tell you how we found framework extension bundle a useful concept while developing GlassFish V3 to run on OSGi.
Java Persistence API specification requires its users to not only provide a persistence.xml file but also enumerate managed persistence class names in that file. In this article, I talk about a Java compiler plugin that can create the persistence.xml file for you automatically during normal course of Java code compilation and show how easy it is to use in your existing build scripts - be it maven or ant or shell script.
FOSS.IN is one of the world's largest and most focussed FOSS events, held annually in India. GlassFish team of Sun Microsystems, which participate in one of the most important open source efforts initiated by Sun Microsystems, will not only talk about GlassFish & Java EE platform, but will also have a live demo running at their booth. This blog gives details about the demo that's going to be shown their.
While using Java Persistence API in an enterprise application, there is often a need to access access entities in the same persistence context in different components involved in a particular request. Using a very simple Java EE application, this article shows how to achieve this in an elegant and portable way. The technique described here is completely portable across any Java EE 5 compatible application server because it uses a standard feature called *persistence context propagation*.
Pluggability of third party Java Persistence API providers into a Java EE container offers Java EE users exciting combinations to use. Earlier we had shown how to use Hibernate and Kodo in GlassFish. Now it's time for OpenJPA. I thought I shall give a try using it in GlassFish. This blog reinforces the fact that it could not be easier to plug in a third-party persistence provider in GlassFish.
Pluggability of third party Java Persistence API providers into a Java EE container offers Java EE users exciting combinations to use. Earlier we had shown how to use Hibernate in GlassFish. Now it's time for Kodo, which is another high performance & popular O/R mapping solution. Recently Kodo 4.0GA was released and it supports Java Persistence API. So, I thought I shall give a try using it in GlassFish.
Some of the recent postings in the GlassFish forum suggest that there is some confusion in the GlassFish user community about which GlassFish build to use. This is largely because of activities happening in more than one branch in CVS. I will try to respond to the confusion here.
The Java Persistence API is the standard API for the management of persistence and object/relational mapping in Java EE 5 platform. It can be used in three types of containers, viz: ejb container, web container and application client container. In this blog, we will talk about using this API in application clients. We also discuss two different way of packaging the application.
A number of folks have asked me question about using Hibernate in GlassFish. Read on to know the state of things...
In this article we will talk about developing and using JSP tags to access database using Java Persistence API in a web application. It includes a complete sample as well as a tag library with a handful of ready to use custom tags. It also shows how to inject persistence context into JSPs.
It's a common mistake to inject an EntityManager into a web application that uses Java Persistence API. Let's discuss why?
It's a walk through for using Java Persistence API in a multi-tier (web->ejb->db and appclient->ejb->db) Java EE application in a portable way. This example also shows how simple it is to write web applications and application clients that invoke EJBs in Java EE 5 platform. More over this article also talks about a portable way to package common classes using the new library directory facility of Java EE 5 platform.
Java Persistence API specification requires that for portability reasons, persistence.xml file should contain the list of managed persistence classes. In this article, I shall show you how a simple program can be written using JAXB and APT to automatically generate persistence class list and update persistence.xml. An implementation of Java Persistence API is available in open source project called glassfish.
Lot of developers still believe that when they use Java Persistence API (confusingly part of EJB 3 JSR), they need to bundle entity beans in a .par file. They would be relieved to know that, its not true any more. Sun's next version of application server which is being develped in open source project called glassfish does not require it's users to use any such extensions like .ejb3 or .par. Let's see why?
javax.persistence.TransactionRequiredException is a common exception that a web appliction developer gets while using the Java Persistence API (EJB 3.0) in Java EE 5 platform which is being reference implemented in prject glassfish. Let's try to find out what is the cause of this exception and how to fix it. We also compare this behavior with an EJB trying to do similar work.
Example of a very simple web application using Java Persistence API in Java EE environment is shown here. I will also discuss how how to package such an application in a portable way. We will do all these without using any kind of IDE so that we don't miss the details that often happen while using a super smart IDE. Although the example uses Java EE 5 RI (i.e. project glassfish) to build and run, it does not use any proprietary APIs.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
