struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Marrotte" <marro...@nicusa.com>
Subject JSP (with Struts tags) for Child Support Payments
Date Thu, 06 Jun 2002 13:46:20 GMT
Here's the JSP and XML config files for the Child Support Payment System.  I
know it's still not enough to completely analyze the system, but it might
give some ideas on how I implemented certain behaviors with Struts.  Feel
free to read the JSP and use the system.  Below is my last post that
includes info on getting started.  I hope to have a complete package with
source coming soon.

--Michael Marrotte

I recently finished a beta release of a Child Support Payment (CSE-PAY)
system for the state of Florida.  The system is a Struts-based webapp where
I use several Struts features -- as much Struts as I could figure for my
first Struts project.

You can access the system at:

http://test.myfloridacounty.com/cse-pay/

Login to the web server with:

User:  myflc
Pass:  myflc

Once logged in you're welcome to experiment with the system as much as you
like, i.e. sign up a phony user, credit card (e.g. Visa 4111111111111111),
add casses, make payments, etc...

I have not got the OK to release all the source as a bundle, yet.  But, I
can release snippets on a case-by-case basis -- that is, I can send the code
that implements some behavior you're interested in.  Hopefully I can release
the complete source, soon.

The system connects to two private and distinct (Oracle, Informix) DBMS.  To
release all the source I might create mock copies of the databases
(usernames, passwords).

My intention in releasing this to the Struts User Group is two-fold.  First
I would like to give back for all the help I received from the group putting
this project together.  Second I hope that users might help do beta testing
as a side-effect.

Don't be afraid to make payments with a fake credit card number (e.g. Visa
4111111111111111).  None of the orders are attached to a real merchant
account.  But, They will get processed by our payment engine where I can do
some analysis.

Here's some test data for data entry into the system:

UNIFORM CASE NUMBERS
COUNTY       LEGACY CASE NUMBER    UNIFORM CASE NUMBER

12            22-0000023-CA  121922DR000023CAXXCR
12            22-0000024-CA  121922DR000024CAXXCR
12            23-0000065-CA  121923DR000065CAXXCR
12            23-0000076-CA  121923DR000076CAXXCR
12            23-0000096-CA  121923DR000096CAXXCR
12            25-0000059-CA  121925DR000059CAXXCR
12            26-0000036-CA  121926DR000036CAXXCR
12            54-0000044-CA  121954DR000044CAXXCR
12            73-0000000-CA  121973DR000000CAXXCR
12            73-0000015-CA  121973DR000015CAXXCR

12 is Flagler county...

LEGACY CASE NUMBERS
County 01 (Alachua)

00-0000000-DR
00-0000009-DR
00-0000017-DR
00-0000023-CA
00-0000029-DR
00-0000030-DR
00-0000035-DR
00-0000039-DR
00-0000040-DR
00-0000041-DR
00-0000044-DR
00-0000051-DR
00-0000060-DR
00-0000067-DR


County 02 (Baker)

00-0000002-DR
00-0000012-DR
00-0000015-DR
00-0000020-DR
00-0000022-DR
00-0000023-DR
00-0000024-DR
00-0000025-DR
00-0000026-DR
00-0000027-DR
00-0000028-DR
00-0000041-DR
00-0000042-DR
00-0000043-DR


County 03 (Bay)

00-0000000-CA
00-0000034-CA
00-0000035-CA
00-0000036-CA
00-0000041-CA
00-0000042-CA
00-0000043-CA
00-0000056-CA
00-0000071-CA
00-0000075-CA
00-0000078-CA
00-0000080-CA
00-0000082-CA

Please let me know what you think.

--Michael Marrotte

Mime
View raw message