On Sat, Sep 12, 2009 at 7:04 AM, measwel <marek_karczew...@yahoo.com.au>wrote:
> > LS, > > I would like to clarify some of the things one can encounter when looking > at > the appfuse code, which are not clear to a new user like me: > > 1) DB connectivity. One can see the DB connection properties defined in > pom.xml. These are obviously used when building or testing with maven. But > there are also jdbc references present in jdbc.properties and > ApplicationContext-resources.xml both in the main and test directories. > When > are these used? > jdbc.properties is read by applicationContext-resources.xml. I'm not certain there should be a *-resources.xml file in both src/main/resources and src/test/resources. If there is, I'd compare file contents and see if they're the same. If so, delete the one in the test directory. > > 2) Enigmatic files. > What are the following files used for: > - appfuse.tld > Tag Libraries - urlrewrite.xml > The UrlRewriteFilter, which allows you to make pretty URLs or even extensionless URLs. http://raibledesigns.com/rd/entry/extensionless_urls_in_java_web > The following files seem empty. Are they needed: > - resin-web.xml > Needed if you're using Resin, possibly not with the latest release. > - context.xml > > This is for Tomcat and allows you to configure your application to talk to Tomcat's resources. It also allows you to adjust the contextPath of your application w/o changing the name of your WAR. It's not necessary, but moreof a placeholder for you to configure your application with Tomcat. > 3) Web service. Why is the UserManager also implemented as a web service? > Is > it to demonstrate how a web service is to be implemented in appfuse? How is > security configured for it? Can anybody who connects to the webservice get > the list of users from my system? > It's mostly for demonstration purposes. Security is not configured for it. As far as "anybody" being able to connect - my guess is yes, but you'd have to write code to verify. > > 4) Generic Manager / Universal Manager confusion (at least I am confused > that is :). Why are they both present? Which one is preferred to be used > and > when? > Universal Manager has been deleted in trunk. > > 5) Code generation. The manager bean for a generated class gets defined in > context.xml, while the present beans are defined in > ApplicationContext-service.xml. Why is it so? > Code generation is designed to run in embedded mode. The applicationContext-service.xml file is stored in a JAR by default. That's why we modify the (originally empty) applicationContext.xml file. > > Furthermore; present classes like the UserManager extend the > UniversalManager, while generated classes make use of the genericManager. > Why? > Fixed in trunk. Hope this helps, Matt > > A clarification is much appreciated! > MPK > -- > View this message in context: > http://www.nabble.com/Some-appfuse-clarification-requested-tp25414317s2369p25414317.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net > For additional commands, e-mail: users-h...@appfuse.dev.java.net > >
