Skip to main content

generating ejb with xdoclet 1.2.3

Generating EJBs with Xdoclet

Based on xdoclet 1.3

In this example I will create a simple HelloWorld stateless entitybean and create jboss and websphere deployment descriptors.

I used the following file structure:

.
|-- build-dist.properties
|-- build.xml
|-- etc
| |-- application.xml
| |-- jboss
| | `-- jndi.properties
| |-- merge
| | |-- jboss-service.ent
| | |-- jboss-webservices.ent
| | `-- weblogic-security-role-assignment.xml
| `-- websphere
| |-- deploy_helloworld.jacl
| |-- jndi.properties
| |-- was.properties
|-- lib
| |-- xdoclet-1.2.3.jar
| `-- all other xdoclet jars
|-- lib-samples
| |-- ejb.jar
| |-- jboss-j2ee.jar
| |-- jmxri.jar
| |-- jsf-api.jar
| |-- readme.txt
| |-- servlet.jar
| |-- struts-1.1-beta-2.jar
| |-- velocity-1.4-dev.jar
| `-- webwork.jar
|-- src
| `-- com
| `-- jankester
| `-- tryout
| |-- client
| | `-- HelloWorldEjb.java
| `-- ejb
| `-- session
| `-- HelloWorldBean.java

The lib directory contains the xdoclet libs, the lib-samples directory I used for some additional libraries. Further I made use of libs that are part of the websphere 6 installat
ion.

The most important files in this listing are build.xml, and HelloWorldBean.java. The HelloWorldEjb.java file is just a client file that will call the EJB.
The HelloWorldBean.java and build.xml are just adaptions of samples that come with the xdoclet 1.2.3.

Generating EJBs with Xdoclet

Based on xdoclet 1.3

In this example I will create a simple HelloWorld stateless entitybean and create jboss and websphere deployment descriptors.

I used the following file structure:

.
|-- build-dist.properties
|-- build.xml
|-- etc
| |-- application.xml
| |-- jboss
| | `-- jndi.properties
| |-- merge
| | |-- jboss-service.ent
| | |-- jboss-webservices.ent
| | `-- weblogic-security-role-assignment.xml
| `-- websphere
| |-- deploy_helloworld.jacl
| |-- jndi.properties
| |-- was.properties
|-- lib
| |-- xdoclet-1.2.3.jar
| `-- all other xdoclet jars
|-- lib-samples
| |-- ejb.jar
| |-- jboss-j2ee.jar
| |-- jmxri.jar
| |-- jsf-api.jar
| |-- readme.txt
| |-- servlet.jar
| |-- struts-1.1-beta-2.jar
| |-- velocity-1.4-dev.jar
| `-- webwork.jar
|-- src
| `-- com
| `-- jankester
| `-- tryout
| |-- client
| | `-- HelloWorldEjb.java
| `-- ejb
| `-- session
| `-- HelloWorldBean.java

The lib directory contains the xdoclet libs, the lib-samples directory I used for some additional libraries. Further I made use of libs that are part of the websphere 6 installat
ion.

The most important files in this listing are build.xml, and HelloWorldBean.java. The HelloWorldEjb.java file is just a client file that will call the EJB.
The HelloWorldBean.java and build.xml are just adaptions of samples that come with the xdoclet 1.2.3.

Comments

Post a Comment

Popular posts from this blog

SSL handshake failed: Secure connection truncated

Got this problem on Ubuntu 9.10 and 10.10. svn co --username=xx https:/yy zz “SSL handshake failed: Secure connection truncated” According to this link bug-ubuntu The solution is: sudo apt-get install libneon27 cd /usr/lib/ sudo rm libneon-gnutls.so.27 sudo ln -s /usr/lib/libneon.so.27 libneon-gnutls.so.27
12 comments
Read more

Junit4 running parallel junit classes

To run junit testcases parallel, you can create your own class to run junit with: Add this tag to your class declaration. @RunWith(Parallelized.class) Implementation of this class looks like: package mypackage; import java.util.concurrent.ExecutorService; import java.util.concurrent.Executors; import java.util.concurrent.TimeUnit; import org.junit.runners.Parameterized; import org.junit.runners.model.RunnerScheduler; public class Parallelized extends Parameterized {         private static class ThreadPoolScheduler implements RunnerScheduler     {         private ExecutorService executor;                 public ThreadPoolScheduler()         {             String threads = System.getProperty("junit.parallel.threads", "16");    ...
Post a Comment
Read more

Interactive selenium testing

The problem Location of elements When I started using selenium, I noticed that it is not easy to do it right. First you start with IDE, but you notice, that the IDE does not really record a lot. In a next step I added firebug, and started analyzing how the elements where to be located: either by tag, id, class etc. Junit testcase With this information I could then create my junit testcase: @Test public void testMapView() throws Exception { //assert that we cannot see submenu of MapCreator elem = driver.findElement(By.className(SeleniumConstants.MAP_SUB_MENU)); String style = elem.getAttribute("style"); assertTrue("Element must have style display off.",style.matches("display: none.*")); logger.debug("Located element " + SeleniumConstants.MAP_SUB_MENU); //find menu and click on mapview elem = driver.findElement(By.id(SeleniumConstants.MAP_CONTROL)); actions.moveToElement(elem).click().perform(); //assert su...
3 comments
Read more