This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am new to JBOSS...
We are migrating our application from WAS4 to JBOSS4.3.
We have some scripts in WAS4, that we need to migrate to JBOSS
Those scripts are using application launcher to launch the JAR file present in a ear.(The code was developed long back and we are not actually sure about the code details...we are analyzing the code to get the details)
I have search lot of places and it looks like in JBOSS4.3, we don't have application client launcher.
Attaching a sample of script that we have in WAS4 (using websphere client launcher), not sure how to migrate it in JBOSS 4.3
-classpath $WAS_CLASSPATH com.ibm.ws.bootstrap.WSLauncher \
com.ibm.websphere.client.applicationclient.launchClient $EARFILE -CCclasspath=$CLASSPATH -CCBootstrapHost=$COMPUTERNAME -CCBootstrapPort=4000 -CCverbose=true -CCjar=VendorUpload.jar Here VendorUpload.jar is present in the ear file mentioned as $EARFILE
You are launching the client? I assume that your client is attempting to access EJBs deployed to JBoss AS. If that is the case, then you need to include the JAR that contains the client interfaces for your EJBs within your client's classpath. If you haven't created a separate interface JAR for your EJBs, then you might be able to get away with simply including the EJB JAR file in your client's classpath.