AgileSites 1.8 requires Java 7. If you have Java 6 in your path the code won't compile since it is using features found only in JDK version 7 or greater.
The framework is, by design, source only. The build will actually create 2 jars, one is the core and will be deployed (by the integrated installer) inside the WebCenter Sites webapp.
Another jar is built and deployed in the shared folder and contains your application logic. This jar is continously built and deployed by the
wcs-package-jar command. Both the jar are built automatically by an heavily tested automated build.
The framework lets you create one eclipse project, typing
eclipse and importing the
app folder in eclipse as an Eclipse project.
class not found mysite.Setupin the logs
First, ensure you have done all the steps to create a new site:
If the error persists,
verify in futuretense.ini there is an entry
check the content of that directory and ensure there is only ONE jar
agilesites-all-assembly-* in that folder.
You may have more if you tried a previous release. If there are more, just delete all of them and recreate it with
If you do not see any file created you may have a permission problem.
You need to locate it in a repository accessible by maven, using websites like MVN repository. Assuming you want something like, for example, jfreechart, locate it and locate its sbt dependency. In the site you will find a string like this:
libraryDependencies += "jfree" % "jfreechart" % "1.0.13"
Then open the file
project/AgileSitesBuild and locate the:
val coreDependencies = Seq( "javax.servlet" % "servlet-api" % "2.5",
add your dependency at the beginning as follows:
val coreDependencies = Seq( "jfree" % "jfreechart" % "1.0.13", "javax.servlet" % "servlet-api" % "2.5",
Note you dropped the
libraryDependencies += and added a comma to the end.
This is enough to download the jar and use it for compilation. If you want also to deploy in the application server together the other jars, you need to add in the deployment filter.
val addFilterSetup = "junit*" ||
and change as:
val addFilterSetup = "jfreechart*" || "junit*" ||
This filter is used to select the jars to add to the Sites webapp, so you use only the initial part of name of the jar without the version.
NOTE if a jar has additional dependent jars that are required to run it, you need to add those to the filter, too.
Finally you can use them. Shut down the application server, enter in the shell and execute:
reload update eclipse wcs-setup
Restart the application server, refresh your eclipse project and enjoy using your new library both in the project and in the deployment.
wcs-generate for templates, cselements and layouts generates normally just 2 classes, one is the actual element class and another is the test class. All you need is to remove those 2 classes.
Sometimes the compilation system get confused by intensive changes done to the source code. If the behaviour appears illogical, you can try exiting from the shell cleaning up everything running the
clean.bat or the
Warning: this will remove all the jars and a somewhat time consuming rebuild will be then performed when you access the shell again.
When you start the shell, the script will build the core library if it is not already there. However, if you are not connected to internet (for example you are behind a proxy without direct access to internet) the initial build may file and the core library ends up not being build.
Ensure java can access the internet (for example configuring a proxy for Java), exit the agile shell, execute the
clean batch/shell script and then run again the
agileshell. After those steps the build should rebuild correctly.
Check the workspace actually exists. See below how to do it.
Check the site is actually in the Workspace.
wcs-dt the help command will display the available workspaces.