does this happen if you take your jar / project and deploy ti once from the
command line via file system copy? is it just a tooling error or does it also
happen always?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255837#4255837
Reply to the post :
http:
Thank you, that worked.
I thought it had to do with birt-seam integration, not just a jboss problem.
Thank you all really much - Problem solved
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250247#4250247
Reply to the post :
http://www.jboss.org/index.
Continuous redeployments without any apparent changes is a known bug in
AS-5.1.0 with Seam applications
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156898. It has been
fixed in JBDEPLOYERS project:
https://jira.jboss.org/jira/browse/JBDEPLOY-192
The fix will be integrated in the n
It is just a few lines before deployment, the lines between deployment and
automatic undeployment and a few lines of undeployment.
My problem is to check what really happens. I can not see any error message in
the whole file.
Birt 2.5 Webviewer works fine, my seam application works fine, but
this looks like being just in the middle of the restart. maybe better if you
open a jira and attach a more complete log output there ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250108#4250108
Reply to the post :
http://www.jboss.org/index.html?module=bb
I hope this works
| 009-08-18 01:44:57,227 INFO
[org.hibernate.impl.SessionFactoryObjectFactory] (HDScanner) Factory name:
persistence.unit:unitName=#xeric
| 2009-08-18 01:44:57,231 INFO [org.hibernate.util.NamingHelper] (HDScanner)
JNDI InitialContext
properties:{java.naming.factory.in
I think this most likely will be more an AS specific question than tooling but
since i'm curious please attach part of the log just before and the first
couple of lines the restart occurs.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250063#4250063
Repl