[
https://jira.jboss.org/jira/browse/JBPM-2022?page=com.atlassian.jira.plug...
]
Tom Baeyens resolved JBPM-2022.
-------------------------------
Resolution: Won't Fix
test suite of module enterprise should not be executed this way. only modules examples
and test-db should run in the integration test suite. in this case the normal deployment
is done on jboss.
reopen and discuss if you don't agree, heiko.
EnvironmentFactory cannot be bound to JNDI
------------------------------------------
Key: JBPM-2022
URL:
https://jira.jboss.org/jira/browse/JBPM-2022
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: jBPM 4.0
Bonanova:enterprise hbraun$ mvn -Djboss.bind.address=localhost -Dtest=CommandExecutorTest
test
10:13:45,303 ERROR [STDERR] Feb 6, 2009 10:13:45 AM org.jbpm.log.Jdk14Log info
INFO: WARNING: environment factory binding failed
javax.naming.CommunicationException [Root exception is java.io.NotSerializableException:
org.jbpm.pvm.internal.svc.DefaultCommandService]
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:664)
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:598)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at
org.jbpm.enterprise.internal.ejb.CommandExecutorSLSB.bind(CommandExecutorSLSB.java:184)
at
org.jbpm.enterprise.internal.ejb.CommandExecutorSLSB.ejbCreate(CommandExecutorSLSB.java:149)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira