I can duplicate the bug on my computer by creating a new wonder app called test1.0
Something in wolips doesn't like the period, or at least something on my computer doesn't. And I can assure it's not a classpath issue because I meticulously copied and pasted EVERY file between a non-working app and a working app and the only difference came from 3 things: 1) turning off bundleless builds 2) setting <nature>org.objectstyle.wolips.incrementalframeworknature</nature> in .project or 3) removing the period from the app name. Moreover, this ONLY affected my eclipse builds and not my jenkins builds. So IMO, everything seems to be pointing to something in the incremental app builder and the name of the app. Luckily I just migrated over to git the last weekend, so now I'm not so scared to rename apps and merge it back, so I can finally move on. On Mon, Apr 2, 2012 at 1:02 PM, Chuck Hill <ch...@global-village.net> wrote: > That also seems unlikely. This should be a classpath order problem and > having ERExtensions first on the classpath (assuming you are using it, > WOLips should do this) should prevent this error. > > Chuck > > > On 2012-04-02, at 9:32 AM, Ted Archibald wrote: > > > Well I think I got it cased now, I think it's because the app name had a > period in the name, perhaps that freaks out the incremental builder. > > > > On Mon, Apr 2, 2012 at 9:34 AM, Ted Archibald <ted.archib...@gmail.com> > wrote: > > 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/chill%40global-village.net > > > > This email sent to ch...@global-village.net > > -- > Chuck Hill Senior Consultant / VP Development > > Practical WebObjects - for developers who want to increase their overall > knowledge of WebObjects or who are trying to solve specific problems. > http://www.global-village.net/gvc/practical_webobjects > > > > > > > > >
_______________________________________________ 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
