Figured out. Here is what works for both IE and Firefox:

<ice:outputMedia>
<f:param name="src" value="svgfilename.svg"/>
<f:param name="type" value="image/svg+xml"/>
<f:param name="height" value="300"/>
<f:param name="width" value="900"/>
<f:param name="pluginspage" value="http://www.adobe.com/svg/viewer/install/"/>
</ice:outputMedia>

Hi,
I'm trying to use this component ice:outputMedia to render SVG into the page. It works fine for Firefox, but not for Internet Explorer. Here is what I am doing:
<ice:outputMedia source="svgfilename.svg" mimeType="image/svg+xml" />

Can someone suggest what I need to do to get this working for IE. Thanks in advance.

1.7 Beta 1 will be released today which includes the component.

In answer to Sheng's question:
The component translates to an <object> tag and an <embed> tag. So it only has the capabilities of those tags. Those tags don't do true streaming. They rely on the browser to do some "fake" streaming? If the amount of media data is small, I suppose you can write it to a file and serve the file? Otherwise, I suppose you can point the media source URL to a servlet that reads the data from the DB and output it to the HTTP response output stream? I haven't done these before, so I am not 100% sure.

Great work guys is there any chance of getting a packaged war of the component to test it...
dim5b

It is very nice to see ICEfaces implemented the new component. Just a shot question, can the ice:outputMedia play a video/movie from byte data in database? Thank you.

Screenshot of testing the component showcase example.

Screenshot of testing the component. From left to right: flash player, windows media player, quicktime player, real player.

From Ken:
It looks like your missing some of our standard extended attributes, such as renderedOnUserRole and enabledOnUserRole.

From Frank:
Not sure if this component really need width and height. the function is already duplicated in style attribute.

IBM has a set of media player components that are useful to consider for reference

http://publib.boulder.ibm.com/infocenter/radhelp/v6r0m1/index.jsp?topic=/com.ibm.etools.webreference.doc/topics/rjsfallatt.html

however, it is likely not necessary for the developer to distinguish between the different media types at the component level as they have done.

To reduce the complexity of the HTML, it may be desirable to detect the user-agent and serve browser-specific HTML.

This component will have to be tested carefully under Ajax Push since some of the "browser-independent" HTML strategies make use of HTML that is not well formed. HTML that is not well-formed would be unpredictable under DOM update.

<ice:outputMedia value="#

" width="int" height="int"
controller="bool" autoplay="bool" type="mime-type-String" />

The outputMedia component can use the type to produce the correct
HTML for the particular piece of embedded media. Note that this
HTML is not simple in the cross-browser case:

http://www.alistapart.com/articles/byebyeembed

If the type is not present, it can be guessed from the extension of the value attribute.