Approach:

1. Make a Web application that acts as a Quartz Server (RMI)
2. Configure Glassfish to allow RMI communication with the Webapp
3. Make a test EJB

Make a Web application that acts as a Quartz Server (RMI):

Create normal webapp with the following libs packed in WEB-INF/lib:

1. quartz-1.6.5.jar
2. commons-collections-3.2.jar
3. commons-logging-1.1.jar

include quartz.properties file in WEB-INF/classes with the following entries:

org.quartz.scheduler.instanceName = Sched1

org.quartz.scheduler.rmi.export = true

org.quartz.scheduler.rmi.registryHost = localhost

org.quartz.scheduler.rmi.registryPort = 1099

org.quartz.scheduler.rmi.createRegistry = true

org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool

org.quartz.threadPool.threadCount = 10

org.quartz.threadPool.threadPriority = 5

org.quartz.jobStore.misfireThreshold = 60000

org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore

Add this to the web.xml:

<listener>

    <listener-class>org.quartz.ee.servlet.QuartzInitializerListener</listener-class>

</listener>

add to sun-web.xml:

    <class-loader delegate="true"/>

Configure Glassfish to allow RMI communication with the Webapp:

Activate the Security Manager:

Go to Glassfish Admin Console, Go to [Configuration -> Security] and activate [Security Manager]

Edit server.policy file placed in the domain config folder, and add the following rule:

 grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/[web app name]/WEB-INF/lib/quartz-1.6.5.jar” {

     permission java.security.AllPermission;

 };

replace [web app name] with the apropiate name.

Ok. that is all. Copy the war to the autodeploy dir and restart Glassfish.

Make a test EJB:

Package the following jars into the ejb jar:

1. quartz-1.6.5.jar
2. commons-collections-3.2.jar
3. commons-logging-1.1.jar

put quartz.properties file in jar root with the following entries:

org.quartz.scheduler.instanceName = Sched1

org.quartz.scheduler.logger = schedLogger

org.quartz.scheduler.rmi.proxy = true

org.quartz.scheduler.rmi.registryHost = localhost

org.quartz.scheduler.rmi.registryPort = 1099

Ok. It is ready, now you can access the Scheduler from any EJB:

SchedulerFactory sf = new StdSchedulerFactory();

Scheduler sched = sf.getScheduler();

Download sample code:

1. Quartz Server WebApp
2. EJB Quartz Client

Node: All dependency jars were removed, just download quartz-1.6.5.jar, commons-collections-3.2.jar, commons-logging-1.1.jar from Quartz home site and put it in lib dir in both projects.

original post in spanish: http://www.frankdavidmartinez.com/2009/03/glassfish-quartz-ejb/

http://wikis.sun.com/display/Jersey/Overview+of+JAX-RS+1.0+Features

This is a simple Wrapper over Apache Commons Configuration, so you get all the power of it but decoupled from any additional dependency jar. And additionally you can easy reload the configuration without restart the server.

This was initially developed for Glassfish V2 and has been tested on it only.

Glassfish V2 integration:

1. Download the zip here.
2. Unzip it in some folder
3. There will be some files and a directory:
- eac4j-api.jar  Contains shared interfaces and utilities
- eac4j-impl.jar  Contains the Apache Commons Configuration Wrapper
- eac4j-demo.war  Contains a web application demo.
- config.xml  Contains a sample configuration file.
- app.properties  Contains a sample configuration file.
- deps   Contains all dependency jars
- all.src.zip  Contains all source code.
4. Copy eac4j-api.jar into ${glassfish-domain-root}/lib/ext
5. Create folder ${glassfish-domain-root}/lib/eac4j
6. Copy eac4j-impl.jar into ${glassfish-domain-root}/lib/eac4j
7. Copy all files from deps to ${glassfish-domain-root}/lib/eac4j
8. Restart Glassfish
9. Copy config.xml and app.properties somewhere together (And remember where)
10. Open the Admin Console
11. Go to Resources - JNDI - Custom Resources - New
12. Fill the fields: (see the screenshot) IMPORTANT: Do not forget Property configFile

13. deploy eac4j-demo.war
14. Try  http://localhost:8080/eac4j-demo/DemoServlet on your browser.

Replace ${glassfish-domain-root} for your glassfish domain root: for example /var/glassfish/domains/domain1

