• 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: Can't get the Apple examples run
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't get the Apple examples run


  • Subject: Re: Can't get the Apple examples run
  • From: "Yung-Luen Lan" <email@hidden>
  • Date: Sat, 19 Apr 2008 22:27:32 +0800

Thanks, Mike. It really clarify my confusion about build path.

Regards,
yllan

On Thu, Apr 17, 2008 at 1:33 AM, Mike Schrag <email@hidden> wrote:
>
> > I don't have the time to watch your movie.  There is a very good chance
> that the Apple examples simply do not work with Wonder installed.
> >
> > Look at your error message.  It is complaining about JavaWOExtensions.
> This comes with WO and also comes with Wonder (Wonder has a fixed version).
> You probably have both of them installed.
> >
>  Yes ... The WO Examples are sort of messed up.  For one, they link against
> WO Eclipse source projects, which obviously nobody has but Apple, which is
> what you fixed in the first part.  But the other problem is that you're
> mixing framework and jar file libraries.
>
>  If you look at the build path for WOExamples, it depends on
> WOComponentExamples and WOComponentElements.  In WOExamples, you added the
> bundle versions (.framework folders) of the WO frameworks via the WebObjects
> Libraries build path container.  However, if you look at the build path of
> WOComponentExamples (which it depends on), that has the jar file library
> versions on the classpath.  You then end up with two versions of the same
> framework (from different places) in your build path.  If they were both the
> jar version or both the bundle version, WOLips will remove duplicates, but
> with the jar version and the framework bundle version it doesn't really know
> they're the same, and it sends them on their way into WO, which then
> explodes with a duplicate bundle error.
>
>  I actually have a patched version of NSBundle, and I've submitted a patch
> to Pierre for it also, to prevent this from being a catastrophic failure,
> which I don't believe it should be in most cases.  This should really be a
> warning, as the most common explanation is this exact scenario.
>
>  Anyway, you have two choices -- either switch the WOExamples framework to
> link to the jar frameworks like the dependent projects do, or switch the
> dependent projects to link to the bundles.  Pierre/Apple recommends going to
> the jar framework ... I personally don't like them and only use the bundles
> ... Both are supported (and, as I understand, will continue to be), but this
> is a great debate for another day :)
>
>  ms
>
>
>  _______________________________________________
>  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
>
 _______________________________________________
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

References: 
 >Can't get the Apple examples run (From: "Yung-Luen Lan" <email@hidden>)
 >Re: Can't get the Apple examples run (From: Chuck Hill <email@hidden>)
 >Re: Can't get the Apple examples run (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: WOTextField to BigDecimal
  • Next by Date: Re: IE SSL cache bug
  • Previous by thread: Re: Can't get the Apple examples run
  • Next by thread: Upgraded to Leopard - what do I need to do?
  • Index(es):
    • Date
    • Thread