> yes, yes, of course - sorry. I should read more carefully. I thought > Matthias meant that it's easier to debug if you do not have splittet > jars - API and Impl. One of the other 7 discussions we are having > concurrently within this thread, you know. ;-) > Debugging "shared" IS horror today, sure! Agreed!
"easy" means minimum of the horror. > > I don't see any reason why we shoulnd't being able to provide a stable > > api even for shared. > > Thing is: One beneficiary of shared (and not the least important!) is > the myfaces-impl, which is a candidate to be provided by J2EE > containers. Therefore we MUST ensure that ALL classes that form the > actual jsf implementation reside in a private namespace. This is the > only way to avoid unwanted sideeffects when users deploy their apps > together with other beneficiaries of "shared" (Tomahawk, ...) > Please note: this is no unusual case. Some containers use re-packaged > XML-Parsers to avoid unwanted sideeffects when a user deploys an app > together with a newer (or older) Xerces. Even Sun Java runtime is > shipped with a re-packaged Xalan. right, /com/sun/foo/org/apache/.... is there, always. So, no real way around? (perhaps not for -impl?) > > --Manfred > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
