[JBoss Seam] - ICEFaces components don't work using Dynamic Includes
by OoSVS
Hi
I have a problem.
I made a template similar to the component-showcase's template but in my case my content-facelet.xhtml has 5 dynamic includes. I have mainTemplate.xhtml that includes navigation.xhtml and content-facelet.xhtml. I start the application calling the archive vgrcDemo.xhtml (showcase.xhtml in component-showcase project).
The application run well, all the components and content are displayed (panel collapsibles, panelTab sets; tree; etc) but when I click on any component it doesn't work , however the connection status get in active state for a long time and then the browser shows me the page for default without changes (vgrcDemo.xhtml).
The log for this issue is:
18:00:10,856 ERROR [STDERR] Nov 12, 2007 11:00:10 PM com.sun.facelets.impl.DefaultFacelet refresh
INFO: Facelet[/layout/content-facelet.xhtml] was modified @ 11:00:10 PM, flushing component applied @ 10:59:46 PM
the strangest thing is that if I shutdown the server and after few minutes start it again, the componentes continues failing. However, if I shutdown my server for many hours and I start it again and prove my application without changes, the application and all components work fine.
But if i open any of xhtml archives,for example: content-facelet.xhtml and I make an insignificant change (for example: an space ) and i save it, when i run my application the log doesn't show any error but if I click on any component that belong to content-facelet.xhtml
the log show me:
18:25:14,296 ERROR [STDERR] Nov 12, 2007 11:25:14 PM com.sun.facelets.impl.DefaultFacelet refresh
INFO: Facelet[/layout/content-facelet.xhtml] was modified @ 11:00:10 PM, flushing component applied @ 11:25:11 PM
If i open navigation.xhtml and make the same change, and when I click on any component the log show me:
18:26:42,919 ERROR [STDERR] Nov 12, 2007 11:26:42 PM com.sun.facelets.impl.DefaultFacelet refresh
INFO: Facelet[/layout/navigation.xhtml] was modified @ 11:26:42 PM, flushing component applied @ 11:25:11 PM
18:26:42,935 ERROR [STDERR] Nov 12, 2007 11:26:42 PM com.sun.facelets.impl.DefaultFacelet refresh
INFO: Facelet[/layout/content-facelet.xhtml] was modified @ 11:26:42 PM, flushing component applied @ 11:26:38 PM
if I open mainTemplate.xhtml and make the same change, and when I click on any component the log only show me:
18:30:25,774 ERROR [STDERR] Nov 12, 2007 11:30:25 PM com.sun.facelets.impl.DefaultFacelet refresh
INFO: Facelet[/layout/mainTemplate.xhtml] was modified @ 11:30:25 PM, flushing component applied @ 11:30:20 PM
And if I shutdown the server and start it again, the componentes continues failing. However, if I shutdown the server for many hours and I start it again, the application and all components work fine.:S
I'm working with:
seam2
icefaces 1.6.1
jbossAs 4.2.2 on linux 1.5
firefox 2.0.0.3
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104300#4104300
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104300
18 years, 8 months
[JBoss Seam] - SpringTransaction exception handling enhancement required
by dapeng
Hi,
currently if a tx will be rollbacked, the SpringTransaction class kind of swallow the root cause in the following code
catch (TransactionSystemException e)
| {
| log.error("Exception cause:", e);
| throw new SystemException(e.getMessage());
| }
| catch (UnexpectedRollbackException e)
| {
| log.error("Exception cause:", e);
| throw new RollbackException(e.getMessage());
| }
It is essential to pass the whole cause exception in SystemException and RollbackException instead of only a text message.
My use case is the following:
JSF delete action method tries to delete a row in the db. When the tx commits, it discovers the row can not be deleted because of foreign key constraint. I would like to have the ConstraintViolationException wrapped in the RollbackException, so that I have a chance to handle this exception later with the exception handler.
In the current implmenetation, the RollbacklException with only text message and no cause stack will later be wrapped as an IllegalStateException, which is not helpful for exception handling at all.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104298#4104298
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104298
18 years, 8 months
[JBoss Messaging] - Re: Message stranded in cluster
by timfox
Looks like you are sending message to both of the partial queues, but both your service instances are connected to the same node for consuming.
For this kind of topology you probably only want each consumer to consumer from its local node? If so, then you should just use the standard connection factory /ConnectionFactory not /ClusteredConnectionFactory, this is how MDBs configured since clearly an MDB also only wants to consume from its local node.
/ClusteredConnectionFactory will round robin connections between nodes which is probably not what you want.
Also, you're using 1.4.0.CR2 this is a CR (non producttion) release and is superceded by 1.4.0.SP1. We're bringing out a SP2 soon too. I recommend you upgrade to that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104291#4104291
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104291
18 years, 8 months