I was wondering what one can do to eliminate style class collisions in portlets which return an EcsServletElement...for instance, we have some portlets that set up some request data for a JSP to render, then return an EcsServletElement w/ the URL of the JSP.
This works fine, but the style classes we are using are colliding with the ones of the same name that Jetspeed uses...for example, "td.content". I was wondering how this issue is addressed in general, i.e. how does the WebPagePortlet deal with style classes in content it retrieves from remote URLs, to avoid having the Jetspeed styles applied when you really want it formatted how it appears on the remote site. More specifically, does anyone have a solution for resolving this for internal URLs that doesn't involve either renaming all of Jetspeed's style classes or renaming all of ours? b.t.w., we already are familiar with skins, and have implemented our own. Is it feasible to simply delete the style classes from Jetspeed's "default.css" that are causing a problem, given that we have already implemented our own skin style? I welcome anyone's .02 on this. :) peace, Joe Barefoot -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
