[JBoss Seam] - Redisplaying generated pictures
by zakhan
Hi guys,
could anybody give me a hand on this, please. I have page which contains 2 graphs, which are generated pictures stored somewhere in my temporary folder on the hard drive. This part of page is enclosed in <a:outputPanel> tag. When I reRender this part using <a:support> the graphs change physically on the hard drive, but not on the page. There are several other items in the same <a:outputPanel> which change properly. The situations looks like this:
| <a:outputPanel id="projectEfforts">
| <h:graphicImage style="border:0" alt="Normal graph" url="#{graphNormalURL}"
| usemap="#chart" />
| <h:outputText escape="false" value="#{normalGraphData.HTMLArea}" />
| <h:outputText escape="false" value="#{normalGraphData.dayDetailsStr}" />
| <br />
| <h:graphicImage url="#{graphCumulativeURL}" alt="Cumulative graph" />
| </a:outputPanel>
|
For example, I use area tag for the graph to be clickable (#{normalGraphData.HTMLArea} in this example) and this is reloaded in the same function as the graphs. After the ajax call is changed and reRendered properly on the page, but the images are not.
Many thanks in advance,Z
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076926#4076926
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4076926
18Â years, 8Â months
[JBoss Portal] - Re: LDAP Authentication
by sohil.shahï¼ jboss.com
Guys-
A simple explanantion for the admin user requirement is that the CMS Security Engine, is built to provide unix like access control to resources stored in the cms (read,write,manager) to users and groups of users (we call roles in portal lingua).
Now, the 'admin' user is designated as what we call 'root' in the Unix world. The reason being, say you have your security policy fudged up, and no one can access the system, someone with access to the 'admin' account, can go in and fix things without any restrictions. However, just like the root user, admin user information should be kept secret.
Now, I will have to look and see if 'root' designation can be made configurable to any user you suggest instead of the core 'admin' user that is selected in the code.
I will update the JIRA task with details on the fix.
Thanks again
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076923#4076923
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4076923
18Â years, 8Â months