Download XMLPortal 3.0 Beta 1
A ready to deploy WAR file can be downloaded in project's files at java.net, see XMLPortal files.
Things you need to know
XMLPortal 3.0 have some dependencies that must be satisfied by your JSP/Servlet container. These dependencies are:
You can find these libraries in project's CVS repository. To install them in your container copy jdom.jar, jaxen-1.1-beta-8.jar, rome-0.7.jar and commons-fileupload-1.0.jar into:
For Tomcat: [install_dir]/common/lib
For GlassFish: [install_dir]/domains/[domain]/lib
Default database
XMLPortal 3.0 uses Derby as default database. In case you want to use Derby copy derby.jar following the above instructions.
Default database isn't really a concept in XMLPortal 3.0, the fact is that the examples were constructed using Derby. Each component can have its own database, that is, its own JDBC connection url. If you don't mind about database issues then just use the default settings.
Mail system
XMLPortal 3.0 uses Java Mail for Mail Lists and Applies. Remember making mail.jar and activation.jar available to the application. You can do so following the above instructions.
Using libraries locally in your web application
Copying libraries into container makes them available for all web applications. I think this approach optimizes container's memory usage and makes it ready to support more XMLPortal powered applications. But I might be wrong or you could decide not to disturb your container and install all these libraries locally. To do so, copy the JAR files into application's /WEB-INF/lib folder.
Administering content
Once your application is up and running you can start administering content by adding /xplogin to application's home url. Type admin in both fields, login and password. You can also login as guest using guest in both fields.
|
