No. I didn't know there was a ejb3 feature pack for was...
In the related forum, it is said that it needs exactly was v6.1.0.3 ma ybe it's your problem (we are in v6.1.0.7)
In fact we are using regular POJO + Hibernate 3.2.4 + @Transactional annotations and plain standard jta transactions.
I had to patch Hibernate to make it work (org.hibernate.JTATransactionFactory) to make it work due to a problem Hibernate tries to get the JTA Transaction Statusat some point in the sessioN/transaction lifecycle (pls search on hibernate for this one)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045146#4045146
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045146
I'm getting
| SEVERE: Error Rendering View[/index.xhtml]
| java.lang.RuntimeException: org.dom4j.DocumentException: jboss.com Nested exception: jboss.com
| at org.jboss.seam.core.Pages.getDocumentRoot(Pages.java:836)
| at org.jboss.seam.core.Pages.parse(Pages.java:822)
| at org.jboss.seam.core.Pages.createPage(Pages.java:179)
| at org.jboss.seam.core.Pages.getPage(Pages.java:154)
| ...
|
... the weird thing is, first render of the page works, I can even refresh, but when I hit the login button, if authentication succeeds it throws that exception, when authentication fails it just rerenders index with login fields. It works nice on development server, production server has no dns way out :(
... I'm guessing it has something to do with that offline dtd validation. I'm running jBoss 4.0.5.GA with SEAM 1.2.1.GA
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045141#4045141
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045141
This is a forum for JBoss MQ, not JBoss Messaging.
However, your question seems pretty general so I'll attempt to answer it.
In general it's up to you to make sure your durable subscription exists before you start sending messages to the topic.
You can't expect the jms provider to store messages for you if you haven't yet told it you want to store them.
If you are using MDBs, you can deploy an MDB that consumes from a durable subscription, which will get deployed at startup.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045135#4045135
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045135