That’s all, see the source code of eac4j-demo (Just one class: DemoServlet.java) to see how to use it in your applications, the class JNDIServiceLocator.java is just a service locator.

See the Apache Commons Configuration documentation for further details.

If you have any problem, please tell me. If you want to test it in another Application Server, please share your experience.

Thanks,
Frank.

1. Usability
2. Development productivity
3. Scalability
4. Security
5. Reusability
6. Performance
7. Standards compliance
8. Community support
9. Costs and ROI

Virtual appliances are easy to install, easy to manage and easy to restore if there are any problems. The developer is free to select his favorite OS for the development and the customer is free to select his favorite OS for runtime.

- The battle of platforms Round I was portability (IT centric topic)
- The battle of platforms Round II will be Productivity, Time to market and ROI (Business centric topics)

Now the problem is that in few years you will be running all your applications on two levels of virtualization. For example a Java application running on a guest Linux running on a Windows host. or a Dot Net application running on a guest Windows running on a Linux host.

Paradox: Maybe it is time to go back to native compiled code because there will be no real machines anymore in the world.

There are no Software solutions, there are only partial implementations of fuzzy human ideas.

Hey Hibernate guys, how can you call this a production release when it is no at least a working JPA feature complaint release?

The idea is very simply:

0. Write your model POJO
See the code here

1. Write an interface and annotate it with @DAO
2. Add methods to the interface and annotate they with @SelectStatement, @UpdateStatement, ….
See the code here

3. Write the sqlmap.xml in the same package of the interface and with the same name but with extension .ibatis.xml
See the code here

4. Write your sqlMap config file and place it in the classpath.
See the code here

5. Obtain an IBatisExtSessionFactory using the static build(sqlConfig) method.
6. Create a threadsafe session using the createSession method.
7. Obtain a dao instance using the getDAO(…) method.
8. Call your dao methods.
See the code here

Download the library:

• Complete source code and Netbeans 6.0 project
• Just the jar file
• Javadoc
• Complete CRUD Sample (MySQL)

I am using this code in a project right now and works like a charm. I posted it here because maybe it can be useful for you too. Any feedback is appreciated.

http://www.theserverside.com/tt/articles/article.tss?l=IntroducingApacheWicket

Project architecture image (click it to enlarge) :

Project Tree image (click it to enlarge) :

Explanation of the numerated marks in the images above:

1. static html, css, javascript, images, and so forth
2. Seam configuration files:
- components.xml see: reference
- pages.xml see: reference
3. JPA based data model (Annotated persistent pojos)
4. EJB 3.0 Layer. Business logic goes here. Access to the EntityManager, Other EJBs, JNDI Resources, Web Services, etc …
5. Wicket pages. All Wicket java code goes here.
- To get seam support in a wicket page it must be a subclass of SeamWebPage.
- To get seam support in your application it must be a subclass of SeamWebApplication.
6. Wicket html code goes here. The package tree must be consistent with (5)
7. JUnit tests packages…
8. Ant build script
- clean : Clear all compiled classes, jars, ears, etc…
- ear : Generate the deployable ear.
- deploy : Deploy the ear to the glassfish v2 autodeploy dir.
- undeploy : Removes the ear from the glassfish v2 autodeploy dir.

Download: Project with all dependencies

Instructions:
1. Install Netbeans 6.0 with JEE support: http://www.netbeans.org/
2. Download de example project: download
3. Unzip it where you want.
4. Edit the private.properties file in the project root and set the glassfish.home property to your Glassfish installation dir.
5. Open the project with Netbeans
6. Start Glassfish
7. Right click on the build.xml - execute task - deploy
8. Point your browser to http://localhost:8080/wicket-seam/

You can get more specific documentation from Apache and RedHat sites:
- Apache Wicket home page: http://wicket.apache.org/
- JBoss Seam home page: http://labs.jboss.org/jbossseam/

• Download it form the svn repository: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/
• Build it from source: with maven 2: mvn -Dmaven.test.skip=true package
• Or download the binary: wicket-seam-1.3.0-SNAPSHOT.jar

There is a basic example here: wicket-seam-project It is a netbeans 6.0 project configured to deploy to Glassfish V2. This example contains all required dependencies. IMPORTANT: Before use it you must set the glassfish.home property in the private.properties file.

The general architecture of the example project is this: