Hi Paul,
On 25/06/2011, at 22:09, Paul Hoadley wrote:
> An advantage of being in an obscure timezone is having conversations with
> yourself on mailing lists...
>
> On 26/06/2011, at 9:37 AM, Paul Hoadley wrote:
>
>> On 26/06/2011, at 8:30 AM, Paul Hoadley wrote:
>>
>>> On 26/06/2011, at 4:23 AM, Henrique Prange wrote:
>>>
>>>> Is the framework B in the classpath when running your tests? WOUnit rules
>>>> are unable to load eomodels for bundles that are not in the classpath (in
>>>> this case the test's classpath).
>>>>
>>>> If framework B is in classpath, the following configuration should be
>>>> enough:
>>>>
>>>> public MockEditingContext ec = new MockEditingContext("Foo", "SomeModel");
>>>
>>> That's what I would have thought, and yes framework B is on the classpath.
>>
>> Let me revise that slightly. On the classpath (built by WOPath in
>> build.xml) are all the JARs contained within Framework B, but none of those
>> contain the model. How do I make the model visible at test time?
>
> Apparently it needs a path element pointing right down to the Resources
> folder of the framework:
>
> <pathelement location="Root/Library/Frameworks/B.framework/Resources" />
>
<pathelement location="Root/Library/Frameworks/B.framework" /> should also work
(I haven't tested).
> This is in addition to the classpath I set up using the WOPath element.
> Sorry for the noise, Henrique—obviously this is not actually related to
> WOUnit.
>
Your scenario is a very common use case. I'll improve the documentation on the
website to illustrate this scenario and how the configuration should be made.
Thanks again for your feedback.
Cheers,
Henrique _______________________________________________
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]
