I think that you have your perspective reversed. If you are going to
use any D2W technology in your app, you basically have a D2W app. You
may do most of the work outside D2W, but you will still need all the
frameworks and basic application setup of a D2W app.
Again, I do D2JC, not D2W so I may be off-base here.
Dave
On Dec 2, 2008, at 7:43 AM, Paul Hoadley wrote:
On 02/12/2008, at 10:22 PM, Paul Hoadley wrote:
On 02/12/2008, at 9:46 PM, David Avendasora wrote:
Do you have a .d2wmodel file in your project that has the
appropriate rule in it for the list function of the AMPerson entity?
No. Though that's where I was heading next. What would that rule
look like? (And would it go in user.d2wmodel or d2w.d2wmodel,
which I see are the two files generate when I create a new D2W
project?)
Actually, just in case I've confused the issue here: I created the
new (Wonder) D2W project just to see what it would look like. I'm
not making a full-blown D2W app. All I really want to do is use
some D2W reusable components in an existing non-D2W app. I started
with D2WList, and didn't get very far.
--
Paul.
w http://logicsquad.net/
h http://paul.hoadley.name/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
