On Jun 23, 2008, at 5:27 PM, Joshua Dubey wrote:
> Hi,
>
> I having a strange problem where after renaming a framework, the
> dependent applications are no longer finding its bundle if I run/
> debug the applications from within wolips.
>
> Scenario:
>
> I had a framework MyFramework. Within it was a class Foo, which
> had the line
>
> bundle = NSBundle.bundleForClass(this.getClass());
>
> Applications which used this framework would call the above on
> startup. It worked fine, i.e. a bundle was returned.
>
> Recently, I renamed the framework to MyNewFramework. Nothing else
> was changed. Build paths of dependent projects were updated and
> everything builds fine. However, now
>
> bundle = NSBundle.bundleForClass(this.getClass());
>
> returns null. This happens whether MyNewFramework is added to the
> build path as a dependent project or an external jar.
>
> Any ideas? What have I missed?
Did the build.properties file in the framework get updated? If so,
carefully check what the launch configuration is using for a
classpath. A full clean and rebuild of everything is in order if
that all looks OK.
Chuck
--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
This archive was generated by hypermail 2.0.0 : Tue Jun 24 2008 - 20:36:07 EDT