Revision History
| Description | Author | Version | Date |
|---|---|---|---|
| Initial Creation | Scott Fehrman | 0.9.0 | December 2007 |
| Update for release | Scott Fehrman | 1.0.0 | January 2008 |
| Update for release, move to wiki | Scott Fehrman | 1.1.0 | August 2008 |
| Update / Testing with Netbeans 6.5 | Derrick Harcey | 1.1.1 | Jan 2009 |
This Document
This document provides instructions on how to use NetBeans with the OpenPTK source files.
Related Documents
Project OpenPTK includes a collection of related documents to assist teams that want to:
- Install Project OpenPTK in their environment
- Configure it for a specific situation
- Customize the samples
- Develop extra features
The following Project OpenPTK version 1.1 documents are available:
- Overview
- Release Notes
- Architecture Guide
- Configuration Reference Guide
- Developers Guide
- Samples Guide
- NetBeans Reference Guide
- Sample XML Configuration File (openptk.xml)
- Java Client (Consumer) APIs javadocs
Overview
This document will assist the developer in setting-up NetBeans Projects that leverage the various packages within Project OpenPTK.
The processes outlined in this document will allow the developer to leverage the bundled build process (ant and build.xml file) that is provided with Project OpenPTK while using the development features of NetBeans.
The process involves downloading the entire Project OpenPTK source code distribution and then creating a specific NetBean's projects (both Java and Web) that "map" to OpenPTK projects.
Setup
Create a directory (folder) structure which will be used to hold the Project OpenPTK checked-out source code and NetBeans Projects. This document will use the following variable for the structure:
| ${NB_HOME} | /work/Software/netbeans |
|---|---|
| ${PTK_HOME} | /work/Software/openptk |
NetBeans
Install NetBeans 5.5 or higher. The instructions in this document have been tested on Netbeans 5.5, 6.0, and 6.5. The screenshots included in this page were taken on Netbeans 6.0 on Mac OSX, other Netbeans versions and operating systems may vary slightly from these screenshots.
New NetBeans projects will be created for the components of the Project OpenPTK. The new NetBeans projects will be created under the
${NB_HOME} directory.
Project OpenPTK
Checkout the source code for Project OpenPTK from http://openptk.dev.java.net. Use the following svn command to obtain the source code.
Version 1.1, Released Oct 2008
svn checkout https://openptk.dev.java.net/svn/openptk/tags/release-1.1/openptk openptk-1.1 --username <username>
Current Development Release
svn checkout https://openptk.dev.java.net/svn/openptk/trunk/openptk openptk --username <username>
Replace the "<username>" with your java.net login or you can use "guest".
Place the source code tree under the ${PTK_HOME} directory. The following files/directories will be available:
bash-3.00$ ls -F PROJECT build.xml lib/ projects/ resource/
The projects sub-directory contains a collection of packages:
bash-3.00$ ls -F projects Apps/ OpenPTK/ Samples/
The "Apps" directory contains complete applications that demonstrate Project OpenPTK:
- CLI
- Portlets
- UserManagementLite
- WebServiceWSDL
The "OpenPTK" directory contains the three tiers of the project:
- Consumer
- Framework
- Service
The "Samples" directory contains focused projects that are used to test different parts of Project OpenPTK:
- JavaAPI
- Taglib
OpenPTK Framework
Create a NetBeans Project called "OpenPTK-Framework". The Framework package within Project OpenPTK is a core component and needs to be established first. This project will be needed by the other NetBeans projects.
New Project
|
|
Name and Location
Specify the name of the new NetBeans project and where it will be located.
|
|
Existing Sources
Add Project OpenPTK source files for the Framework (ONLY).
|
|
Includes and Excludes
| The last dialog will show all the Java files that will be referenced by the new NetBeans Project. This dialog allows you to include and/or exclude other files. No changes will be made. Click the "Finish" button. NetBeans will create the new Project. |
|
Verify New Project
After the project has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components of the new Project.
See the images below:
|
|
Clean and Build
You can now build the project. Select the "OpenPTK-Framework" Project from the Projects panel. Right-click on the selected project and select "Clean and Build". The Project should build successfully.
OpenPTK - Service - SPML
Create a "OpenPTK-Service-SPML" NetBeans Project that maps the Project OpenPTK's Service for SPML. The Service Provisioning Markup Language (SPML) Service is used by Project OpenPTK to interface with Sun's Identity Manager user provisioning solution.
New Project
|
|
Name and Location
Specify the name of the new NetBeans project and where it will be located.
|
|
Existing Sources
Add Project OpenPTK source files for the Service SPML.
|
|
| OPTIONAL: Add Sun SPML Service source files This additional source file is used for integration with Sun Identity Manager's SPML interface. It includes SPML extensions for authentication with userId and Password of the proxy user being used. This source file is highly recommended for integration with Sun Identity Manager. This source file also assumes that the openspml.jar file being used by the openptk framework will include the required extentions for authentication.
|
|
Includes and Excludes
| The last dialog will show all the Java files that will be referenced by the new NetBeans Project. This dialog allows you to include and/or exclude other files. No changes will be made. Click the "Finish" button. NetBeans will create the new Project. (If the Sun SPML source file was added an additional file will also be in the include SPMLSunService.java or SPMLSunOperations in OpenPTK v2.0) |
|
Verify New Project
After the project has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components of the new Project.
See the images below:
|
|
Resolve Dependancies
From the section above, "Verify New Project", notice that the Project is marked with a red exclamation symbol. This symbol indicates that there are references to other packages and/or libraries that are not resolved.
We need to configure this Project use the following:
- OpenPTK-Framework NetBeans Project.
- OpenSPML Library (openspml.jar)
|
|
|
|
Clean and Build
The red indicators on the project should now be gone. You can now build the project. Select the "OpenPTK-Service-SPML" Project from the Projects panel. Right-click on the selected project and select "Clean and Build". The Project should build successfully.
OpenPTK - Service - JNDI
Create a "OpenPTK-Service-JNDI" NetBeans Project that maps the Project OpenPTK's Service for JNDI. The Java Naming and Directory Interface (JNDI) Service is currently under development and incomplete. Some of it's classes are used by other Project OpenPTK packages and therefore needs to be created as a NetBeans project.
New Project
|
![]() |
Name and Location
Specify the name of the new NetBeans project and where it will be located.
|
![]() |
Existing Sources
Add Project OpenPTK source files for the Service JNDI.
|
![]() |
Includes and Excludes:
| The last dialog will show all the Java files that will be referenced by the new NetBeans Project. This dialog allows you to include and/or exclude other files. No changes will be made. Click the "Finish" button. NetBeans will create the new Project. |
![]() |
Verify New Project
After the project has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components of the new Project.
See the images below:
![]() |
![]() |
Resolve Dependencies
From the section above, "Verify New Project", notice that the Project is marked with a red exclamation symbol. This symbol indicates that there are references to other packages and/or libraries that are not resolved.
We need to configure this Project use the following:
- OpenPTK-Framework NetBeans Project.
|
![]() |
Clean and Build
You can now build the project. Select the OpenPTK-Service-JNDI Project from the Projects panel. Right-click on the selected project and select Clean and Build. The Project should build successfully.
OpenPTK - Service - JDBC
Create a "OpenPTK-Service-JDBC" NetBeans Project that maps the Project OpenPTK's Service for JDBC. The Java Database Connectivity (JDBC) Service is currently under development and incomplete.
New Project
|
![]() |
Name and Location
Specify the name of the new NetBeans project and where it will be located.
|
![]() |
Existing Sources
Add Project OpenPTK source files for the Service JDBC.
|
![]() |
Includes and Excludes:
| The last dialog will show all the Java files that will be referenced by the new NetBeans Project. This dialog allows you to include and/or exclude other files. No changes will be made. Click the "Finish" button. NetBeans will create the new Project. |
![]() |
Verify New Project
After the project has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components of the new Project.
See the images below:
![]() |
![]() |
Resolve Dependencies
From the section above, "Verify New Project", notice that the Project is marked with a red exclamation symbol. This symbol indicates that there are references to other packages and/or libraries that are not resolved.
We need to configure this Project use the following:
- OpenPTK-Framework NetBeans Project.
|
![]() |
Clean and Build
You can now build the project. Select the OpenPTK-Service-JDBC Project from the Projects panel. Right-click on the selected project and select Clean and Build. The Project should build successfully.
OpenPTK-Consumer-Taglib
Create a "OpenPTK-Consumer-Taglib" NetBeans Project that maps to Project OpenPTK's Consumer module for the JSP Taglib.
New Project
|
![]() |
Name and Location
Specify the name of the new NetBeans project and where it will be located.
|
![]() |
Existing Sources
Add Project OpenPTK source files for the Consumer Taglib package.
|
![]() |
Includes and Excludes
| The last dialog will show all the Java files that will be referenced by the new NetBeans Project. This dialog allows you to include and/or exclude other files. No changes will be made. Click the "Finish" button. NetBeans will create the new Project. |
![]() |
Verify New Project
After the project has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components of the new Project.
See the images below:
![]() |
![]() |
Resolve Dependencies
We need to configure this Project use the following:
- OpenPTK-Framework NetBeans Project.
- Servlet JSP Library (servlet2.5-jsp2.1-api.jar)
|
![]() |
|
![]() |
Clean and Build
The red indicators on the project should now be gone. You can now build the project. Select the "OpenPTK-Consumer-Taglib" Project from the Projects panel. Right-click on the selected project and select "Clean and Build". The Project should build successfully.
Samples-JavaAPI
The Samples-JavaAPI package contains Java programs that demonstrate the use of Project OpenPTK's Consumer Tier API.
New Project
|
![]() |
Name and Location
Specify the name of the new NetBeans project and where it will be located.
|
![]() |
Existing Sources
Add Project OpenPTK source files for the Samples JavaAPI package.
|
![]() |
Includes and Excludes
| The last dialog will show all the Java files that will be referenced by the new NetBeans Project. This dialog allows you to include and/or exclude other files. No changes will be made.
Click the "Finish" button. NetBeans will create the new Project. |
![]() |
Verify New Project
After the project has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components of the new Project.
See the images below:
![]() |
![]() |
Resolve Dependencies
We need to configure this Project use the following:
- OpenPTK-Framework NetBeans Project.
- OpenPTK-Service-SPML Project.
- OpenPTK-Service-JNDI Project.
- OpenSPML Library (openspml.jar, soap.jar, mail.jar, activation.jar)
- OpenPTK Configuration files.
|
|
|
![]() |
Clean and Build
You can now build the project. Select the "Samples-JavaAPI" Project from the Projects panel. Right-click on the selected project and select "Clean and Build". The Project should build successfully.
Running
|
![]() |
Samples-Taglib
The Samples-Taglib package contains Java Server Pages (JSPs) that demonstrates the use of Project OpenPTK's Consumer Tier custom JSP Taglib.
New Project
|
![]() |
Add Existing Sources
|
![]() |
Existing Sources and Libraries
| We will not be making any changes to this part of the set-up. Click the "Finish" button |
![]() |
Verify New Project
After the Web Application has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components.
See the images below:
![]() |
![]() |
Resolve Dependancies
Configure this Project use the following:
- Projects:
- OpenPTK-Framework
- OpenPTK-Service-SPML
- OpenPTK-Service-JNDI
- OpenPTK-Service-JDBC
- OpenPTK-Consumer-Taglib
- OpenSPML JAR files:
- openspml.jar
- soap.jar
- mail.jar
- activation.jar
- mysqljdbc.jar
- OpenPTK Configuration files
|
![]() |
Clean and Build
You can now build the project. Select the "Samples-Taglib" Project from the Projects panel. Right-click on the selected project and select "Clean and Build". The Project should build successfully.
Deploying and Running
If you are connected to the Internet, you can test the sample taglib JSPs. The default configuration for Project OpenPTK is setup to access a user repository (via SPML) hosted on http://www.openptk.org
Right-click on the "Samples-Taglib" project and select "Undelpoy and Deploy".
Right-click on the "Samples-Taglib" project and select "Run".
![]() |
![]() |
|
![]() |
|
![]() |
Apps-CLI
The Application CLI package contains is a Project OpenPTK solution that delivers a "Command Line Interface" (CLI) for performing user provisioning operations.
New Project
|
![]() |
Name and Location
Specify the name of the new NetBeans project and where it will be located.
|
![]() |
Existing Sources
Add Project OpenPTK source files for the Samples JavaAPI package.
|
![]() |
Includes and Excludes
| The last dialog will show all the Java files that will be referenced by the new NetBeans Project. This dialog allows you to include and/or exclude other files. No changes will be made. Click the "Finish" button. NetBeans will create the new Project. |
![]() |
Verify New Project
After the project has been created, verify it's components. Select the "Projects" tab and the "Files" tab. Explore tabs to verify the components of the new Project.
See the images below:
|
![]() |
Resolve Dependencies
We need to configure this Project use the following:
- OpenPTK-Framework NetBeans Project.
- OpenPTK-Service-SPML Project.
- OpenPTK-Service-JNDI Project.
- OpenPTK-Service-JDBC Project.
- OpenSPML Library
- openspml.jar
- soap.jar
- mail.jar
- activation.jar
- mysqljdbc.jar
- OpenPTK Configuration files.
|
![]() |
Add the missing run-time libraries (JAR files).
|
![]() |
Clean and Build
You can now build the project. Select the "Apps-CLI" Project from the Projects panel. Right-click on the selected project and select "Clean and Build". The Project should build successfully.
Running
If you are conncted to the Internet, you can test the sample java programs. The default configuration for Project OpenPTK is setup to access a user repository (via SPML) hosted on http://www.openptk.org
|
![]() |
Apps-UserManagementLite
The Apps-UserManagementLite package is a Project OpenPTK solution that delivers a custom web-based (JSP/Taglib) solution for performing user provisioning operations.
New Project
|
![]() |
Add Existing Sources
|
![]() |
Existing Source and Libraries
| We will not be making any changes to this part of the set-up.
Click the "Finish" button |
![]() |
Verify New Project
After the Web Application has been created, verify it's components. Select the "Projects" tab and the "*Files8" tab. Explore tabs to verify the components.
See the images below:
|
![]() |
Resolve Dependancies
Configure this Project use the following:
- Projects:
- OpenPTK-Framework
- OpenPTK-Service-SPML
- OpenPTK-Service-JNDI
- OpenPTK-Service-JDBC
- OpenPTK-Consumer-Taglib
- OpenSPML JAR files:
- openspml.jar
- soap.jar
- mail.jar
- activation.jar
- ldapbp.jar
- mysqljdbc.jar
- OpenPTK Configuration files
|
![]() |
Clean and Build
You can now build the project. Select the "Apps-UserManagementLite" Project from the Projects panel. Right-click on the selected project and select "Clean and Build". The Project should build successfully.
Deploying and Running
If you are connected to the Internet, you can test the sample taglib JSPs. The default configuration for Project OpenPTK is setup to access a user repository (via SPML) hosted on http://www.openptk.org
- Right-click on the "Apps-UserManagementLite" project and select "Undeploy and Deploy".
- Right-click on the "Apps-UserManagementLite" project and select "Run".
|
![]() |
|
![]() |
Apps-Portlets
The Apps-Portlets package is a Project OpenPTK solution that delivers a set of JSR-168 Portlets for performing user provisioning operations. The portlets include: Forgotten Password, Self Service and User Administration.
New Project
|
![]() |
Add Existing Sources
|
![]() |
Existing Source and Libraries
| We need to add the Java source packages:
Select the "Add Folder" Button for Source Package Folders. From the browse panel, locate the src folder that's under the Apps/Portlets folder. These folder are found in the ${PTK_HOME} folder. Select the src folder and click open Click the Finish button |
![]() |
Verify New Project
After the Web Application has been created, verify it's components. Select the Projects tab and the Files tab. Explore tabs to verify the components.
See the images below:
![]() |
![]() |
Resolve Dependancies
Configure this Project to use the following:
- OpenPTK Projects:
- OpenPTK-Framework
- OpenPTK-Service-SPML
- OpenPTK-Service-JNDI
- OpenPTK-Service-JDBC
- OpenPTK-Consumer-Taglib
- Third-party JAR files
- OpenPTK Configuration files
|
![]() |
Clean and Build
You can now build the project. Select the Apps-Portlets Project from the Projects panel. Right-click on the selected project and select Clean and Build. The Project should build successfully. A WAR file will be created in the dist directory called Apps-Portlets.war
Deploying and Running
If you are connected to the Internet, you can test the sample taglib JSPs. The default configuration for Project OpenPTK is setup to access a user repository (via SPML) hosted on http://sample.openptk.org
The WAR file needs to be deployed to a JSR-168 compliant Portal Server. This project has been tested with the open source JetSpeed 2.1.x portal server and the Sun Portal Server 7.1
Here are the Portlets running in JetSpeed:
Forgotten Password
|
![]() |
Self Service
User Administration
Apps-WebServiceWSDL
The Apps-WebServiceWSDL package is a Project OpenPTK solution that delivers a WSDL-based web service for performing user provisioning operations. The Project will need to generate JAX-RPC Java code to implement the solution.
| Warning This project uses JAX-RPC for the web service. You will need to install the JAX-RPC plug-in for NetBeans. If the plug-in is not installed, you will see an error message when you try to create the Web Service. |
You can check to see if the JAX-RPC plug-in is installed. Open the plugin manager and look for the plugin that is highlighted in the image below:

