Re: [Wonder-cvs] any reason for framework double-includes?

[Ray K. <ra...@ga...>]

On Jan 25, 2010, at 12:53 PM, Mike Schrag wrote:

> I know that at the app level, you have to include explicitly ...  
> It's a painful story, but if you want to be able to override a class  
> in WO inside one of your frameworks, you can't have transitive  
> dependencies turned on, otherwise the order gets messed up.
>
> Take, for example, ERX, which depends on JavaFoundation. If you have  
> your own framework RayExtensions that depends on ERX, and some other  
> framework that depends on ERX, you get kind of screwed. Only the  
> FIRST framework you include can override a class in the base  
> frameworks, because:
>
> YourApp
> 	RayExtensions
> 		ERX
> 			JavaWebObjects
> 			JavaFoundation
> 	OtherFramework
> 		ERX
> 			JavaWebObjects
> 			JavaFoundation
>
> Notice that Ray brings in ERX and JavaWebobjects before  
> OtherFramework. If OtherFramework wants to override foundation  
> classes, it can't, because JavaFoundation was already brought in  
> first in the classpath. To free your app to be able to control this  
> explicitly, we turn off transitive dependency exporting from child  
> frameworks. This makes it more annoying at the app level, but if we  
> don't, it's basically impossible to resolve that problem (which i  
> had).
>
> ms

Well, my "correctness" spider-sense tingles annoyingly at this answer,  
but it certainly seems to be a good reason to do anything very  
carefully, or more to the point, to not touch it.

There is somewhere on the wiki we could be documenting these issues  
and I will see if I can locate the place and put something there.

Thanks for the response.

- ray


>
> On Jan 25, 2010, at 3:45 PM, Ray Kiddy wrote:
>
>>
>> I was curious if this is just accidental or, for some reason,
>> something we did on purpose. There are lots of projects that have
>> something in their build path that is already in something else in
>> their build path. For example, ERExtensions references
>> JavaWOJSPServlet. Then, there are a bunch of projects that reference
>> ERExtensions and JavaWOJSPServlet in their build paths. It seems that
>> they could just use ERExtensions. Unless there is some reason to
>> doubly-reference the JavaWOJSPServlet framework that I am not seeing.
>> Is there a reason?
>>
>> cheers - ray
>>
>>
>> ------------------------------------------------------------------------------
>> The Planet: dedicated and managed hosting, cloud storage, colocation
>> Stay online with enterprise data centers and the best network in  
>> the business
>> Choose flexible plans and management services without long-term  
>> contracts
>> Personal 24x7 support from experience hosting pros just a phone  
>> call away.
>> http://p.sf.net/sfu/theplanet-com
>> _______________________________________________
>> Wonder-cvs mailing list
>> Won...@li...
>> https://lists.sourceforge.net/lists/listinfo/wonder-cvs
>
>
>