"kukeltje" wrote : yes... use a 'globalOnly=true' on the top messages thing. Is a generic jsf issue though...
Hi,
Thanks for your response. This 'globalOnly=true' can be used with <h:messages> and as i don t want the default message at the top or not to be displayed so I am setting it as: <h:message globalOnly="false" /> but still on execution I am getting the error message at the top also as well as in the field level. I want the validation error messages to come on each field but not at the top in red(global)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209360#4209360
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209360
Hi
Now all webservices are logged to a file as xml. We need to log in a MySQL database. I used JDBCAppender and the configuration is as shown
<param name="sql" value="insert into logTable (message, class, priority, log_date)
values ('%m', '%c', '%p', '%d{dd.MM.yyyy}')"/>
<appender-ref ref="JDBC"></appender-ref>
But in the database, i get only debug and info, not the Traces from MessageTrace class
Why?
regards
KRS
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209358#4209358
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209358
"chris.laprun(a)jboss.com" wrote : It seems indeed like SharePoint is mangling the interaction state by appending the navigational state to it. This seems like something you might want to see with Microsoft as no WSRP producer can deal with modified interaction state (which is supposed to be treated opaquely by the consumer).
|
hmm if this is true, we do have a serious problem here...
I posted this question on msdn: http://code.msdn.microsoft.com/WSRPToolkit/Thread/View.aspx?ThreadId=1314
Any more clues where I can ask?
"chris.laprun(a)jboss.com" wrote :
| Another point, it seems as if your portlet is sending complete markup (i.e. a complete xhtml document) as opposed to a fragment as mandated by the specification. This might cause issues with portals as portlets are only expected to generate markup fragments to be aggregated in a complete page.
we will have to look into that issue, but i cannot imagine that it causes the mangled interactionState. :S
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209356#4209356
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4209356