Actually, I'd keep the decision out of the Action, too.
I would create a TransactionHandler class that does it. You pass it
the information, and it returns information back - it should know
nothing about your web front end, and your web front end should know
as little as possible about the business logic in the backend.
That would also have the added benefit of hiding the strategy pattern
as well, so if you decide that I am smoking crack, and that you want
to implement it a different way, you have an easier time refactoring
and testing (because you do not need struts for the unit tests).
Larry
On Tue, 01 Feb 2005 12:58:02 -0500, Brandon Mercer <[EMAIL PROTECTED]> wrote:
> So check to see what type of transaction it is in the Action and then
> send it to the corresponding method in the data class? Sounds good,
> Brandon
> Larry Meadors wrote:
>
> >I think I'd use a strategy pattern for this. Basically, one interface
> >with several implementations; the implementation is dynamically
> >selected at runtime, based on the tranaction type.
> >
> >Larry
> >
> >On Tue, 01 Feb 2005 12:19:03 -0500, Brandon Mercer <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Ok, I've officially NOT followed some standard somewhere. :-( Shame on
> >>me! Can somebody help me with the following predicament? I've got a
> >>table of transactions that need to be processed. In that table I have a
> >>column for that persons account number... which gets assigned in a
> >>different table which is keyed on account number and transaction number
> >>:-(. So I can't very well insert.... (break in thought) so I guess I
> >>don't NEED to key it on transaction because that particular table of
> >>information will only have ONE entry with one account number. This
> >>brings me to my next crossroad.
> >>
> >>Lets say that I have a table that has a field that references another table
> >>+--------------+---------------------+
> >> | transcode | typeoftrans |
> >>+--------------+---------------------+
> >> |00000002 | payment |
> >>+--------------+---------------------+
> >> |00000003 | transfer |
> >>+--------------+---------------------+
> >>
> >>and the value of transtype determines the next table that I have to
> >>insert information into. How do I handle the insert of information in
> >>that scenario? I've got as far as INSERTing it into the first table,
> >>recalling the transcode (which auto_inc), and I know the type of
> >>transaction before I do the insert. Is it best to just have some logic
> >>in my data class that says if (typeoftrans.equals("somevalue")) {
> >>perform this insert
> >> }
> >>I think I may have just answered my own questions... but I'm curious to
> >>see how the savvy struts pros would do it :-). Thanks!
> >>Brandon
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
