Re: WO and Java 'packages'?
Re: WO and Java 'packages'?
- Subject: Re: WO and Java 'packages'?
- From: Dov Rosenberg <email@hidden>
- Date: Wed, 21 Apr 2004 21:46:36 -0400
When we develop our frameworks we always use distinct packages for each
framework. All of our subprojects are also in their own packages. Our
Application, Session, DirectAction, and Main classes are also in packages.
What we found is that the bindings must either be public or have public
get/set methods. Every binding in all components must have a public
interface otherwise the WO runtime will cause errors complaining about
bindings not found for WOComponent xyz.
When you place your Application into a package and deploy as a servlet you
need to modify the web.xml to indicate the fully qualified class that is
your Application.java.
You DO NOT need to use the fully qualified path in pageWithName() calls, the
WO components are loaded by the resource loader in WO just the same as
always.
You DO NOT need to use fully qualified classes in your WOD bindings
You DO need to fully qualify your classes in EOModeler
--
Dov Rosenberg
Conviveon Corporation
http://www.conviveon.com
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.