[JBoss Seam] - Re: <s:validate/>, <s:decorate> and Trinidad
by lowecg2004
Hi Pete,
Cheers for the tip. I'd seen that but my components are in simple="true" mode so I lose this sort of behaviour. I can't really change this either since:
1. simple="false" causes most components to use tables for their layout and this has implications for accessibility/screen readers etc. therefore I am avoiding it like the plague;
2. my screen design is sensitive to changes in the size of the fields - my fields are constrained to a relatively small space, so any expansion of my fields' real estate due to error messages will cause problems with layout;
3. Yes, I would need to customise the l&f. A custom skin would probably allow this, but the <s:decorate> offers the ideal solution in that I can report errors globally and then use simple field highlighting (say, change border colour or add a small icon) to draw attention to the offending field.
Are you familiar with the <s:validateAll> <s:decorate> UI tag code? I might look to creating a patch to handle Trinidad components - I wonder if making this modification is simple or potentially opening a huge can of worms?
Cheers,
Chris.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020071#4020071
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020071
19Â years, 2Â months
[Messaging, JMS & JBossMQ] - Message is redelivered more than once if MDB takes too long
by MrForms
We have a situation in our clustered environment.
Simply put, we receive a message in our JbossMQ server. There is a single MDB instance that gets notified when the message arrives.
It then calls a Stateless EJB on a node of the cluster. The processing by the EJB is VERY long, somewhere around 15 minutes (which is normal). The problem is that after a certain amount of time, the message gets redelivered even if the Stateless EJB completes normally and the transaction is finished/commited.
We have absolutely no exceptions, no logs etc. that indicates a problem.
The jmsRedelivered flag is set to true on the second call. Also, it is to be noted than when the call to the Stateless EJB is made from the MDB on the second try, it is done to another node in the cluster, probably because of the round robin implementation.
The transaction timeout in the jboss-service.xml is set to a high enough value and as said, there are no Rollbacks done. The MDB is container managed and set to auto consume on a commit. It seems that after a while the Message dispatcher is simply not aware of the successful completion and just redelivers the message.
Any help / comments or pertinent documentation would be appreciated.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020060#4020060
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020060
19Â years, 2Â months