Hi Dmytro, someone who uses EOF might probably be better able to help you. But just for testing I tried this out: Opened an old project that uses EOF, created a FetchSpec in a model in a framework it referenced and was successfully able to get to it using EOFetchSpecification.fetchSpecificationNamed( "FetchSpecName", "EntityName" ).
So not much help here—I just wanted to confirm that it *should* work. Does the framework throw a stack trace at you or do you just get null when attempting to resolve the fetchSpec? Cheers, - hugi > On 29 Apr 2019, at 17:38, Kantala, Dmytro R. <dkant...@motleyrice.com> wrote: > > > > I finally gotten around to make the switch from Ant to Maven, really had to. > I am able to successfully build the project, so far everything runs in > eclipse, and attempting to run from command line. > > The first thing this app does is use a fetch spec to pull in some entities. > This is failing because it can’t find the fetch spec by name. I then wrote > some code that looked over the entities to see if any fetch specs were loaded > and none were. > > It appears to find the plist from the jar, just not the fetch specs. > > How did everyone get around this issue? > > Environment: > - Wonder 7.1-SNAPSHOT > - WebObjects 5.4.3 > - The model is in a framework used by the application. > - I can open the Maven packaged framework jar and see the .fspec > files. > - Windows 10 > - JDK 1.12 (had same issue with 1.9) > > Thanks, > > Dmytro > > > Confidential & Privileged > > Unless otherwise indicated or obvious from its nature, the information > contained in this communication is attorney-client privileged and > confidential information/work product. This communication is intended for the > use of the individual or entity named above. If the reader of this > communication is not the intended recipient, you are hereby notified that any > dissemination, distribution or copying of this communication is strictly > prohibited. If you have received this communication in error or are not sure > whether it is privileged, please immediately notify us by return e-mail and > destroy any copies--electronic, paper or otherwise--which you may have of > this communication. > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com > <mailto:Webobjects-dev@lists.apple.com>) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is > <https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is> > > This email sent to h...@karlmenn.is <mailto:h...@karlmenn.is>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
