• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOLips new Wonder app+framework creation fails
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOLips new Wonder app+framework creation fails


  • Subject: Re: WOLips new Wonder app+framework creation fails
  • From: Jonathan 'Wolf' Rentzsch <email@hidden>
  • Date: Wed, 18 Mar 2009 02:00:20 -0500

On Mar 17, 2009, at 11:40 PM, Chuck Hill wrote:
Is ERExtensions included? That is what has the properly genericized NSDictionary class.

Nice thought, but it's in there:

<http://skitch.com/rentzsch/bexbd/erextensions-it-s-in-there>

The "The type NSDictionary..." build error is only part of the picture -- it's transitory and often "goes away" when I force a rebuild of everything. However, the bug also results in a broken build -- Application.java never gets compiled, resulting in a "Exception in thread "main" java.lang.NoClassDefFoundError: your/app/Application" runtime error.

On Mar 17, 2009, at 9:33 PM, Jonathan 'Wolf' Rentzsch wrote:

When creating a new Wonder Application in Eclipse+WOLips that references an existing Wonder Framework project, I get a build error ("The type NSDictionary is not generic; it cannot be parameterized with arguments <String, Object>".

* Creating a new Wonder app referencing an existing non-wonder Framework project works.
* Creating a new Wonder app that doesn't reference any project frameworks, works.
* Creating a new non-Wonder app that references an existing Wonder Framework, works.


Here's a screencast of the reproduction:

<http://www.viddler.com/explore/rentzsch/videos/17/>

Console.app logs this error during when building the app:
org.eclipse.jdt.internal.compiler.problem.AbortCompilation
at org .eclipse .jdt .internal.compiler.ast.TypeDeclaration.abort(TypeDeclaration.java:72)
at org .eclipse .jdt .internal .compiler.problem.ProblemHandler.handle(ProblemHandler.java:157)
at org .eclipse .jdt .internal .compiler.problem.ProblemReporter.handle(ProblemReporter.java:1808)
at org .eclipse .jdt .internal .compiler.problem.ProblemReporter.handle(ProblemReporter.java:1871)
at org .eclipse .jdt .internal .compiler .problem .ProblemReporter .nonGenericTypeCannotBeParameterized(ProblemReporter.java:5189)
at org .eclipse .jdt .internal .compiler .lookup .ParameterizedTypeBinding.resolve(ParameterizedTypeBinding.java:844)
at org .eclipse .jdt .internal .compiler .lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:104)
at org .eclipse .jdt .internal .compiler .lookup .ParameterizedTypeBinding.resolve(ParameterizedTypeBinding.java:839)
at org .eclipse .jdt .internal .compiler .lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:104)
at org .eclipse .jdt .internal .compiler .lookup.BinaryTypeBinding.resolveTypesFor(BinaryTypeBinding.java:907)
at org .eclipse .jdt .internal .compiler .lookup .MethodVerifier15.computeSubstituteMethod(MethodVerifier15.java:531)
at org .eclipse .jdt .internal .compiler .lookup .MethodVerifier15.isParameterSubsignature(MethodVerifier15.java:727)
at org .eclipse .jdt .internal .compiler .lookup.MethodVerifier15.areMethodsCompatible(MethodVerifier15.java: 38)
at org .eclipse .jdt .internal .compiler .lookup.MethodVerifier.computeInheritedMethods(MethodVerifier.java: 559)
at org .eclipse .jdt .internal .compiler .lookup.MethodVerifier.computeInheritedMethods(MethodVerifier.java: 493)
at org .eclipse .jdt .internal.compiler.lookup.MethodVerifier.verify(MethodVerifier.java: 858)
at org .eclipse .jdt .internal .compiler.lookup.MethodVerifier15.verify(MethodVerifier15.java:780)
at org .eclipse .jdt .internal .compiler .lookup.SourceTypeBinding.verifyMethods(SourceTypeBinding.java:1666)
at org .eclipse .jdt .internal .compiler .lookup .CompilationUnitScope.verifyMethods(CompilationUnitScope.java:794)
at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java: 740)
at org .eclipse .jdt .internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java: 137)
at java.lang.Thread.run(Thread.java:613)


I'm pretty much on the latest of everything. I'm on Mac OS X 10.5.6. Eclipse 3.4.2, WOLips 3.4.5694, WebObjects 5.3.3, http://webobjects.mdimension.com/wonder/Wonder-latest-Frameworks-53.tar.gz @ 17-Mar-2009.

- jwr

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


-- 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/products/practical_webobjects








- jwr

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: WOLips new Wonder app+framework creation fails
      • From: David Avendasora <email@hidden>
References: 
 >WOLips new Wonder app+framework creation fails (From: Jonathan 'Wolf' Rentzsch <email@hidden>)
 >Re: WOLips new Wonder app+framework creation fails (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: WOLips new Wonder app+framework creation fails
  • Next by Date: Antw: Re: Prevent 'NSUtilities.rawRowsForSQL()' from making changesin the database
  • Previous by thread: Re: WOLips new Wonder app+framework creation fails
  • Next by thread: Re: WOLips new Wonder app+framework creation fails
  • Index(es):
    • Date
    • Thread