We are building server components, beans, web services, etc. I thought the
client libs were for client applications accessing jboss as opposed to running
within (but I might very well be confused... still learning).
It works if I use :
<path id="jboss.compile.classpath">
| <fileset dir="${jboss.dir}/client"
includes="**/jbossall-client.jar" />
| <!--fileset dir="${jboss.dir}/lib">
| <include name="**/*.jar" />
| </fileset>
| <fileset dir="${jboss.dir}/server/all/lib">
| <include name="**/*.jar" />
| </fileset-->
| <fileset dir="${jboss.dir}/server/all/deploy/ejb3.deployer">
| <include name="*.jar" />
| </fileset>
| <fileset
dir="${jboss.dir}/server/all/deploy/jboss-aop-jdk50.deployer">
| <include name="*.jar" />
| </fileset>
| </path>
Guess the jbossall-client does not contain the ejb3.0 stuff yet.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3894464#3894464
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3894464
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
