Hello, I'm having the same problem, opened a bug -
https://jira.jboss.org/jira/browse/JBREM-1153
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254286#4254286
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4254286
_
Under JBoss 4.0 and earlier versions I had an MDB with the following jboss.xml
deployment descriptor:
|
|
|
| LoggingMDB
| queue/loggingQueue
| LoggingMDB Message Driven
Bean
|
|
|
|
| LoggingMDB Messa
"lincao123" wrote : Hi, gturner,
|
| Recently I got the same error while invoking remote ejb from jboss 4.0.5 to
4.2.0. Can you share your solution with me? Thanks a lot!
|
| Lin
Sorry I have no work-around, we decided to postpone deployment of 4.2 servers
until we commit to
I'm testing whether we can mix JBoss 4.0.4.GA and 4.2.1.GA in our environment
while performing upgrades to 132+ hosts!
We have an old EJB 2.1 Session Bean that works fine if the EJB is deployed on a
4.0.4.GA server and accesses by a client on 4.2.1.GA, however if we deploy the
EJB on 4.2.1.GA a
I have a JAX-WS 2.0 RI based project deployed on JBoss 4.0.4.GA that I am
upgrading to JBoss 4.2.1.GA with JBossWS 2.0.1.GA.
An endpoint packaged in a war makes use of @PostConstruct, as well as some
Handlers that make use of @PostConstruct as well. @PostContruct on the web
service class is n
I have a JAX-WS 2.0 RI based project deployed on JBoss 4.0.4.GA that I am
upgrading to JBoss 4.2.1.GA with JBossWS 2.0.1.GA.
Deployment of the .war fails with the following stacktrace:
| 2007-10-17 09:31:32,361 ERROR [org.jboss.deployment.MainDeployer] (main:)
Could not start deployment:
fil
