]
Nick Boldt updated JBIDE-14629:
-------------------------------
Labels: jbds711 (was: )
Errors when creating and deploying seam2 project with Seam
2.3.Final
---------------------------------------------------------------------
Key: JBIDE-14629
URL:
https://issues.jboss.org/browse/JBIDE-14629
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: upstream
Affects Versions: 4.1.0.Beta1
Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP
6.1.0.Beta1
Reporter: Vlado Pakan
Assignee: Rob Stryker
Priority: Critical
Labels: jbds711
Fix For: 4.1.2.Final, 4.2.0.Alpha2
Attachments: seamerror.png
ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file
with JDBC driver for HSQLDB.
1. Fix DefaultDS Database connection definition
ASSERT: It's possible to connect to DefaultDS
2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final
ERROR: There is error in Problems view:
!seamerror.png!
3. Start seam project on server
ERROR: This error appear in Server log. Application is not deployed:
{noformat}
3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012:
Deployment deployment "seam.war" contains CDI annotations but beans.xml was not
found.
13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml")
13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "seam.war" (runtime-name : "seam.war")
13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559:
Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar")
13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service
status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service
jboss.data-source.java:/seamDatasource]
{noformat}
Is this supported scenario?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: