>Rickard �berg wrote:
> > Makes sense?
Vaugn replied:
>Does now. And based on what we have both finally stated clearly I think we
>have been *thinking* about the same or similar solution.
Okay, I changed my build procedure for travelagent.jar to this:
#!/bin/sh
# make cabin
javac -classpath \
/usr/local/jboss/lib/ext/ejb.jar:. \
com/titan/cabin/Cabin*.java
cp com/titan/cabin/ejb-jar.xml META-INF/ejb-jar.xml
jar cvf cabin.jar \
com/titan/cabin/Cabin*.class \
META-INF/ejb-jar.xml
# make travelagent
javac -classpath \
/usr/local/jboss/lib/ext/ejb.jar:. \
com/titan/travelagent/TravelAgent*.java
cp com/titan/travelagent/ejb-jar.xml \
META-INF/ejb-jar.xml
jar cvf \
travelagent.jar \
com/titan/cabin/CabinHome.class \
com/titan/cabin/Cabin.class \
com/titan/travelagent/TravelAgent*.class \
META-INF/ejb-jar.xml
# jBoss needs the Home and Remote interfaces
# of the Cabin bean in travelagent.jar so that
# TravelAgent*.class can access the Cabin bean
rm -f META-INF/ejb-jar.xml
cp cabin.jar /usr/local/jboss/deploy
cp travelagent.jar /usr/local/jboss/deploy
Victory! The travelagent.jar file deploys with no errors!
Now to get the Travel Agent client working...
-- Ken Jenks, http://abiblion.com/
Tools for reading.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
