Hi Bruce,

Bruce Snyder wrote:

Thanks for building the application. I'm very curious to take a
look at it.

Great, I look forward to hearing your thoughts, comments, and criticisms.

At this time, I have an odd question. How is the code in the jspf
file used? I see that it is used to determine what type of AggregatorDAO
to use, but I'm not sure how actual Java code is used, so I'm very
curious. I've always used a properties file for this type of thing
where the class type is grabbed by a Broker object to take a separate
path through the app to hand out the proper DAO type. Please explain
how the jspf file contents are used.

That setup.jspf file is just a JSP fragment that is included in my other JSP pages, it is responsible for creating the DAO implementation and putting it into the web application context. This is not a best practice.

It would be much better to do what you suggested, use a property file or a Servlet Context parameter to specify which DAO implementation class is to be used. Right now the only way to switch from Hibernate to Castor is to edit that setup.jspf file.

- Dave




Thanks,
Bruce
--

perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'

----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev



----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev

Reply via email to