The plot thickens...

I'm not sure if this is a bug in wolips or what.

But the symptoms are:

-When you run the app you get an error like: Class 'Session' exists
(interfacce org.jabsorb.client.Session) but is not a subclass of WOSession.
-In the component validation, some (but not all components) will give: The
class for 'X' is either missing or does not extend WOElement.
-Bundleless builds do not work, but Bundle builds work fine.

I discovered a bizarre fix... in the .project file for the app if you switch

<nature>org.objectstyle.wolips.incrementalapplicationnature</nature>


to

<nature>org.objectstyle.wolips.incrementalframeworknature</nature>


then everything works fine again.  But that doesn't quite make sense to me.
 I downloaded the wolips source and I haven't a clue why this would or
would not work.


On Fri, Feb 17, 2012 at 5:06 PM, John Huss <johnth...@gmail.com> wrote:

> I think you should spend a few more weeks on this.  That's the responsible
> thing to do.
>
>
> On Fri, Feb 17, 2012 at 2:06 PM, Ted Archibald <ted.archib...@gmail.com>wrote:
>
>> Feels like I'm beating a dead horse:
>>
>> After trying many combinations of changes I finally found one change that
>> helps.  If I have wolips generate bundles, everything works perfectly.  But
>> I wonder how I can get bundleless builds to work again.
>>
>> If I have wolips generate bundles, clean the project then run, everything
>> is back to normal.  But if I go back to bundleless builds, then the issues
>> come back.
>>
>
 _______________________________________________
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

Reply via email to