Hi all,
I have come up with a pretty good way to use EOModeler to manage Java
Interfaces as well as normal classes. By using a combination of
entries in the userInfo dictonary and EOGenerator custom templates I
can get EOGenerator to generate interfaces properly and put the
proper "implements xyz" in any class flagged in EOModeler as
implementing the interface. It works very slick.
With one exception. (come on, you knew it was coming)
Because this is a Java Client project, not a Web Client, the custom
classes generated by EOGenerator are all on the CLIENT side and must
be put in the Web Server target (confusing, I know), but the
application will only function properly if I put them in the
Application Server target, which causes my other custom logic NOT to
work.
This problem seems to be a Java Client problem, so I'll post the
interface creation instructions to the list later as well.
Dave
_______________________________________________
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]
