To facilitate iterative development and keep application source separate from compiled files, the tutorial examples use the Java BluePrints application directory structure.
Each application module has the following structure:
build.xml: Ant build file
src/java: Java source files for the module
src/conf: configuration files for the module, with the exception of web applications
web: web pages, style sheets, tag files, and images (web applications only)
web/WEB-INF: configuration files for web applications (web applications only)
nbproject: NetBeans project files
When an example has multiple application modules packaged into an EAR file, its submodule directories use the following naming conventions:
example-name-app-client: application clients
example-name-ejb: enterprise bean JAR files
example-name-war: web applications
The Ant build files (build.xml) distributed with the examples contain targets to create a build subdirectory and to copy and compile files into that directory; a dist subdirectory, which holds the packaged module file; and a client-jar directory, which holds the retrieved application client JAR.
The tut-install/examples/bp-project/ directory contains additional Ant targets called by the build.xml file targets.
For some web examples, an Ant target will open the example URL in a browser if one is available. This happens automatically on Windows systems. If you are running on a UNIX system, you may want to modify a line in the tut-install/examples/bp-project/build.properties file. Remove the comment character from the line specifying the default.browser property and specify the path to the command that invokes a browser. If you do not make the change, you can open the URL in the browser yourself.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4