New Project
|
![]() |
Add Existing Sources
|
![]() |
Existing Sources and Libraries
| Nothing should need to be done on this page. Click the Finish button |
![]() |
Verify New Project
After the Web Application has been created, verify it's components. Select the Projects tab and the Files tab. Explore tabs to verify the components.
See the images below:
|
![]() |
| Note: The project will NOT build at this point. The source Java files have a dependancy on files that need to be generated. These files will be generated in a later step. You will see RED indicators on the files that can not resolve their dependancies. |
Resolve Dependancies
Configure this Project to use the following:
- OpenPTK Projects:
- OpenPTK-Framework
- OpenPTK-Service-SPML
- OpenPTK-Service-JNDI
- OpenPTK-Service-JDBC
- Third-party JAR files
- OpenPTK Configuration files
|
![]() |
New Web Service from WSDL:
Create the Web Service from the projects WSDL file.
NOTE: There is a known issue which may prevent this step on Netbeans 6.5 (http://statistics.netbeans.org/analytics/exception.do?id=151622), previous versions of Netbeans did not have this issue.
|
![]() |
Code generated
NetBeans created Java file under the "generated" package.
Some files need to be updated. The defined servlet class references the Web Service Implementation that was generated by NetBeans. We need to replace this with the ProvisionPerson class.
|
![]() |
Clean and Build
You can now build the project. Select the Apps-WebServiceWSDL Project from the Projects panel. Right-click on the selected project and select Clean and Build. The Project should build successfully. A WAR file will be created in the dist directory called Apps-WebServiceWSDL.war
Deploying
If you are connected to the Internet, you can test the Web Service. The default configuration for Project OpenPTK is setup to access a user repository (via SPML) hosted on http://www.openptk.org
Right-click on the "Apps-WebServiceWSDL" project and select "Undeploy and Deploy".
Running
Use Firefox to test access to the Web Services at this URL:
http://localhost:8080/ProvisionService/ProvisionPerson?wsdl
Review the WSDL
![]() |
soapUI
Download soapui from http://www.soapui.org to test the web service.
|
![]() |
| Name | Size | Creator (Last Modifier) | Creation Date | Last Mod Date | Comment | ||
|---|---|---|---|---|---|---|---|
| 56 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 62 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 56 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 25 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 35 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 56 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 64 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 77 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 36 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 40 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 82 kB | ScottFehrman | Sep 02, 2008 | Sep 02, 2008 | ||||
| 55 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 61 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 79 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 34 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 35 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 75 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 81 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 177 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 65 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 84 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 82 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 40 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 48 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 94 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 25 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 45 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 71 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 57 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 63 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 36 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 79 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 30 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 58 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 63 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 62 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 24 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 36 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 78 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 81 kB | ScottFehrman | Aug 26, 2008 | Aug 26, 2008 | ||||
| 38 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 27 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 32 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 29 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 54 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 61 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 60 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 28 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 24 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 77 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 91 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 40 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 85 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 88 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 29 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 28 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 103 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 37 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 38 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 57 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 57 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 80 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 84 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 26 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 25 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 82 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 102 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 32 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 38 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 26 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 37 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 40 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 27 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 36 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 47 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 42 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 39 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 88 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 82 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 85 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 38 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 28 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 78 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 93 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 91 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 68 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 42 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 153 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 16 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 52 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 117 kB | ScottFehrman | Sep 03, 2008 | Sep 03, 2008 | ||||
| 86 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 25 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 27 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 56 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 66 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 71 kB | harcey | Jan 06, 2009 | Jan 06, 2009 | ||||
| 63 kB | harcey | Jan 06, 2009 | Jan 06, 2009 |
































































































