]
Len DiMaggio commented on JBDS-1670:
------------------------------------
Also - seeing these exceptions deploying the quickstart - unless the ESB runtime
preference is set to the JBossESb distribution dir, and not the AS dir tree into which ESB
has been deployed.
DEPLOYMENTS IN ERROR:
Deployment
"jboss.esb.vfsfile:/jboss/local/jboss-5.1.0.GA/server/all/deploy/helloworld.esb/"
is in error due to the following reason(s): java.lang.ClassNotFoundException:
AbstractActionLifecycle
Seeing "Target runtime jboss-soa-p-5.0 Runtime is not
defined." error - in spite of the name of the runtime being set - with JBDS + AS +
JBossESB
-------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-1670
URL:
https://issues.jboss.org/browse/JBDS-1670
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Environment: Version: 4.0.0.GA
Build id: v20110216-1930-H239-GA
Build date: 20110216-1930
JBoss AS 5.1
JBossESB 4.9
Reporter: Len DiMaggio
Attachments: log, Screenshot-200.png, Screenshot-201.png, Screenshot-202.png,
Screenshot-203.png, Screenshot-204.png
With JBDS 4 GA + AS 5.1 GA and JBossESB 4.9, I'm seeing this issue with the ESB
examples
Regardless of whether the AS server runtime is named "jboss-soa-p-5.0 Runtime",
this error is raised:
Target runtime jboss-soa-p-5.0 Runtime is not defined.
See attached screenshots and .log file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: