[jboss-dev-forums] [Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

[scott.stark@jboss.org]

"adrian at jboss.org" wrote : 
  | * TEST CLASSPATH
  | 
  | Why is it necessary to add jars other than jbossall-client.jar to the classpath
  | to run the client? See my comment in ejb3/build-test.xml
  | 
  | I added jboss-metdata.jar which should be included (at least in part)
  | in jbossall-client.jar?
  | 
  | 
  |   |    <path id="client.classpath">
  |   |       <pathelement path="${jboss.dist}/client/jbossall-client.jar"/>
  |   |       
  |   |       <!-- FIXME - shouldn't these be in jbossall-client.jar???? -->
  |   |       <path refid="apache.codec.classpath"/>
  |   |       <path refid="apache.log4j.classpath"/>
  |   |       <path refid="apache.logging.classpath"/>
  |   |       <path refid="jboss.test.classpath"/>
  |   |       <path refid="sun.servlet.classpath"/>
  |   |       <pathelement path="${jboss.dist}/client/jboss-ejb3-client.jar"/>
  |   | 	  <pathelement path="${jboss.dist}/lib/jboss-vfs.jar"/>
  |   |       <path refid="jboss.microcontainer.classpath"/>
  |   |       <path refid="jboss.metadata.classpath"/>
  |   |    </path>
  |   | 
  | 
  | I'll leave Carlo to decide which of these issues needs further attention
  | in the EJB3 project.
  | 
  | We should probably raise a main appserver JIRA for the jbossall-client.jar issue?
The client container/launcher requires jboss-metadata.jar, jboss-container.jar (AbstractAnnotationImpl), and jboss-vfs.jar (for the vfs usage I added) to be in the client classpath as well.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104172#4104172

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104172