Welcome !

This is the starting point of your JBoss environment. [Note: to open a .html file in the editor from within AnyJ, click the icon of the treenode. Double clicking the treenode's text will open the html file in a browser.]

Run Samples:
  • Choose 'Workspace | Build All Workspace Files'
  • Choose 'Workspace | Deploy All Modules'
  • Start JBoss using 'Run | Run Class | JBoss Server' or 'Tools | External Tools | Run JBoss Server' from the menu.
  • Verify that JBoss starts up correctly (check output in the Output Pane)
  • Click [http://localhost:8080/webmodule/Sample.jsp] to run a Sample JSP.
  • Click [http://localhost:8080/webmodule/sample] to run a Sample EJB-using Servlet.
  • To run the standalone EJB-client, stop JBoss and restart it using 'Tools | External Tools | Run JBoss Server'. Then choose 'Run | Run Class | sample.EJBClient'.
Debugging:
  • When debugging a Web Client, only one process is required. You can update your application without restarting JBoss using the HotDeploy feature of JBoss. Note that the classes of your application must not be in the classpath of JBoss, else hot deploying will not work. This is set up correctly when a fresh workspace is created (see 'Preferences | Run And Debug Settings', Checkbox 'Take Classpath from Compile Options'). However, hot deploying seems to fail in some cases if you are updating the configuration files of your ejb's or web application. It is therefore recommeded to restart JBoss, if you change your configuration files or deployment descriptors.
  • Within one single instance of AnyJ, only one process (Client or Server) can be debugged at a time. Start a second instance of AnyJ to debug a standalone client and the server-side simultanously. It is recomended then to have a separate workspace for the client and the server (Choose 'Copy Workspace' in the New Workspace Panel) in order to avoid concurrent modification of the workspace's files.
How the workspace is organized:
  • Initially there are two modules, an ejb module and a web module.
  • In the 'deploy' directory you can create and edit the deployment descriptors of a module (WEB-INF or META-INF directories).
  • If you deploy a module, AnyJ copies the relevant classes to the deploy directory (configure deployment in 'Tools|Deployment'), jars them and copies the jar to the JBoss application directory. Note that no build is performed implicitely.
  • The deployment support of AnyJ relies on the directory structure of a module, so do not rename or move the 'source' or 'deploy' directory of a workspace.