Overriding components - bug or feature?
Overriding components - bug or feature?
- Subject: Overriding components - bug or feature?
- From: Marius Soutier <email@hidden>
- Date: Wed, 21 Apr 2010 11:04:41 +0200
Hi there!
I've just experienced a strange issue in WebObject 5.4. Our application uses several internal frameworks to display certain areas of the application. All frameworks are always included and only a property defines if the area should be displayed or not.
A colleague created a new framework which was a customer-specific version of an existing one. So he went ahead and copied the old components to the new framework and made sure the component classes were in a different package than the original ones. So far, no problem, he even enabled both frameworks side by side, everything working fine.
However, when we deployed it on the server, the framework that came first on the classpath was used over the other one - the Java classes were loaded correctly, only the WODs were wrong. I could reproduce this behavior on my machine, but not on my colleague's. Turns out he is still on WO 5.4.2, while I'm on 5.4.3.
Is this behavior known, intended? Is there a fix except renaming the components?
Thanks,
- Marius
_______________________________________________
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